Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

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.

57 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Nash Pherson (MVP) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

8 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
An error occurred while saving the comment
  • Terrence Miller commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    What if I want to disable the Computer Restart setting all togather - for Server OS. How can I manage that?

  • Garth commented  ·   ·  Flag as inappropriate

    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.

  • Garth commented  ·   ·  Flag as inappropriate

    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.

  • Nash Pherson (MVP) commented  ·   ·  Flag as inappropriate

    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.

  • Nash Pherson (MVP) commented  ·   ·  Flag as inappropriate

    ??? 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?

  • Garth commented  ·   ·  Flag as inappropriate

    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.

  • Nash Pherson (MVP) commented  ·   ·  Flag as inappropriate

    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"

Feedback and Knowledge Base