Windows 10 – Set Registry Keys Under Current User During OSDeploy Task Sequence

sccmwindows 10windows-registry

I have the TS setting the registry keys in the HKEY_Local_Machine no problem.

My issue is that I want to, by default, set a key for the HKEY_Current_User.
I want to have the "Automatically detect settings" in Internet Properties LAN settings unchecked, for anyone logging in.

I think that the correct key is

Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings

but as it is in the Current User I am finding it hard to have it set by default, through the OSDeploy TS. Want it set by default for a no-touch build of all our machines.

Any help would be appreciated.

Best Answer

Generally speaking this is more something you would control by a GPO than OSD but technically it is no problem.

What you have to do is modify the default user profile, i.e. the template from which all future profiles are created. The most basic way (and by far not the worst) to do this is using the built in tool REG.EXE First load the default user profile like this:

reg load "hku\Default" "C:\Users\Default\NTUSER.DAT"

Next modify your key (binary data should be entered without spaces or seperator as the /d parameter):

reg add HKU\default\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections /v DefaultConnectionSettings /t REG_BINARY /d 460000... /f

Finally unload the hive

reg unload "hku\Default"

The biggest problem here is probably that you have got a binary key which is a little rough to manage.

You could work around this by loading the default user profile on a running machine (in the same location hku\default) with regedit. Then navigate to your path, modify the key and export it into a reg file. Then you could use

reg import <path to regfile>

in place of reg add.

Whichever way you find better, put those steps in a simple cmd and run with run command line during osd. In theory you could even do it directly in your reference image and thus bypass the need to do it during OSD at all. I would personally advise against such things however as this always means that a change in this setting is a complete rebuild of the reference image.

Related Solutions

Windows – How to deploy a single .reg file so that it can be stored to a whole bunch of different USER accounts on a non-domain terminal server

If the server is Windows Server 2008, Windows Server 2008 R2 or Windows Server 2102 you can create a local Non-Administrators group policy object that will apply to all non-administrators logging on to the server. You should be able to deploy the REG file in a logon script.

Add, remove, and test for the existence of a registry value * at the Command Prompt

The tricky part of checking a registry value named * (actually a wildcard of meaning all):

query only one-character named values using ? wildcard i.e. at most one character, and
narrow the result to the value named * using findstr utility;
- in fact, reg query "%_TestKey%" /v ? | findstr /I /C:" * REG_" could suffice.

The following batch-file code snippet shows that there is no issue with adding, removing or changing a value named *.

The code is commented using <NUL set /P =::: … trick i.e. echo ::: … with no ending CRLF to show comments in output with minimum of empty lines.

@ECHO ON
@SETLOCAL EnableExtensions DisableDelayedExpansion
@<NUL set /P =::: define a registry key
set "_TestKey=HKEY_CURRENT_USER\Software\Test Key"
@<NUL set /P =::: check all one-character named values 
reg query "%_TestKey%" /v ?
@<NUL set /P =::: narrow above result to the value named * using findstr utility 
reg query "%_TestKey%" /v ? | findstr /I /C:"%_TestKey%" /C:"    *    REG_"
@<NUL set /P =::: delete the value named *
reg delete "%_TestKey%" /v * /f
@<NUL set /P =::: add the value named *
reg add "%_TestKey%" /v * /t REG_DWORD /d 4 /f
@<NUL set /P =::: check the value named * 
reg query "%_TestKey%" /v ? | findstr /I /C:"%_TestKey%" /C:"    *    REG_"
@<NUL set /P =::: change the value named *
reg add "%_TestKey%" /v * /t REG_DWORD /d 1 /f
@<NUL set /P =::: check the value named * 
reg query "%_TestKey%" /v ? | findstr /I /C:"%_TestKey%" /C:"    *    REG_"

Output:

==> D:\bat\SF\a867740.bat
::: define a registry key
==> set "_TestKey=HKEY_CURRENT_USER\Software\Test Key"
::: check all one-character named values
==> reg query "HKEY_CURRENT_USER\Software\Test Key" /v ?

HKEY_CURRENT_USER\Software\Test Key
    a    REG_SZ    Latin Small Letter A
    .    REG_SZ    Full Stop
    ?    REG_SZ    Question Mark
    *    REG_DWORD    0x1

End of search: 4 match(es) found.
::: narrow above result to the value named * using findstr utility
==> reg query "HKEY_CURRENT_USER\Software\Test Key" /v ?   | findstr /I /C:"HKEY_CURRENT_USER\Software\Test Key" /C:"    *    REG_"
HKEY_CURRENT_USER\Software\Test Key
    *    REG_DWORD    0x1
::: delete the value named *
==> reg delete "HKEY_CURRENT_USER\Software\Test Key" /v * /f
The operation completed successfully.
::: add the value named *
==> reg add "HKEY_CURRENT_USER\Software\Test Key" /v * /t REG_DWORD /d 4 /f
The operation completed successfully.
::: check the value named *
==> reg query "HKEY_CURRENT_USER\Software\Test Key" /v ?   | findstr /I /C:"HKEY_CURRENT_USER\Software\Test Key" /C:"    *    REG_"
HKEY_CURRENT_USER\Software\Test Key
    *    REG_DWORD    0x4
::: change the value named *
==> reg add "HKEY_CURRENT_USER\Software\Test Key" /v * /t REG_DWORD /d 1 /f
The operation completed successfully.
::: check the value named *
==> reg query "HKEY_CURRENT_USER\Software\Test Key" /v ?   | findstr /I /C:"HKEY_CURRENT_USER\Software\Test Key" /C:"    *    REG_"
HKEY_CURRENT_USER\Software\Test Key
    *    REG_DWORD    0x1

Best Answer

Related Solutions

Windows – How to deploy a single .reg file so that it can be stored to a whole bunch of different USER accounts on a non-domain terminal server

Add, remove, and test for the existence of a registry value * at the Command Prompt

Related Topic