In our organization we distribute all MSI packages through a portal solution from Altiris, and all the packages are running/installing as an account with administrator privileges since the users doesn't have local admin rights. Now i have a MSI package with a registry key that installs on HKEY_CURRENT_USER, in other words on the account that runs the package. I need to get this key to register on the user that is logged in as the key contains some vital information regarding license server. I've tried to put the key under HKEY_LOCAL_MACHINE but it seems it won't read the value there.

Is there any easy workaround to resolve this issue?
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
You can either use an advertised shortcut / self repair so that the CU keys get created for each user when they first run the app, or you can use Active Setup to deliver the CU keys when they logon. I'd only suggest Active Setup if the app has no shortcuts with which to invoke a repair though.

There will be literally hundreds of posts on here about this.

Regards,
Rob.
Answered 03/24/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Can you set the install to run as the Local System account? Then have the job run only when a user is logged in. That would get you the correct current user, and the system account will be able to place the key, since it has full rights.

On a machine that has multiple users, you would need to run it once for each logged in user.

Hope this helps!
Answered 03/24/2010 by: FunWithApps
Senior Yellow Belt

Please log in to comment
0
Thanks for your quick replies.

I've just read about Active Setup on [url=http://wisepackager.com/KJ/Active_Setup_and_how_to_implement_it.txt]this page[/url] and if i understand it correctly i need to create a separate MSI file that contains the registry key i want to set for each user when they log on?
Answered 03/25/2010 by: RS|Stian
Orange Belt

Please log in to comment
0
No you add the HKLM reg entries to your existing MSI.

The active setup command line would them typically be msiexec /fu {MSI_productcode} /qb to repair current user entries for each user the first time they logon.

More AS info here:

http://www.etlengineering.com/installer/activesetup.txt
http://wikidesktop.org/index.php?title=Active_Setup

Regards,
Rob.
Answered 03/25/2010 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Remember that AS doesn't get healed/self-repaired. It's a one-time-only "install". If you want to be sure that user profile stuff is present, go the advertised entry-point route. Search John McFadyen's blog on Windows Live for details on healing/self-repair.
Answered 03/25/2010 by: VBScab
Red Belt

Please log in to comment
0
Active Setup worked like a charm. Many thanks for all your help, much appreciated [:)]
Answered 03/25/2010 by: RS|Stian
Orange Belt

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