Forum Discussion
SOLVED: Group Policy setting CSP
Yes look into using MDMWinsOverGP, define your Software updates > Windows 10 update ring before making CSP changes as you will likely resolve some of the issues.
If you need more info on the Update CSP settings, check out
https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update
The first two settlings looks like;
./Vendor/MSFT/Policy/Config/Update/AllowAutoUpdate
./Vendor/MSFT/Policy/Config/Update/AllowNonMicrosoftSignedUpdate
I am not sure about the third, however Update CSP has had a number of recent changes so this may not matter so much.
,Andrew
So I was able to figure out the issue with the GP settings. Adding here for anyone to refer in the future.
There are some policies that even after you disable, stick around on the computer. https://docs.microsoft.com/en-us/archive/blogs/grouppolicy/gp-policy-vs-preference-vs-gp-preferences
- tattoo. In other words, when a GPO goes out of scope, the preference value will remain in the registry. An administrator is responsible for making sure these values are set to disable, prior to the GPO going out of scope, if the administrator wants the preference setting removed. The preference setting will not be replaced with the original application configuration value.
Based on this, I checked my registry and found the entry HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU as NoAutoUpdate : 1
Just changed the value to zero and my update settings are all now with MDM and I don't need any other CSP policies now! 🙂 It was a good learning about the CSP policies though
Ambarish Haridathan Great work ! all CSP settings can also be found here https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update