Hi guys.

Ok not sure if there is a solution for this.

I am using SMS 2003 to push apps out through the state restore phase.

The state restore phase is installing the apps in the order i want them to , lets just say package A, B, C, D, E, F, G, H, etc etc

On most of my packages i am using the /fup to force a repair when the machine logs in , but what is happening is that the apps are not repairing in the order of install.

Lets just say it is package A, C, F, G, B etc

Any ideas as to how i can get them to do this on the order of install?

Many thanks
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


Well i'm guessing that when you say you are using /fup when the machine logs back in that you are talking about using Stubpath?

I believe the installations happen in alphanumerical(0 - F) order....

Create a command file(*.cmd), or vbs --- I would recommend vbs .... Which calls the msiexec /fup <GUID> /qb!(or /qn) in the order you want and just use one of the GUIDS to create the Active Setup Key, from there call that VBS script(or .CMD) ... This vbs and Active Setup key(values) would have to be installed via one of your installation packages.


You can call the vbs script from the RunEx registry and have the script check whether or not it was already run - i.e. via CU key/value

Hope this helps
Answered 08/29/2006 by: gmorgan618
Blue Belt

Please log in to comment