Product Documentation

Managing Application Properties

Oct 09, 2015
After publishing applications through the Publish Application wizard, manage the published applications and their properties:
  • Rename, move, disable, and delete published applications
  • Change, duplicate, import, and export published application settings

Only a Citrix administrator with full access to the Published Applications task can change published applications. Use the application properties to change settings for a published application, including the location of the published application, the servers on which the published application is available, and the user accounts allowed to access the published application.

From the Action menu, select Application properties.

Important: The resource type you publish (application, content, or server desktop) determines your path through the Publish Application wizard; consequently, the properties associated with the resource may vary.

To rename a published application

Use the Name property to change the application name and description that you selected in the Publish Application wizard. Changes take effect after the user reconnects or refreshes the user device. This feature can distinguish among multiple versions of the same application.
  1. In the left pane of the console, select the published application.
  2. From the Action menu, select Application properties and then select Name.
  3. The Display name is the name users see on their user device, and it must be unique within the folder. XenApp supports application names that use Latin-1 and Unicode character sets, including characters used in Japanese, Chinese, and Korean.
  4. The Application name appears in the console and should be unique within a farm (maximum 38 characters). When the application is published, this name is the same as the display name by default.
  5. The Application description appears in Web Interface.
Important: If a duplicate application name is found in the farm, a four-digit hexadecimal number is appended to the original string. If the character limit is reached and duplicated, the console replaces the end characters with four-digit hexadecimal numbers, starting from the right. The application name appears in the left pane of the Properties dialog box for an application.

To configure locations of servers for published resources

Choose the server on which the published application or desktop is available through the Servers page of the Publish Application wizard. To modify the setting, from the Action menu, select Application properties and then select Servers.

Important: For installed applications, select the server where the published application is installed. For streamed-to-server applications, select the server to which the profiled application will stream and execute.
  • The Servers list displays the servers that belong to the farm. Initially, all servers in the farm appear. Use a filter to display only servers running a particular operating system or Citrix version.
    Note: If you apply a filter (in the Select Servers dialog box), the filter settings remain in effect each time the Publish Application wizard is run until the filter is removed or changed.
  • Use the Import from file option to import an application server list file (*.asl). You export the server list of a previously published application and then import this settings file when creating a new published application.

If you modify your servers for a published application, some users may not be in a trusted domain for that server. If you receive an error message when trying to modify configured servers for a published application, duplicate the application and then modify the servers and users lists of the new application.

To specify locations of applications for streaming

Before you publish applications for streaming, you must create an application profile using the Citrix Streaming Profiler, a stand-alone utility, and save the profile to a network file share in your App Hub that is accessible to the Publish Application wizard.

As you publish the application in the Publish Applications wizard, specify the location of the profile:

  1. Citrix streaming application profile address. Provide the location of the manifest file (.profile). For example, enter the Full Universal Naming Convention (UNC) path (such as \\citrixserver\profiles\Adobe Reader\Adobe Reader.profile).
  2. Application to launch from the Citrix streaming application profile. After this field populates with files, choose the application from the drop-down menu.
  3. Extra command-line parameters. (Optional) These parameters are used when the profiled application includes asterisks (**) as a placeholder for additional parameters. If no asterisks are in the command-line string, the extra parameters are added at the end of the command-line.

To enable an application for offline access

Before you publish applications for streaming, you must create an application profile using the Citrix Streaming Profiler, a stand-alone utility, and save the profile to a network file share in your App Hub that is accessible to the Publish Application wizard.

Configure streamed applications for offline access as you publish them or later in the Application Properties:

  • As you publish applications in the Publish Applications wizard, click the Enable offline access check box on the Offline Access page.
  • In Application Properties, select Basic > Streaming settings > Offline Access. Click the Enable offline access check box to enable the feature.
Tip: If, later, some operation in the application fails offline due to a missing component, it will fail while connected as well. The solution is to ensure that you package all the necessary components by thoroughly testing the profile.

The server fully caches applications enabled for offline access on user devices; the entire application is sent to user devices while the user is online so that the user can launch the application offline and have full functionality of the application. By default, applications are cached when a user logs on.

Select when to cache the streamed application:

  • Pre-cache application at login. Caches the application when the user logs on (selected by default). However, concurrent logons may slow network traffic.
  • Cache application at launch time. Caches the application when users launch it. Use this option if the number of users logging on at the same time (and pre-caching their applications) could overload the network.

Pre-caching is also possible using third-party tools, such as Microsoft System Management Server (SMS) or Altiris. If you use a third-party caching method, ignore this setting because it is not used; that is, applications are not cached twice.

To configure user access to applications

Choose the user accounts that can access applications through the Users page of the Publish Application wizard. To modify user accounts, from the Action menu, select Application properties and then select Users.

Before you publish resources, consider how the configuration of user accounts can affect their access, including anonymous access and explicit (configured) user account access.

Note: As a best practice, use groups for unique roles to categorize and assign permissions to large numbers of users. An application published to one group of 1,000 users requires the validation of only one object for all 1,000 users. That same application published to 1,000 individual user accounts requires the validation of 1,000 objects.
  1. Select how to configure user accounts:
    • Select Allow anonymous users to let all users log on anonymously and start the streamed application without specifying a user name, domain name, and password (selected by default). This selection disables the remaining options on the page.
    • Select Allow only configured users to allow only configured users to start the application. For example, select this option for all streamed applications.
      Selecting this option enables the Select directory type drop-down list, which allows you to configure the users for this application. You can configure the list later in the application properties.
      Note: Streamed applications do not support anonymous users. Additionally, if you enable the streamed application for offline access, these options are not shown.
  2. Use the Select directory type drop-down box to select either Citrix User Selector or Operating System User Selector.
  3. Click Add.

    If you selected Citrix User Selector, complete the following tasks in the Select Users or Groups dialog box:

    • Select your account authority from the Look in drop-down list. The drop-down list contains all trusted account authorities configured on the servers in the farm. These include Novell Domain Services for Windows (NDSfW) domains, Windows NT domains, Active Directory domains, and local servers. (NDSfW domains appear only if previously configured.) When you select an account authority, the user accounts that are part of the selected authority appear in the window below the drop-down list. By default, only user groups appear.
    • Select Show users to display all user names in the selected domain. This option displays every user in the selected domain. For NDS, alias objects also appear. The user accounts you select are listed in Configured users.
      Tip: Instead of selecting names from the list, type them in a text box. To do this, click Add List of Names and use semicolons (;) to separate names.
    If you selected Operating System User Selector, use the standard Windows dialog box to select your user or group.
    Note: This option has several limitations. You can browse only account authorities and select users and groups that are accessible from the computer running the console. In addition, you might initially select users and groups outside the trust intersection of the farm, which causes errors later. Other limitations include the inability to add NDS users and groups.

The list of user accounts is added to the Configured Accounts list. Changes take effect the next time the user launches the application.

Granting Access to Explicit or Anonymous Users

Before you publish resources, decide how to configure user accounts so that as you publish applications in the wizard, you can select appropriate user access.

Granting Access to Explicit Users

An explicit user is any user who is not a member of the Anonymous group. Explicit users have user accounts that you create, configure, and maintain with standard user account management tools.

There are limitations on explicit users who log on to a server farm to run applications: administrators can specify the type of profile, settings, and other configurations for these users.
Important: Do not assign any explicit users to the Anonymous group.

Granting Access to Anonymous Users

During XenApp installation, Setup creates a special user group named Anonymous. By default, anonymous users have guest permissions. Publishing applications for this special Anonymous user group lets you completely eliminate the need for user authentication for those applications. When a user starts an application that is configured for anonymous users, the server does not require an explicit user name and password to log the user on to the server and run the application.

Anonymous users are granted minimal session permissions that include the following restrictions:

  • Ten-minute idle (no user activity) time-out
  • Logoff from broken or timed out connections
  • The user cannot change the password (none is required)
When an anonymous user session ends, no user information is retained. The server does not maintain desktop settings, user-specific files, or other resources created or configured for the user device.
Note: The anonymous user accounts that XenApp creates during installation do not require additional configuration. If you want to modify their properties, do so with the standard Windows user account management tools.

To configure shortcuts for user devices

Configure or modify the application shortcut presented to user devices on the Shortcut presentation page of the Application Publishing wizard. To modify the setting, from the Action menu, select Application properties and then select Shortcut presentation.
  1. To select a new icon for the application, click Change icon and use the options on the window.
  2. To organize applications within folders on the user device, under Client application folder, enter a folder name for this application. When users view their applications, this application is listed in the folder you entered.
  3. To specify the placement of the application shortcut, in the Application shortcut placement section, select one or more of these options:
    • Add to the client’s Start menu. Creates a shortcut to this application in the user’s local Start menu. A folder appears in the first pane of the Start menu in the location you select:
      • Place under Programs folder. This option creates a shortcut under the Programs folder of the local Start menu. If a folder structure is specified in the Start Menu Folder text box, the folder structure is created within the local Programs folder.
      • Start menu folder. The location of the shortcut within the Start menu (or Programs folder, if selected). For example, to have the application appear under a folder called “Reports,” enter Reports. For more than one level of folders, separate each folder name with a backslash; for example, “Reports\HR\survey.” If no folder structure is specified, the application is available from the top level of the Start menu.
    • Add shortcut to the client’s desktop. Creates a shortcut to this application on the user’s local desktop.

Changes take effect after the user reconnects or refreshes the user device.

To configure access controlled by the Access Gateway

If Access Gateway (Version 4.0 or later) is installed, use the Access Control page of the Publish Application wizard specify the type of connections that allow the application to appear in the list of published applications on the user device. To modify the setting, from the Action menu, select Application properties and then select Access control.

For example, if Access Gateway is installed and the application has software requirements, define a filter in Access Gateway and apply the filter to the published application using XenApp.

Important: To use this feature, set your servers that receive XML requests to trust those requests.

Use this page to view or modify connection types:

  • Allow connections made through Access Gateway Advanced Edition (Version 4.0 or later). This is the default. Select the type of connections that allow the application to appear in the list of applications:
    • Any connection. Allows connections made through Access Gateway (Version 4.0 or later), regardless of filters. This is the default.
    • Any connection that meets any of the following filters. Allows connections made through Access Gateway (Version 4.0 or later) that meet one or more of the connection filters specified in the list.

      To Add or Edit a filter, click the respective button and enter the predefined Access Gateway farm name and filter.

  • Allow all other connections. Allows all connections except those made through Access Gateway (Version 4.0 or later). This is the default.
Users who do not have the required software running on the user device cannot access the published application.

To associate published applications with file types

As you publish applications, you associate the published item with certain file types present in the Windows registry on the server. Associate published applications with file types initially from the Publish Application wizard. To modify the file types, from the Action menu, select Application properties and then select Content redirection.

By associating published applications with file types and then assigning the applications to users, you implement the following automatically:
  • Content redirection from user device to server. Users running a Citrix plug-in open all files of an associated type with a specific published application and delivery method. For example, when users double-click an email attachment, the attachment opens in an application based on the file type and delivery method set for those users.
    Note: If you do not want specific users to launch published applications automatically when opening published content, do not assign published applications associated with file types to those users.
  • Content publishing. Users connecting through the Web Interface or using the online plug-in open content published on servers with applications published on servers. For example, you publish a Microsoft Word document. When you also publish the Microsoft Word application, associate it with a list of file types (files with the .doc extension, for example), and assign it to a group of users, the published content is opened in the Microsoft Word application published on the server.
File type association is a two-step process. For example, if you want to associate Microsoft Word with the .doc file extension:
  • Publish a document of the Microsoft Word for Windows file type.
  • Publish the Microsoft Word application and associate it with the Microsoft Word for Windows file type. When users double-click the document from the user device, it opens in the Microsoft Word application published on the server. Users connecting through the Web Interface or using the online plug-in can open published content with published applications.
  1. Select one or more of the buttons to select the file types that you want the application to open when a user opens a file. Published applications can be associated with one or more file types.
  2. To list all file types associated with the application, click Show all available file types for this application. Clear the check box to display only the selected file types.

    When changing the available file types for an application, select this check box to display the superset of file types available, not just those selected when initially publishing the application.

    Note: When you associate a file type with a published application, several file extensions can be affected. For example, when you associate the Word document file type, file extensions in addition to the .doc extension are associated with the published application.

To update file type associations

File types are associated with applications in a server’s Windows registry. If you install and then publish applications after installing XenApp, you must update the file type associations in the Windows registry on the server. To verify which file types are associated with a published application, from the Action menu, select Application properties and then select Content redirection.

Use Update file types to associate these file types with the application in the server farm’s data store.

Important: Updating the file type association data for a farm can take a long time. It depends on the number and availability of servers, the number of streamed applications, and the availability of the streamed application file shares. If you do not have permission to access these file shares, an alert appears.

Update the file type associations in the data store if:

  • You installed an application but have not yet published it.
  • You plan to enable content redirection from user device to server or have users open published content using the application.
  • The data store does not already contain the file type associations. If you updated the file types from the registries of other servers hosting the application, the data store already contains the associations.
If needed, update file types for the farm or for an individual server:
  • In the console, select a farm in the left pane and from the Action menu, select Other Tasks > Update file types.
  • Select a server in the left pane and from the Action menu, select Other Tasks > Update file types from registry.

Choose which file types are opened with a published application. When you publish an application, a list of available file types appears on the Content redirection page. This list is current only if the data store was updated with the file type associations for the application. Update the data store from the registries of several servers containing an application to associate a complete set of file types with the application.

If you publish applications to be hosted on more than one server, be sure to update the file types on each server.

To configure alternate profiles

For streamed applications only, use this feature to add an alternate profile for connections that come from specific IP addresses. For example, use an alternate profile to allow one published application for users on either side of a WAN with file servers on their side. When you create an alternate profile, you create a duplicate of the primary profile that is located on a different file share, which is more accessible to the user device.

Note that if the alternate profile is different from the primary package, the user device may exhibit strange behavior.

To access this dialog box, from the Publish Application wizard, continue to the Alternate profiles page. Alternatively, select a published application in the left pane and from the Action menu, select Modify application properties > Modify all properties > Advanced > Alternate profiles.

When you click Add, enter the starting and ending IP range for which the alternate profile applies.

Specify the full path of the alternate profile or browse to locate the profile, such as a UNC: \\citrixserver\profiles\Adobe Reader\Adobe reader.profile. After you configure the range, user devices from IP addresses within the specified range access the applications from the alternate profile instead of from the default profile.

To pass parameters to published applications

Use the Location page of the Publish Application wizard to enter the command line and pass parameters to published applications. To modify the setting, from the Action menu, select Application properties and then select Location.

When you associate a published application with file types, the symbols “%*” (percent and star symbols enclosed in double quotation marks) are appended to the end of the command line for the application. These symbols act as a placeholder for parameters passed to user devices.

If a published application does not launch when expected, verify that its command line contains the correct symbols. By default, XenApp validates parameters supplied by user devices when the symbols “%*” are appended. For published applications that use customized parameters supplied by the user device, the symbols “%**” are appended to the command line to bypass command-line validation. If you do not see these symbols in a command line for the application, add them manually.

If the path to the executable file includes directory names with spaces (such as “C:\Program Files”), you must enclose the command line for the application in double quotation marks to indicate that the space belongs in the command line. To do this, follow the instructions below for adding quotation marks around the %* symbols and then add a double quotation mark at the beginning and the end of the command line. Be sure to include a space between the closing quotation mark for the command line and the opening quotation mark for the %* symbols.

For example, change the command line for the published application Windows Media Player to the following:

“C:\Program Files\Windows Media Player\mplayer1.exe” “%*”

To reduce user privileges for a streamed application

For applications configured to stream to client devices, only, use this setting to reduce the user privileges for the application, thus reducing security risks. From the User privileges page of the Publish Application wizard or from the Action menu, select Modify application properties > Modify all properties > User privileges.

Important: Before you select this option, test the application with a limited access configuration. Some applications expect users to have elevated privileges and might fail to operate correctly when launched by users with a least-privileged user account.

Select Run application as a least-privileged user account (not selected by default). This setting configures all users, even those with an administrator account, to run the application with normal user privileges.

For more information about least-privileged user accounts, search the Microsoft Technet Web site.

To configure application limits and importance

When a user starts a published application, the plug-in establishes a connection to a server in the farm and initiates a session. If the user then starts another published application without logging off from the first application, the user has two concurrent connections to the server farm. Use this page to limit the number of concurrent connections that users can make.

You can configure application limits and importance from the Publish Application wizard Limits page, or from the Action menu > Modify application properties > Modify all properties > Advanced > Limits.

Under Concurrent instances, select from the following options:
  • Limit instances allowed to run in server farm and then enter the numerical limit in Maximum instances
  • Allow only one instance of application for each user

If Preferential Load Balancing is available in your XenApp edition, this setting (along with the session importance policy setting) determines the Resource Allotment associated with the session. The higher the Resource Allotment of the session, the higher the percentage of CPU cycles allotted to it.

In the Application Importance list box, set the priority that is used with the Session Importance setting to determine the level of service for the session in the XenApp farm: High, Normal, and Low.

To configure audio and encryption options for published applications

For applications published for an online connection, use the Client options page of the Publish Application wizard to configure the Citrix plug-in audio and encryption options for when users connect to a published application. To modify the setting, from the Action menu, select Application properties and then select Client options.

The settings that Citrix plug-ins use to communicate with a published application vary according to the type of plug-in. The Citrix online plug-in and Web Interface automatically use the settings you specify here to communicate with this published application.

You can set the encryption level for communications in multiple places in XenApp and your Windows operating system. If a higher priority encryption level is set elsewhere, the settings that you specify can be overridden. The most secure setting out of the following settings is used:

  • The setting in Remote Desktop Server Configuration and/or the setting in Citrix Connection Configuration Tool (Mfcfg.exe)
  • The policy setting that applies to the connection
  • The application setting (that is, the level you are setting in this dialog box)
  • The Microsoft Group Policy

The encryption settings specified here when publishing an application should be at the same level as the encryption settings you specified elsewhere. That is, any encryption setting you specify in the Remote Desktop Server Configuration tool or connection policies cannot be higher than the application publishing setting.

If the encryption level for an application is lower than any settings you specified for Remote Desktop Server Configuration and connection policies, those settings override the application settings. If the minimum requirements check box is selected and the plug-in connection does not meet the most restrictive level of encryption, the server rejects the connection when the plug-in tries to connect to the application. If the minimum requirements check box is selected, the plug-in setting is always used. However, the plug-in setting must be as secure as the server setting or the connection is denied.

If you select Minimum requirement under the Encryption list box, plug-ins can connect to the published application only if they are communicating using the specified level of encryption or higher. After you set this encryption level on the server, any plug-ins connecting with that server must connect at that encryption level or higher.

If a plug-in is running on a 64-bit computer, only basic encryption is supported. In this situation, setting a level of encryption higher than Basic and selecting the minimum requirements check box prevents plug-ins from connecting.

  • Select Client audio options:
    • Enable legacy audio. Select this option to allow audio support for applications to which HDX MediaStream Multimedia Acceleration does not apply.

      Note: By default, audio is disabled on the user device. To allow users to listen to audio in sessions, turn on audio or give the users permission to turn on audio themselves in the plug-in interface they are using, such as Citrix XenApp.
    • Minimum requirement. Select this option to allow plug-ins to connect to the published application only if they have audio support. The Minimum requirement check box under the Client audio list box applies only to the legacy audio setting. It does not apply to HDX MediaStream Multimedia Acceleration.
  • In the Connection encryption section, select one or more of the following options:
    • Select Enable SSL and TLS protocols to request the use of the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols for plug-ins connecting to the published application.
    • Select Encryption to apply the RC5 encryption level for the connection.
  • In the Printing section, select or clear Start this application without waiting for printers to be created. Selecting this option can allow the plug-in to connect faster. However, if you select this option, the printers may take a few seconds to be created; do not select this option for applications that print to the printer immediately after being launched.

To configure application appearance

Define how the application appears to the user through the Appearance page of the Publish Application wizard, or from the Action menu, select Application properties and then select Appearance.

  • To set the default window size, select the Session window size. Specify window size as a standard resolution, custom resolution, percentage of the screen, or full screen.
  • To set the color depth for the application, select the Maximum color quality. The available options are Better appearance (32-bit), Better speed (16-bit), or 256-color (8-bit).
  • To hide the application title bar and maximize the application at startup, change the setting in the Application Startup Settings.

To disable or enable a published application

Take published applications offline temporarily or indefinitely when you are maintaining a published application, such as applying an upgrade or a service pack to it. While an application is offline, it is not accessible to users. You can disable multiple applications simultaneously.

You can initially disable an application as you publish it in the publishing wizard or enable or disable it anytime from the console.

  • From the Publish Application wizard, continue to the Publish immediately page and select the Disable application initially check box. When checked, the application is published, but users cannot access it until you enable it.
  • In the console, select the application in the navigation pane, and from the Action menu, select Enable application or Disable application.
  • In the console, select the application in the navigation pane, and to modify the file types, from the Action menu, select Application properties and then select Name. On this page, select Disable application.
Note: If the Disable application initially option is selected and cannot be cleared, either the application requires configured users but none are specified, or the application is of a type that runs on a server (such as an installed application or streamed-to-server application) but no servers are specified.

To delete a published application

As you publish updated applications on your servers, delete the older or less-frequently used applications. Deleting a published application does not uninstall the application. It simply removes access to the application through plug-in connections. You can delete multiple applications simultaneously.
  1. In the left pane of the console, select the application.
  2. On the Action menu, select Delete application.

To move a published application to another folder

Use this option to move a published application to another folder in the console tree or to move servers to another server folder. Published applications can be moved only to Applications or folders under Applications. Similarly, servers can be moved only to Servers or folders under Servers. You can move multiple applications simultaneously.
  1. In the left pane of the console, select the application.
  2. On the Action menu, select Move to folder.
  3. Use the Select destination folder dialog box to change the location of the application.

Alternatively, drag applications into a new folder.

To duplicate published application settings

Use the settings of a published application as a template to publish other applications. For example, if you published an application with a specified user list, you might want to apply the same user list to a new application hosted on the same set of servers. If so, copy the first published application, change the name and location to those of the second application, and thereby publish a different application with the same user and server properties. You can duplicate multiple applications simultaneously.
  1. In the left pane of the console, select the application.
  2. From the Action menu, select Duplicate application and a copy of the application appears under the Applications node.
  3. Select the duplicated application and change the required properties.

To export published application settings to a file

Exporting published application settings to a file allows you to import these settings files and create new applications at a later time. First you export the desired settings to a settings file, and then you import this file to create new applications easily. In particular, import these settings files to overwrite the settings on a previously published application.

This export option offers choices to export a single application, the user list only, or server list only.

A Citrix administrator requires the View permission for the application folder in which the application resides to export published application settings.

  1. In the left pane of the console, select the application whose settings you want to export. To export multiple published application settings to a file simultaneously, in the right pane of the console, press CTRL and select the names of the applications you want to export.
  2. From the Action menu, select Other Tasks > Export application settings to a file. Select what to export:
    • Entire Application. Exports the application and all the settings associated with the published application to an .app file. If you choose this option, you can export settings from multiple applications; select them from the left pane of the console before selecting the export task.
      Important: If application settings are exported as a batch, they must be imported as a batch.
    • Server List Only. Exports only the list of configured servers for the application to an ASL file, including any per-server command-line overrides, if applicable. Then select an application and import the server list, replacing the existing server list. Alternatively, import this list of servers when publishing an application by clicking Import from file on the Servers page of the Publish Application wizard.
      Note: This task is available only for applications that have servers associated with them. For this reason, this task is unavailable for published content or streamed-to-client applications. You can export the server list associated with one published application only.
  3. Settings files are saved in XML format. The settings associated with your published application are saved to a settings file with one of the following extensions: APP, AUL, or ASL. The file name is the same as the application by default. For example, if you choose to export all the application settings of a published application called Notepad123, the default file name for the exported application settings file is Notepad123.app.

To import published application settings from a file

After you export published application settings to a file, use them to create a new application or alter the user or server settings of a previously published application.

Citrix administrators require Published Application permissions for the application folder in which the application resides to import application settings.

  1. In the left pane of the console, select either the folder into which you would like to place a new published application or the published application whose user or server settings you want to change.
  2. From the Action menu, select Other Tasks > Import application settings from a file.
  3. Use the Open dialog box to locate the settings file you want to import.
    • If you selected a folder in Step 1 of this procedure and an APP file in Step 2, the new application appears under the folder you selected.
    • If you selected a previously published application in Step 1 and either an ASL or AUL file in Step 2, click Yes to confirm that you want to overwrite existing settings. The imported ASL or AUL file updates the server settings or user settings of the application, respectively.
Note: If any of the servers or users that were exported for a published application cannot be imported, a warning message appears identifying the list of users or servers that could not be imported. You either proceed or cancel the import at that point. Cancelling the import cancels the entire import operation. This situation might occur if a server was removed from the farm after a published application was exported, if a user was removed from the domain, or if the administrator does not have proper permissions to publish the application on one or more of the servers that were exported.