ConfigMgr SUM installs should update the date of last install in Windows Update control panel applet
When you only use ConfigMgr to install updates, the date on the Windows Update control panel applet often reflects something that is really inaccurate as ConfigMgr doesn't update it. This often leads to a very negative reaction of "I thought those darn ConfigMgr admins were updating our workstations and servers!?!" And then we have to explain that we are, but that date doesn't get changed.
Can we please just ensure that when Software Update Management installs any updates, the Windows Update control panel applet gets set to the current date?
I stole the screenshots from this thread: https://social.technet.microsoft.com/Forums/en-US/b33dd5b2-64b3-476d-8fc5-232cbafced47/sccm-updates-are-installed-but-windows-update-status-wrong?forum=ConfigMgrCompliance
And I stole the idea of submitting the feedback from this thread:
Thank you for your help!
Never heard this before. Makes sense.
Alex Hillmann commented
It would be really great if this could be fixed, as this is causing some headache if people always need to check on Update history to make sure Server has been patched correctly.
Markus Hornum-Stenz commented
This is still a problem that really needs to be fixed.
Professional management of WSUS updates via ConfigMgr should be rewarded with accurate update of the Server Manager info
That this is still a issue more than 3 years after being noted by a Product Director or Executive, is not something that brings honour and respect to the MS brand.
Rick Bywalski commented
I have had the same issue multiple times with people freaking out that their server had not been patched in over a year when it was in fact patched every month. I spoke with Brad Anderson about it at Ignite two years ago.
Aaron Flaugh commented
This would be a awesome improvement.
Same problem, would love to see it fixed.
Matt Bailey commented
I have this exact problem not just with the users, i also have this problem with the help desk. Adding the fact that Endpoint pushes updates separately to SCCM explaining to them how to note the difference between SCCM updates and Endpoint definitions in the update history to tell if the updates are working doesn't help me. This would be a great fix.
Nash Pherson (MVP) commented
Had another conversation with a customer last week who thought updates had not been installed because this date didn't get updated.