cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Nested Installation with 2 msi & 2 MST?

What is the prefered method of installing msi which are getting installed one after other ?

Thanks a lot in advance
skj
(5) Replies
From a setup developers point of view this is typically handled by a bootstrapper. From a network administrators perspective it can be done through `chaining` using your distribution tool. For example, SMS 2003 can create an advertisement where one package depends on another so they will run in a sequence. This can actually be better then rolling a bootstrapper since you have more control over the deployment process. ( In a bootstrapper scenario everything is in one package and gets distributed to the machine for execution. If some of the packages are not needed they are skipped. In an SMS scenario SMS already knows which ones are needed and skips the distribution. )
Tried to get SMS to deploy one package before another, but SMS only deploys the one app.

Tried to package 2 apps into one .msi with Admin Studio by specifiying "edit setup list" in the Repackaging Wizard, but it just goes on to create on .msi from only the .exe specified in the list only....that's it.

What gives? How do I get out of this jam?
I know SMS will deploy multiple apps in a single advertisement. You just chain the package/programs and then create an advertisement that includes the LAST program. This way when the program runs it'll walk the tree backwards and then start forward installing programs.

You'll get very nice status messages in your advertisement report showing each package being downloaded and executed.
Adding as Chris's has mentioned, you can create a simple .bat and/or .cmd file referencing for the msi(s) and put that .bat/.cmd into the SMS package advertisement.
You can, but you don't get nearly as much flow control and reporting as you do with package chaining.