That is allowing me to specify which DPs to service first.
As it is right now Distribution Manager / Package Transfer Manager might generate the requests for the Pull DPs prior to copying contents to the source DPs.
NOTE: Not sent in status message by Software Distribution, but may be used by task sequence. This error code is returned to task sequence when there is no run request that is currently running, but task sequence tries to get the currently running request.
This program cannot run because it depends on another program that has not run successfully before.
For geographically dispersed hierarchies it can make good sense to optimize content distribution to the network topology.
Consider an environment where you have a fully meshed network (MPLS) and you have a primary in Europe and two remote offices in Asia, Bangkok and Hanoi.
This is error code indicates that an error was encountered while creating the internal execution context object.
The installation is initiated from distribution manager (see distmgr.log) When a package is assigned to a pull DP distribution manager will instruct package transfer manager to transfer the package.
The program cannot be run again from the client UI because it is already pending, an optional (initiated from the UI) run request already exists for it.
NOTE: This error code is only returned to the UI and is not present in status messages.
Another scenario would be to have a hierarchy spanning two locations.
In the “remote” location you wish to have two DPs for redundancy and performance.