This solution which includes a collection of Orchestrator runbooks (MMSPatching.ois_export) and one SCSM Management Pack (Patching.xml), which enables application owners to handle the time of patch installation by themselves and follow ITIL processes to document the change by a change request. This situation fits to all app servers which cannot be patched and rebooted during standard maintenance windows because app owners need to handle that depending on production timeframes.

The process has these requirements:

The systems which need to be patched, need to be SCCM clients and are in a collection which is synchronized with SCSM. SCCM admins deploy Software Updates to the servers with available status. OrchestratorTemp SQL DB to store process information.

The main Orchestrator runbook needs to be synchronized with SCSM to have this process available as Runbook Automation Activity in SCSM.


Tested with SCSM 2012 R2, SCORCH 2012 R2 and SCCM 2012 R2.

This solution was part of my presentation at MMS 2015

Some ideas how solution can be extended: add approval steps, Software Update groups to SCSM, multiple SCCM collections or also reboot the servers with Orchestrator.


Process description:

Also see my blog at