Editing Group Policy Settings
- Thread starter RobertX
- Start date
-
- Tags
- group policy
Group Policy Editor creates a local policy file, which is basically a modified reg hive that is applied on every Windows startup, or after you run "gpupdate /force". When applied, GPO's will create a set of corresponding reg changes in the system or user hives. But anyone or any process with Admin rights can modify the registry after the GPO has been applied.
So the idea behind the policy is it's a protected reg template which pushes changes out in one direction, but not in reverse. You can force the changes back to your template's settings at any time they're overwritten.
Some users don't want to play with GPE, and instead capture the end result of all of those forced reg changes. This can be done by exporting the different HKLM and HKCU registry paths that include Policy changes.
The captured changes may be in the form of a reg file, or reg commands inside a script.
NTLite doesn't support direct editing of policy files. Instead you have two options:
1. If you prefer to manage by formal policy, use the MS LGPO tool to export the policy file from a live system, and use the same tool to import the saved policy into a new system. Policy files are re-applied whenever Windows is restarted.
2. If your prefer to use reg files or scripts, you can invoke them from Post-Setup. Added reg files are executed by NTLite using "reg import" commands. HKLM-based changes should be added to Post-Setup (Before logon), which runs under the SYSTEM identity. HKCU-based changes should be added to (After logon), which runs under your user's profile.
NTLite has a number of Settings tweaks, and maybe half of the them exist in real life as policy-based reg edits. There will be no visible clue that a specific Settings tweak is actually performed by something you could do as an equivalent reg file or script change.
So it's up to you, whether you want to browse through the different Settings, or just import a reg file or script because that's easier for you.
So the idea behind the policy is it's a protected reg template which pushes changes out in one direction, but not in reverse. You can force the changes back to your template's settings at any time they're overwritten.
Some users don't want to play with GPE, and instead capture the end result of all of those forced reg changes. This can be done by exporting the different HKLM and HKCU registry paths that include Policy changes.
The captured changes may be in the form of a reg file, or reg commands inside a script.
NTLite doesn't support direct editing of policy files. Instead you have two options:
1. If you prefer to manage by formal policy, use the MS LGPO tool to export the policy file from a live system, and use the same tool to import the saved policy into a new system. Policy files are re-applied whenever Windows is restarted.
2. If your prefer to use reg files or scripts, you can invoke them from Post-Setup. Added reg files are executed by NTLite using "reg import" commands. HKLM-based changes should be added to Post-Setup (Before logon), which runs under the SYSTEM identity. HKCU-based changes should be added to (After logon), which runs under your user's profile.
NTLite has a number of Settings tweaks, and maybe half of the them exist in real life as policy-based reg edits. There will be no visible clue that a specific Settings tweak is actually performed by something you could do as an equivalent reg file or script change.
So it's up to you, whether you want to browse through the different Settings, or just import a reg file or script because that's easier for you.
- Messages
- 1,197
- Reaction score
- 235
When I used it, I just copied the corresponding files (the ones on Windows) into the image, and it worked without any problems
But that was with Windows 7 (or very early Windows 10)
Now I add the registry keys via a REG file and NTLite (Registry Page)
But that was with Windows 7 (or very early Windows 10)
Now I add the registry keys via a REG file and NTLite (Registry Page)