Exactly. My experience with Maintenance Windows is with Embedded so that’s an entirely different animal.
But Daniel is right. You are going to have to trigger the reboot yourself through a script or some other solution. Maintenance Windows don’t actually DO anything. They simply allow things to be done. It is simply nothing more than CM having a block of time in which deployments can start. If you want a reboot you are going to have to trigger it. You could create a simple task sequence that does everything you need to happen like installing updates. Then at the end call shutdown with a fair enough timer to allow CM to clean up after the sequence. Keep in mind that a Maintenance Window is like an entrance gate. Doors open at 1 and close at 3 and only those (deployments) in line that get through before the doors close are all that get in for the show. If the line is long and you’re still outside when the doors close you’re out of luck. So your solution will need to be aware of that. That is why we use a task sequence to do it all. Since it’s just one deployment, no matter how long it takes to run it will start and we don’t have to worry that the window expired before our reboot solution was run. Mike From: <[email protected]<mailto:[email protected]>> on behalf of "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, February 25, 2016 at 8:26 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: Maintenance Windows and reboots No its not. Maintenance windows are for any deployments from CM, not just reboots. If you want a reboot to happen around the same time, you will need to put a solution together. Setup a separate deployment, run a PowerShell script locally, or something like that. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Thursday, February 25, 2016 6:13 PM To: '[email protected]<mailto:'[email protected]>' Subject: [mssms] RE: Maintenance Windows and reboots Ours is unchecked. So what happens is out of the 29 test servers a hand full of them actually rebooted without issues, and the rest didn’t reboot. When I looked at the updates that were installed, none of the updates needed a reboot, so the servers didn’t … at least that is my assumption at this point. If I am not mistaken, one of the servers only install Silverlight, which no reboot is required. Is CM programmed to reboot within that MW regardless? It seems to me it is supposed to reboot if the update tells CM to reboot. KEVIN JOHNSTON From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Thursday, February 25, 2016 5:10 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Maintenance Windows and reboots You don’t have this box checked on your deployment by chance, do you? [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Thursday, February 25, 2016 1:44 PM To: '[email protected]<mailto:'[email protected]>' <[email protected]<mailto:[email protected]>> Subject: [mssms] Maintenance Windows and reboots I am still testing out using Maintenance Windows in our company for servers. When we did our trial run, I noticed that not all the servers rebooted. Upon further inspection it looks like the updates that were applied did not need to reboot the server. Just curious how others “force” a reboot (automatically), as it is always nice to reboot servers when you can, I was hoping that the MW would force a reboot regardless. But it seems once this happens I need to then go back in and see which ones did not reboot and manually do it. We don’t have a lot so it is not too bad, but I am trying to automate it as much as possible. I don’t have Orchestrator or anything that can do this. It would be nice I guess if you could force the reboot on the servers. Any tips, tricks or suggestions. KEVIN JOHNSTON The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
