Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM restart/shutsown problem after software update installation

  • Thread starter Thread starter lui
  • Start date Start date
  • Replies Replies 2
  • Views Views 6K
Status
Not open for further replies.

lui

New Member
Messages
2
Solutions
1
Reaction score
0
Points
1
Hello,

we are currently running Configmgr version 2203 hotfix (KB14244456). We have a very strange problem with the restart options after installing updates. The updates are installed on the clients and also the message that a restart is necessary appears on the clients afterwards.

However, we have a couple of machines that do not show the "Shutdown and Update" and "Restart and Update" option in the power menu after updates are installed. We have been using Configmgr version 1902 until recently. After updating to version 2203 it got a little better, and the installation was done on shutdown.

Meanwhile, the options "Shut down and update" and "Reboot and update" appear in the power menu after a software update, but if another update is installed before the computer is rebooted, these options disappear from the power menu. If the option "Shutdown" (without update) is then selected, logically no update takes place (we have Fast Boot enabled). The update is then only possible via the restart popup window of SCCM or via the button "restart" (also without update).
This is a bit of a pity, because this way the updates can only be partially installed during shutdown and most employees shut down their PC in the evening and start it up again tomorrow, but rarely do an explicit restart.

But why do these options disapear ? Does anyone have an idea how we can solve this?

Thank you in advance for any help !
lui
 
Solution
The problem has been solved in the meantime. I had accidentally enabled the suppression of reboots for workstations in the deployment settings.
The problem has been solved in the meantime. I had accidentally enabled the suppression of reboots for workstations in the deployment settings.
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,159
Messages
27,945
Members
18,241
Latest member
ljrb

Latest posts

Back
Top