SCCM updates: User Experience - Reboot notifications
Here is the User experience for the update process as I understand it:
1. System tray balloon appears saying 'software changes are required'
2. System tray balloon appears saying 'downloading and installing software'
3. System tray balloon appears saying 'Restart required: Recently installed updates require your machine to be restarted'
4. *It is here I would like the larger temporary notification reboot window to appear but it doesn't.
5. Permanent notification reboot window appears and stays on the screen
I would like option 4 to be possible. Without this it seems quite easy for users to miss seeing the balloon notification and therefore not know that a restart is coming.
It would be good if there was an option in Client Settings > Computer Restart to automatically show the temporary restart notification window. It would also be good if there was an option here to permanently set the 'SCNotification.exe' in Notification Area Icons to 'show icon and notification' to further improve the visibility to users of pending restarts so they know to save their work before they leave their computer for lunch or when they go home.
I've attached an image of the temporary notification window I am talking about
I’m re activating this one based on the fact that we don’t show the intrusive reboot countdown after the software was installed. We still have some work to do here to make this experience meet the requested behavior.
Murray Webber commented
This is super-important. The toasts are fine, but if you're not at your device at the time, or are looking elsewhere, the result is a hidden-by-default system tray icon. This isn't ideal, and has led to a few complaints about forced reboots at inappropriate times even though we gave users a week to reboot. Furthermore, despite our best efforts to date, it's also exceedingly rare that the defined "temporary notifications" are displaying with the reboot warnings - i.e. 48 hours, 24 hours, 12 hours, 4 hours, etc. - causing users to go from nothing to forced reboot.
I'm not sure if it's necessarily related to the same thing, but I'd also suggest a reboot notification is required between the online phase and the offline phase of an In-Place Upgrade Task Sequence. Right now, the online phase can take so long, that user's are opening up applications and starting to do more work, then BAM! Sudden reboot for the offline phase, and they complain of losing work, or the reboot happening at an inappropriate time. Having some type of reboot notification in there would be perfect. But failing that, enhanced reboot notifications for Software Updates would be nice.
also keen to see your script Marcus Urban
Robert Stein commented
Any time there is a pending reboot for any reason (required for update to complete, required before next install can continue, etc). there needs to be a more prominent notification to the user. The green systray icon is not enough.
Nick C. commented
I worked with MS support and our Tam below are the resolution notes from the case.
Problem: Design Change Request for reboots- https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/9664707-sccm-updates-user-experience-reboot-notificatio#comments
Cause: Product Bug#3122690 which is marked to fix in SCCM 1902
Resolution: Product Bug#3122690 which is marked to fix in SCCM 1902.Since this issue was related to known code defect, the case will be closed as "non-decrement", and <company name> will not be charged for the support incident.
Austin WongCarter commented
Yes, This would be great, but let's also add a postpone option for a configurable amount of time. (Such as with the CoreTech reboot tool)
William Ellison commented
This would be great.
Michael Adams commented
Yes....this is needed.
Steve Lozano commented
I like this idea.
Add a new client setting to always display the 'User reboot experience' prompt when restarts are triggered regardless of deployment type. This prompt would allow the user to be reminded of the pending restart in X amount time, restart now, or simply hide and ignore the prompt. This intention is to provide a consistent user reboot and deferral process across software update and application/package deployments. When enabled, this prompt would be triggered instead of the temporary dialog prompt. Just looking to improve the user experience when we force a reboot of their system.
your solution sounds like the holy grail. I would be happy to get in touch with you (as well as Lars and Mark). Looking forward....
Hello Marcus Urban,
we would be interested in this script as well. If possible.
Mark Broughton commented
Marcus Urban - I'm very interested in your script if you are willing to share. We've been fighting to find a way to make everyone happy and it sounds like you've got a great solution. TIA.
Would be great to do the opposite. Need to see the notifications in console but suppress all reboot notifications. Only option currently is too suppress all notifications, show all notifications or show only reboot notifications.
A re-notify option for step 4 would be great. Something like show 2 day count down with 6 hour postpone and then custom time for window you cannot hide. We need to remind people more often and give people ample time to restart on their own with interrupting critical work.
Keith Nail commented
Marcus Urban - Could you please send more information on this?
Microsoft has been looking forward so long that they keep forgetting to look back to notice they have left their customers in the mud they have made.
Marcus Urban commented
Hi, because Microsoft is not willing to implement such a small Feature in a adequate time, i managed to solve the problem on my own. I wrote a powershell script which checks for pending reboots. This will be triggered every hour via Compliance Baseline in SCCM. Currently we have implemented 6 steps of warning levels for users. The User get Toast notifications more often, based on the time which is already gone since the first information, which is calculating the "nagging Level". At the end, the Toast notification appears on the screen and will only disappear if the user click on it. If the User not rebooting his System in the configured time, which is in our case separated to real personal accounts and functional accounts (10 Days and 21 Days), the script will enforce a reboot of the System. This is how i solved the problem regarding inform the user and reboot systems.
If you need more info on this, let me know
Toast notifications were so bad that I was tasked to creates a windows XP style popup for when passwords were about to expire. NOBODY noticed the 5-second toast long enough to read them or care about reading them. Users thought "It went away so it fixed itself".