The Associations tab includes only one page. This page lets you associate the Application object with users and workstations.
The Associations property page is available on Application objects created for all application types (simple, AOT/AXT, MSI, Web, and terminal server).
The Associations property page, shown below, lets you associate the Application object with the users and workstations to which you want the application distributed.
You can associate the Application object with individual users or workstations by selecting the appropriate User or Workstation objects. You can also associate it with groups of users or workstations by selecting Group, Workstation Group, Organizational Unit, Organization, and Country objects.
NOTE:Associating an Application object with a Group, Workstation Group, or other container object is the preferred method of associating the Application object in eDirectory. Associating the application to a large number of User or Workstation objects (for example, more than 250) might cause increased server utilization.
Although you are not restricted from associating Application objects with Alias objects, do not do so; Alias objects are not a supported object for associations.
Figure 48-24 Application Object > Associations Tab > Associations Page
The
list displays the objects associated with the Application object and lets you add or delete objects.To associate an object with the Application object, click
, browse and select the object, then click . All objects receive the default characteristics ( , , , , , , ) selected in the list. After you add an object to the list, you can modify its characteristics by selecting or deselecting the appropriate check boxes.To disassociate an object from the Application object, select the object in the
list, then click .When you add an object to the Associations list, the object receives the default characteristics selected in this box. The characteristics determine the locations (App Launcher, Start Menu, Desktop, System Tray, and Quick Launch) where the Application object’s icon are displayed and the actions (
and ) that are performed on the application. If you change the characteristics that are selected, any objects you add after that receive the new characteristics.Automatically runs the application. With a user-associated application, the application is run immediately after Application Launcher starts. With a workstation-associated application, the application is run immediately after the workstation starts up (initial startup or reboot).
You can use the
option in conjunction with several other settings to achieve unique behaviors. For example, if you use the option with the option ( tab > page), as soon as the Application object is distributed it is run one time and then removed from the workstation. Or, suppose that you want to run the Application object immediately one time at a pre-determined time. If so, select , select the option on the page tab), and define a schedule using the page ( tab).If you want to force run several applications in a specific order, mark each of them as
. Then give each Application object a numeric order by using the option on the page ( tab).IMPORTANT:When using the .msi files reside. Otherwise, the distribution and subsequent forced running of the application fails.
option for an MSI application associated with a workstation, you must also turn on the option ( tab > page) and assign the workstation the appropriate file system rights to access the network location where the sourceIf an application requires a reboot during installation, you must select
or in the group box and in the group box.Adds the Application object’s icon to the Application Window, the Application Explorer window, and the Application Browser window.
If the workstation is running Application Explorer, this option adds the Application object to the Windows Start menu. The Application object is added to the top of the Start menu, unless you assign the Application object to a folder and use the folder structure on the Start menu. See the Application object’s Folders page (
tab).If the workstation is running Application Explorer, this option displays the Application object’s icon on the Windows desktop.
If the workstation is running Application Explorer, this option displays the Application object’s icon in the Windows system tray.
If the workstation is running Application Explorer, this option displays the Application object’s icon on the Windows Quick Launch bar.
This option applies only if the Application object is marked as disconnectable (
tab > page).Without Section 39.0, Users: Supporting Disconnected Users.
enabled, users can launch the application while in disconnected mode as long as the application has already been distributed (installed) to the workstation. With enabled, Application Launcher automatically copies the application source files and other files required for distribution to the workstations cache directory. The user can then install or repair the application while disconnected from Novell eDirectory. The files are compressed to save space on the workstation's local drive. For more information about caching applications, seeWhen distributing an MSI application, you must use the .msi files. The Microsoft Windows Installer requires file access that is provided by a network client but not by the ZENworks Desktop Management Agent. Consider the following examples:
option if users or workstations do not have network client access to the sourceUsers outside your firewall need an MSI application but have no network client access to the source .msi files on a server inside your firewall. They log in to the ZENworks Middle Tier Server and Application Launcher displays the MSI application. For successful distribution to occur, the MSI application must be marked as so that the source .msi files are copied to the user's cache directory (through the Middle Tier Server) and then distributed from the cache directory.
Users inside your firewall need an MSI application. They don't have the Novell Client installed, so they log in to the ZENworks Middle Tier Server to authenticate to eDirectory. The users are part of an Active Directory domain, and the source .msi files are located on a Windows share that they have rights to. The distribution succeeds without force caching the application because the Microsoft network client provides file access to the source .msi files.