In the zeal to get windows updating… or rather rebooting … more palatable I think Microsoft swung a little too far away from notifications. I’m running 1511 and so many times odd things start occurring and I realize that updates have been installed, but the system hasn’t been rebooted.
I personally feel that you need to reboot after installing updates so I’m going to run this Windows 10 testbed that I have here with the “metered” connection trick. Lifehacker has blogged this long ago trick where you make the network connection think it’s on a metered connection which then holds back the patches. Windows 10 has no “download but do not install” in the gui.
I know when windows updates come out, but I don’t like the side effects one gets when updates have been installed and the system hasn’t yet been rebooted.
When Group Policies Suddenly Stop Working
My apologies, I didn’t blog my follow up to the issues introduced by MS16-072. Wayne blogged a solution over on the thirdtier blog site that you can do to fix up your group policies and get them back working again. I’m not a fan of uninstalling security updates and leaving them off, rather find the solution to fix the underlying problem.
On SBS 2011 and 2008 certain preconfigured group policies provided by Microsoft no longer work.
Log into the server, and drill down into the event logs, and specifically the one for Group policy. Look for Event 5313 and it will list the Group policies no longer working.
The three in particular that no longer work are:
Update Services Client Computers Policy
Windows SBS User Policy
Windows SBS CSE Policy
To fix this log into the Group policy console and in the security filtering section add the Domain Computers.
Literally click on add and type in domain computers in the window and click ok.
Do the same for each group policy indicating that it failed to process.
More Recent Articles