Installshield and MSIs
I am trying to install an app with the silent parameter for Installshield. It then refrences a MSI file as part of the install. Options given are /L Language, /S Silent and /V parameters to MsiExec.exe.
I'm assuming for the last param I should be doing something like this:
D:\Setup.exe /S /VD:\Install.msi /QB or D:\Setup.exe /S /Vi msiexec.exe D:\Install.msi /QB
None of the above working. Can someone help?
jprins
I'm assuming for the last param I should be doing something like this:
D:\Setup.exe /S /VD:\Install.msi /QB or D:\Setup.exe /S /Vi msiexec.exe D:\Install.msi /QB
None of the above working. Can someone help?
jprins
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
bkelly
20 years ago
I've actually seen InstallShield-wrapped installations offer these command line switches and then find that they don't seem to work. Your best bet is probably to separate the MSI from the wrapper. Run the setup and then look in your %temp% directory when the wizard is done "preparing the setup". You can copy these files out of temp and use them to address the MSI directly.
It should be that simple, but what happens quite often with InstallShield setups is that the MSI is wrapped in a setup for a reason- to ensure that the required version of the InstallShield Script Engine is installed before calling the MSI. What you would want to do then is take both the InstallShield Script Engine MSI and the application MSI and install them separately. However, InstallShield automatically builds in a dependency to the application MSI that it must be run by the setup.exe (so it can be sure it had a chance to verify the proper version of the InstallShield Script Engine). To get around this, you will then need to modify the application MSI to remove and/or bypass this. For details on the changes needed, see my tip "Getting Around MSI Packages That Require Setup.exe".
Not the quick answer you were hoping for, but this is the unfortunate solution. I've seen this with a growing number of applications (basically any one where the developer chose to make use of InstallScript). Please check for specific information (and post any of your own findings) in our Package Knoweldge base.
Good luck!
It should be that simple, but what happens quite often with InstallShield setups is that the MSI is wrapped in a setup for a reason- to ensure that the required version of the InstallShield Script Engine is installed before calling the MSI. What you would want to do then is take both the InstallShield Script Engine MSI and the application MSI and install them separately. However, InstallShield automatically builds in a dependency to the application MSI that it must be run by the setup.exe (so it can be sure it had a chance to verify the proper version of the InstallShield Script Engine). To get around this, you will then need to modify the application MSI to remove and/or bypass this. For details on the changes needed, see my tip "Getting Around MSI Packages That Require Setup.exe".
Not the quick answer you were hoping for, but this is the unfortunate solution. I've seen this with a growing number of applications (basically any one where the developer chose to make use of InstallScript). Please check for specific information (and post any of your own findings) in our Package Knoweldge base.
Good luck!
Posted by:
Alim
20 years ago
Why not try : msiexec /i D:\Install.msi /qb
the /i stands for install.
Regards
the /i stands for install.
Regards
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.