How do you handle large server patching initiatives in Change Management

[TammyClark]

I am looking for feedback on how you handle large server patching change requests.   Do you utilize any grouping from the CMDB and do how do you handle validation by application teams.

[philmurray]

Hi Tammy, we also do something for Windows servers and monthly Microsoft patches which I can share.

Within each server CI we define three attributes: the Patch Week (either 1 or 2), the Patch Day (any day of the week), and the time to apply the patch.   That means the schedule is pretty much predefined and ensures every server will be patched within 2 weeks of the patch release unless the owner obtains an exception.   An integration with Microsoft Orchestrator reads all the CI entries, pulls together all the ones that have matching attributes and builds change requests (including populating all the servers into the Affected CI related list).   In a typical patching cycle we auto-raise about 100 patching change records some of which have 200+ server attributes.

We used Orchestrator rather than a script within ServiceNow itself because we also hook into a process where servers are auto-rebooted if that additional attribute on the CI has been selected.

It works really well for us.

Phil

[TammyClark]

Thank you Philip!   Do you also create Validation tasks?

[philmurray]

We don't create any other tasks with this process but perhaps you could expand on what you mean by validation tasks?

[salok702]

Hello Phil,

I wanted to know if you explored the option of using Release Management for Patching activity. If you are raising 100's of changes, would it be beneficial managing it via. the ServiceNow release management.?

I was looking for experiences of organization who have done that.

[lindawong]

HIi Phil

I just found this reply but we have a similar pathcing process I was wonder how this worked in your ServiceNow instance.

Could we talk or email about it?

Linda Wong

linda.l.wong@sfdph.org