I have a key I want to have installed on all users computers.
The file contains a setting to a software that we wants as default (software: SAP GUI 7.20)
Im a newbie with creating MSI files and need your help.

The MSI file will only have the registry entry in it. no exe file or anything.
I hope thats not any problem?

If I understand it right, I need to have a Active Setup registry entry in my MSI package.
This entry will force the MSI package repair and give the user the rregistry on all new logons to the computer (also old ones that havent recived the registry setting before).

Im working with Wise Package Studio.

This is the setting for the user:


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SAP\SAPGUI Front\SAP Frontend Server\Customize]


And this is the Active Setup setting:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Active Setup\Installed Components\{167EADCA-13DC-4FE6-B5F8-31C164CD0A99}]


Install for Profile:
Per-machine installation

Reinstallation Options
File Replacement: Reinstall if file does not exist or existing version older

[ X ] Reinstall all per-user based registry keys
[ X ] Re-cache local copy of installation
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


A couple of pointers:

1) Make sure the MSI's ALLUSERS property is set to 1
2) Make your component with the HKCU keys, and indicate one of the values as a keypath
3) I dunno what that stubpath is that you have there, but what I would use is a commandline like msiexec.exe /fu <ProductCode of your MSI> /qn

Some additional remarks:

1) an MSI for just one regkey might be considered overkill, you could perhaps attain the same result with a vbscript and an active setup to trigger said script. Or through GPO and logon scripts..
2) if you are packaging SAP GUI at the same time, you might want to consider incorporating this registry key into the main SAP installation. Don't forget that while you might need a seperate package to propagate this change in the field for existing installs, you'll also probably want future SAP installs to contain this key natively.

Hope this helps,

Answered 10/07/2011 by: pjgeutjens
Red Belt

Please log in to comment