So I've been duly schooled in the SCCM forums and told that I need to use Orchestrator for the problem.  The issue is:  I need to install SCCM updates and trigger a reboot within a defined maintenance window.  The trick is that the reboot needs to be tiered - there will be a small number of servers (generally one) that the other servers depend on.  Those servers need to go down first, come back up, and the rest of the servers need to reboot.

I've got a few ideas on how to approach this issue but there's a couple of big problems I need to address that I can't find any suggestions on:

1.  How do I code the the server relationships in such a way that it doesn't become a massive management headache, and

2.  How do I set a trigger so that this fires but stays within the maintenance window?

• Edited by Square721bt Friday, September 04, 2015 8:55 PM

Hi,

we are doing something like this at a Customer, there are a few ways.

If you are using SCSM, you can configure the Realtionships and dependencies there. Start a Runbook which queries every hour for Server in your maintenance Window

If not, just use a simple Excel Sheet, SharePoint List, ore something else.

Query this list for dependend Servers, reboot them, wait for reboot successfully and restart your master Server.

Also, create a Runbook which query for Servers in Your Maintenance Windows and Start the Reboot.

i Have created a simple Reboot Runbook here:

http://scoosp.com/reboot-runbook-for-scoosp/