Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Prompt users for reboot, but NEVER force it

The reboot settings only allow for the user to postpone a reboot for up to 24 hours. Why can't we expand that time or just keep reminding them forever until they reboot themselves? The longer that they have been pending a reboot, remind (pester) them more frequently. Or auto reboot if nobody is logged on.

902 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Joe shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Noted  · 

    23 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Bill Dunn commented  ·   ·  Flag as inappropriate

        How about just fixing Windows so Updates rarely if ever require actual reboots, just cycle the proper services. Linux pretty much only needs reboots when you touch the Kernel which isn't often.

      • Simon commented  ·   ·  Flag as inappropriate

        This still is a huge point of contention, we have many customers where the behavior of coming back on the network after a deadline for updates leads to some pretty poor user experience and often CIO-level complaints.

        The notifications leading up to the restart aren't prominent enough, and when it is required they just aren't sufficiently manageable for environments where some users must be able to opt out at critical times

      • Josh commented  ·   ·  Flag as inappropriate

        Throwing in a "Me Too" for my enterprise. ~20,000 workstations.

      • Robert commented  ·   ·  Flag as inappropriate

        Agreed, the level notification is not currently customizable and it needs to be. Specifically for patching and servicing, why can't the sccm admins increase the level of notification. It appears that nothing "really" notifies the user until a deadline is met. It needs to be MORE nagging to ensure that a forced reboot won't make them lose all of their work. It was great back in the PRE-servicing and PRE-win10 - not sure why they turned down the notifications and suspends.

      • Tom Steger commented  ·   ·  Flag as inappropriate

        This is a huge deal for us. No auto-restart with logged on user existed before we switched from WSUS/GP/WPP to SCCM.

        For now, we keep extending the deadline... not a good choice or method.

      • Brachus commented  ·   ·  Flag as inappropriate

        Microsoft - you MUST do something to improve this if you really want customers using the Windows 10 Servicing capabilities of SCCM.

        Enterprise End Users have to be babied and coddled or else there are backlashes against IT.

      • Claus Ilginnis commented  ·   ·  Flag as inappropriate

        I would prefer (of course) something like Linux. Tell user what packages have to be updated and also the reason (security or simple update) then leave it up to 14 days to the user for security updates ( and even longer for others).
        Because forcing something is alway a bad idea - better improve the way to schedule a nightly update.

      • Roberto Franke commented  ·   ·  Flag as inappropriate

        I also would prefer the "Spam" method mentioned by Steffen Weik. Or at least there should be a possibility to postpone a reboot for up to 72 hours. Maybe with an additional "work in progress" switch. So in case a reboot is required it would automatically be postponed for a configured duration. So it's possible to start a long running test on Friday evening and receive the results on Monday morning without being afraid your test-results are gone because of an unexpected reboot.

      • Steffen Weik commented  ·   ·  Flag as inappropriate

        I would prefer a mechanism where the prompt to reboot pops up more and more frequently for important updates. Something like first every 4 hours then every 2 hours then every 1 hour and finally every half an hour. Critical updates could start at a higher frequency but I hope that there are only very few use cases when an immediate restart will really be necessary.
        The prompt should be done by use of a window, not only a tray popup. But with the possibility to close it every time. That way it is not necessary to decide automatically what kind of user task is that urgent that it must not be disturbed by a reboot. And at the same time it gets that annoying that it is very likely that the user will do the restart, soon.
        To inform by use of a window will increase the chance that the user actually recognizes the necessity for a restart, which might very well be overlooked if it is only a shortly visible tray bar information. That way more users might decide to do the restart even within the 4 hour information phase, before they start a presentation.

      • Steffen Weik commented  ·   ·  Flag as inappropriate

        I would prefer a mechanism where the prompt to reboot pops up more and more frequently for important updates. Something like first every 4 hours then every 2 hours then every 1 hour and finally every half an hour. Critical updates could start at a higher frequency but I hope that there are only very few use cases when an immediate restart will really be necessary.
        The prompt should be done by use of a window, not only a tray popup. But with the possibility to close it every time. That way it is not necessary to decide automatically what kind of user task is that urgent that it must not be disturbed by a reboot. And at the same time it gets that annoying that it is very likely that the user will do the restart, soon.
        To inform by use of a window will increase the chance that the user actually recognizes the necessity for a restart, which might very well be overlooked if it is only a shortly visible tray bar information. That way more users might decide to do the restart even within the 4 hour information phase, before they start a presentation.

      • John Williamson commented  ·   ·  Flag as inappropriate

        Some of the competitors of SCCM have this feature. It pops up a window and pesters the user to reboot. They can postpone, but at some point, they are no longer given the choice to and the window can no longer be closed at that point. Their only option to make it go away permanently (other than moving it) is to complete the action. I'm +1 on this.

      • Oliver commented  ·   ·  Flag as inappropriate

        i would also like to see an option of an reboot reminder even for a scheduled reboot. If software updates are installed an you have a 24h reboot countdown it would be helpful to have an Option to notify the user frequently that a reboot is pending as this sometimes blocks other deployments.

      • Sonja commented  ·   ·  Flag as inappropriate

        The issue is that the behavior when deploying an Application is different from the behavior when you deploy a Software Update. When deploying a Software Update, you can suppress the reboot and you will see a notification in Software Center that a restart is required but the reboot is not forced. When deploying some certain types of applications (like a .NET Framework update) you cannot suppress the restart and users are forced to reboot within a configured timeframe. This behavior should be the same in both cases.

      • Cristopher commented  ·   ·  Flag as inappropriate

        Reboots need to be a lot more flexible.
        Our organization is currently using a weekly scheduled task to prompt the user for a reboot if one is needed. The GUI presented then gives them up to 24 hours to defer.
        Script to check for pending reboot: https://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Query-bdb79542
        Reboot GUI for end user: http://blog.coretech.dk/kea/new-version-of-the-coretech-shutdown-tool/

        We also recently implemented a separate scheduled task to reboot computers with nobody logged in. It also checks for a pending reboot and then initiates one if required. This runs daily between 2AM and 3AM.

      ← Previous 1

      Feedback and Knowledge Base