I'm having a ridiculous amount of trouble getting MSI's with HKCU bits to install with Radia (as an aside, never buy HP Radia, it's the worst deployment tool on the planet).

The only way to deploy HKCU bits in the new version is to split the MSI into two (one that does HKCU, one that does everything else) and deploy one after the other. Stupid, I know.

I'm trying to get around this and their Dev team came up with this:

-----------------------------------
Set the HKCU keys with Root= -1 in the registry table, which means:

If this is a per-user installation, the registry value is written under HKEY_CURRENT_USER.

If this is a per-machine installation, the registry value is written under HKEY_LOCAL_MACHINE. Note that a per-machine installation is specified by setting the ALLUSERS property to 1.
----------------------------------

Does anyone see a problem with this approach?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If your application is optional you can choose not to install the application under the system account(Setting is found in the service level)... the HKCU settings are written correctly to the user who installed the app. Use active setup (making sure to write the GUID to the same location in the HKCU - to block the installation from running again)

If the application is mandatory and can be installed under a system connect... then use Active Setup and have the user reboot...

Or you can create a seperate script that runs after your installation to commit the HKCU to all users on the machine by loading all ntuser.dat - writing the info and then unloading the ntuser.dat --- (leaving them loaded will cause log on problems)

I use the active setup method and I have no problems with my HKCU
Answered 09/19/2006 by: gmorgan618
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity