Product Documentation

Publish applications

May 02, 2016

The Connector enables you to easily publish applications to Receiver on any user device supported by XenApp or XenDesktop. The Connector does not require the Citrix deployment type for such publications and provides a wizard that steps you through the setup.

If, however, you want to deploy Citrix hosted applications to the Configuration Manager Application Catalog or Software Center, you must add the Citrix XenApp and XenDesktop deployment type to the publication.

You can set Configuration Manager policies to determine how an application is delivered to the user. Suppose that you deploy an application with three deployment types (MSI, App-V and the Citrix XenApp and XenDesktop deployment type) and then publish the application to a user collection that contains the Delivery Group. Configuration Manager processes the deployment types according to their priority order.

In addition, you can create requirement rules for deployment types. For example, you might create requirement rules to specify that the device used to launch an application determines the application version that opens. If the user makes the request from:

  • Their office computer, the MSI version opens.
  • A shared device, the App-V version opens.
  • A device co-located at a partner facility, the XenDesktop version opens to ensure no data remains on the partner device.

Another example: Suppose that you set the global condition "if not users primary PC" on the Citrix XenApp and XenDesktop deployment type. As a result, if a user is logged on to a shared kiosk machine, the Adobe Reader icon on the desktop launches a XenDesktop version of Adobe. If the user is logged on to their primary PC, the Adobe Reader icon on the desktop launches an MSI installed version of Adobe Reader.

For information about requirement rules and global conditions, refer to the Microsoft TechNet documentation for System Center Configuration Manager.

Publish applications to Receiver

After you deploy an application you can immediately perform the steps in this topic. The Connector delays publishing until the application is fully deployed to all active machines in the associated machine catalogs. Active machines are those that are online and not in XenApp or XenDesktop maintenance mode.

If an application is not fully deployed, the Citrix Application Publishing Wizard alerts you during its pre-flight checks.

  1. In the Configuration Manager console, expand Software Library > Application Management.
  2. Right-click Citrix Application Publications.
  3. Choose Create Publication.

    The Citrix Application Publishing Wizard opens.

  4. On the Application page, click Browse and select the application you want to publish. The list contains only the applications with one or more of these deployment types: MSI, App-V, or Script.
  5. Review the Introduction page to see if there are any steps you need to take before proceeding.
  6. If the Pre-flight Checks page includes any red icons you must resolve each issue and then click Re-run Pre-flight Checks.
    Tip: To expand the description of a pre-flight check, click its status icon.

    If a pre-flight check indicates that the application is not fully deployed, you can complete these steps. The Connector delays publishing until the application is fully deployed to all active machines in the associated machine catalogs.

  7. On the Delivery Groups page, select a group.
  8. On the General page, change the publication name if needed.
  9. On the Location page, accept the defaults unless you need to change them for your environment.
  10. On the Desktop Integration page, specify the user experience:
    Important: The settings on this page override those specified in Studio.
    • To change the application icon that displays in Receiver or in the Windows Start screen or menu, click Change icon.
    • To organize the shortcuts in subfolders in the Windows Start screen or menu, specify a folder path in Application category.
    • To add an application shortcut to Windows desktops, click the related check box.
  11. On the Visibility page, specify whether to show the application to a subset of users and then click Finish.

    By default, applications in Receiver are visible to all users in a Delivery Group.

  12. To check publication status: Right-click the publication, choose Properties, and review the status on the General page.
After you complete the wizard, you can edit the properties of the publication: In the Configuration Manager console, right-click the publication and then choose Properties.

Verify the publication

To see the published application in Citrix Receiver:

  • Log on to a device that is in the Delivery Group where you published the application and then log on to Receiver.

To view the published application in Citrix Studio:

  1. Log on to the Citrix Delivery Controller and then open Studio.
  2. In the Studio console, click Delivery Groups and then click the Applications tab.

    The Connector-published application should appear in the list. The application name is prefixed with ConfigMgr_ and the description includes KEYWORDS:ConfigMgr, which is used by StoreFront to prevent the application from appearing in Receiver on managed devices. The Connector also adds the tag ConfigMgr12 to the application metadata in Studio.

Deploy Citrix hosted applications to managed devices

Use this procedure to deploy Citrix hosted applications to the Configuration Manager Application Catalog or Software Center on devices managed by Configuration Manager. Users can also access the applications from any supported Citrix Receiver.

  1. In the Configuration Manager console, expand Software Library> Application Management and then click Applications.
  2. Add the Citrix XenApp and XenDesktop deployment type to the application: Right-click the application, choose Create Deployment Type, and complete the Create Deployment Type Wizard:
    1. On the General page: For Type, choose Citrix XenApp and XenDesktop.
    2. On the General Information page: Specify a Name for the application.
    3. On the Publishing page: Click the New or Add button, and then click through the remainder of the Create Deployment Type wizard.
  3. Give the Citrix XenApp and XenDesktop deployment type the highest priority to enable application delivery through the Application Catalog or Software Center:
    Tip: You can also use global conditions or requirements to control how deployment types are used.
    1. With the application still selected in the application list, click the Deployment Types tab.
    2. Right-click the Citrix publication you just created and then choose Increase Priority. Repeat as needed until that publication has a Priority of 1.
  4. Deploy the application to a delivery site in a user collection:
    1. In the application list, right-click the application and select Deploy.
    2. Across from Collection, click Browse, select the collection under User Collections > Citrix Delivery Sites > site > Delivery Groups, and then click OK and Next.
    3. On the Content page: Choose a distribution point.
    4. On the Deployment Settings page: For Action, choose Install. For Purpose, choose Available.

      The Available setting means that the application will be available in the Application Catalog and Software Center, where users can select it for installation. After the user installs the application, the Citrix deployment handler adds the application to the Windows Start screen or menu.

      The Required setting forces the application to install in the Application Catalog and Software Center. The Citrix deployment handler adds the application to the Windows Start screen or menu.

      For more information, including the requirements for Start screen or menu integration, refer to Configure Windows Start screen or menu integration.

    5. On the Summary page: To make the application immediately available, click Next. Otherwise, specify a schedule.
    6. Click through the remainder of the wizard.
  5. Verify the deployment:
    1. Log on to a managed user device and then open Configuration Manager Software Center.
    2. In the Available Software tab, select the application and then click Install. The application icon appears on the Start screen or menu.
    3. Verify that the application starts.

Configure Windows Start screen or menu integration

When you use the Citrix deployment type to publish an application to managed devices, the Connector interacts with Receiver in the background to add an application shortcut to the Windows Start screen or menu. That occurs only if the Configuration Manager agent determines that the Citrix deployment type is best for the application and the following requirements are met:

  • The standard edition of Receiver for Windows 4.1, 4.0, or 3.4 is installed.

    The Enterprise version of Receiver is not supported for Start screen or menu integration.

  • Receiver is installed with the Enable_SSON property set to Yes (the default value).
  • User devices and the StoreFront server (version 2.5 or 2.1) are configured as follows to support single sign-on:
    • The user is a domain user (not a local machine user).
    • The user device is on the same Active Directory domain as the Storefront stores.
    • Pass-through authentication is configured on the Storefront server.
    • The StoreFront server URL is in the Internet Explorer Trusted Zone.
    • If the store service uses HTTPS, the certificate and trust chain are correctly configured for the server being used.
  • Optional: To organize applications into categories on the Start menu, Receiver has the Registry entry UseCategoryAsStartMenuPath.

If those requirements are met, the Citrix deployment handler subscribes the application and places it on the Start screen or menu after these actions:

  • The user installs an application deployed as "available" from the Configuration Manager Application Catalog or Software Center.
  • Configuration Manager automatically installs an application deployed as "required."

Change how installation and uninstallation is reported

Updated: 2014-06-21

Applications installed from the Configuration Manager Application Catalog or Software Center are reported by the Connector deployment handler as installed.

Applications subscribed to by a Receiver user (and thus installed on the local computer) are reported by the Connector deployment handler, by default, as installed in the Application Catalog even if the application was not installed by Configuration Manager. With this behavior, an administrator can determine from Configuration Manager reporting that the computer is out of compliance. This default is controlled on the Windows user device by the registry key ReportSubscribedAppsAsConfigMgrInstalled.

In the case of an application that is installed by Receiver but not by Configuration Manager, that registry key affects installation and uninstallation as follows:

  • If ReportSubscribedAppsAsConfigMgrInstalled is True and the user tries to uninstall the application from the Application Catalog, the Application Catalog reports to the user that the uninstallation attempt failed. The user must unsubscribe the application from Receiver or use Windows Add/Remove Programs to uninstall it.
  • If ReportSubscribedAppsAsConfigMgrInstalled is False and the user installs the application from the Application Catalog, the Application Catalog reports to the user that the installation attempt succeeded. The application was, however, already installed on the computer. If the user then uses the Application Catalog to uninstall the application, it remains available in Receiver. In this scenario the user actions in Application Catalog are correctly reported.

    If ReportSubscribedAppsAsConfigMgrInstalled is False, applications subscribed to by a Receiver user (and thus installed on the local computer) are reported as not installed in the Application Catalog, if the application was also not installed by Configuration Manager.

The registry locations are:

HKLM\SOFTWARE\Citrix\Dazzle

HKCU\SOFTWARE[\Wow6432Node]\Citrix\Dazzle

Note: Applications delivered from older clients that support legacy Web Interface XenApp Services sites are not included in Configuration Manager reporting.

Streamline the deployment of mandatory applications published with the Citrix deployment type

Updated: 2014-06-21

In an environment that includes mandatory deployments to a user collection, a user in that collection can experience about a 90-second delay (for about 20 applications) during each log on while the Citrix hosted applications deploy to the user's desktop.

A best practice to reduce this overhead is to use roaming profiles for the user collection experiencing delays. Although a first-time user will experience the delay, applications will be available almost immediately for subsequent logons.

  1. Specify the share location to store a user's roaming profile: You need elevated domain privileges to perform this task.
    1. From within Active Directory Users and Computers, search for the user account and open RoamingUser Properties.
    2. Select the Profile tab and specify the location of the share where the user's roaming profile is to be stored in Profile path:

      \\ServerName\ShareName\UserID

      The users must have read/write access to this share. The user's account profile will be stored in a folder contained in the share you specified.

  2. Configure Citrix Receiver to also use this network share to store its information so that it will be available from any machine the user logs into:
    1. In the Windows Registry Editor, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle.
    2. If the entry Local does not exist, create it: Right-click Dazzle, select New > String Value, enter a Value name of Local, and enter the Value data: %APPDATA%\Citrix\selfservice\local
  3. Restart Citrix Receiver and log on the user.