How do you approach rolling out a program that is a series of .msi's that are called upon by a .exe? Also what if the install needs be run locally on the machine, what are my options for deployment. I use Wise and Desktop central if that helps. Thanks
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
I'd say, first of all, drop the exe.
if you need granular control over the different MSIs, get them out of the exe (I'm assuming it extracts them at some point during the installation)
Once you have these, write a script that copies over the MSIs to your target machines and then triggers them in order, with the required command line parameters.
Answered 05/11/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Thanks - I used a vbs script that called the msi's.
Answered 05/25/2010 by: BerkApp
Senior Yellow Belt

Please log in to comment
0
If the packages are inter-dependent, I hope your script checks the installed state of each package's "parent" before progressing.
Answered 05/25/2010 by: VBScab
Red Belt

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