Idea ID 2781143
Provide a non-snoozable notification as last step before a forced reboot
Status:
Waiting for Votes
Submitted by
JasonB1
on
2015-06-09
15:07

As an end user when my machine is patched and needs to reboot I was to see some kind of notification before it actually reboots so that I know why the machine is rebooting. This notification should be configurable by the administrator.
Additional Information: Today if the administrator configures snooze for instance and the total allowed snooze time is say 2 hours, and the end user snoozes and then hibernates his PC then comes back in the morning, the system will immediately initiate a reboot without any kind of notification.
Happy Path:
1) The admin configures a reboot to be required after some period of time and allows snooze and configures this option for final notification.
2) The user snoozes the reboot and then sleeps or hibernates their PC
3) The user boots up their machine the next morning and instead of immediately rebooting they have a message indicating that their machine will now reboot with only an OK button.
Additional Information: Today if the administrator configures snooze for instance and the total allowed snooze time is say 2 hours, and the end user snoozes and then hibernates his PC then comes back in the morning, the system will immediately initiate a reboot without any kind of notification.
Happy Path:
1) The admin configures a reboot to be required after some period of time and allows snooze and configures this option for final notification.
2) The user snoozes the reboot and then sleeps or hibernates their PC
3) The user boots up their machine the next morning and instead of immediately rebooting they have a message indicating that their machine will now reboot with only an OK button.
Labels
- Labels:
-
Other
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.