The following requirements must be met before creating and sending Desktop Application Distributions using Tiered Electronic Distribution:
In order to use Novell Application Management with ZENworks 7 Server Management, you must have ZENworks for Desktops 4.01 or ZENworks 7 Desktop Management or later installed. Chained applications in Desktop Application Distributions are only supported in ZENworks for Desktops 4.01 and later.
Desktop Management and Server Management must both be installed to the same tree, including their respective schema extensions.
For golden Application objects to be functional in a Desktop Application Distribution, the snap-ins for both Server Management and Desktop Management must be installed in ConsoleOne.
Make sure all of the associations in the golden Application object are in the source root context or below.
IMPORTANT:If even one of your associations is outside the source root context, the Distributor fails to build the Distribution.
For Windows and Linux servers, you must have a shared location established for extracting the Distribution’s files, where all users can have access to those files.
The source path must point to application files that are located on the Distributor server’s file system, because the Distributor cannot gather files from other servers’ file systems.
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.
The Subscriber object must have the Working Context attribute defined. This is the eDirectory context where the Subscriber creates the objects related to the Desktop Application Distributions that it receives.
Multiple Subscribers can use the same working context if you intend to use them for load balancing or fault tolerance.
If extended characters (such as ê, ë, ì, or í) exist in the path to the .fil files for an AOT Application object, you must define a code page variable for the Distributor and Subscribers. For more information, see Extended Characters in Directory Paths.
Determine whether you are using Samba or NCP shares for client access to files on Linux or OES Linux servers, then set up that access. For more information, see Section G.0, Client Access in Linux.