First off, please excuse my very jr. knowledge of packaging. Here's my issue. We have several applications in our environment that need to write to HKCU during installation. The issue is we deploy using the service account using Computer Associates Desktop & Server Mgmt software. What I have been told is that we cannot access the regular user of that machine's HKCU registry using the service account during deployment. Could anyone please shed some light on this issue, does this make sense to you, and if you have experience with it, what you have done to work around this issue?

Thank you for any help you can provide.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


If you think about your question for a moment, the problem (if not the answer) should be immediately apparent: the System account has no way of knowing who the currently logged-on user is, particularly if there is NO user logged in at deployment time.

The answer depends on what you want to do in HKCU but, in general, you'll probably want to take a look at either using Active Setup or creating a 'CurrentUser' feature which contains one of the package's main features as a child.. AS is too lengthy a topic to go into here: use the forum's Search facility or Google for 'deployment +"Active Setup"'. Similarly, a search for 'CurrentUser' will turn up lots of useful advice.
Answered 02/06/2008 by: VBScab
Red Belt

Please log in to comment
If you know that the deployment will happen when a user is logged in then I can provide you with a WMI script that will take the currently logged in user and domain and add it to an array which you can then add to an MSI property or add the additonal code into the script to add the HKCU keys during the scripts run.

Answered 02/06/2008 by: Inabus
Second Degree Green Belt

Please log in to comment