HKEY_CURRENT USER ... how to add a key


I have a problem here. After applying  new Custom Outlook Security Settings, I am told by this documentation that I need to add a new registry key to the HKEY_CURRENT_USER subkey.

The Current User cannot add it in, if I export it - as they don't have permissions - they are standard users.

What is the way around this ?



1.      Start the registry editor and expand the following subkey:
2.      From the Edit menu, choose New, then click DWORD value to add a new registry key.
The value name for the key must be CheckAdminSettings.
Who is Participating?
the *\policies\* keys are (for good reasons) not writable for regular users, as SpencerSteel already pointed out. The logon script runs in the user's security context, so the user will not be able to change any of those settings in it.

you need a Group Policy for that. Save this as "OutlookAdmin.adm" (or whatever.adm), import it into the proper GPO in the group policy editor, and configure away:


CATEGORY !!AdditionalSettings

  CATEGORY !!Outlook

    POLICY !!CheckAdminSettings
      KEYNAME "Software\Policies\Microsoft\Security"
      VALUENAME "CheckAdminSettings"
    END POLICY ; !!CheckAdminSettings

  END CATEGORY ; !!Outlook

END CATEGORY ; !!AdditionalSettings

AdditionalSettings=Additional Settings
Outlook=Microsoft Outlook
CheckAdminSettings=Look for custom administrative settings

You could run this as part of a login script - just apply to logon script of gpo containing users or to users in script through netlogon -

On outlook machine, set the registry change correctly - then export the key only to a reg file. Edit the reg file so it only contains the key you want to change, save it as outlook.reg and copy it to the share you specify below:

then in the logon script
add the following line
regedit.exe /s \\yourdc\share\outlook.reg
regedit.exe /s \\yourdc\netlogon\outlook.reg

Or you could use a more elegant (and speedy) solution using a vb script as illustrated in this PAQ:


Deb :))
So your vb script would be something like: The 0 is just an example of the value assigned to your new key,

Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")

WshShell.RegWrite "HKEY_CURRENT_USER\Software\Policies\Microsoft\Security\CheckAdminSettings", 0, "REG_DWORD"

Deb :))
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Sorry - SpencerSteel too much scripting ideas and not enough consideration of the question :((
Thanks for that oBdA  - I stand corrected (But why if I get it wrong which isn't really that often believe it or not - is it always you?)

Deb :))
SpencerSteelAuthor Commented:

Thanks for all your help so far - you realise the main problem here.

However, I am a novice with your scripting ... however, I've done what you said and saved the file, and imported it into the Scripts (Logon/Logoff) of the User Configuration in the GPO. Is this right?

Sorry to be an idiot - i'm still not very up with the GPO settings ... slowly getting there.

Thanks again

SpencerSteelAuthor Commented:
Well - after a bit of investigation, that seems to be in ... it's gone into the USERS (as opposed to CurrentUser) Subkey - which I assume is like ALL USERS or something ...

The damn thing I'm trying to get to work still doesn't - but you've solved the Reg issue (I'm 99% sure)

So thanks - have some points.

Sorry Debs :)

Hi Spencer, Hopefully I'll get this bit right at least ;)

Obda is on a different time zone I think, and as you're obviously working on this right now I thought I should respond - ObDa has given you a custom admin template that you can import into your the relevant group policy object for your ou - as I think you've already done, paste oBda's text into a text file and save it as described with a .adm extension.

Then edit your relevant group policy and add it as a template - right click administrative templates under user configuration and click add/remove templates - Then add the custom template you just created. You can then enable this reg entry as a policy which will apply to the users in the ou -

Deb :))

**********Do not accept as answer - oBdA was correct*******************************
SpencerSteelAuthor Commented:
Wow ! I get it ... now that is impressive.

Never seen that before. Makes a lot more sense now - thanks for clearing that up Deb ... you're on my Christmas list.

No probs - Some redemption at least - (I'd like a porsche please ;))

Deb :))
SpencerSteelAuthor Commented:
Actually - I have to add to this ... this has just totally sorted everything.

So, full marks to oDdA for his template thing ... and full marks for Debs for seeing my complete lack of understanding as to what to do with the damn thing.

Thank you both ... I have just finally got rid of those hugely irratating 'outlook warnings' when my application uses Automation to access it.

You will both go to heaven.

What no assist?
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.