Hi Guys

In the environment I am in they are using SMS 2003 for Software installation and BigFix for patching, (don't ask!). On building a workstation I would like SMS to install all the other applications and then install the BigFix client last, which will in turn start patching the newly built machine.

I know you can make dependencies of packages in SMS.
That will not work for this scenario as it must install last, no matter what applications are created in the future.

It seems there are lots of ways of controlling priority for WAN related traffic, e.g. priority of sending packages to DP's etc, but nothing obvious for saying the order of installing the apps to the desktop ?

Does anyone have any ideas on:

A) How to make one package always last to install ?
B) How the package installation sequence is controlled ?

(e.g. If there are 100 packages, what order do they hit the desktop in, is it the advertisement creation date ?)

Any help would be much appreciated.

0 Comments   [ + ] Show 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.


With SMS you can do either

Sending priority
The priority of this package when sent to distribution points in child sites. Packages can be sent with High, Medium, or Low priority. The default setting is Medium priority.
If a package has High priority, it will be sent before packages with Medium or Low priority. If a package has Low priority, it will be sent after packages with higher priority settings.


Create a Criteria for the Installation of a Package, and run another program first.
This can be done using the Advanced tag in the Properties of your SMS Package

But a Package will be sent in the order in which they were created in the SMS Administrator console.
Answered 05/15/2006 by: cookie
Yellow Belt

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