Create msi with Paramater | Installshield Adminstudio
Hello,
I want to know if it is possible to create a msi with special parameters.
Background: I want to deploy RSA Software as package so far so good.
Now I have got 20 different VPN Konfigurations ; I want to create a msi package that includes an. .exe from RSA (Tokenimporter.exe) and the configurations.
How should it work:
1) Create Tokenimporter.msi
2) Run it with Tokenimporter.msi /config=1
/config=1 is for setting VPN setting one .
3) The package should then run: TokenImporter -f “c:\RSA SecurID\Token Files\Config1.sdtidâ€Â
How can I add own Parameters to an msi for this?
Thanks a lot!
Wolfgang
I want to know if it is possible to create a msi with special parameters.
Background: I want to deploy RSA Software as package so far so good.
Now I have got 20 different VPN Konfigurations ; I want to create a msi package that includes an. .exe from RSA (Tokenimporter.exe) and the configurations.
How should it work:
1) Create Tokenimporter.msi
2) Run it with Tokenimporter.msi /config=1
/config=1 is for setting VPN setting one .
3) The package should then run: TokenImporter -f “c:\RSA SecurID\Token Files\Config1.sdtidâ€Â
How can I add own Parameters to an msi for this?
Thanks a lot!
Wolfgang
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
aogilmor
15 years ago
Wolfgang,
Properties are what you're interested in, and can be used in pretty much the same way as the parameters you're talking about, minus the "/" character. Simply set your public property (e.g.CONFIG=1 ) at the command line, giving it the value you want for it to install the correct file.
As for the action I think you're looking at a Type 18 since you're installing the EXE with the MSI.
You'll need to put each config file in its own component and condition the component's installation on the value of the CONFIG property. (e.g. CONFIG=2 would install the second config file etc.)
I don't have Installshield-specific knowledge, but it should work the same way as in Wise (where I've found it necessary to put config files of this sort into their own components, as Wise only does this automatically with EXE, DLL and OCX files, and sometimes it's inconsistent even with those). This is where it's useful to have "under the hood" knowledge of Windows Installer to get your desired results. I'm sure many posters here have worked with Installshield, maybe they can help with the steps. Best regards and welcome.
Owen
Properties are what you're interested in, and can be used in pretty much the same way as the parameters you're talking about, minus the "/" character. Simply set your public property (e.g.CONFIG=1 ) at the command line, giving it the value you want for it to install the correct file.
As for the action I think you're looking at a Type 18 since you're installing the EXE with the MSI.
You'll need to put each config file in its own component and condition the component's installation on the value of the CONFIG property. (e.g. CONFIG=2 would install the second config file etc.)
I don't have Installshield-specific knowledge, but it should work the same way as in Wise (where I've found it necessary to put config files of this sort into their own components, as Wise only does this automatically with EXE, DLL and OCX files, and sometimes it's inconsistent even with those). This is where it's useful to have "under the hood" knowledge of Windows Installer to get your desired results. I'm sure many posters here have worked with Installshield, maybe they can help with the steps. Best regards and welcome.
Owen
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
