The package execution order allows you to manage the order in which packages are executed on computers.
When packages are added to the Configuration Database they are given a default execution order. You can change the order for any package as long as the change does not violate the package order rules.
The package execution order rules are defined in this order:
|
Rules |
Description |
|
Dependencies |
First, the package execution order is determined by the package dependencies. For example, if package B is dependent on package A, then package B will always execute after package A. Package dependencies, including class dependencies, cannot be broken when determining the package order. |
|
Package Type |
Second, if package dependencies do not define a package execution order, then the packages are executed according to package type. System packages are ordered first, and all remaining packages, regardless of type, are ordered later. |
|
Alphabetical Order |
Third, if package dependencies and package type do not define a package execution order, then the packages are executed by alphabetical order. |
In the Package Execution Order dialog box you must explicitly lock the Package Depot from other administrators, then you can manage the package order by moving packages to a different order and setting package execution properties. You can view the order that is allowed and not allowed for each package based on the above package execution order rules.
Administrators must have the Manage Packages permission as part of their Administrator Role in order to modify the package ordering.
When packages are uninstalled from computers, they are uninstalled in the reverse order in which they were installed. For example, if package A, B, and C were installed in that order (A, then B, then C), then they will be uninstalled in the order C, then B, then A.
How to...
Set the Package Execution Order