For example, the policy "Always use classic logon" relates to the following registry key value:
0 = Classic logon (Policy is "Enabled")
1 = Welcome Screen (Policy is "Disabled")
If I use gpedit.msc to enable the policy, and then use regedit.exe to disable it (manually changing the value for LogonType), the GUI in gpedit.msc still says "Enabled".
I've now realised that gpedit.msc keeps the status for every policy in the following registry key:
So when you use gpedit.msc to change a policy, it saves the status in the "Group Policy" reg key, and then writes changes to the "Registry.pol" file in the policy folder "%SystemRoot%\System32\GroupPolicy\" (User or Machine)
At logon time, Windows reads "Registry.pol" and updates the registry accordingly.
This is no news to most people here I suppose.
But since I found no good info on the web about the relation between gpedit.msc and the registry, I wanted to raise the topic here in order to clarify.
Please confirm my following conclusions:
- gpedit.msc is not just a GUI for editing registry values for policies.
- gpedit.msc is rather a GUI to manage policy settings stored in "Registry.pol".
- gpedit.msc becomes irrelevant when you edit the registry settings manually (using scripts or regedit.exe).
- Using gpedit.msc when you are editing the registry settings manually makes no sense and will only confuse things.
I hope I've made things a little clearer for some tweakers out there.