servers not rebooting after maintenance window

MaryP 6 Reputation points
2020-08-24T14:07:59.157+00:00

We have a few servers that are not rebooting after the monthly updates are installed. On these few servers, the updates are installed manually prior to the maintenance window (sometimes the updates are installed days before the maintenance window).

When the maintenance window time starts, the servers are not rebooting. They are in a "waiting for restart" state.

Is this because the updates were installed manually that the server will not reboot (during the mw)?

I have verified that the udpates are actually installed, the mw is 6 hours, the runtime on the updates is 60 minutes (which I suppose does not matter if the updates are installed manually).

the only thing I can think of is that the manual install of the updates is preventing the servers from automatically rebooting.

Thoughts?

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,005 questions
0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Sandys 31,186 Reputation points Microsoft Employee
    2020-08-24T14:32:04.223+00:00

    Have you reviewed rebootcoordinator.log on the systems?

    Are restarts suppressed in the applicable deployment(s)?

    Are you sure the systems have a maintenance windows applied?

    0 comments
  2. MandP 1 Reputation point
    2020-08-24T15:57:34.06+00:00

    No, the restarts are not suppressed. There are 81 other servers that the update deployment is deployed to. Each month, the same few servers are always waiting for a reboot.

    All of the 81 servers have the same maintenance window. There is only 1 maintenance window for these servers.

    There are no errors in the rebootcoordinator.log file. I do see the Servicewindowstart and Servicewindowend which is the same as the mw.

    I'm not sure where to look next.

    0 comments
  3. Jason Sandys 31,186 Reputation points Microsoft Employee
    2020-08-24T16:24:02.137+00:00

    Logs aren't just about errors. You need read them in context of the issue you are trying to address to see what did or didn't happen. Comparing the log from a system where the expected action occurred to a log where the action did not occur is often very useful to determine this.

    Additionally, have you reviewed the Windows Event Logs? Same caveat here, it's not about errors necessarily.

    0 comments
  4. Kent Agerlund 11 Reputation points Microsoft Regional Director
    2020-08-25T05:45:35.79+00:00

    Could also be different Agent settings for restart values. Do all the servers have the exact same client settings applied?

  5. Amandayou-MSFT 11,051 Reputation points
    2020-08-25T09:51:14.573+00:00

    Agree with Jason, we could check if the update is required to reboot by WUAHandler.log first.

    20217-8255.png
    Besides, please check Pending Restart status of client on the SCCM console.
    20184-8256.png

    If the response is helpful, please click "Accept Answer" and upvote it.