I am looking for a way to "chain" the installation of 3 applications so that once one is finished installing, number 2 begins and then number 3 begins when number 2 is done. Does anyone have any suggestions?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


The First suggestion would of course be DO NOT DO IT!
That being said I understand that there are sometimes good reasons to play Russian Roulette with a fully loaded Gun.

I have done just such a thing a few times.

I have found that the best method is to run the installations from a controlling executable.

Compiled WinBatch was the easiest with its native "RunWaite" function.

I have also done it in VB, but handling the run thread completion can be cumbersome.

Answered 02/23/2004 by: Robo Scripter
Orange Senior Belt

Please log in to comment
Ok, thank you. I will give that a shot!
Answered 02/23/2004 by: joshua
Yellow Belt

Please log in to comment
I'm not sure why Robo Scripter has a problem with chaining MSIs. We use long chains of applications in our post-deployment scripts (unique business units and machine types) and include scores of MSI's as well as other scripted apps. There are over 1600 machines with our post-deployment image on them and we're unaware of any chained MSI's causing problems. You just need to test your process thoroughly to ensure that they don't step on each other.
Answered 03/09/2004 by: mcquitp
Senior Yellow Belt

Please log in to comment
Chaining MSI installs is no big deal AS LONG AS:

1) each MSI install happens seperately - otherwise you will get errors saying that the installer service is already in use.

2) none of the MSIs requires a reboot. Even if you set REBOOT to ReallySupress, if one of your MSIs requires a reboot, the installer service will NOT allow any additonal MSIs to be installed until the system has been rebooted.

An exception to this: SMS can deploy multiple MSIs, even ones requiring reboot, as long as SMS has been told to reboot when all pending jobs have been pushed.
Answered 08/02/2004 by: sean_c_roberts
Senior Purple Belt

Please log in to comment