Extent of Source Application at Destination

In ZENworks^® Desktop Management you can create Application objects for applications that you want distributed to users and workstations using Novell^® Application Launcher^TM. The source application object is known as the "golden" application and the object created from the Desktop Application Distribution is known as the "distributed" application.

On this wizard page, you can determine whether to create the distributed Application object in a unique target location in the tree, or mirror the golden Application object's tree structure at the destination location in the tree.

Source Tree Structure
Choose whether to maintain the source tree information in the Distribution object:

Maintain the Source Tree Structure
Select this option to duplicate the source tree's structure at the destination's location (the target Subscriber's working context) for placing the distributed Application objects. If you are selecting chained applications, you must select this option.

Source Root Container
Select a container to be used as the root container for the golden Application objects to be distributed. You should select golden Application objects only from this root container and its subordinate containers.

Maintain Associations
Select this option to distribute the associated groups or containers at the target location if they do not exist. However, users or workstations contained in the groups or containers in the source location are not distributed.

You must enable this option if you have chained applications in the Distribution.

IMPORTANT: Rights previously set in the associated user/workstation groups or containers that are maintained are not distributed, but set to the minimum necessary in the distributed groups or containers so that users can use the applications.

Overwrite Existing Target Folder Object Attributes
When selected, this check box causes existing target folder objects to be overwritten with the relevant content of the source folder objects, meaning all previous folder associations for the application are replaced by the new folder associations. (This was the default function in previous versions of ZENworks for how folder objects were handled.)

To retain previous folder associations while adding new ones, deselect this option.

Always Replicate Association Flags
Causes the launch configuration flags for each group or container associated with the golden Application object to be replicated with each distributed application.

Load Balance and Fault Tolerance Support
Choose whether to use automated load balancing, fault tolerance, or neither:

Load Balance
Select this option to automatically spread server workloads over the servers being used for the Desktop Application Distributions. The functionality of fault tolerance (redundancy) is automatically accomplished through load balancing.

Fault Tolerance
Select this option to allow a server being used for Desktop Application Distributions to assume the distribution duties of another server that goes down. Fault Tolerance does not provide load balancing.

None
Select this option to apply neither option. You must individually configure each distributed Application object for load balancing or fault tolerance, if you want that support on an individual basis.

For these two features to work:

• Multiple Subscribers receiving the Distribution must be using the same working context
• The User Source List button must be selected on the Fault Tolerance > Fault Tolerance or the Fault Tolerance > Load Balancing properties page of the Application object

Depending on the selected options, the Load Balancing or Fault Tolerance pages are populated with the file locations on all servers that share this working context.

Rebuild Distribution
Determine when to automatically rebuild a Desktop Application Distribution:

Rebuild Only If Any Application Version Number Changes
Allows you to control Distribution rebuilding based on the Build schedule. Select this check box to withhold modifications to a golden Application object until you are ready to release them.

Regardless of the status of this check box, if applications are added to or removed from the Distribution, it is rebuilt according to its Build schedule.

• Selecting the Check Box: This feature is useful for withholding modifications to a golden Application object until you are ready to release them.
  
  The Distribution is rebuilt according to its established Build schedule, but only after you have manually incremented the Version Number field in the golden Application object, or its dependent application, and the Distributor has read Novell eDirectory^TM to discover the change in the Version Number field.
  
  If there are multiple applications in a Distribution, a version number change in only one of them triggers a rebuild of the Distribution for all of them.
  
  The Version Number field is on the Distribution Options > Options tab of the Application object's properties.
  
  Regardless of the status of this check box, the Distribution is rebuilt according to its Build schedule if applications are added to or removed from the Distribution.
  
  See the ZENworks Desktop Management Administration Guide for information on how to manually change an application's version number.
  
  
• Leaving the Check Box Disabled: If you do not select this option (it is deselected by default), the Distribution is rebuilt according to its established Build schedule. In this case, there can be two scenarios:
  
  Modifying an Object: When you modify a Distribution object or one of its golden Application objects, its internal revision number is automatically changed, which triggers a rebuild of the Distribution according to its established Build schedule.
  
  Modifications include adding or removing applications from the Distribution. However, if you simply update, add, or remove application files in the Distributor server’s file system, this does not alter the internal revision number of the Desktop Application Distribution object. The ZENworks file synchronization feature does not apply to the files in Application objects. Therefore, no rebuild is triggered.
  
  If you add, remove, or update any files belonging to a golden Application object, those changes are included when the next rebuild is triggered.
  
  Removing a Distributed Application Object: Removing a distributed Application object causes a backlink to the golden Application object to change without any other changes being made to the object. This causes the internal revision number to change on the golden Application object, which triggers a rebuild of its Distribution according to the established Build schedule.

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For more information, see Legal Notices.