[German]Windows 10 November 2019 Update (Version 1909), seems to have issues with Group Policy because changes cannot be set reliably. At least a blog reader has made this experience in a test environment.
Blog reader Markus K. runs some test systems with the Windows 10 November 2019 Update (Version 1909) at a university in Austria and wanted to deal with the topic of Group Policy deployment for Windows clients. He noticed a problem. Markus wrote me before Christmas:
We have been trying to roll out in our test environment for quite some time in 1909.
Since we have a lot of GPOs, it is essential that they work in a reliable way.
Now comes the fun part, sometimes it works and sometimes it doesn’t :).
Markus states that the Windows 10 version 1809 machines never have issues with the distribution of the GPOs. On the computers with Windows 10 version 1909 it is just coincidence if a group policy is working or not.
Markus wrote me that neither the event logs nor the GPSVC log are very useful. In the GPSVC log, Markus sees that the CSE registry is creating a kind of error (permission denied?). And it comes even harder, as Markus found out:
It’s funny that if you manually start “gpudate /force” some time later, the application of group policies works after the next reboot.
The problem also does not affect all Windows 10 version 1909 clients. Markus writes the following:
Other [Windows 10] V1909 [clients] will be installed and are usable after a marginal delay.
Markus says about this: It looks like a random bug to me, which makes the diagnosis especially pleasant. They have about 700 GPO objects in the test environment alone, which doesn’t make debugging any easier. At this point he asks if something is known, or someone who has heard about it. Then he and probably the rest of the blog readers would be grateful for any tip. Thanks for the tip.