Hi All,

I have re-packaged an application (SAP GUI 6.2) which requires an environmental variable (EnVar) be set, which I set within the MSI. This works fine once the user has launched the app (thereby installing it) and logged out and back in. But because the package is user assigned and comes as an advertised install - the EnVar doesn't set itself until the user logs off and logs on, which is when Windows reads its EnVars. The program install perfectly when the user launches the advertised shortcut, but the EnVar doesn't get set until the user logs off and back on. So I tried the following at the command line:
but even though it shows as being set (when I type SET at a command prompt), the application doesn't (resolve?) the EnVar. So I have two questions:
Does anyone know how to instantly set a User Environmental Variable so that it will resolve for the user right away?
If so, am I on the correct path in thinking that I can create a Custom Action that will set this right away, thereby doing away with the current need for the user to logoff and back on for the EnVar to set?

Any help here would be very appreciated.
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


Hmm whenever I've set Environment Variables within an MSI they take effect immediately...

Presuming you using the Environment Table to create them - ensure you have the correct prefixes in the name column (e.g. * for a W2k or XP variable / = to create and set during install / - to remove on uninstall etc)

Check out the SDK for all the options...

Hope this helps,
Answered 05/25/2006 by: MSIPackager
Third Degree Black Belt

Please log in to comment
Thanks MSIPackager, you sent me on the right path. What ended up working for me was changing the value in the Environment table for my Environment Variable from:

Which I guess forced Installer to determine the path of the APPDATA property before writing it into the user Enviroment Variables and voila, it worked. Whereas before it was just putting the plain old verbatim text of %APPDATA%\SAP\SAPLOGON.INI into the value of the user's Environment Variable, which meant Windows had to resolve it - which only seems to happen when Windows starts.

Thanks again - you got me looking in the right spot.

Answered 05/25/2006 by: fosteky
Purple Belt

Please log in to comment