I have an HKCU key I need applied to all users on a W2K server

[doobster1]

I am looking for a way to load the below registry key for all users. This is a "read-only" key and these users are not in the admin group.

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Security]
"CheckAdminSettings"=dword:00000002


This key will stop the Outlook pop-up about another application trying to access Outlook.

 

[ITPangaeaArchitect]

since the specified target is in HKCU, users do not have to be in the local administrators group to edit the registry. They have full control by default, so unless a registry policy is setting this as ready only (which may cause potential corruption in ntuser.dat/profile), then they can adjust this value fine.
With that being said, the best option is to either set this via a registry policy, or put it into a login script.

the alternative is painful, and involves adding the ntuser.dat hives for the users and putting the value in...whether scripted or manual, its painful....

-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+
Manager - Global AD Operations
ACS, Inc.

 

[oisnds]

Try putting the key in Hkey_users, HKCU is generated from multiple hives and is specific to one user.

 

[w33mhz]

Well one way you can do it is by creating an .adm file (administrative template) and apply it to just the local group policy or make a domain gpo and just apply it to that machine.

Here is a good link to show you how to create one.

http://support.microsoft.com/kb/323639

 

[ITPangaeaArchitect]

if you go with an adm, be advised that it will tattoo the registry. What this means, is that if you wish to ever remove the setting, you must first disable the policy setting, force gpo update on clients, then set it to not configured. This must be done to fully turn off the policy setting.

adm files can be tricky to create properly...also no need to do this really since you could make a registry policy to achieve the goal. No point in reinventing the wheel when the wheel already exists.

I would set in HKU instead of HKCU as mentioned earlier on though to ensure you dont cause permissions issues inside of HKCU.

-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+

 

[w33mhz]

you could also create a logon script to set the HKCU setting as well.