KACE Product Support

What I had done in the past is upload a reg file and then import with this command line regedit.exe /s test.reg as a post install task on K2000 image. - mlathrop 12 years ago

Can you suggest how to import using regedit to the 64 bit hive? - mlathrop 12 years ago

For those of us not using script tasks for our software deployments, this is not a working solution. Certain software developers have their install check for registry entries specifically in the native HKLM\SOFTWARE location. Using REG ADD in a batch script to satisfy this works except for when KBOX Managed Installation is asked to run that batch script. KBOX changes the registry location to HKLM\SOFTWARE\WOW6432Node which means the software install fails.

I have tried both REG ADD HKLM64\SOFTWARE and HKLMNAT\SOFTWARE, which is what we are instructed to use for REG QUERY, but both of these fail to do anything at all when using REG ADD. If I run the script from other management systems there is no issue with this, so it is not MS, it is a KBOX thing. Does anyone have a working method to include a native registry REG ADD command within a batch script running from a KBOX Managed Installation (not kscript)?

I don't mind another work-around, but I need something I can script in a KBOX Managed Installation, not kscript. - WayneMan 4 years ago

well, I have found the Registry changes seems to only affect the WOW64 hive, - mlathrop 12 years ago

I am not sure I understand what you mean by that.
Whatever key you export and put into your .reg file will get modified on target computer.
Ex. I used the following content in .reg file to disable Reader Browser integration:
"
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\Originals]

"bBrowserIntegration"=dword:00000000
"
This was a HKCU key, so I had to run it while users are logged on, but for HKLM it's same idea...
Create the key you need, export it, then push it out... - nchirtes 12 years ago

I think Christian has a good point, You might do some reading on Registry Redirector... Some keys would get redirected there as well, but that does not mean that those keys do not work. It all depends on the type of application you try to control.. is it a 32 or 64 bit one.

Best yet, let us know what exactlly are you trying to do here, as Christian mentioned... - nchirtes 12 years ago

The critcal thing I was trying to do awhile back was to suppress the Windows Update for IE9 by changing a key. Other things are simple as setting the default IE start page. On XP I was able to do reg edits just fine under the agent, however under Win 7 I can't seem to do regedit under the agent credentials - mlathrop 12 years ago

I was trying to do exactly the same thing - prevent IE9 from auto-installing by updating the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Setup\9.0\DoNotAllowIE90 to a value of 1.

If I manually run Microsoft's tool (which is really just a .cmd file), it will set the value in the exact location I listed, above. If I try to apply the change via the K1000, it instead sets the value under the Wow6432Node:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Setup\9.0\DoNotAllowIE90.

I read the MS article on registry redirection, and it seems to me that having this setting in the wrong section of the registry will render it ineffective, though I haven't tested it, yet.

In the end, I used PHKace's suggestion of using HKLM64\... in my script, and that set the value in the expected location.

I'd be curious to know if setting the value in Wow6432Node would also disable auto-installation of IE9 on a 64 bit Win 7 machine. - palmerEldritch 12 years ago

exactly what I was trying and setting the key under Wow6432 is not effective. - mlathrop 12 years ago