Client Settings - Computer Restart - Allow longer than 1440 minutes, show friendly time
Currently, the maximum an administrator can give users to reboot their systems is 1440 minutes (24 hours). Please let us specify up to 7 days. The goal of the delay is to allow a reasonable amount of time for an end user to save their work and reboot without losing anything. The 24 hour limit means that if a user is gone for a day, there is a strong chance they could lose their work. Allowing up to 7 days seems like a better compromise between end user control and respecting admin intent/organizational need.
In 1906 you can now delay reboots for up to two weeks. Thanks for the feedback!
Ricardo Martins commented
We have been heard.
In SCCM 1906 is allowed up to two weeks (20160).
Terrence Miller commented
It would also be helpful if restarts for application installs could be deferred indefinitely in the way that that can for software update deployments - the "Suppress the System Restart on the Following Devices: Workstations | Servers" option.
What if I want to disable the Computer Restart setting all togather - for Server OS. How can I manage that?
Another thing to consider is the affect this will have on Maintenance Windows (MW). Currently MW using the reboot countdown time when determining if an application can run or on during the MW. If you increase the reboot time, you also need to fix MW to allow for them to be greater than 1440.
If the power goes out at the office, they will lose their docs too. So how does that solve anything by promoting user to lock their WS verse shutting them down.
These days even more organizations are going green, as such having a computer left on and locked, is generally frown on.
So this is NOT solving anything to have a LONG reboot notification. If fact it will cause even more issues, for example, if a Software Update /Application is applied but they have not rebooted, then for most application/ SU it is still vulnerable until the PC is rebooted.
IMO, This is begging for more problems than it solves.
Wait... that wasn't true of the Windows 95/98 machines at my first IT job... but then we got Windows 2000 and it was true.
??? Every org I have ever worked with uses a locked screen saver and has a policy that says you must lock machines when not in use. Where have you been that this wasn't both a technical and policy reality?
IMO, this is a bad idea..
This promotes users to be logon when they are not within the office. IMO this is a security risk.
The follow on is to make the time dialog show localized text with something like "Your machine will reboot on <Date and Time>. Time until reboot: X Days XX Hours XX Minutes"