Add registry key using GPO

I am having some trouble creating a new GPO that will add a registry key to all computers in an organizational unit.

As per this Microsoft KB, adding a registry key corrects a network performance problem we are having at a customer site.  We have tested it by adding the key manually and it works great.  We now need to deploy it to all workstations within an OU.
Method 4. Disable the OFV Add-in by using a registry setting

I created a new GPO, linked it to the appropriate OU and configured it as follows:

Computer Configuration--> Preferences --> Windows Settings --> Registry

New --> Registry Item

General Tab
Action:  Create
Key Path: Software\Microsoft\office\11.0\excel\security\filevalidation\
Value Name:  EnableOnLoad
Value Type:  REG_DWORD
Value Data: 00000000
Base:  Hexadecimal

Unfortunately, we are not getting the key.  Any thoughts?

See attached print screen for settings.
Who is Participating?
djcanterConnect With a Mentor Commented:
alternatiely,you can also use a logon script for the ou to import a .reg file containing your changes.
I think the key is for users and the GPO need to be place in User configuration preferences and applied on OU containing users
Since these preferences are run in security context of system account, it should work even if user is standard user.

and for windows XP, you must 1st deploy CSE on windows XP to support GP preferences

Lastly try to change mode from create to update so if key is not there it will be created and from next time it will just check that value 1st and if found it will just skip that

Adam BrownSr Solutions ArchitectCommented:
Try using the Update method for the preference instead of Create. Sometimes that works better for some reason. Also make sure that any windows XP machines have the necessary updates to use GPO preferences. If you have the latest service pack on them, they should have the updates, but I have seen some XP machines still fail to pick up Preference settings without having the client side extensions explicitly installed on them. It's available here:

You may also need to have two preferences for it to work. One to create the Security folder and another to create the Key that is a child of that folder.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Will SzymkowskiSenior Solution ArchitectCommented:
Is the policy even making it to the client machine? Use rsop.msc, right click>Computer Config>select properties.

On the general tab it will show all of the policies that are being applied to the machine. If you are using Group Policy Preferences and applying this to Windows XP or 2003 you will need to have the GPP windows patch (client side extensions) in order to get the policy.

If the machines are Windows 7 then it should be fine from that perspective.

Also check the event viewer to get additional detail if the policy is being applied to the machine from rsop but it failing to load.

Adam BrownSr Solutions ArchitectCommented:
Actually, on checking it looks like mahesh is correct. This registry modification is supposed to go to the HKEY_CURRENT_USER registry hive, which can only be appropriately modified by using a User Configuration profile setting. You can get this to work properly on an OU of computers by enabling group policy loopback processing and setting the GPO to modify the registry preference under User Configuration instead of computer configuration. has info on loopback processing.
Since this is non conflicting setting and GP preference can be set in Update mode,
hence Loopback mode is not required.
Enabling loop back mode settings will unnecessarily change other users GPO settings if any.

Adam BrownSr Solutions ArchitectCommented:
Entering the preference in the User Configuration section will cause the preference to be ignored when the users log in to the *computers* that need this setting. Note that this is a problem impacting computers in a specific site and not users. If the OP wishes to apply the setting only to those computers, then GP Loopback is necessary. If he just wishes to apply it to the users that log in to those computers, he can link the policy to the user account. As it stands, his current GPO is linked to an OU of computers, not an OU of users.
You are right, GPO need to be applied on OU containing Computers and loop back processing will be required since registry key is for logged on users but for specific computers only.

LenCepedaAuthor Commented:
Thank you all for your help.  I had a hard time getting the GPO to work when I applied it to the computers container.  Rather, I took djcanter's advice and imported a .reg file using a GPO that was linked to users container instead of computers.  It looks like all users received the update.

Unfortunately, we did start to receive reports that users' home directories were not mapping properly.  Basically mapping looks like this
\\Fileserver\ShareHidden$ instead of \\Fileserver\ShareHidden$\Users\User_Name...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.