How to Use Orchestration Groups For Software Updates in SCCM

[@ravindrarawat]

You make it super easy to understand and test!! Appreciate..Thank you.

[@PatchMyPC]

You're very welcome!

[@ga57cas]

Great video as always Justin. Very nicely presented. Thanks.

[@PatchMyPC]

Thanks for the feedback!

[@yogeshgupta1991]

gr8 content mate...

[@PatchMyPC]

Thanks for watching!

[@soumenbhattachryya5232]

Thanks for keeping my request

[@PatchMyPC]

Most welcome 😊

[@ehabgalal9181]

Thanks. I was wondering if I have group of 10 machines and I need 5 machines to start at same time and other 5 start after the first 5 finish. Is that possible instead of doing it one by one

[@PatchMyPC]

Set it to install 50% of clients at a time.

[@ehabgalal9181]

@@PatchMyPC is there a chance to specify which servers to be in 50% instead of sccm choose them randomly

[@steemy11]

@@ehabgalal9181 It likely does the first 50% of the service order.

[@azizmohamed1591]

Thank you

[@PatchMyPC]

You're welcome

[@calvinwoods7667]

Fantastic video as per usual. One question, In what context does SCCM run the pre/post Powershell cmd?

[@PatchMyPC]

System

[@Atreus21]

What I'm principally interested in is heavily scripting pre- and post- reboot actions. I mean crazy stuff like sending a maintenance email out a week in advance of the deadline, then connecting to vSphere to take a snapshot an hour before the deadline, then once patches are installed and reboots completed, sending another maintenance email. This doesn't sound like the appropriate tool to use for that.

[@steemy11]

If the system is pending a reboot to complete the software update. The orchestration will wait until this task is completed?

[@PatchMyPC]

I think so, but I haven't tested.

[@asmitha797]

great

[@SimonBaldock]

So to confirm: each member (if a server and using monthly WIndows updates as an example) would be patched and then rebooted before moving to the next server in the list ?

[@praveena7458]

Thank you

[@PatchMyPC]

Thanks for watching