A Customizable Reboot/Postpone Prompt for Application and Software Updates Deployments
Basically would like something similar to the Windows Updates Reboot/Postpone nag prompt except with the ability to customize the notification text as applicable to the deployment.
For example:, as a sub-setting of the deployment type for the application you have the option to enable the reboot/postpone prompt and customize the notification text of the dialog box.
If the user that receives the prompt, postpones they will be re-prompted at the end of the postponement period until they either reboot or shutdown the system. (basically exactly the same behavior as the Windows Updates reboot/postpone prompt).
Scott Breen commented
a) allow a setting that will reboot if a pending reboot is detected prior to installing an application
b) detect pending reboots and allow handling with notifications via client settings
c) surface pending reboot status in console
please this is extremely important.
Matt Edminster commented
Same thing here:
Today when users receive patches they are expecting to be down for 10-15 minutes. With the new Windows servicing model we are expecting major updates to take 45-60 minutes.
Our users typically bring their devices home and may not boot them up on the evening. So most updates take place during the business day. (At least the laptop devices)
I fear when one of these major updates is released the users will click “install now” expecting to be down for the typical 10-15 when in reality they will be down for 45-60 minutes. They may miss meetings or other important work because of this unexpected downtime.
I would like to see MS introduce the ability for us to inform the user of how long an upgrade may take so they can plan for the downtime.
We have the same request
Zeb Smith commented
I can't enforce strict reboots for non-technical reasons, but I can certainly pop up nag windows. Something that would allow the user to postpone reboots after updates for a decreasing amount of time each loop would be fantastic.
Law YT commented
Should group all the updates into single reboot.
If there are software updates & applications requires reboot at the same times, should group it all together and ask for single reboot rather reboot one after another. This will enhanced user experience.
We also need control on how long the bubble messages stay open, most of our end users state that they never see them and only get the last countdown timer.
I'd like to see the ability to set the bubble messages to stay up until the user clicks on them or at least have the ability to config how long they are visible.
I would also like the ability to change IT department requires changes, in a previous company we had big fix and could customize the reboot prompt messages for each deployment
Steve Nowowiejski commented
Hallelujah! My biggest argument falls in line here. I was going to create a new post, but I hope it gets noticed here.
I do NOT like the fact that the reboot notification bubble only appears ONCE after updates are ran BEFORE the deadline is reached. In my testing, I only see it one initial time right after the updates are ran. If the bubble is not clicked and goes away, it turns into an icon and never reminds you with another bubble. When the deadline is reached, then you get your countdown.
I'd like to see an interval setting for reboot notifications much like the ones you get when "software is available", outside of the user manually "snoozing". At least with those, it will bug you every X hours if its greater than 48hrs to the deadline...etc.
Granular control over reboot/postpone/notification prompts that allows control on a per package or application deployment.
I'd like to add that the reboot prompt should be standardized across all reboot scenarios. A user gets a different reboot prompt from a task sequence initiated reboot compared to an application initiated reboot based on return codes. Have all reboot functionality consolidated into a single familiar prompt that admins can customize and even stick some branding on.
We have other apps and systems that auto update and put devices in a pending reboot state, which can cause SCCM App and Patch Deployments to fail. Would be nice if that option could be added as a pre-preq to prompt the user to restart (particularly for laptops).