Config Manager - SU Deployemnt Server Reboot

Cosmic Storm 21 Reputation points

We recently had an issue with Windows Software Update deployment to Server Collection.

We have the following settings.

  1. Client Agent - "Computer Restart" is left to default settings.
  2. Software Update Deployment is configured to Suppress Server Reboot
  3. Server Collection has no Maintenace Windows configured.

Despite Suppressing the Server reboot, the Servers in the Collection still rebooted.

This did not happen in the past.

With our settings listed above, what behavior is expected in context of "Server Reboot"?

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).
960 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. CherryZhang-MSFT 6,481 Reputation points

    Hi @Cosmic Storm

    Thanks for your information.

    According to my research. To better manage our servers, it is highly recommended to configure maintenance windows.

    1) Even if we do not configure maintenance windows, our computer will also create maintenance window based on the usage.

    2) In my environment, I didn't configure Maintenance Windows. We can see the detail about the evaluation of maintenance windows in ServiceWindowManager.log.

    Path(client): … \CCM\Logs\ ServiceWindowManager.log

    3) Software Update Deployment is configured to Suppress Server Reboot means that will restart during maintenance time, otherwise the system no reboot.

    Thank you for your patience and understanding

  2. CherryZhang-MSFT 6,481 Reputation points

    Hi @Cosmic Storm ,

    Thanks for your reply. I have done more test for this case. We may need more information to discuss why the server restart.

    1) After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot. let’s investigate which patch caused the restart. This is shown in UpdatesDeployment.log.
    Path(client): …\CCM\Logs\UpdatesDeployment.log

    For example:



    2) We can see why the server restarts from the log. For example, this restart was caused by the User logoff system task.

    3) Furthermore, please check the version of the server.

    4) In addition, according to the official article. Suppressing system restarts can be useful in server environments, or when you don't want the target computers to restart by default. However, doing so can leave computers in an insecure state. Allowing a forced restart helps to ensure immediate completion of the software update installation.

    The link for your reference:
    Manually deploy software updates - Configuration Manager | Microsoft Learn

    Thank you for your time and patience!

    0 comments No comments