To create the Application object in eDirectory™ and configure it:

1. In ConsoleOne®, right-click the container where you want to create the Application object, click New, then click Application to display the New Application Object dialog box.

   

2. In the New Application Object dialog box, select the Terminal server application option, then click Next.

3. Specify a name for the Application object.

   The Application object’s name must conform to the following rules:

   • The name must be unique in the container.

   • The following special characters are invalid in Application object names, Windows folder, and file names and are not allowed even if they are preceded by a backslash (\):

     / : * ? " < > | period (.)
     

   • Uppercase and lowercase letters, as well as underscores and spaces, are displayed as you first entered them, but they aren’t distinguished. For example, ZENworks_Desktop_Management and ZENWORKS DESKTOP MANAGEMENT are considered identical.

   The Application object's name is visible in eDirectory. By default, the name is also used as the Application object’s icon title when displayed by Application Launcher on a user’s workstation. You can, if necessary, change the icon title after the Application object has been created (Application object > Identification tab > Icon page).

4. Click Next, then fill in the following information to configure the terminal server client session in which the application runs.

   ICa session: Select this option if the terminal server requires the application to run in an ICA (Independent Computing Architecture) client session. Citrix MetaFrame requires ICA client sessions. Fill in the following fields:

   • Published application name: By default, this field is populated with the Application object name you previously entered. If the name does not match the application name exactly as it is defined in Citrix, change the name to the Citrix published application name.

   • Servers hosting this application: Add the Citrix servers that host the application. To add a server, click the Add button, specify the server's IP address or hostname, then click OK.

     The server's you define here are used only when the application is launched from Application Launcher or the NAL plug-in. The ZENworks Launch gadget uses the servers defined in its configuration settings. For information about the ZENworks Launch gadget's configuration settings, seeSection 26.0, ZENworks Launch Gadget: Configuring Settings.

   RDP session: Select this option if the terminal server requires the application to run in an RDP (Remote Desktop Protocol) client session. Microsoft Windows Terminal Server requires RDP client sessions.

   • Terminal server address and port: Specify the terminal server's IP address or hostname. If the terminal server is not using default port 3389, edit the Port field to specify the correct port number.

   • Server domain: If the terminal server is part of a Windows NT domain or an Active Directory domain, specify the domain name. If the user's eDirectory username and password match the domain username and password, the user is not prompted to log in to the server when the RDP session is initiated.

   • Application path: Specify the path to the application's executable file. If you are running ConsoleOne on the terminal server, you can browse for and select the file.

   • Working directory: Specify the path to the directory you want the application to use for its working files.

5. Click Next, then define the rules used by Application Launcher to determine if a workstation meets the requirements for the application.

   The distribution rules ensure that Application Launcher does not distribute the application to workstations that cannot support the application. For example, if the application runs on Windows 2000/XP only, you can create an operating system rule that prohibits distribution to Windows 98 workstations.

   NOTE:The requirement for an operating system to be defined before an application is available has been removed.

   In previous ZENworks versions, an OS platform had to be defined in the System Requirements before an application would be available for distribution and launching. This requirement has been removed.

   The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

   To add a distribution rule:

   1. Click Add, then select the type of rule you want to define.

   2. Fill in the information for the requirement (click Help for information about the requirement or refer to Distribution Rules Page), then click OK to add the requirement to the list.

      If you want to create additional distribution rules for the application at a later time, you can use the Distribution Rules page on the Application object. For information, see Distribution Rules Page.

6. Click Next, then associate the Application object with the users or workstations that you want to distribute the application to. To do so:

   1. Click Add, then browse for and select User or Workstation objects.

      Each workstation that you want to associate with applications must first be imported into eDirectory as a Workstation object. If a workstation with which you want to associate the application has not been imported as a Workstation object, see Section III, Automatic Workstation Import and Removal.

      You can also select Group objects, Workstation Group objects, and container objects (Organizational Unit, Organization, or Country). If you select a container object, you are given the choice of associating all the container's User and/or Workstation objects with the application.

      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.

      IMPORTANT:Do not associate the Application object with Alias objects. Alias objects are not supported.

   2. After you add the user or workstation to the list, select the appropriate check boxes for the user or workstation to set the characteristics (Force run, App Launcher, Start menu, Desktop, System tray, Quick launch, and Force cache) you want applied to the application. Click Help for a description of each of these characteristics, or refer to Associations Page.

      If you want to associate the application with additional users or workstations at a later time, you can use the Associations page on the Application object. For information, see Associations Page.

7. Click Next, review the Application object settings, then click Finish to create the Application object.