Script for Group Policy Registry Keys

[medyo21]

I need help in obtaining the registry locations/keys that are modified when I make a change to the local security policy in group policy.

Everytime I build a new PC I have to go to regedit.msc to set up the settings that I want. Is there a way I can find out which registry keys are modified when I enable/disable a setting in group policy? I want to create a script containing all those values so next time I build a PC all I need to do is execute that script instead of going through the entire computer and user configuration again.

Thanks!

[Eric]

Take a look at ART - Advanced Registry Tracer from Elcomsoft. Here's a link:

http://www.elcomsoft.com/art.html

Enjoy!!

Eric

[medyo21]

Thanks Eric!

I tried ART and it is able to detect the changes that I make on the group policy but it does not provide me the exact names and keys that was changed. It would show me the location but when I go to it, or even manually go to to it through the registry, the name isn't comparable to what was changed.

[Eric]

This is the spreadsheet Microsoft releases that has all of the settings and all of the registry keys in it.

http://www.microsoft.com/downloads/details.aspx?FamilyID=7821c32f-da15-438d-8e48-45915cd2bc14&displaylang=en

That might have what you are looking for.

[medyo21]

Amazing how you are able to find this. I've been searching all over the net only to discover that it can be found through Microsoft directly...duh!

Thanks Eric! This is what I needed.

[AdamV]

Daft question, but is this in a domain environment?

Setting policies by using scripts to edit the registry keys used by local policies sounds like a horrible mess to me.
Why not use 'real' group policy to set these settings in a managed fashion so you can unset, reset and alter them at will, and never need to use local policies again?

[medyo21]

No, if this was in a domain environment I would have used the default domain policy. I mentioned on my initial post that I need it for new PCs that I build. On a domain environment you typically would have an image of the PC already set, thus eliminating the need to configure the local policy again.