What is the best way to include the affected CI's when doing Server Patching

[Dave Hoglund]

When we do monthly server patching  (Windows or Linux), there are a lot of servers being patched.
What is the best way to capture these?  Do we use a generic Server, or 1 primary server, or is it best to add all of the Server names to the Affected CI Tab?  or would CMDB Groups be a way to include all of the Server CI's being patched?

Note:  I noticed if I add the server to the Affected CI in the CHG, I don't see the CHG in the "Change Requests" related list in the Server.  The CHG only shows in the related list of the Primary CI added to the CHG.

Thank you.

[Sukhbir Singh2]

You can use one primary CI and add others as affected CI.

If you want to add the CHG in the related list of the servers, you can create a new relationship and add a new related list in Servers.

Please hit correct/helpful, if it helped.

Thanks

Sukhbir Singh

[Sukhbir Singh2]

Hi Dave

Following up on my response.

If it answers your question, please mark correct/helpful.

Thanks

Sukhbir Singh

[Dave Hoglund]

Hi Sukhbir,

Not sure if this gets to my overall question:  what is the best practice for when we have a CHG for Patching Servers  (where there can be 1000+  CI's that are being touched).

We don't want to manually add all 1000+ to the CHG, 

We have the CHG related list showing on Servers, although this got me thinking about possible need to add for "Application Services" CI class.