Citrix Cloud Connector
The Citrix Cloud Connector is a Citrix component that serves as a channel for communication between Citrix Cloud and your resource locations, enabling cloud management without requiring any complex networking or infrastructure configuration. This removes all the hassle of managing delivery infrastructure. It enables you to manage and focus on the resources that provide value to your users.
Services that require the Cloud Connector
The Virtual Apps and Desktops service requires the Cloud Connector. Citrix Endpoint Management requires the Cloud Connector for enterprise connectivity to the Endpoint Management service. The Secure Browser service requires the Cloud Connector for authenticated external web apps.
Cloud Connector functions
- Active Directory (AD): Enables AD management, allowing the use of AD forests and domains within your resource locations. It removes the need for adding any additional AD trusts.
- Virtual Apps and Desktops publishing: Enables publishing from resources in your resource locations.
- Endpoint Management: Enables a mobile device management (MDM) and mobile application management (MAM) environment for managing device and app policies and delivering apps to users.
- Machine catalog provisioning: Enables provisioning of machines directly into your resource locations.
Although operational, functionality might be reduced for the period of time that the connection to Citrix Cloud is unavailable. You can monitor the health of the Cloud Connector from the Citrix Cloud console.
Cloud Connector communication
The Cloud Connector authenticates and encrypts all communication between Citrix Cloud and your resource locations. Once installed, the Cloud Connector initiates communication with Citrix Cloud through an outbound connection. All connections are established from the Cloud Connector to the cloud using the standard HTTPS port (443) and the TCP protocol. No incoming connections are accepted.
Cloud Connector availability and load management
For continuous availability and to manage load, install multiple Cloud Connectors in each of your resource locations. Citrix recommends at least two Cloud Connectors in each resource location. If one Cloud Connector is unavailable for any period of time, the other Cloud Connectors can maintain the connection. Since each Cloud Connector is stateless, the load can be distributed across all available Cloud Connectors. There is no need to configure this load balancing function. It is completely automated.
As long as there is one Cloud Connector available, there will be no loss in communication with Citrix Cloud. The end user’s connection to the resources in the resource location does not rely on a connection to Citrix Cloud, wherever possible. This enables the resource location to provide users access to their resources regardless of a connection being available to Citrix Cloud.
Where to obtain the Cloud Connector
You can download the Cloud Connector software from within Citrix Cloud.
- Sign in to Citrix Cloud.
- From the menu in the top-left of the screen, select Resource Locations.
- If you have no existing resource locations, click Download on the Resource Locations page. When prompted, save the cwcconnector.exe file.
- If you have a resource location but no Cloud Connectors installed in it, click the Cloud Connectors bar and then click Download. When prompted, save the cwcconnector.exe file.
Where to install the Cloud Connector
Review the system requirements for supported platforms, operating systems, and versions.
Install the Cloud Connector on a dedicated machine running Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019. This machine must be joined to your domain and able to communicate with the resources that you want to manage from Citrix Cloud.
- Do not install the Cloud Connector, or any other Citrix components, on an Active Directory domain controller.
- Do not install the Cloud Connector on machines that are part of other Citrix deployments (for example, Delivery Controllers in a Virtual Apps and Desktops deployment).
For more deployment information, see the following articles: