Change InstallDir location through WPS
Hi all
I'm creating an msi for one software call ADAM. This software require client machine to run the .exe file on the Server through an mapped network drive. The short cut has Target is O:\Adam\achper.exe and Start in have to be O:\ADAM. But well i take a second snapshot and deploy it through GPO, in "Start in" change from O:\ADAM to C:\ADAM. I open the package through Wise and in Directory table i saw the InstallDir = ADAM. I change it to O:\ADAM and save it. But then i'm not able to push it out through GPO due to error.
I really need help on how to change that Directory location from C:\Adam to O:\Adam through Wise Package Studio.
My O:\ was mapped to \\Server\Shared\
Thanks in advance.
Enz
I'm creating an msi for one software call ADAM. This software require client machine to run the .exe file on the Server through an mapped network drive. The short cut has Target is O:\Adam\achper.exe and Start in have to be O:\ADAM. But well i take a second snapshot and deploy it through GPO, in "Start in" change from O:\ADAM to C:\ADAM. I open the package through Wise and in Directory table i saw the InstallDir = ADAM. I change it to O:\ADAM and save it. But then i'm not able to push it out through GPO due to error.
I really need help on how to change that Directory location from C:\Adam to O:\Adam through Wise Package Studio.
My O:\ was mapped to \\Server\Shared\
Thanks in advance.
Enz
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
AngelD
16 years ago
Try
If NOT Installed then
Run WiseScript From Installation [WiseCustomActionPath] InstallScript.exe (Action)
End
If REMOVE~="ALL" then
Run WiseScript From Installation [WiseCustomActionPath] UninstallScript.exe (Action)
End
If NOT Installed then
Run WiseScript From Installation [WiseCustomActionPath] InstallScript.exe (Action)
End
If REMOVE~="ALL" then
Run WiseScript From Installation [WiseCustomActionPath] UninstallScript.exe (Action)
End
Posted by:
anonymous_9363
16 years ago
You can't use drive letters in INSTALLDIR for starters. Use a script Custom Action to create your shortcut (search the archive for a sample) or simply copy the shortcut as a file.
Posted by:
AngelD
16 years ago
Or create a vbscript and install it with the package, the shortcut should be pointed to execute the vbscript.
The vbscript will execute the network exe + set the working directory for whatever you want.
Make the shortcut advertised and you will get resilience for free on that shortcut.
The vbscript will execute the network exe + set the working directory for whatever you want.
Make the shortcut advertised and you will get resilience for free on that shortcut.
Posted by:
Mackan75
16 years ago
Hi Kim.
I usually create a property with the correct path to the exe-file and in this case one for the "start in" and modifies the Shortcut tabel with the properties.
Just of curiosity, do you se any problem with that?
/Mackan
I usually create a property with the correct path to the exe-file and in this case one for the "start in" and modifies the Shortcut tabel with the properties.
Just of curiosity, do you se any problem with that?
/Mackan
Posted by:
AngelD
16 years ago
Hi Marcus!
If I recall correct from previous experience [;)]
As the exe file is located on a network and when the shortcut is created by the CreateShortcuts action which is run in system context this account does not have network access or access to the mapped drives and will therefore fail.
For a local file using a property for the shortcut target should not be any problem except for that it will not create an advertised shortcut.
If I recall correct from previous experience [;)]
As the exe file is located on a network and when the shortcut is created by the CreateShortcuts action which is run in system context this account does not have network access or access to the mapped drives and will therefore fail.
For a local file using a property for the shortcut target should not be any problem except for that it will not create an advertised shortcut.
Posted by:
Mackan75
16 years ago
Ah! Good points.
First now (dammit) I saw that enzogoy deploys through GPO... I usually deploy with SMS 2003, and if I recall I usually sets the "program" to run "Only when a user is logged on" to get around the problem that you describes [:D].
/Mackan
First now (dammit) I saw that enzogoy deploys through GPO... I usually deploy with SMS 2003, and if I recall I usually sets the "program" to run "Only when a user is logged on" to get around the problem that you describes [:D].
/Mackan
Posted by:
enzogoy
16 years ago
Thank you very much for those quick responses and really show me the way to solve my problem. The shortcut is working now but i have a different problem. [;)]
It actually installs but when I uninstalled it, the shortcut still there. I get into the script where the installation sequence are and put this in:
If Installed then
Run WiseScript From Installation [WiseCustomActionPath] InstallScript.exe (Action)
End
If Uninstalled then
Run WiseScript From Installation [WiseCustomActionPath] UninstallScript.exe (Action)
End
But the above things didn't work at all. Not even install the shortcut. Did i do something wrong for the if statement?
enz
It actually installs but when I uninstalled it, the shortcut still there. I get into the script where the installation sequence are and put this in:
If Installed then
Run WiseScript From Installation [WiseCustomActionPath] InstallScript.exe (Action)
End
If Uninstalled then
Run WiseScript From Installation [WiseCustomActionPath] UninstallScript.exe (Action)
End
But the above things didn't work at all. Not even install the shortcut. Did i do something wrong for the if statement?
enz
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.