The following requirements must be met before creating and sending Desktop Application Distributions using Tiered Electronic Distribution:
IMPORTANT: If even one of your associations is outside the source root context, the Distributor fails to build the Distribution.
If the Package Source List box contains a local drive mapping, no application files are gathered or distributed.
If the Package Source List box contains a mapped drive, Keep the Same Source Paths for Replicated Objects must be selected. The drive letter is treated like a variable that needs to be resolved on both the Distributor and Subscriber to complete a valid UNC path.
Use a policy to define the variables on a Distributor. On the Subscriber you can use either the variable list in the Subscriber object, or a policy that is associated to the container where the Subscriber object resides.
Multiple Subscribers can use the same working context if you intend to use them for load balancing or fault tolerance.