Change management CI for patchingall workstations

DaveThibode
Giga Contributor

11 hours ago

Hi there, we are recently live in SN and someone asked us if we can just create a CI called "All workstations" or "All Servers". The reason is when they patch or do large scale updates, they are not sure what to choose for a CI since we make choosing a CI mandatory. Their patching will affect all of that machine class not just one CI. How are others managing change management when it comes to patching or updates of all systems. 

Labels:
0 Helpfuls
  • 552 Views
1 REPLY 1

Dr Atul G- LNG
Tera Patron

8 hours ago

Hi @DaveThibode 

No, it is not a best practice to create a CI with this name. If you want to perform patching, it’s better to use the change model named Patch Services. Use one main server as the parent CI and add the remaining servers as impacted or affected CIs. Alternatively, you can use the standard change model, but having a CI name that represents all servers is not a good option.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************
0 Helpfuls