Hello All,

For deploying our software we use MSIEXEC for the installation. The msiexec command is,

msiexec.exe /I “test.msi” transforms=”test.mst” /q

After the install is completed it adds the path of install source to the system PATH environment.

To explain better,
1. I am installing from D:\Image\install path(Where test.msi is present) and my binaries to be installed are under D:\image\install\program files\Test.
2. Software gets installed at "c:\program files\Test".
3. After the install is complete source path "D:\image\install\Test\program files\Test" is getting added to the PATH environment variable along with the install path("c:\program files\Test"). This is causing some problem.

I would like to know why is source path getting added to PATH environment variable and what could be the problem. If anyone has faced the similar problem and was able to fix it. Please help me.

Thanks in advance.
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
Personally never had that happen to me..

What's in the environment table of the transformed MSI ?

Cheers,
Rob.
Answered 09/18/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
What are you using to package it?
In Windows Installer, the WriteEnvironment Strings standard action writes to your environment variables based on what is in your Environment Table.
If you want to remove this completely then remove the action from your sequence, and/or delete the entry in the Environment Table.
Answered 09/18/2009 by: smooochy
Orange Belt

Please log in to comment
0
Thanks for quick reply. We are using SMS.
Answered 09/18/2009 by: maker.rain1
Senior Yellow Belt

Please log in to comment
0
Well SMS is the deployment tool, for packaging you use Installshield, WISE, etc.
Just asking because if you use Installshield I could tell you where to look, but I'm not familiar with other packaging tools.
Answered 09/18/2009 by: smooochy
Orange Belt

Please log in to comment
0
Installshield is used for creating the install package. But for deployment SMS is used.
Answered 09/18/2009 by: maker.rain1
Senior Yellow Belt

Please log in to comment
0
Okay well then in the buttons on the left-hand side there should be a "Sequences and Custom Actions" selection, where the WriteEnvironmentStrings action should be listed.
Look for the Environment table in the Direct Editor.
Answered 09/18/2009 by: smooochy
Orange Belt

Please log in to comment
0
Thanks will try that.
Answered 09/18/2009 by: maker.rain1
Senior Yellow Belt

Please log in to comment
0
I checked the Environment table in the .mst file but i dont see anything that adds the additional path. Any other thing that could be causing the problem?

Thanks
Answered 09/18/2009 by: maker.rain1
Senior Yellow Belt

Please log in to comment
0
- A Custom Action?
- A direct addition to the registry? If it's a user-level variable, it'll be in HKCU\Environment. For machine-level, check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Answered 09/18/2009 by: VBScab
Red Belt

Please log in to comment
0
If it's a vendor MSI you might want to run through the custom actions, see if there's one that looks suspect.
I guess it could be injected straight into the registry too at [HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].

If this is a bust, combined with the tests already mentioned above, I think it's time to start looking to your SMS server as the possible culprit.

PJ
Answered 09/18/2009 by: pjgeutjens
Red Belt

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