Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 22, 2012 3:56 PM
I was noticing over the maintenance window that a few servers were not auto-rebooting. I just checked one of them and checked the rebootcoordinator.log file and found these little gems;
ServiceWindowsManager says that we will not be able to Reboot in the future
We may not Reboot ever. Sending 'System May Never Reboot' Status Message
Anyone know where this setting would be??? Most of the servers in this collection, that I've checked thus far, installed and rebooted.
Edit: "Suppress reboot" was not selected for servers.
All replies (5)
Tuesday, November 20, 2012 10:44 PM âś…Answered
same issue here. completely puzzling me....
maintenance windows set correctly, we are outside of business hours....
some logs say:
Duration is 0 days, 07 hours, 00 mins, 00 secs
Program can run! Setting *canProgramRun to TRUE
Proceeding to non-business hours activites as presentation mode is off.
A user-defined service window(non-business hours) is available. We will attempt to install any scheduled updates.
etc...
so the updates install correctly, but the machine never reboots.
reboothandler logfile says:
<![LOG[ServiceWindowsManager has not allowed us to Reboot]LOG]!><time="23:37:03.520-60" date="11-20-2012" component="RebootCoordinator" context="" type="1" thread="6000" file="rebootcoordinator.cpp:1643">
<![LOG[Succesfully raised SoftDistRebootWaitingForServiceWindowEvent event ]LOG]!><time="23:37:03.520-60" date="11-20-2012" component="RebootCoordinator" context="" type="1" thread="6000" file="rebootcoordinator.cpp:1516">
<![LOG[ServiceWindowsManager says that we will not be able to Reboot in the future]LOG]!><time="23:37:03.520-60" date="11-20-2012" component="RebootCoordinator" context="" type="1" thread="6000" file="rebootcoordinator.cpp:1675">
<![LOG[We may not Reboot ever. Sending 'System May Never Reboot' Status Message]LOG]!><time="23:37:03.520-60" date="11-20-2012" component="RebootCoordinator" context="" type="1" thread="6000" file="rebootcoordinator.cpp:1527">
<![LOG[Succesfully raised SoftDistErrorSystemMayNeverRebootEvent event ]LOG]!><time="23:37:03.551-60" date="11-20-2012" component="RebootCoordinator" context="" type="1" thread="6000" file="rebootcoordinator.cpp:1534">
edit:
i think i figured it out. the MTW seems to be too short (currently 3 hours) - but for a very special reason.... let me explain:
ServiceWindowManager logfile shows:
<![LOG[WillProgramRun called with: Runtime:14401, Type:3]LOG]!><time="00:39:25.260-60" date="11-21-2012" component="ServiceWindowManager" context="" type="1" thread="4308" file="servicewindowhandler.cpp:2275">
is Runtime:14401 the time in seconds required to run the reboot? i guess so.
i changed the MTW to 5 hours, initated a policy reload on the server and voila, server shows a message:
your computer is about to restart. 03:58:34 remaining....
what happened was that we have set a very large "force reboot" timeframe (4 hours) in client settings policy / computer restart, so that our employees have enough time to finish their work, close programs and save data before the computer force reboots when an installation deadline is hit. it seems this policy is also affecting the servers when they are looking for a maintenance window for rebooting, so the 4 hour "grace period" before shutdown is counted in ServiceWindowManager component.
i have now simply change that grace period for restarting servers to 15 minutes, and tested with a much shorter maintenance window. works perfectly.
@Juice 13610 - hope this helps you.
Tuesday, October 23, 2012 1:09 PM
Anyone?
Thursday, October 25, 2012 1:42 PM
No??
Wednesday, July 30, 2014 9:53 PM | 1 vote
I was just working with a customer, and came across the message "servicewindowsmanager has not allowed us to reboot" in the RebootCoordinator.log. We had a 22-hour Maintenance Window, and were deploying only six software updates. The Maintenance Window was of type All Deployments.
As a last-ditch effort, to get the servers to reboot automatically (within the Maintenance Window), we changed the type of Maintenance Window to Software Updates (new in 2012 R2), updated Machine Policy (via Client Notification / Fast Channel), and it immediately took effect.
In my opinion, there is a bug with how the All Deployments Maintenance Windows work.
Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
If this post was helpful, please click the little "Vote as Helpful" button :)
Trevor Sullivan
Trevor Sullivan's Tech Room
Twitter Profile
Monday, November 24, 2014 7:32 PM
Found this to be the case with us as well. Fixing the MW to target "Software Updates" fixed allowing reboots.
Jay