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 7.5 and XenDesktop 7.5 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 7.5 and XenDesktop 7.5 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:
Another example: Suppose that you set the global condition "if not users primary PC" on the Citrix XenApp 7.5 and XenDesktop 7.5 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 2012 Configuration Manager.
The topics in this section describe how to publish applications.
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.
The Citrix Application Publishing Wizard opens.
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.
By default, applications in Receiver are visible to all users in a Delivery Group.
To see the published application in Citrix Receiver:
To view the published application in Citrix Studio:
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.
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.
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.
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 Enterprise version of Receiver is not supported for Start screen or menu integration.
If those requirements are met, the Citrix deployment handler subscribes the application and places it on the Start screen or menu after these actions:
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 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:
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.
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.