CM: Software Updates: Installed updates, shutdown, startup and still Restart required state...

Question

I'm having this issue(if it's not by design). We are running Configuration Manager 2006 and currently we are introducing restarts after the software updates. We install the software updates "outside the maintenance window" and we perform the System restart "during the maintenance window" from 11PM to 1AM. Computers that are switched on during maintenance window are restarted as expected.

But.....Users that will shutdown(in Windows) their system at 6PM(and miss the maintenance window) and startup the next morning still gets the restart notifications and in software center. The status of the updates is "Restart Required". Initiate software deployment evaluation doesn't fix anything. Despite several shutdowns and startups it stays in Restart required state. Also when shutdown from Start >> Shutdown you don't see the expected: Configuring updates 10%..... during the shutdown.

However when we restart from the Restart Notification of ConfigMgr then it will restart, configure the updates and software center is not showing the restart required state anymore after checking software center once logged in again.

Is this normal behaviour? In my opinion shutting down and starting up a device it's the same as an restart. But it looks that if you skip the "ConfigMgr Restart way" and will never finish the updates.

Is there a way that a "Windows shutdown" is completing the updates? For specific reasons, where I'm not going talk about now, WOL will not be used in my organisation.

Answer 1

Hi @D. Aartman ,

At first, our opinion is right. The operation of shutting down and starting up a device is equal as restarting.

At the point of update, the cycle of installing and restarting has been completed. However, as the SCCM client, the operation of the client restart was not monitored by the monitoring component. So even through the client restart, the status of the updates is "Restart Required" in software center.

To avoid this situation, we could run the action of Software Updates Deployment Evaluation Cycle manually or wait for the evaluation, and then the problem will be solved.

Besides, it is important to restart during the maintenance window to reduce other accidents.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.