Microsoft acknowledges permission problems with MS16-072 patches KB 3159398, 3163017, 3163018, 3163016Posted on June 16th, 2016 at 08:21 Comment on the AskWoody Lounge
It took 36 hours, but they came clean.
InfoWorld Woody on Windows
Rod Trent notes on WindowsITPro that there’s a PowerShell script that will go out and see if any of your domain’s computers are affected.
UPDATE: Susan Bradley notes this “doesn’t have to be listed in the client side patches – Windows 10 for example. The fix for this group policy mess has to be done on the servers. so 2012/2012 r2 is where the known issue stuff should be documented.”
That means if you see the problem on your machine (client, not server), your admin has to solve the problem. And the solution is in the KB article directed to your admin.
Posted on June 15th, 2016 at 09:56 Comment on the AskWoody Lounge
I’m coming up to speed on this one, on a very busy Wednesday morning. Anything new to add?
From DC_FS on the TechNet forum:
I found out that if you give the Group authenticated users the right to read the GPO (Just Read, not to Apply the GPO) then the Policies work again.
Details from Rod Trent on WindowsITPro.