The following requirements must be met before creating and sending Desktop Application Distributions using Tiered Electronic Distribution:
- Desktop Application Distributions can be sent to only NetWare and Windows servers. This Distribution type is not supported on Linux and Solaris servers.
- In order to use Novell Application Management with ZENworks for Servers 3.0.2, you must have ZENworks for Desktops 3.x or 4.01 installed. However, chained applications in Desktop Application Distributions are only supported in ZENworks for Desktops 4.01 and later.
- For Windows NT/2000 servers that have eDirectory installed on them, to be able to send a Desktop Application Distribution to these servers you must install Policy and Distribution Services by browsing for the server object in the eDirectory listing, not by browsing for the computer object in the Microsoft* domains listing.
- ZfD and ZfS 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 ZfS and ZfD 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 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.
- Under some circumstances, you might receive a Java Out of Memory error when a Desktop Application Distribution is extracted. To prevent this, edit the ted.ncf file on the Subscriber server and change the memory variable on the last line from 128 to 256. Then the Distribution should extract. However, this treats the symptom and not the cause, which you might eventually need to resolve.