You can start with a basic proof-of-concept deployment for Citrix Connector and then scale it for the following:
The same components are used for all deployment types. Be sure to review system requirements before starting a deployment.
The following proof-of-concept deployment diagram includes one Configuration Manager site, one Citrix Connector service machine, and one Citrix Delivery Site. For a non-production environment, the Citrix Connector service can reside on a separate VM, as shown, or on the Configuration Manager site server.
The Citrix Connector service communicates with the Configuration Manager SMS Provider and the Citrix Delivery Controller.
For a step-by-step guide through the entire process, from installation to deploying and publishing an application, refer to the Citrix Connector 7.5 Proof-of-Concept Deployment Guide.
Your deployment can include both Citrix Connector 7.5 and XenApp Connector 6.5 in either of the following mixed environments:
In a mixed environment, Citrix Connector displays a unified list of hosted applications from XenApp 6.5 farms and XenApp or XenDesktop Delivery Sites. You can configure maintenance windows for the mixed environment and deploy and publish applications from both environments.
Note: The XenApp 6.5 Connector supports only SCCM 2012 SP1 and SCCM 2012 R2. The XenApp 6.5 Connector does not support SCCM 2012 R2 SP1, SCCM 1511 or SCCM 1611.
The installers for Citrix Connector components will assist you in installing the correct combination of components in a mixed environment. For example, if you attempt to install the Connector 3.1 agent on a machine that has the XenApp 6.5 Connector agent, the installer will let you know that action is invalid and prevent the installation.
The following deployment diagram shows a mixed environment with one XenApp or XenDesktop Delivery Site and one XenApp 6.5 farm. One Citrix Connector service machine and one XenApp Connector service machine point to a single Configuration Manager site.
The two Connectors can reside on the same or separate VMs.
For a production environment we recommend that you do not install the Connector service on the Configuration Manager site server.
The Citrix Connector service and XenApp Connector service communicate with the Configuration Manager SMS Provider. The Citrix Connector service communicates with the Citrix Delivery Controller. The XenApp Connector service communicates with a XenApp host, which must be a Controller and not a worker machine.
The Connector high availability feature provides a reliable fault tolerance mechanism to ensure service continuity during disruptions in infrastructure components such as software, hardware, network, and power.
A high availability deployment includes multiple Connector service machines. The Connector optionally uses an active/passive model for high availability: Only one Connector service operates at a time per XenApp or XenDesktop Delivery Site, thus minimizing resource usage while ensuring operation continuity. If the active Connector service becomes inoperable, another Connector service automatically takes its place. Adding Connector service machines does not increase capacity, so a high availability deployment is recommended regardless of the size of your operation.
Active instance and related information are stored in the Configuration Manager database for persistence.
The following deployment diagram shows a mixed environment with one XenApp or XenDesktop Delivery Site and one XenApp 6.5 farm. Two Citrix Connector service machines and two XenApp Connector service machines provide high availability for their respective Delivery Site and farm.
The two Connectors can reside on the same or separate VMs. For a production environment we recommend that you do not install the Connector service on the Configuration Manager site server.
The Citrix Connector service and XenApp Connector service communicate with the Configuration Manager SMS Provider. Any number of Connector services can point to a Configuration Manager site server. Different Connector services can point to different SMS Providers per Configuration Manager site to improve fault tolerance by avoiding a single point of failure on the Configuration Manager side.
The Configuration Manager site database is also used to store the High Availability table, which contains information about which Connector service is currently active for a given Delivery Site or farm.
The Citrix Connector service communicates with the Citrix Delivery Controller. The XenApp Connector service communicates with a XenApp host, which must be a Controller and not a worker machine. For a Delivery Site with multiple Delivery Controllers, pointing multiple Connectors to one Delivery Controller does not provide high availability if the Delivery Controller becomes unavailable. Thus, be sure to use at least one Connector service per Delivery Controller.
The simplest way to use Citrix Connector to manage multiple Citrix Delivery Sites is to set up one or more Connector service machines for each of those Sites. You configure each Connector service independently as if the Site it points to is the only one in the enterprise. Citrix Connector automatically handles the existence of the other Citrix Delivery Sites and operates without conflict.
In all other respects, the following deployment diagram has the same setup as a mixed environment with high availability.
The following example deployment shows a large multi-geography site hierarchy that uses a Configuration Manager Central Administration Site (CAS) with three Primary Sites (Americas, Europe, and Asia).
When planning the deployment of Citrix Connector within a given Configuration Manager topology:
Secondary sites, not shown in the diagram, are managed by their parent Primary Site and therefore by the Citrix Connector service(s) on or pointing to their respective Primary Site. Installing Citrix Connector on Secondary Site machines serves no purpose and is not recommended.