• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
troxy

Gpedit.msc and the registry

2 posts in this topic

Hi! I've noticed that the gpedit.msc tool (Group Policy Editor console) doesn't show the actual registry value for a policy.

For example, the policy "Always use classic logon" relates to the following registry key value:

HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\LogonType

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:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\

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.

/Emil

0

Share this post


Link to post
Share on other sites

Troxy,

Thank you for sharing! I actually looked for this sort of info the other day on the Microsoft site, but I couldn't find anything (maybe I didn't search hard enough).

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.