I have a complicated client/server application that has a LOT of .msi files that are called by custom actions. I've tried to .MST what appeared to be the main one but it didn't add all of the components and also resulted in a 2717 WI error. I've tried creating a response transform which again gave limited success. I believe that I'll have to use the setup.exe file but would like to know how to call the msiexec.exe properties (/v) such as ALLUSERS=1, COMPANYNAME=ABC Company, etc. I am really uncertain of the syntax, quotes, etc. Thanks for your help!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
What is the application? Maybe we have had success with it?
Answered 03/19/2012 by: Roonerspism
Second Degree Brown Belt

Please log in to comment

Answers

0
u can check for setup.exe if any commandline parameters available with setup.exe -help or setup.exe /?
Answered 03/21/2012 by: mayur_mak
Senior Purple Belt

Please log in to comment
0
Have you seen this: http://www.itninja.com/blog/view/installshield-setup-silent-installation-switches
Answered 03/19/2012 by: bkelly
Red Belt

Please log in to comment
0
For silent install check to see what's available using /? or /help and other properties you might want to use this for a reference:
C:\PATHTO\Setup.exe /unattended=true /allowShutdown=false /add="FaxUtil,FaxCtrl..etc" /Server="your-server-name"

AK
Answered 03/19/2012 by: 786_ak
Second Degree Green Belt

Please log in to comment
0
Hi

As roonerspism said, what is the application?

How many MSI's are we talking I would normally just apply transforms to each of them as they are most likely to be different components, if there is nothing you need to configure in the msi's do as 786_ak said and see what switches you can run on the setup.exe

spef
Application packaging tips comming to www.spefdata.com
Answered 03/20/2012 by: Spef
Orange Senior Belt

Please log in to comment
0
Why are you calling MSIs via CAs in another MSI? Nested MSIs are A Really Bad Idea (think patching...upgrades)

If the deployment system you're using can call one MSI, surely it can call a sequence of them? Hell, even Group Policy can do that!
Answered 03/20/2012 by: VBScab
Red Belt

Please log in to comment
0
Or check the vendor's documentation or contact the vendor directly. If this is an "in house" app, see what VBScab said and get the developers to fix the app. Lastly, if neither are available, you could try to dig through the CA's and see if you can find the actions for each of the MSI's. The problem will be (among others) that you really won't know exactly what the setup.exe is doing.
Answered 03/20/2012 by: jmaclaurin
Third Degree Blue Belt

  • I've done that in the past - it can be a real pain in the neck if there are more than 3-4 nexted MSIs. But it does take control back over an install.
Please log in to comment
Answer this question or Comment on this question for clarity