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.
This would be a great approach:
1) Set a deadline for the patch to be installed.
2) begin prompting the user daily to install/reboot up until the deadline.
3) on the final day prompt the user hourly until the deadline timer has expired.
4) Allow for a small deferral window past the deadline time. maybe 3-4 hours.
The big complaints from our user now are they do not see the toast notifications showing the update is available. They only see the final countdown timer that can't be moved off the screen before the computer reboots. We had to set this to 4 hours because users were constantly getting that prompt while presenting in a meeting or while running a big workload and it will kill their work. The biggest improvement would just be multiple prompts to the user that they have to acknowledge before any forced reboot happens of any kind. Let the user control more of their own destiny instead of IT having to decide on the exact time their computer will reboot.
Our company recently went to the MTC in Dallas and discussed this issue with them. The MS recommendation to us was to stop using ConfigMan for patching and switch to a different solution. I am not making that up. There was no other solution that MS could come up with to solve all the user complaints about how disruptive Software Updates are. Its crazy because this could be easily solved. I guess MS shows no love to SCCM anymore and wants all their customers to stop using it in favor of 3rd party tools.
How is it we have a simple user enhancement with almost 900 votes that is still being ignored by the product team even after several years of complaints? I have even personally given this feedback to the PMs at multiple conferences. Our users have been furious with how Windows Updates work for years. The only option we have is to just tell them its Microsoft's fault and there is nothing we can do about it. Huge black eye for MS on this one. If I could give this 10 votes I would. There isn't a single enhancement for ConfigMan that is more important than this one.
This is a major complaint of our end users. They never see these little balloon pop-ups and so they never know to restart their computer until the final countdown timer starts. The prompting for reboots should be the same as for software installs. The closer it gets to the deadline the more frequently they should be prompted.
This also occurs on our Win10 In-place upgrade TS as well as the Win10 Feature upgrades TS. We put a reboot in early on the in the TS because we see a lot of errors happen if the OS is not rebooted 1st. But then it just sits at the login prompt waiting for the Agent to initialize and continue on with the TS. Users think its already finished and try to login causing interference with the running TS.
Normally we update to started when the feature is in a TP… but this can’t be in a TP (as CAS isn’t allowed in a TP.) But the code is in TP. :)
Since Microsoft at RTM gave guidance to use a CAS and then later changed that guidance. Please give us a way to correct that bad guidance by making the migration easier.