Long time admirer, first time poster..
This is probably more of a general SCCM question but hopefully one of you guys can help me out with this.
We give users a 14 day grace period to reboot after updates have been deployed (I don't agree with this, but out of my hands) Something very common I see is users and our service desk try to install software from software center and it fails. Its just a generic error and doesn't give the user any information like "Failed because pending reboot".
Is there anything I can do about this? I am the lone SCCM admin and still learning so any help would be great.
Hey !
Thank you for reaching out.
Certainly! The situation you described is quite common in environments where software updates are deployed through SCCM (System Center Configuration Manager).
Personaly, I don't think there is anything they can do except reboot the machines. What I can suggest is : Only give a few days restart grace period instead of 14.
You can configure SCCM to automatically schedule reboots after updates are installed. This ensures that systems are rebooted within a reasonable timeframe, minimizing the likelihood of pending reboots causing issues during software installations. However, be cautious with this approach, as unexpected reboots can disrupt user workflow.
Regards,
Raunak
Quote from: Raunak Desai (Patch My PC) on April 02, 2024, 01:53:24 AMHey !
Thank you for reaching out.
Certainly! The situation you described is quite common in environments where software updates are deployed through SCCM (System Center Configuration Manager).
Personaly, I don't think there is anything they can do except reboot the machines. What I can suggest is : Only give a few days restart grace period instead of 14.
You can configure SCCM to automatically schedule reboots after updates are installed. This ensures that systems are rebooted within a reasonable timeframe, minimizing the likelihood of pending reboots causing issues during software installations. However, be cautious with this approach, as unexpected reboots can disrupt user workflow.
Regards,
Raunak
Hello, I'm pretty new to everything, but why 14 days are not a good option, and you offer to make this period shorter?
Quote from: JamesRodgers on October 22, 2024, 02:48:44 PMQuote from: Raunak Desai (Patch My PC) on April 02, 2024, 01:53:24 AMHey !
Thank you for reaching out.
Certainly! The situation you described is quite common in environments where software updates are deployed through SCCM (System Center Configuration Manager).
Personaly, I don't think there is anything they can do except reboot the machines. What I can suggest is : Only give a few days restart grace period instead of 14.
You can configure SCCM to automatically schedule reboots after updates are installed. This ensures that systems are rebooted within a reasonable timeframe, minimizing the likelihood of pending reboots causing issues during software installations. And about it and more you can find info online. Here is one article about creating LXP from scratch (https://ddi-dev.com/blog/case/how-to-build-learning-experience-platform-lxp-from-scratch/) and it may be useful for you. However, be cautious with this approach, as unexpected reboots can disrupt user workflow.
Regards,
Raunak
Hello, I'm pretty new to everything, but why 14 days are not a good option, and you offer to make this period shorter?
I actually have the same question. I've always thought that 2 weeks in an optional time.
The issue you're encountering with software installations failing due to a pending reboot is common, especially with a grace period for updates.
Hi there,
As my colleague Raunak suggested in an earlier post, you can reduce the grace period days in the client settings.
Alternatively, you can configure Maintenance Windows in Configuration Manager to control when updates and reboots occur. This will enable you to specify when a device installs an update and reboots at a particular time.
Please note that the Maintenance Window will be applicable for the following tasks as well (non Patch My PC deployments):
- Application and package deployments
- Software update deployments
- Compliance settings deployment and evaluation
- OS and custom task sequence deployments
For more details, you can refer to the official documentation.
https://learn.microsoft.com/en-us/mem/configmgr/core/clients/manage/collections/use-maintenance-windows