Welcome to Published Application Manager

Published Application Manager is the Citrix utility used to publish and maintain applications. Application publishing is a method of making specific applications available to ICA Client users as ICA connections. Published application ICA connections contain only the specified application in the ICA session and do not involve the ICA Client user in the mechanics of the Windows NT server environment hosting the session.

You can use Published Application Manager to configure applications that can be accessed by specific Windows NT users or anonymous users. If you have installed Citrix Load Balancing Services, you can configure applications that run on the least busy server in a group of servers.

Published Application Manager includes powerful ICA session configuring abilities with its support for server farms and Program Neighborhood.

You can create published applications that are automatically available to Program Neighborhood users, freeing them from client-side configuration of their ICA sessions. You can determine which applications a user sees in his or her Program Neighborhood and how those applications appear on the desktop.

Please see What's New in Published Application Manager for an introduction to Published Application Manager’s new features.


What's New in Published Application Manager

WinFrame 1.7 and MetaFrame 1.0 users familiar with the Citrix utility Application Configuration will find Published Application Manager to be an enhanced version of Application Configuration.

Published Application Manager includes the following new features:

Server Farms. A server farm is a group of Citrix servers that is managed as a single entity and that share some form of physical connection and a common base of user accounts. After you place your servers in a server farm, you can publish applications on servers in the farm for users in the common base of accounts.

Program Neighborhood. A Program Neighborhood is the user’s view of all the server farms and published applications to which he or she can connect. When a user starts Program Neighborhood, he or she automatically sees a list of pre-configured applications. This list contains each application accessible to his or her user name or user group.

Support for Citrix Installation Management Services. Citrix Installation Management Services is a Citrix server product that gives administrators the ability to perform remote, unattended installations of applications on Citrix servers. You can use Published Application Manager to publish an application enabled for Installation Management deployment. Publishing an Installation Management application installs the application on all configured servers.

Support for Citrix VideoFrame. Citrix VideoFrame is a Citrix server product that enables Citrix ICA Client devices to play videos stored on a VideoFrame server. You can use Published Application Manager to publish videos to ICA Client users throughout your enterprise.

See Also

Introduction to Server Farms


Joining a Server Farm

If a Citrix server is not a member of a farm, you can add it to a farm at any time.

1.	Start Published Application Manager on the machine you want to enter into a server farm. You can run Published Application Manager from the console or in an ICA session on the server.

2.	From the Configure menu, click Join or Create Server Farm.

3.	The Create or Join Citrix Server Farm wizard appears. Click Help in any screen of the wizard for additional help.

After joining a farm, you can begin to publish applications.

If the Citrix server contains applications published prior to becoming a member of the farm, you can migrate those applications.


Introduction to Server Farms

Citrix server farms provide you with a flexible and robust way of deploying applications to ICA Client users. Server farms let you centralize your control over the application deployment process by grouping Citrix servers into a single administrative unit. Citrix servers in a farm function together to make applications easily available to your ICA Client users.

Setting up a server farm requires little configuration. Published Application Manager includes a wizard that lets you individually enter servers into a farm. Once you place your server(s) in a farm, you do not have to perform any additional administrative duties related to administering the farm structure itself. The focus of farm administration is Published Application Manager’s main function: application publishing.

Published Application Manager’s server farm implementation is complemented on the client side of the ICA connection by Program Neighborhood. Program Neighborhood users benefit from the following features:

Program Neighborhood users find their applications automatically available without having to configure connections to Citrix servers. When you publish an application in a server farm, you manage both ends of the ICA connection. Client users need only authenticate themselves to the server farm to receive a list of all the applications you have published for their specific user account or user group.

Applications published for Program Neighborhood (or in a server farm) are pre-configured for such connection properties as session window size and colors and supported level of encryption, audio, and video.

When publishing an application you can opt to place a shortcut to the published application in the Start menu or on the desktop of the Program Neighborhood Client user’s client machine.

Although the applications you publish in a server farm include features usable only by Program Neighborhood, all ICA Clients can access these applications in the usual manner. Users of non-Program Neighborhood ICA Clients (Citrix ICA Win16 Client, Citrix ICA Client for DOS, Citrix ICA UNIX Client, Citrix ICA Mac Client, etc.) can connect to these applications by using ICA Client Remote Application Manager or Remote Application Manager-like interfaces or on the Internet or Intranet (in the case of the ICA Web Clients). These ICA Clients can also benefit from Program Neighborhood features by connecting to a published Program Neighborhood.


Changing Farm Membership

You can change server farm membership for individual servers using the Change Server Farm wizard. This wizard lets you move a server from its current farm to an existing or new farm. You cannot remove a server from a farm altogether.

Note

If the server whose membership you want to change has any load balanced applications with other servers in its current farm, you must remove the server from the list of servers configured for those applications before changing its membership. See Changing Configured Server List for more information.

1.	Make sure you are in the server farm management scope. (From the View menu, click Select Scope. In the dialog box that appears, click the Within a Citrix server farm radio button and then select the farm of which the server is a member in the Select a Citrix server farm pull-down list.)

2.	Make sure you are viewing the server whose membership you want to change. (From the View menu, click Select Server. In the dialog box that appears, select the server from the list and click OK. If the server does not immediately appear in the list, click Refresh Server List.)

3.	From the Configure menu, click Server Farm. The Server Farm Properties dialog box appears.

4.	Click Change Server Farm. The Change Server Farm wizard appears. Click Help in any screen of the wizard for additional help.


Creating a New Farm

You can create a new farm in one of two ways:

Start Published Application Manager on a Citrix server that is not a member of a farm. The first time you start Published Application Manager, the Create or Join Citrix Server Farm wizard appears. When asked to select a farm to join, specify a new farm name in the text field. If you choose to exit the wizard without joining a farm, the Create or Join Citrix Server Farm wizard can be accessed at a later time by clicking Join or Create Server Farm in the Configure menu.

Change the membership of a server from an existing farm to a new farm. Use the Change Server Farm wizard and when prompted, specify a new farm name instead of selecting an existing farm. See the procedure To change farm membership for information on starting the Change Server Farm wizard.


Selecting a Management Scope

The Select Scope menu option lets you switch between Published Application Manager’s two scopes of management: Citrix server farms and Windows NT domains.

In order to take advantage of the features of Program Neighborhood, you must publish and manage your applications within a Citrix server farm. If you have not yet defined a server farm, click Cancel to exit the wizard and follow the instructions in Creating a New Farm.

To select a scope of management

1.	From the View menu, click Select Scope. The Select Management Scope dialog box appears.

2.	To publish applications in a server farm, click Within a Citrix server farm. The Choose Server Farm panel appears in the bottom half of the dialog box. Select a server farm from the list.

To publish applications in a Windows NT domain context, click Using Only NT Domains. The Choose NT Domains panel appears in the bottom half of the dialog box. Select a single, multiple, or all displayed domains.

3.	Click OK. The Published Application Manager main window appears. The displayed applications are those hosted by server(s) in either the specified server farm or Windows NT domain(s).

You can now begin to edit existing applications or publish new ones. If you selected the server farm scope, all applications you publish will support Program Neighborhood features.


Selecting a Server

The currently displayed list of applications depends in part upon the servers being viewed. For example, if you are using the server farm scope of management to view all servers in a farm, the application list includes all applications published on the servers that make up the farm. If you are using the server farm scope of management to view a selected server in a farm, the application list includes only those applications published on that server.

To select a server

1.	From the View menu, click Select Server.

2.	In the Select Citrix Server dialog box, select the desired server from the list or select All Servers. You can also click the Filter Servers By button to narrow down the list of servers according to specifiable criteria. Click OK.

3.	The main window reappears displaying applications hosted by the specified server(s). The main window’s title bar displays the currently selected server or servers.


Filtering Servers

The currently displayed list of applications depends upon your management scope and the servers being viewed. For example, if you are using the server farm scope to view all servers in the farm, the application list includes all applications published on the servers that make up the farm.

Published Application Manager includes a filtering utility that lets you narrow your view of applications based upon certain specifiable criteria including server capabilities, supported encryption levels, and operating system type of the servers hosting the applications.

The criteria can be selected individually or in combination to produce a filtered server list. Filtered server lists show only applications that are hosted by servers that meet your specified requirements.

To filter servers

1.	From the View menu, click Select Server.

2.	In the Select Citrix Server dialog box, click Filter Servers By. The Filter Servers By dialog box appears. Select the criterion, or criteria, by which you want to filter your servers. For example, if you select Load Balancing and SecureICA, the applications displayed are those running on servers with SecureICA Services and Load Balancing Services installed.

3.	After selecting the desired capabilities and requirements, click OK. You are returned to the Select Citrix Server By dialog box. The servers in the list meet the specified criteria. Select an individual server or All Filtered Servers and click OK. When you return to Published Application Manager’s main window, the applications displayed are those that are hosted by servers that meet your requirements.

To remove filtering from your view

1.	From the View menu, click Select Server.

2.	In the Select Citrix Server dialog box, click Filter Servers By. The Filter Servers By dialog box appears. Deselect the criterion, or criteria, by which you filtered your servers.

3.	After deselecting all options, click OK. You are returned to the Select Citrix Server By dialog box. All servers in the farm or Windows NT domain are displayed. Select an individual server or All Servers and click OK.


Standard Published Applications

Published Application Manager includes the Windows NT domains scope of management to provide backward compatibility and interoperability with existing Citrix server installations (WinFrame 1.7 and MetaFrame 1.0) that contain existing published applications. Using Published Application Manager to publish applications in this scope results in applications that are not enabled for automatic configuration of Program Neighborhood Client sessions.

To publish a standard application

1.	Make sure you are in the Windows NT domains management scope. (From the View menu, click Select Scope. In the dialog box that appears, click the Using only NT Domains radio button and then select the domain on which the server is a member in the domain list.

2.	Make sure you are viewing the server on which you want to publish the application. (From the View menu, click Select Server. In the dialog box that appears, select the server from the list and click OK. If the server does not immediately appear in the list, click Refresh Server List.)

3.	From the Application menu, click New to start the New Application wizard. Click Help in any screen of the wizard for additional help.


Publishing an Application In a Server Farm

In order to publish an application in a server farm, the server or server that is to host the application must be a member of a farm. Make sure the server or servers is a member of a farm before attempting to publish the application. See Joining a Server Farm.

To publish an application in a server farm

1.	Make sure you are in the server farm management scope. (From the View menu, click Select Scope. In the dialog box that appears, click the Within a Citrix server farm radio button and then select the farm of which the server is a member in the Select a Citrix server farm pull-down list.)

2.	Make sure you are viewing the server on which you want to publish the application. (From the View menu, click Select Server. In the dialog box that appears, select the server from the list and click OK. If the server does not immediately appear in the list, click Refresh Server List.)

3.	From the Application menu, click New to start the New Application wizard. Click Help in any screen of the wizard for additional help.


Installation Management Services

Citrix Installation Management Services performs remote unattended installation of applications on Citrix servers. Using Installation Management Services, you can simultaneously install an out-of-the-box application on all Citrix servers on your network from a single point without manual intervention. You can install applications on servers regardless of their physical locations, network connection type, or individual hardware setup.

Installation Management uses three Citrix technologies to deploy application installations to Citrix servers:

Citrix Packager. An application that monitors application installation routines. The Packager monitors the changes that an application’s installation makes on a server, records those changes as installation commands in a script, and packages all application files for distribution to Citrix servers.

Citrix Installer. An application that runs on each of your Citrix servers. The Installer executes requests to install applications.

Published Application Manager enhancements. Installation Management includes enhancements to Published Application Manager that give it the ability to push application installations to your Citrix servers and also to uninstall those applications if necessary.

For procedural information on publishing an application packaged for Installation Management Services, see Publishing an Installation Management Application.


Publishing an Installation Management Application

Before publishing an application for deployment, you must package the application using the Citrix Packager. The resulting installation script and package for the application must be on a file server on your network.

The installation script and package for the application must be stored in the same directory on the file server and the file server must be accessible to all Citrix servers running Installation Management Services.

1.	Use the standard application publishing wizard to publish an Installation Management application. (From the Application menu, click New.) When you start the wizard, you are asked to select a default server for the application if you are currently viewing more than one server. Select any server in the farm or domain and proceed.

2.	Proceed through the wizard as usual until you reach the Define the Application screen. In the Command Line field, enter the full path and file name of the installation script for the application you want to install on your Citrix servers (installation scripts have a .wfs file extension); for example, \\Server-name\share-name\application-name\example.wfs.

Unless each of your Citrix servers contains a network drive of the same letter mapped to your file server’s share point for installation scripts, you must use only Universal Naming Convention (UNC) names when publishing an Installation Management application.

When running Published Application Manager on a MetaFrame server, you can click Browse to locate the file server that contains your installation script. In the Choose Application dialog box that appears, select Installation Scripts from the Files of type list box, and then locate and select the script.

When running Published Application Manager on a WinFrame server, you can click Browse and then Network to locate the file server that contains your installation script. In the Connect Network Drive dialog box, make sure you specify None in the Drive field (None is the last option in the Drive list) before locating the file server. Otherwise, the network resource is mapped to a drive letter, not a UNC name. In the Choose Application dialog box, select Installation Scripts from the Files of type list box, and then locate and select the script.

3.	Proceed through the wizard as usual until you reach the Add the Application to Citrix Servers screen. Click Filter Servers By. In the Filter Servers By… dialog box, check Installation Management. When this option is checked, the Citrix servers that appear in the Available list in the Add the Application to Citrix Servers screen are only those that have the Installer and a Citrix Installation Management Services license installed. Click OK. In the Available list, select the Citrix servers on which you want to install the application and click Add.


Citrix VideoFrame

Citrix VideoFrame is a Citrix server product that enables Citrix ICA Client devices to play videos stored on a VideoFrame server. Using VideoFrame, you can publish videos to ICA Client users throughout your enterprise.

Users play published videos the same way they launch published applications. When a user selects a published video in Program Neighborhood, the Program Neighborhood Client connects to one of the WinFrame or MetaFrame servers where the video was published. The client reads the location of the video from the .cvi file and then passes that location to the Windows Media Player, which launches the video.

Citrix VideoFrame uses three Citrix technologies to deploy videos to Citrix ICA Clients:

Citrix VideoFrame Server Service. A Windows NT Service that can be installed on a Windows NT Workstation or Server computer.

Citrix ICA Streaming Channels protocol (ISC). A set of network protocols designed to stream high-quality multimedia content to ICA Clients.

Citrix ICA Client enhancements. Supported Citrix ICA Clients include enhancements to allow playback of videos from an ICA session or Program Neighborhood.

You can publish videos only on servers in server farms (not servers administered using the Windows NT domains scope of management).

For procedural information on publishing videos, see Publishing a Video.


Publishing a Video

Before publishing a video, you must encode the video using the Citrix VideoFrame Encoder and then copy the .avi file to a VideoFrame server.

You can publish videos only on servers in server farms (not servers administered using the Windows NT domains scope of management).

1.	Use the standard application publishing wizard to publish a video. (From the Application menu, click New.) If you are viewing more than one server when you start the wizard, you are asked to select a default server for the video. Select any server in the farm. If necessary, change to the server farm management scope for the server farm in which you want to publish the video.

2.	Proceed through the wizard as usual until you reach the Define the Application screen. In the Command Line field, enter the full path and file name of the VideoFrame Information file (.cvi) for the video; for example, \\Server-name\share-name\example.cvi. The path must be in Universal Naming Convention (UNC) format.

When running Published Application Manager on a MetaFrame server, you can click Browse to locate the file server that contains your VideoFrame Information file. In the Choose Application dialog box that appears, select VideoFrame Information files from the Files of type list box, and then locate and select the .cvi file.

When running Published Application Manager on a WinFrame server, you can click Browse and then Network to locate the file server that contains your Citrix Video Information file. In the Connect Network Drive dialog box, make sure you specify None in the Drive field (None is the last option in the Drive list) before locating the file server. Otherwise, the network resource is mapped to a drive letter, not a UNC name. In the Choose Application dialog box, select VideoFrame Information files from the Files of type list box, and then locate and select the .cvi file.

3.	Proceed through the remainder of the wizard as usual.


Load Balancing Services Overview

Published Application Manager supports publishing of an application on multiple servers if Citrix Load Balancing Services is installed on those servers.

When a published application configured for multiple servers is launched, load balancing support selects which server will run the application based on server load. The ICA Client contacts the master browser, which maintains a list of servers configured to run the published application, to find the address of a server containing the published application. The master browser selects one of the servers based on load and returns the address of that server to the ICA Client.

You can tune how load balancing support calculates server load for each server in a load balancing server farm using the Load Balancing Administration utility.

See Publishing a Load Balanced Application for procedural information.


Publishing a Load Balanced Application

1.	Use the standard application publishing wizard to publish a load balanced application. (From the Application menu, click New.) When you start the wizard, you are asked to select a default server for the application if you are currently viewing more than one server. Select any server in the farm or domain and proceed.

2.	In the Add the Application to Citrix Servers screen of the wizard, you can specify multiple servers to run the session. If Load Balancing Services is not installed, only the current server is displayed in the Configured list and the Add button is unavailable.

3.	Use the Edit Configuration button in the Add the Application to Citrix Servers screen to individually specify command lines and working directories on servers that have the application installed in a directory structure that differs from the installation on the default server.

See Also

Load Balancing a Citrix Server Desktop


Load Balancing a Citrix Server Desktop

Publishing an application on multiple load balanced servers without specifying a working directory or command line for the application creates a load balanced Citrix server desktop. ICA Client users can connect to this type of published application and run any applications accessible from the desktop of the Citrix server.

To publish a load balancing Citrix server desktop

1.	Start the standard application publishing wizard. (From the Application menu, click New.) When you start the wizard, you are asked to select a default server for the application if you are currently viewing more than one server. Select any server in the farm or domain and proceed.

2.	In the Define the Application screen, leave the Command Line and Working Directory fields blank. An unspecified command line causes WinFrame servers to run Program Manager and MetaFrame servers to run Explorer.

3.	In the Add the Application to Citrix Servers screen of the wizard, you can specify multiple servers to run the session. If Load Balancing Services is not installed, only the current server is displayed in the Configured list and the Add button is unavailable.

If you do not have Load Balancing Services, you can still publish a Citrix server desktop by publishing without a specified command line and working directory. The published desktop runs on a single Citrix server.


Enabling and Disabling Published Applications

When you publish an application, it is enabled by default. Enabled applications are available to the users you specify in the New Application wizard. You can also temporarily disable your published applications. Disabling an application makes it unavailable until you re-enable it.

You can enable and disable applications:

Over which you have full administrative rights

Hosted by MetaFrame 1.8 or WinFrame 1.8 servers

To disable an application

Select the entry for the published application. From the Application menu, click Disable, or right-click an entry and click Disable.

To enable an application

Select the entry for the published application. From the Application menu, click Enable or right-click an entry and click Enable.


Changing Properties of Published Applications

The Properties dialog box for each application lets you edit the following settings:

Published application name

Program Neighborhood Client settings applied to this application when it is accessed by a Program Neighborhood Client (for applications created in the server farm management scope only)

Users allowed to access the published application

Servers configured to host the published application

To change the properties of a published application

Select the entry for the published application. From the Application menu, click Properties or right-click an entry and click Properties. Click Help in any tab of the Properties dialog box for additional help.

The properties of applications published for a Citrix server farm (or migrated into a server farm) cannot be edited when viewed from the Windows NT domains scope (all tabs in the dialog box are grayed-out). To edit the application, change your scope to the Citrix server farm scope. You must also have full administrative access to an application’s configuration information to edit its properties.

A lock appears over an application that you cannot copy, delete, or edit. For information about why an application is locked, right-click the application and click Properties in the context menu. In the Properties tab, click Why is this read-only?


Deleting Published Applications

Select the entry for the published application. From the Application menu, click Delete, or right-click an entry and click Delete.

Delete is available in the Application or context menu when you select an application over which you have full administrative rights.


Migrating Applications to a Server Farm

Applications created under the Windows NT domains management scope do not have Program Neighborhood capabilities. You can use the Server Farm Application Migration wizard to convert Windows NT domains published applications into server farm published applications. Migrating an application into a server farm makes the application Program Neighborhood capable. After migrating an application, you can edit the application’s properties to configure Program Neighborhood functions.

The server (or servers, in the case of a load balanced application) containing the published application(s) you want to migrate must already be a member of a farm before you can migrate its published applications. See Joining a Server Farm for information on how to join a server farm.

To migrate a published application

1.	Make sure you are in the server farm management scope. (From the View menu, click Select Scope. In the dialog box that appears, click the Within a Citrix server farm radio button. In the Select a Citrix server farm pull-down list, select the farm of which the server containing the published application to migrate is a member.)

2.	Make sure you are viewing the server that contains the published application you want to migrate. (From the View menu, click Select Server. In the dialog box that appears, select the server from the list and click OK. If the server does not immediately appear in the list, click Refresh Server List.)

3.	Select the published application in the main window and from the Application menu, click Migrate, or right-click the published application and click Migrate. The Server Farm Application Migration wizard appears. Click Help in any screen of the wizard for additional help.

After migrating an application, you can edit its properties to configure Program Neighborhood Client connection properties and requirements.


Write ICA File

The Write ICA File wizard provides a way of creating a connection object that you can distribute to ICA Client users or embed in a Web page. This wizard creates an ICA file based upon the currently selected published application. ICA Client users can execute the ICA file to connect to the specified server or published application.

The ICA file contains the following connection parameters:

Window resolution and color depth. The ICA Client uses the size and color attributes specified in the ICA file when connecting to the application or server. (If the resolution and color depth exceed the capabilities of the client hardware, the maximum size and color depth supported by the client is used instead.)

Encryption level. Level of encryption applied to the ICA session.

To start the Write ICA File wizard

Select the desired published application. From the Application menu, click Write ICA File, or right-click an entry and click Write ICA File. Click Help in any screen of the wizard for additional help.

The Write ICA File wizard prompts you to name the ICA file you create. Some Web browsers and servers cannot properly handle long file names or file names with embedded blanks or special characters. For best results, especially with 16-bit software, use FAT file names (8 characters or less, with no special characters or embedded blanks).


Write HTML File

The Write HTML File wizard creates a template Web page that ICA Client users can visit to connect to a specific published application. The Web page contains a reference to an ICA file. You can specify an existing ICA file or create a new file in the Write HTML File wizard. The Web page you create should be edited before use.

The Web page controls the following connection properties:

Embedded or launched sessions. You can create a page that embeds an ICA session (starts the session in the browser window) or launches an ICA session (starts the session in its own window).

ICA Client type. Create a page for the Citrix ICA ActiveX control/Netscape ICA plug-in or the Citrix ICA Java Client.

Window resolution and color depth. The ICA Client uses the size and color attributes specified in the ICA file when connecting to the application or server. (If the resolution and color depth exceed the capabilities of the client hardware, the maximum size and color depth supported by the client are used instead.)

Encryption level. Level of encryption applied to the ICA session. Also specified in the ICA file.

To start the Write HTML File wizard

Select the desired published application. From the Application menu, click Write HTML File, or right-click an entry and click Write HTML File. Click Help in any screen of the wizard for additional help.


Farm Requirements

When you use the server farms scope of management, you group your Citrix servers (MetaFrame 1.8 and WinFrame 1.8) into one or more server farms. When creating a server farm, keep the following in mind:

Common administrator’s rights. The individuals responsible for administration of a farm should have administrative rights over each server in the farm. When you log into a Citrix server console or ICA session and run Published Application Manager, you administer applications under the context of your current Windows NT user name. Although you can view the applications on other servers in the farm without having administrative rights over those servers, you cannot publish or edit applications on those servers. For this reason, users who run Published Application Manager to publish applications should make sure they have full administrative privileges (Read and Write access to the registry) on each server in the farm.

Common base of user accounts. Server farms can include servers, and therefore users, from multiple domains. In order for each server in the farm to be able to publish applications that ICA Client users from each included domain can access, all potential ICA Client users must belong to a group of users common to all involved domains. Published Application Manager draws a common user account base from the intersection of the trust relationships of all affected Windows NT domains.

Physical Connection. Servers in a farm must be connected by some form of network connection. Some possible network connections include LAN, WAN, and dial-up asynchronous connections. Servers can be on different subnets if an ICA Gateway is in place to connect them. ICA Gateways are administered from Citrix Server Administration. See "Connecting Citrix servers across network subnets" in Citrix Server Administration Help for more information.


Changing Configured Server List

Load balanced applications contain multiple Citrix servers capable of hosting a specified application. You can add or remove individual servers from the list of servers configured to host the application using the Properties dialog.

To add or remove a server from the configured list

1.	Select the entry for the published application. From the Application menu, click Properties, or right-click an entry and click Properties.

2.	In the Properties dialog box, click the Server tab.

3.	To remove a server, select the server in the Configured list and click Remove. To add a server, select the server in the Available list and click Add. Click OK.

If the application is an Installation Management application, adding a server causes Installation Management to perform an installation on the additional server. Removing a server causes Installation Management to uninstall the application the specified server.


Trust Intersection

For example, a farm contains servers from:

A single domain named A. The trust intersection of A is A. You can configure published applications for all of A’s users. (This model works for a single server that is a member of a Windows NT workgroup, a single server that is a member of a Windows NT domain, or multiple servers that are members of a single Windows NT domain.)

Two domains, named A and B. Domains A and B have a one-way trust relationship in which domain A trusts B. The trust intersection of these two domains is B. You can configure published applications for all user accounts on domain B. (Note that a server that is a member of a Windows NT workgroup can never belong to a multiple server farm because there is no trust intersection between a workgroup and a domain.)

Two domains, named A and B. Domains A and B have a two-way trust relationship in which domain A trusts B and domain B trusts A. The trust intersection of these two domains is A and B. You can configure published applications for all user accounts on domains A and B.

Two domains, named A and B. Domains A and B have a one-way trust relationship in which domain A trusts B. A server from a third domain, named C, is added to the farm. C has a one-way trust relationship with B, in which C trusts B. The trust intersection of these three domains is B. You can configure published applications for all user accounts on domain B.

Three domains, named A, B, and C. Domains A, B, and C participate in a master domain model network in which domain A is the master domain and B and C are subordinate domains. According to the master domain model, domains B and C each have a one-way trust with domain A in which domain B trusts A and domain C trusts A. The trust intersection of these three domains is A. You can configure published applications for all user accounts on domain A. (Works with multiple master domains as well.)


Backward Compatibility

If you do not enter your server(s) into a Citrix server farm or farms, Published Application Manager functions in what is called the Windows NT domains scope of management. This method of administration lets you publish and maintain applications using the standard Citrix application publishing model.

If you do not enter your server or servers into a farm or farms, the applications you publish are considered published under the Windows NT domains scope and do not support Program Neighborhood features.

The Windows NT domains scope exists for backward compatibility and interoperability with existing WinFrame 1.7 and MetaFrame 1.0 installations and for users who wish to continue using the original Citrix application publishing model.

If you decide to enter a server into a farm, and that server already has applications published under the Windows NT domains scope of management (for example, if you upgraded a WinFrame 1.7 or MetaFrame 1.0 server that already contained published applications), you can migrate those applications into a server farm.


Changing Configured User List

After publishing an application, you can add or remove individual users or user groups from the list of users configured to host the application using the Properties dialog.

To add or remove users from the configured list

1.	Select the entry for the published application. From the Application menu, click Properties, or right-click an entry and click Properties.

2.	In the Properties dialog box, click the Accounts tab.

3.	If the Select Domain or Citrix Server dialog box appears, select the domain or server containing the user accounts you want to add (note: you can select a server’s local accounts only when administering a single server farm containing a workgroup-based server). When removing accounts, you can select any domain.

4.	To remove a user or user group, select the user or group in the Configured list and click Remove. To add a user or group, select the user or group in the Available list and click Add. You can click Select to display a different domain or server from which to obtain users or groups.

5.	Click OK.


Network Layout

The way you configure your server farm(s) depends greatly upon your needs and the existing network structure. You can create server farms that include:

A single server in a Windows NT domain.

A single server in a Windows NT workgroup (called a single-server farm). A farm containing a server that is a member of a Windows NT workgroup can contain only one server. This limitation exists because a workgroup-based server and a domain-based server cannot share a common base of user accounts.

Multiple servers in a single Windows NT domain.

Multiple servers in multiple Windows NT domains.

Servers in a farm can be located in different geographical locations and can be on different subnets as long as the subnets are connected by an ICA Gateway.

A single domain-based server or workgroup-based server should be entered into a farm so that you can take advantage of server farm and Program Neighborhood features.


Uninstalling Installation Management Applications

Use Published Application Manager to uninstall any application installed using Installation Management Services. To uninstall an application, delete its entry in the list of published applications. When you delete the entry, the Installer removes all program files and registry entries created during installation.

Before deleting a published application entry, make sure the application is not in use. Confirm that no ICA Client users are connected to the published application and that the application is not in use on the console. If the application placed components in the Startup group, make sure you stop the execution of these components as well.

If you unpublish an application while users are connected or while any of its components are executing, the Installer does not remove those application files that are in use.

Also, if you just published the application, make sure the Installer completed installation before you unpublish the application. See Monitoring Installation Status for more information. Unpublishing before installation is complete can cause uninstallation errors.

1.	Select the published application entry for the application you want to uninstall.

2.	From the Application menu, click Delete.

As long as the installation script for the application is not referenced by any other published application entries, deleting a published application entry removes the application from all Citrix servers. Uninstallation removes files, directories, and registry entries placed on the server during installation. Uninstallation does not remove files, directories, or registry entries created by the application after installation.

Event Viewer logs the following message when you uninstall an application: "Citrix Installer: Application X has been successfully removed," where X is the name of the application as specified in the application’s installation script. After uninstalling an application, you can check each server’s Event Viewer for this message.

To remove an application from specific servers

1.	Select the published application entry for the application you want to uninstall.

2.	From the Application menu, click Properties.

3.	In the Properties dialog box, click the Citrix Servers tab. From the Configured list, select a server name, or multiple names, and click Remove.

4.	Click OK. The Installer removes the application from the specified server(s).


Making Published Applications Available on the Web

In addition to support for Program Neighborhood, which lets you, instead of your ICA Client users, configure connections to published applications, Published Application Manager includes two wizards that help you create Web access to published applications.

The ICA File and HTML file wizards let you create Web pages containing links to published applications. You can place the Web pages and ICA files on a Web server to make published applications available to ICA Web Client users on the Internet or Intranet.

See Write ICA File for information on how to create ICA files.

See Write HTML File for information on how to create HTML files.


Published Application Icons

When you publish an application in a server farm, Published Application Manager attempts to retrieve the application’s icon from its executable (if the published application contains an executable) by parsing the command line you enter in the New Application wizard. If Published Application Manager cannot parse the command line or if you are publishing one of several specific application types, Published Application Manager uses a default icon to represent the application.

The chosen icon appears in Program Neighborhood users’ application sets.

When you publish an application using the Windows NT domains scope, Published Application Manager always uses default icons for each application.

Published Application Manager uses the following icons to represent published applications:

	Explicit applications. Both of these icons represent explicit published applications. The leftmost icon appears by default when you use the Windows NT domains scope to publish an explicit application. When you publish an explicit application in a server farm (and Published Application Manager is able to parse the application’s command line), the application’s own icon appears (as in the graphic on the right).
	Anonymous applications. Both of these icons represent anonymous published applications. The leftmost icon appears by default when you publish an anonymous application using the Windows NT domains management scope. When you publish an anonymous application in a server farm (and Published Application Manager is able to parse the application’s command line), the application’s icon is overlaid with a small question mark to indicate that it is anonymous (as in the graphic on the right). The anonymous indicator can appear for the next three application types as well when they are published for anonymous users.
	Default Citrix Installation Management Services. This icon appears by default when you publish a Citrix Installation Management application in a server farm.
	Default video. This icon appears by default when you publish a video.
	Default desktop. This icon represents a published desktop. This icon appears by default for desktop sessions (applications that do not have a specified command line and working directory) published in a server farm.

Symbol Overlays and Modifications

Published Application Manager relates additional information about published applications by overlaying symbols on application icons:

	An application that is currently enabled and accessible to you appears without any modification.
	A grayed out icon indicates that an application is currently disabled.
	A lock appears over an application that you cannot copy, delete, or edit. For information about why the current application is locked, right-click the application and click Properties in the context menu. In the Properties tab, click Why is this read-only? See Farm Requirements for information on administrative rights requirements.
	The yellow question mark appears if Published Application Manager is not yet finished retrieving information about an application.
	The "not" symbol and the lock appear over an application when you have neither Read nor Write access to the application’s configuration information. See Farm Requirements for information on administrative rights requirements. You cannot view or edit an application overlaid with the "not" and lock.

To change an application’s icon

The following procedure describes how to change the icon for an application published in a server farm. The application you select appears in Program Neighborhood users’ application sets.

1.	In Published Application Manager’s main window, right-click an application and select Properties in the context menu.

2.	Make sure the Application tab is selected. Click Change Icon. The Change Icon dialog box appears. The Current Icon field displays currently available icons from which you can select an icon to represent the application.

3.	Select an icon in the Current Icon field or click Browse to search for an icon. In the dialog box that appears, click Files of type and select a file type (such as icon files or executables) in the list box and then locate and select the file containing the icon. For example, if you select the application’s executable, Published Application Manager searches the executable file for the application’s icon.

Alternately, click Use Default to select an icon from several available default icons.

4.	After selecting an icon, click OK to exit. The application now is identified by the new icon in Program Neighborhood users’ application sets.


Server Icons

The icons that represent Citrix servers (in the Select Citrix Server dialog box, Add the Application to Citrix Servers panel of the New Application wizard, or Servers tab of an application’s Properties) relate two types of information about Citrix servers:

Color Coding

Server icons are color-coded based on the server’s operating system type:

Teal	WinFrame servers
Blue	MetaFrame servers (Windows Terminal Server)
Red	MetaFrame servers (Windows 2000)

Symbol Overlays and Modifications

Symbol overlays on server icons indicate:

	Published Application Manager has not yet determined your access to this server. When you attempt an operation, such as adding this server to an application, Published Application Manager determines the server’s status, including whether or not you have administrative rights to modify or add to its applications.
	You have only Read access to this server’s published application data. If you select this server, you can view its applications but cannot edit them or publish new ones.
	You do not have Read or Write access to this server’s published application data. You cannot select this server because you cannot view, edit, or create new published applications on it.
	This server is currently offline.
See Also

Farm Requirements for information on administrative rights.

Selecting a Server for procedural information on selecting Citrix servers.


Title Bars

Published Application Manager’s main window displays applications published on the currently selected server(s). The main window’s title bar indicates the:

Currently selected server(s).

Currently selected scope of management. When using the Windows NT domains scope, the title bar indicates NT Domain; when using the server farms scope, the title bar indicates the name of the currently selected farm.

For example:

This title bar indicates that the main window displays all applications on the server LLAMA4M in OLDB FARM.

This title bar indicates that the main window displays all applications on all servers in the currently selected domain (Windows NT domains scope).

See Also

Selecting a Management Scope

Selecting a Server


Anonymous Published Applications

Anonymous applications are applications published for the special Citrix user group Anonymous. ICA Client users can access anonymous applications without specifying a user name, domain name, and password.

You cannot publish anonymous applications on a Citrix server that is either a Primary Domain Controller or Backup Domain Controller.


Explicit Published Applications

Explicit applications are applications published for an explicit user or user group. To access this type of application, each ICA Client must provide a valid Windows NT user name, domain name, and password.


Menus

Published Application Manager’s main window includes the following menus and menu items:

Application	View	Configure	Help
New	Toolbar	Server Farm	Help Topics
Copy	Status Bar	Join or Create Server Farm	About Published Application Manager
Delete	Large Icons
Properties	Small Icons
Enable	List
Disable	Details
Write ICA File	Arrange Icons
Write HTML File	Select Server
Load Data	Select Scope
Migrate	Refresh
Exit

Published Application Manager also includes context menus. When you right-click a published application or blank space in Published Application Manager’s main window, a menu appears including the following items:

Application	Main Window
Copy	View
Delete	Arrange Icons
Properties	New
Enable	Refresh
Disable
Write ICA File
Write HTML File
Load Data
Migrate


Help Topics

Select this menu item to launch Published Application Manager Help.


About Published Application Manager

Select this menu item to view version information about Published Application Manager.


Server Farm

Select this option to change a server's farm membership or, if a server is already a member of a farm, to create a new one. This item is active only when you are using the server farms management scope to view a single server (not all servers).


Join Server Farm
Join or Create Server Farm

This option appears when you are viewing a Citrix server that is not a member of a farm. Use this item to place the currently selected server in an existing farm or to create a new one.


Toolbar

Select this option to hide or display Published Application Manager's toolbar.


Status Bar

Select this item to hide or display the status bar that appears at the bottom of Published Application Manager's main window.


Large Icons

Select this item to display published applications as large icons in Published Application Manager's main window.


Small Icons

Select this item to display published applications as small icons in Published Application Manager's main window.


List

Select this item to display published applications as a list of small icons in Published Application Manager's main window.


Details

Select this item to display published applications as a detailed list of small icons in Published Application Manager's main window. This view displays application type (explicit or anonymous) and whether the application is enabled or disabled.


Arrange Icons

This item sorts the currently viewed applications by application name (alphabetical), type (explicit or anonymous), or state (enabled or disabled).


Select Server

Select this item to change the currently viewed server. When using this item, you can select a specific server, all servers in a domain or farm, or specific server(s) that meet your filtering requirements.

See Selecting a Server


Select Scope

Select this item to change your scope of management. You can publish applications using one of the following scopes: server farms or Windows NT domains.

See Selecting a Management Scope


Refresh

Select this item to re-enumerate all servers in the current scope and to reload all applications on the network.


Exit

Select this option to exit Published Application Manager.


Write ICA File

Select this item to launch the ICA File wizard. The ICA File wizard lets you create an ICA file for the currently selected application that you can reference in a Web page that ICA Web Client users can visit to start ICA sessions.

See Write ICA File


Write HTML File

Select this item to launch the Write HTML File wizard. This wizard lets you create a template Web page for the currently selected application that ICA Web Client users can visit to connect to the application.

See Write HTML File


Disable

Select this item to temporarily disable a published application. Disabling an application makes it unavailable to ICA Client users until you re-enable it. This item is available only if:

You have selected an application that is currently enabled

You have full administrative rights over the application

The application is hosted by a MetaFrame 1.8 or WinFrame 1.8 server

See Enabling and Disabling Published Applications


Enable

Select this item to re-enable a disabled application. Re-enabling an application makes it available to ICA Client users. This item is available only if:

You have selected a disabled application

You have full administrative rights over the application

The application is hosted by a MetaFrame 1.8 or WinFrame 1.8 server

See Enabling and Disabling Published Applications


Properties

Select this item to view or edit the configuration information for a published application.

You can edit a server farm application if:

You have full administrative rights over the application

You are currently using the server farm scope to view the application

You can edit an application published using the Windows NT domains scope if:

You have full administrative rights over the application

See Changing Properties of Published Applications


Delete

Select this item to delete a published application. This item is available when you select an application over which you have full administrative rights.


Load Data

Select this option to reload an application’s configuration information. This function is useful if you believe changes made to an application have not taken effect or if an application, which you believe you should be able to access, is marked inaccessible.


New

Select this item to publish an application.


Copy

Select this item to create a copy of the currently selected application. This function is useful when you want to quickly clone an application to create an application with a similar configuration. After creating the copy, you can edit the copy's properties to change configuration information such as users allowed to access or servers configured to host the application.

You must have full administrative rights over an application to make a copy of it.

See Changing Properties of Published Applications


Migrate

Select this item to migrate an application published using the Windows NT domains scope (or published using a previous version of Published Application Manager such as Application Configuration) into a server farm. Once you migrate the application into a farm, you can configure Program Neighborhood properties for the application.

This item is available when using the server farm scope to view an application created using the Windows NT domains scope.

See Migrating Applications to a Server Farm


View

This item lets you change how published applications appear in the main window. You can view published applications as large icons, small icons, listed small icons, or a details list.


Full Administrative Rights

You have full administrative rights over a server if you have Read and Write access to its registry.

You have full administrative rights over an application if you have Read and Write access to each host server’s registry.

To give yourself full administrative rights to a server or servers, make sure you are a member of each server’s local administrative group.


Program Neighborhood

Program Neighborhood is the program users run to connect to MetaFrame servers with the Citrix ICA Client for Win32 (Windows 95, Windows 98, and Windows NT platforms).


Published Program Neighborhood

To give a broader range of your users the benefits of the new Program Neighborhood features, you can publish the ICA Win32 (Program Neighborhood) Client application on your Citrix servers. Users of the non-Win32 Citrix ICA Clients can then define in their connection managers a single connection to the Program Neighborhood published application. Once they connect to the Program Neighborhood published application, they can launch all other applications published on all the Citrix servers in your farm from a single easy interface.


Monitoring Installation Status

After publishing an Installation Management application, use Citrix Server Administration to determine when installation is complete and when ICA Client users can begin to access the application.

To view installation status

1.	Start Citrix Server Administration. On MetaFrame 1.8, click Start in the Windows Taskbar, point to Programs, MetaFrame Tools, and then click Citrix Server Administration. On WinFrame 1.8, double-click the Administrative Tools program group in Program Manager and then double-click Citrix Server Administration.

2.	The main window appears. In the left pane, click the Published Applications tab. In the list of published applications, select the application whose status you want to determine.

3.	Click the Servers tab in the right pane.

4.	The Installation column displays one of the following values for each server receiving the installation:

  Unknown. The Citrix utility could not gather information about the installation. This message can appear if you do not have permission to gather status information from the server’s registry or if the path indicated for the installation script during application publishing is incorrect. This message may also appear momentarily after installation begins.

  Completed. Successful installation.

  In Progress. Installation is in progress.

  Delayed. Installation is postponed until no ICA Client users are connected to the published application. This value appears during application upgrades. An application in the delayed state does not accept new ICA Client connections. Once all users log off, each Installer can begin installation. The actual time at which installation begins depends upon your upgrade timing configuration. See the product documentation for more information.

  Need Reboot. The server requires a reboot. As with normal application installations, some applications may require a reboot of the server after installation completes; for example, if the application attempts to overwrite a Dll that is in use at the time of installation. Due to the fact that your Citrix servers may vary in previously installed applications and configurations, some servers (and not others) may require a reboot after you publish an application. After the reboot, setup is complete.

  ERROR. Installation encountered an error and did not complete. See Event Viewer on the server for more information.


Choose Your Path

The wizard has novice and expert modes. Use the novice mode if you are not familiar with the available options.


ICA File Window Size and Colors

Specify the window size and color depth. The Citrix ICA Client uses the specified size and color attributes when connecting to the application specified in the ICA file. If the application is embedded in a Web page, the maximum size of the application is specified in the HTML page.

If the resolution and color depth exceed the capabilities of the client hardware, the maximum size and color depth supported by the client are used instead.


ICA File Encryption Level

Select the level of encryption for the ICA connection. The default level is Basic. Strong encryption using the RC5 algorithm is available with Citrix SecureICA Services. SecureICA Services enables RSA RC5 encryption with 40-, 56-, or 128-bit session keys. The Citrix server must be configured to allow the selected encryption level or greater. For example, if the Citrix server is configured to allow RC5 56-bit connections, the Citrix ICA Client can connect with RC5 56- or 128-bit encryption.


ICA File Name

Specify the path and filename for the ICA file, including the .ica extension. By default, files created with this wizard are saved in %SystemRoot%\System32.

Note

Some Web browsers and servers cannot properly handle long file names or file names with embedded blanks or special characters. For best results, especially with 16-bit software, use FAT file names (8 characters or less, with no special characters or embedded blanks).


Write an HTML File

Click Finish to save the new ICA file. To create an HTML file to use this application from a Web browser, click Yes and then click Next.

If you choose to create an HTML file, the Write HTML File wizard begins and leads you through the process of creating an HTML file that references this ICA file.


Write ICA File Parameters

Use this screen to change ICA file parameters. The ICA client uses the specified parameters when connecting to the published application.

The settings that can be changed in this screen are:

Window size. You can specify the window size as an absolute number of pixels or as a percentage of the desktop size.

The color depth.

The encryption level to use when connecting to the application. Strong encryption is only available if Citrix SecureICA Services has been installed.

File name. Specify the path and filename for the ICA file, including the .ica extension. By default, the file is saved in %SystemRoot%\System32.


Write an ICA File

Click Create a new ICA file if you do not have an existing ICA file for the published application.

Click Use an existing ICA file if you have already created an ICA file for the published application.

Click Next.


Write HTML File Parameter

Use this screen to change HTML file parameters.

The settings that can be changed in this screen are:

Application appearance. Click Embedded to have the application windows appear as part of the Web page. Click Launched to have the application appear in a separate window.

The ICA Client used. Click Netscape Plug-In/ActiveX control or Java Client.

The size of the embedded application window. This changes the height and width tags in the HTML code. The size of launched windows is specified in the ICA file.

Select the Verbose page check box to include comments in the HTML file.

File name. Specify the filename for the HTML page using the .htm or .html extension, depending on your Web server. By default, the file is saved in %SystemRoot%\System32.


HTML Application Appearance

Click Launched to create an HTML page that displays the application in a separate window.

Click Embedded to create an HTML page that displays the application within the browser window.


HTML Web Client Type

Specify the Web Client type for the embedded application. The HTML page uses the specified Web Client type to display the application.


HTML Embedded Window Size

Specify the size of the application window in the HTML page.

Note

The Maximize application at startup checkbox in the application definition properties can be used to force the application window to the size of the embedded window.


HTML Verbose Page

Select the Verbose page checkbox to include additional comments in the HTML file that describe each HTML file option.


HTML File Name

Specify the filename for the HTML page. Use the .htm or .html extension depending on your Web server. By default, the file is saved in %SystemRoot%\System32.


Server Farm Application Migration Wizard

You can migrate an application if:

It contains no configured user accounts from domains not trusted by the current server farm

It contains no configured servers that are not part of the current server farm (this condition applies to load balanced published applications)


Ready to Migrate

Click Next to migrate the application.

Click Cancel to exit the wizard without changing the application from its present scope to the server farm scope of management. No changes are made to the application.


Migration Complete

This screen appears after successful migration. The published application now is enabled for Program Neighborhood features and is published in the currently selected server farm.

Use the server farm management scope to view the application’s host server and edit the application’s Program Neighborhood properties.


Enter Application Name

Use the Enter Application Name screen to create a name for the published application. This name identifies the application to ICA Client users.

In the Application Name field, enter the name for the application.

In the Detailed Description field, enter an optional description for the application.


Choose Application Type

This screen lets you specify whether the application is to be used by explicit or anonymous users.

Explicit applications are applications published for an explicit user or user group. To access this type of application, each ICA Client must provide a valid Windows NT user name, domain name, and password.

Anonymous applications are applications published for the special Citrix user group Anonymous. ICA Client users can access anonymous applications without specifying a user name, domain name, and password.

Note

You cannot publish anonymous applications on a Citrix server that is either a Primary Domain Controller or Backup Domain Controller.

Click Explicit or Anonymous and then click Next.


Define the Application

Enter the full command line (with any required parameters) and folder for your application. Click Browse to search local or network drives for the application.

In the Command Line field, enter:

Standard or Program Neighborhood applications: full command line and any required parameters for the application’s executable; for example, C:\MSOffice\Winword\winword.exe.

Citrix Installation Management applications: full command line for the application’s installation script. Installation scripts have a .wfs file extension; for example, \\Server-name\share-name\application-name\example.wfs. Unless each of your Citrix servers contains a network drive of the same letter mapped to your file server’s share point for installation scripts, you must use only Universal Naming Convention (UNC) formatted paths. Please see these special instructions when publishing a Citrix Installation Management application on a WinFrame server or in a mixed server environment.

Citrix VideoFrame videos: full command line for the video’s Citrix VideoFrame Information file. VideoFrame Information files have a .cvi file extension; for example, \\Server-name\share-name\example.cvi. The path must be in Universal Naming Convention (UNC) format. Please see these special instructions when publishing a video on a WinFrame server or in a mixed server environment.

Tip

Leave the command line and working directory fields blank to configure a Windows NT desktop session. When users connect, they have access to a Windows NT desktop.


Specify Window Properties

If the Hide application title bar checkbox is selected, the application’s title bar is not displayed at the top of the ICA session window.

If the Maximize application at startup checkbox is selected, the application window is maximized to fill the ICA session window.

These options can be combined to prevent users from minimizing or closing application windows.


Specify Program Neighborhood Client Settings

The Specify Program Neighborhood Client Settings screen lets you set various conditions under which Program Neighborhood Clients connect to the published application. Each drop-down list contains connection options that Program Neighborhood Clients apply to user sessions for this application. Program Neighborhood Client settings include:

Audio. Select whether Program Neighborhood Clients connect with support for ICA Audio 1.0 or with no audio support. If you specify Audio 1.0, you can check the Minimum Requirement checkbox. If you check Minimum Requirement, Program Neighborhood Clients will connect to the published application only if they support ICA Audio 1.0.

Video. Select whether Program Neighborhood Clients connect with support for ICA Video 1.0 or with no video support. If you specify Video 1.0, you can check the Minimum Requirement checkbox. If you check Minimum Requirement, Program Neighborhood Clients connect to the published application only if they support ICA Video 1.0.

Encryption. Select the level of encryption at which you want Program Neighborhood Clients to connect. You can select the Minimum Requirement checkbox for any value greater than Basic. If you check Minimum Requirement, Program Neighborhood Clients connect to the published application only if they support the specified level of encryption. (The server must support this level of encryption as well.)

Window Size. Select the default window size for Program Neighborhood Client connections. You can specify window size as a standard resolution, custom resolution, or percentage of the client desktop.

Window Colors. Select the color depth.


Specify Neighborhood Administration Features

Select Add this application in the client’s Start menu to create a shortcut to this application in Program Neighborhood Client users’ local Start menus.

Select Add this application on the client’s desktop to create a shortcut to this application on Program Neighborhood Client user’s local desktop.

In the Neighborhood Folder field, you can specify a subfolder in which this application will appear in the Program Neighborhood Client itself. By default, applications appear in a root directory in the Program Neighborhood Client view of the server farm.

Specify an existing subfolder name or create a new one. For example, to create a subfolder named User Applications, enter User Applications in the Neighborhood Folder field. This application then appears in a subfolder of the Program Neighborhood Client window called User Applications. To place this application in a subfolder of the User Applications folder, specify User Applications\subfolder.


Select Domain or Citrix Server

This dialog box displays all trusted domains from which you can obtain user accounts to add to the list of configured users for the published application.

The domain list never displays the current server as a domain from which to obtain accounts if you are using the server farm management scope to create this application in a multiple-server farm.

The domain list contains the current server only if:

You are using the Windows NT domains management scope to create this published application and you are configuring the application only on the current server.

You are publishing this application in a single-server farm containing one server that is a member of a Windows NT workgroup.

Select a domain and click OK.


Configure Accounts

The Configure Accounts screen is displayed only for explicit applications. The Configured list shows the users and groups allowed to run the published application.

The Available list shows the complete list of user groups available in the currently selected domain. Select the Show Users checkbox to display a list of all users on the specified domain or server. Click Select to browse a different domain or server. The dialog box that appears lets you select and display another trusted domain’s user list.

Use the Add and Remove buttons to add or remove users or user groups from the Configured list.


Add the Application to Citrix Servers

Use this screen to specify which Citrix servers will host the application.

If you have installed Load Balancing Services, you can specify multiple host servers. If Load Balancing Services is not installed, only the current server is displayed in the Configured list and the Add button is unavailable.

You can set the command line and working directory individually for each server. Click a server in the Configured list and then click Edit Configuration. Type the command line and working directory in the Application Configuration dialog box. Use this option when paths to applications differ by server.

Click Filter Servers By… to view a dialog box that lets you sort and filter your view of servers to display only servers that run a specific operating system or that have certain Citrix features and capabilities.

Note

If a Citrix server appears with its domain specified as question marks, the server’s domain could not be determined. One common reason for this condition is the server is offline.

See Server Icons for an explanation of icons used to represent servers and their accessibility to the current user.


Filter Servers By

The capabilities, encryption levels, and operating system type requirements can be selected individually or in combination to produce a filtered server list. Filtered server lists show only servers that meet your requirements.

For example, if you select Load Balancing and SecureICA, the servers displayed are servers with SecureICA Services and Load Balancing Services installed.

After selecting the desired capabilities and requirements, click OK. You are returned to the Add the Application to Citrix Servers screen with only those servers meeting the specified conditions displayed.


Application Configuration dialog box

You can set the command line and working directory for each application individually. This option lets you enter paths or working directories that vary from server to server.

Enter the command line (plus any required parameters) and working directory for the application on the currently selected server.

In the Command Line field, enter:

Standard or Program Neighborhood applications: full command line and any required parameters for the application’s executable; for example, C:\MSOffice\Winword\winword.exe.

Citrix Installation Management applications: full command line for the application’s installation script. Installation scripts have a .wfs file extension; for example, \\Server-name\share-name\application-name\example.wfs. Unless each of your Citrix servers contains a network drive of the same letter mapped to your file server’s share point for installation scripts, you must use only Universal Naming Convention (UNC) formatted paths.

Citrix VideoFrame videos: full command line for the video’s Citrix VideoFrame Information file. VideoFrame Information files have a .cvi file extension; for example, \\Server-name\share-name\example.cvi. The path must be in Universal Naming Convention (UNC) format.


Finish Adding the Application

You have successfully configured the application. Click Finish to save the application.


Select Citrix Server

The Select Citrix Server dialog box appears under one of two circumstances:

If you click View, Select Server in Published Application Manager’s main window. You can use the Select Citrix Server dialog box to choose which Citrix server in the current server farm or Windows NT domain to view. Select a single server from the list or (All Servers) to display all servers in the current server farm or Windows NT domain.

If you attempt to publish an application without a default server selected. For example, if you are currently viewing all servers in a server farm or Windows NT domain, the Select Citrix Server dialog box appears to let you specify a default server for the new application. Later in the New Application wizard you can add additional servers for the application (if all affected servers have Citrix Load Balancing Services installed).

Click Filter Servers By… to narrow down your server list to only those servers that support certain specifiable features or capabilities.

Click Refresh Server List if the desired server does not appear in the server list. Clicking Refresh Server List resends a request for the list of configurable servers. Refreshing the server list does not list servers that cannot be configured; for example, servers from untrusted domains.

Note

If a Citrix server appears with its domain specified as question marks, the server’s domain could not be determined. One common reason for this condition is the server is offline.

See Server Icons for an explanation of icons used to represent servers and their accessibility to the current user.


Select Management Scope

The Select Management Scope dialog box lets you switch between Published Application Manager’s two scopes of management: server farm and Windows NT domains.

If you select the Within a Citrix server farm radio button, the applications that you publish are published within a specified server farm. These applications are enabled to automatically configure Program Neighborhood Client ICA sessions with the connection properties you specify during application publishing.

If you select the Using Only NT Domains radio button, the applications you publish are published within the Windows NT domains context. These applications are not enabled to automatically configure Program Neighborhood Client ICA sessions.

To select the server farm scope

Select the Within a Citrix server farm radio button. The Choose Server Farm panel appears in the bottom half of the dialog box. Select a server farm from the list.

To select the Windows NT Domains scope

Select the Using Only NT Domains radio button. The Choose NT Domains panel appears in the bottom half of the dialog box. Select single, multiple, or all displayed domains.


Change Icon

The Change Icon dialog box lets you change the icon that identifies this application in Published Application Manager and to Program Neighborhood Client users. The Current Icon field displays currently available icons from which you can select an icon to represent the application.

Click Browse to search for an icon. In the dialog box that appears, click Files of type and select a file type (such as icon files or executables) in the list box and then locate and select the file containing the icon. For example, if you select the application’s executable, Published Application Manager will search the executable file for the application’s icon.

Click Use Default to select an icon from several available default icons.


Application Properties: Application tab

Use this tab to modify certain basic published application properties:

Note

The properties of applications published for a Citrix server farm cannot be edited when viewed from the Windows NT domains scope (all tabs in the dialog box are grayed-out). To edit the application, change your scope to the Citrix server farm scope.

Name. This name identifies the application to ICA Client users.

Type. The type of application (explicit or anonymous). This property cannot be modified. You must republish the application to change its type.

Disable Application. When you publish an application, it is enabled by default. Enabled applications are available to the users you specify when publishing the application. Select this checkbox to temporarily disable this application. Disabling an application makes it unavailable to ICA Client users until you re-enable it.

Application Window Properties. If the Hide application title bar checkbox is selected, the application’s title bar is not displayed at the top of the ICA session window. If the Maximize application at startup checkbox is selected, the application window is maximized to fill the ICA session window.

Settings for Program Neighborhood Clients. This panel of the tab is visible only for applications created under the server farm management scope. In the Detailed Description field, you can enter an optional description for the application. Your descriptive text appears in the status bar at the bottom of the Program Neighborhood Client window. Click Change Icon to change the icon that identifies this application in Published Application Manager and to Program Neighborhood Client users.


Application Properties: Client tab

Use this tab to set various conditions under which Program Neighborhood Clients connect to the published application. Each drop-down list contains connection options that Program Neighborhood Clients apply to user sessions for this application. Program Neighborhood Client settings include:

Audio. Select whether Program Neighborhood Clients connect with support for ICA Audio 1.0 or with no audio support. If you specify Audio 1.0, you can check the Minimum Requirement checkbox. If you check Minimum Requirement, Program Neighborhood Clients connect to the published application only if they support ICA Audio 1.0.

Video. Select whether Program Neighborhood Clients connect with support for ICA Video 1.0 or with no video support. If you specify Video 1.0, you can check the Minimum Requirement checkbox. If you check Minimum Requirement, Program Neighborhood Clients connect to the published application only if they support ICA Video 1.0.

Encryption. Select the level of encryption at which you want Program Neighborhood Clients to connect. You can select the Minimum Requirement checkbox for any value greater than Basic. If you check Minimum Requirement, Program Neighborhood Clients connect to the published application only if they support the specified level of encryption. (The server must support this level of encryption as well.)

Window Size. Select the default window size for Program Neighborhood Client connections. You can specify window size as a standard resolution, custom resolution, or percentage of the client desktop.

Window Colors. Select the color depth.


Application Properties: Neighborhood tab

Use this tab to modify the ways Program Neighborhood Client users access the published application.

Select Add this application in the client’s Start menu to create a shortcut to this application in Program Neighborhood Client users’ local Start menus.

Select Add this application on the client’s desktop to create a shortcut to this application on Program Neighborhood Client users’ local desktops.

In the Neighborhood Folder field, you can specify a subfolder in which this application appears in the Program Neighborhood Client itself. By default, applications appear in a root directory in the Program Neighborhood Client view of the server farm.

Specify an existing subfolder name or create a new one. For example, to create a subfolder named User Applications, enter User Applications in the Neighborhood Folder field. This application then appears in a subfolder of the Program Neighborhood Client window called User Applications. To place this application in a subfolder of the User Applications folder, specify User Applications\subfolder.


Application Properties: Accounts tab

Use this tab to modify the list of users configured to access the application.

The Available list shows the complete list of user groups available in the currently selected domain. Select the Show Users checkbox to display a list of all users on the specified domain. Click Select to browse a different domain or server. The dialog box that appears lets you select and display another trusted domain’s user list.

Note

You can display and use the host server’s local user accounts only if you created the application using the Windows NT domains scope or in a single-server farm containing a server that is a member of a Windows NT workgroup.

Use the Add and Remove buttons to add or remove users or user groups from the Configured list.


Application Properties: Servers tab

Use this tab to modify the list of servers configured to host the application.

If you have installed Load Balancing Services, you can specify multiple servers to host the application. If Load Balancing Services is not installed, the Configured list displays only the current server and the Add button is unavailable.

The servers displayed in the Configured list depend upon the type of application and the current management scope:

If you created the application under the Windows NT domains management scope, the servers displayed in the Configured list depend upon your currently selected management scope. If your current scope is the server farm scope, the list includes servers in the currently selected server farm. If your current scope is the Windows NT domains scope, the list includes servers in the currently selected domain or domains.

If the application was created under the server farm management scope, the Configured list always displays only the other servers in the server farm for which the application was created.

Note

If a Citrix server appears with its domain specified as question marks, the server’s domain could not be determined. One common reason for this condition is the server is offline.

You can edit the application’s command line and working directory individually for each configured server. Click a server in the Configured list and then click Edit Configuration. Type the command line and working directory in the Application Configuration dialog box.

Click Filter Servers By… to narrow down the list of available servers to only those servers that run a certain operating system or support certain specifiable features or capabilities.

See Server Icons for an explanation of icons used to represent servers and their accessibility to the current user.


Application Configuration: Definition tab

Use this tab to modify the command line and working directory for the application on the currently selected server. Enter the full command line (with any required parameters) and folder for your application. Click Browse to search for the application.

In the Command Line field, enter:

Standard or Program Neighborhood applications: full command line and any required parameters for the application’s executable; for example, C:\MSOffice\Winword\winword.exe.

Citrix Installation Management applications: full command line for the application’s installation script. Installation scripts have a .wfs file extension; for example, \\Server-name\share-name\application-name\example.wfs. Unless each of your Citrix servers contains a network drive of the same letter mapped to your file server’s share point for installation scripts, you must use only Universal Naming Convention (UNC) formatted paths. Please see these special instructions when publishing a Citrix Installation Management application on a WinFrame server or in a mixed server environment.

Citrix VideoFrame videos: full command line for the video’s Citrix VideoFrame Information file. VideoFrame Information files have a .cvi file extension; for example, \\Server-name\share-name\example.cvi. The path must be in Universal Naming Convention (UNC) format. Please see these special instructions when publishing a video on a WinFrame server or in a mixed server environment.


Join Citrix Server Farm Wizard
Create or Join Citrix Server Farm Wizard

Please see Introduction to Server Farms and its related topics for more information on server farms.


Join a Server Farm

The Server Farm Name pull-down list contains a list of all available server farms on your network (including servers from subnets other than the current subnet if ICA gateways have been set up to link them).

If you want this server to join an existing server farm, select the farm from the Server Farm Name pull-down list. If the server does not appear in the list, click Refresh List.

If you want to create a new farm, type a new name for the farm in the text field of the Server Farm Name pull-down list.

Click Next.


The Server Farm Setup Is Complete

You have successfully joined the server farm. Click Finish to exit the wizard and begin publishing applications in this farm.


Server Farm Properties

This dialog box lets you change a server’s farm membership. Click Change Server Farm to start the Change Server Farm wizard.


Change Server Farm Wizard

Click Next to change the server’s farm membership. Click Cancel to exit without changing its membership.


Cannot Join the Specified Server Farm

The text box in the Cannot Join the Specified Server Farm screen displays the reason(s) the server cannot be entered into the specified server farm. To join this farm, you must resolve the conflict.

Some common reasons why a server cannot join a farm include:

Load balanced applications. If the server has any load balanced applications with other servers in its present farm, you must remove the server from the list of servers configured for those applications before removing the server from the farm. Make sure the other server(s) are online and remove the current server from the list of servers configured to host the application. See Changing Configured Server List for more information.

Trust relationship conflict. There must be a trust intersection between the domain on which the current server is a member and the domains on which all other servers in the farm are members. Server farms require this trust intersection so that all servers in the farm can draw users from a common base of accounts that can access each server in the farm

See Farm Requirements for general information.

If you cannot resolve the conflict, you can enter the server into a new farm by creating a new farm name.


Choose a New Server Farm

The Server Farm Name pull-down list contains a list of all available server farms on your network (including servers from subnets other than the current subnet if ICA gateways have been set up to link them).

If you want this server to join an existing server farm, select the farm from the Server Farm Name pull-down list. If the server does not appear in the list, click Refresh List.

If you want to create a new farm, type a new name for the farm in the text field of the Server Farm Name pull-down list.

Click Next.


The Server Farm Membership Has Changed

Click Finish to exit the wizard. If you want to change the server’s farm membership again, click Change Server Farm in the Server Farm Properties dialog box.


Cannot Join the Server Farm

The text box in the Cannot Join the Server Farm screen displays the reason(s) the server cannot be entered into the specified server farm. To join this farm, you must resolve the conflict.

Some common reasons why a server cannot join a farm include:

Trust relationship conflict. There must be a trust intersection between the domain on which the current server is a member and the domains on which all other servers in the farm are members. Server farms require this trust intersection so that all servers in the farm can draw users from a common base of accounts that can access each server in the farm.

Configured user accounts conflict. An application(s) in the farm contains configured user accounts that the current server’s domain does not trust. You must remove those untrusted user accounts from the list of users configured for the application(s) in question so that a trust intersection exists. Once these accounts are removed from the configured accounts list for the application(s), you can enter the server into the farm. See Changing Configured User List for procedural information.

Single-server farm. The farm you are attempting to join is a single-server farm. Single-server farms containing a server that is part of a Windows NT Workgroup cannot be joined by other servers. You cannot join this farm because no trust intersection can exist between your domain-based server and the workgroup-based server in the farm. For information on how you can arrange servers in a farm, see Network Layout.

See Farm Requirements for more information.

If you cannot resolve the conflict, you can enter the server into a new farm by creating a new farm name.


Cannot Join a New Server Farm

The text box in the Cannot Join a New Server Farm screen displays the reason(s) the server cannot be entered into the specified server farm. To join this farm, you must resolve the conflict.

Some common reasons why a server cannot join a new farm include:

Load balanced applications. If the server has any load balanced applications with other servers in its present farm, you must remove the server from the list of servers configured for those applications before removing the server from the farm. Make sure the other server(s) are online and remove the current server from the list of servers configured to host the application. See Changing Configured Server List for more information.

Trust relationship conflict. There must be a trust intersection between the domain on which the current server is a member and the domains on which all other servers in the farm are members. Server farms require this trust intersection so that all servers in the farm can draw users from a common base of accounts that can access each server in the farm.

See Farm Requirements for general information.

If you cannot resolve the conflict, enter the server into a new farm by creating a new farm name.


Create a Single-Server Farm

You can place a Citrix server that is a member of a Windows NT workgroup in a single-server farm. Workgroup-based servers cannot participate in multiple server farms because there can be no common base of user accounts between workgroup servers.

When you create a single-server farm, you can publish applications for the workgroup server’s local account users. These applications support Program Neighborhood features.

Please see Introduction to Server Farms for general information on server farms.

For information on how you can arrange servers in a farm, see Network Layout.


Rename Your Single-Server Farm

Windows NT workgroup-based servers can participate in single-server farms only. Therefore, you can rename the current farm but cannot place this server in an existing farm.

If you want to change this farm’s name, enter a new name in the Server Farm Name field.

Please see Introduction to Server Farms for general information on server farms.

For information on how you can arrange servers in a farm, see Network Layout.


Application Migration Cannot Proceed

This screen displays conflicts that must be resolved before you can successfully migrate an application into the server farm.

Two common errors and the actions you can take to correct them are listed below.

Error message: The application contains the following accounts that are not trusted by all servers in the Server Farm: Servername\Username

Response: you must remove the specified users or user groups from the list of users configured to access the application. See Changing Configured User List for procedural information.

Error message: The application is configured on the following servers that do not belong to the current server farm: Servername

Response: you must remove the specified server(s) from the list of servers configured to host the application. See Changing Configured Server List for procedural information.


Special Instructions

When running Published Application Manager on a WinFrame server, you can click Browse and then Network to locate a VideoFrame Information file or installation script. In the Connect Network Drive dialog box, make sure you specify None in the Drive field (None is the last option in the Drive list) before locating the file server. Otherwise, the network resource is mapped to a drive letter, not a UNC name.

In the Choose Application dialog box, select VideoFrame Information files or Installation Scripts from the Files of type list box, and then locate and select the .cvi file or installation script.


ICA File TCP/IP+HTTP Server Location

Some network configurations restrict broadcast and UDP packets across routers or gateways. To retrieve Citrix server and published application information across a firewall, you can use TCP/IP+HTTP server location.

To use TCP/IP+HTTP protocol to locate servers, enter the name or IP address of a Citrix server and a recognized port number (the default is port 80).