You can try setting 2 desperate MWs. Set your deployments not to reboot for your 1st MW and when the second MW is open the boxes should reboot, in theory. I have never tried it but would be a good test.
You can use windows schedule tasks to reboot them or have a package that its job is reboot those boxes. Shutdown.exe -r On Nov 25, 2013 7:42 AM, "Brian McDonald" <[email protected]> wrote: > Thanks Mark. Are there any other methods or suggestions? > > I'm looking for a way to do this with the capabilities built into the > maintenance window feature natively. > > Brian > > Sent from my iPhone > > On Nov 23, 2013, at 4:37 PM, "Mark A. Mears, Sr." <[email protected]> > wrote: > > I send a reboot script to the machine at 5 minutes into the maint window. > Script is a one-liner Wscript.quit(0). > I let ConfigMgr reboot after execution. Done! > > Thanks, > Mark > > > Sent from my iPhone > > On Nov 23, 2013, at 12:31 PM, Brian McDonald <[email protected]> > wrote: > > > I have a question regarding maintenance windows and reboots for security > updates. > > I have 2 AD Security Groups I'm using for my servers. MW1 and MW2 > accordingly. MW1 includes my primary DC01 as well as 90% of the servers in > my environment. MW2 includes DC02 and 10% of the servers in my environment. > I have collections created in SCCM reflecting this. > > In MW1 I need the servers schedule maintenance windows Monthly, Third > Saturday with patches beginning at 12:01 AM BUT not rebooting the > servers until 10:15 AM the next morning. MW2 as well I need scheduled > Monthly, Third Saturday with patches beginning at 12:01 AM BUT not > rebooting until 10:45 AM the next morning. > > Seems simple enough to Configure the recurrence schedule Monthly, Third > Sat. on the Maint Window tab, but not clear how I tell it when exactly to > reboot the servers? > > Can someone provide some guidance around this please? > > Thanks, > > Brian > > > > >
