2,020 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
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.Anonymous supported this idea ·Anonymous commented
I would like to see the ability to customize timeframes with snooze/remind time options based on when an update becomes available based on offsets from available and required times. Additionally, the ability to allow a user to postpone a restart indefinitely by snoozing repeatedly (ie: not actually allow them to select to postpone a restart, but to cause a nag that will eventually get them to restart, but more at their convenience) with a specified timeframe that can align with these intervals.
For instance, handling various scenarios (and more complex), such as this:
Day 1: Update 1 Available
Day 7: Update 1 Required - Automatically install outside maintenance window, but do not restart
Would like to be able to do things like:
-Display a notification at availability time.
-Two days after it is available, the user can get notified of its availability every day if it has not yet shown for each user.
-Twelve hours after that (2.5 days after available time), this notification could start showing if they haven't seen it in the past 6 hours.
-Two days before its required, change it over to prompt the user to snooze the available reminder up to 4 hours. When the update becomes required and / or is installed, have a custom notification to prompt the user of a pending reboot, allowing them to snooze it up to two hours at a time for the next 72 hours.
-Should detect and prevent overlapping schedules, and force you to fill entire remaining schedule, or specify a default for areas where there is no schedule (preferably also configured)
-Some sort of settings priority for this similar to client settings... but, preferably in a way that the priorities can be changed a little more quickly, or at least sitting there waiting for a refresh to keep clicking increase priority. Something like a "move to priority # and shift any existing up/down".
-Would also be nice to be able to set all of this through ADR and deployments on the SUG and have creation template. Ability to load template independently for this section would also be cool. For instance, if setting up a complex schedule to be used across multiple ADRs/deployments, this notification schedule could be reused. Would be nice to be able to associate a set of schedule rules with an ADR/deployment (ie: just an object reference so it stays up to date rather than a template persay, but would be nice to have both options)
Would also like to see the ability to display a prompt to the user prior to initiating or forcing a restart to help instances where someone opens a device on a Monday and has no choice but to restart sometime shortly thereafter. For instance, require at least one user to have seen the notification for the reboot to even be able occur. Something along similar lines of giving them some form of a custom snooze time that can be postponed indefinitely or per some schedule (ie: change it to three days after required date to be more rigid or something). Might not handle all situations as-is (ie: a lab environment) if its a multi-user scenario, but would help with things like devices assigned to or primary device of certain a single user.
Multiple notification options would be nice. Taskbar, toast, balloons, etc. Would like to see those customizable, at least, something like an IT department icon and logo and customizable sizes. Something like a "click to confirm restart" checkbox before allowing the user to click restart as a basic functionality. It would be nice to have full control of the UI, and have some variables available for display (ie: name of update currently installing if one is installing, progress %). Some ability to mod the XML directly to overcome any limitations here would work, too, but just thinking there should be something in SCCM that will pop it up automatically on a schedule made in rather than having to roll your own via task scheduler and CIM calls or something.