If you are using 2012 or newer you can set deadlines. At the deadline the updates will install as soon as possible. They will only install during a maintenance window unless you set it to ignore maintenance window at deadline. What I do is set the clients to have a deadline a few days before the servers. So you could space out the deadlines. Have one group of servers go one night, the next a few nights later and so on. Be careful that the deadline is set to client local time and not UTC to avoid middle of the day reboots. In my experience the servers pretty much patch right away at deadline (I set it in the middle of the night) as they download the patches prior to it.
Nick Gailfus Computer Technician p. 602.953.2933 f. 602.953.0831 [email protected]| www.leonagroup.com On Tue, Jan 5, 2016 at 3:59 PM, Russ <[email protected]> wrote: > We've been patching our servers with WSUS up until this point, but we'd > like to move over to SCCM. I wanted to get an idea on how people are > handling their 2 and 3 tier applications? Currently we have a number of > different windows to patch the SQL servers, then app tier, then web tier or > whatever. But what I am hoping is to make things a bit more well defined > (and to start building collections for various applications and that sort > of thing.) > > Do you suppress reboots on servers, and then send out a script for > rebooting? Do you make maintenance schedules which would cause reboots in > certain order? Do you patch or reboot manually? What sorts of > methodologies do you deploy? > > It would be nice to put a process and methodology in place so that it's > not reinventing the wheel for every individual group of servers. > > We don't currently have SCCM in place for servers, so that's all new as > well. So we sort of have a unique opportunity to start fresh. > > Would appreciate any feedback or ideas you have give me. > > Thanks, Russ > >
