Scenario :

• You deploy Software Updates to a specific collection that has a maintenance window configured.
• The machine doesn’t reboot as required

This post describe how to fix SCCM maintenance windows reboot problems.

SCCM maintenance windows reboot Troubleshooting :

• Check the Maintenance Windows properties

The maintenance Windows is set to a 2h duration :

• Check the Deployment properties

The first step is to make sure that your deployment allows reboot:

My machine is a Windows 2012 (thus considered a server) and the option to suppress reboot is not selected.

• Check if there’s overlapping maintenance Windows

Using the built-in report “Maintenance windows available to a specified client”, I can see that my maintenance Windows is applied correctly to my server and there’s no other maintenance windows applied.

• Check RebootCoordinator.log

The log to watch for this type of “error” is RebootCoordinator. Let’s see what it has to say :

The interesting part is there :

ServiceWindowsManager has allowed us to Reboot – Maintenance window has permitted to reboot
Scheduled reboot from agent UpdatesDeploymentAgent – Updates were deployed at 11:03 AM and a reboot is required

Then just after it shows the following entries:

ServiceWindowsManager has not allowed us to Reboot
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

We may not reboot… EVER… we’re doomed ! 🙂

So… we’re in a Maintenance Windows but our log says otherwise. (Even if my window is still valid until 12:30PM)

Resolution :

Check your restart settings in your client settings : (Administration – Client Settings – [Your settings Name] – Client Restart

As you can see, the Temporary notification is set to 90 minutes.

11:03AM + 90 minutes = 12:33PM

12:33PM is 3 minutes outside the maintenance window !

The important thing to remember is to take into account the notification time in your maintenance Windows. Reducing the notification time or increasing the maintenance window period fixed the issue.

By the way you can list the collections that have a schedule in maintenance windows with the report Configuration Manager – Collections. Simply sort by the columns Maintenance Windows.