- Remain on the Citrix Virtual Apps and Desktops 1912 release, which has full support for public cloud providers. As an LTSR release, 1912 will not receive new feature updates, but has a support lifecycle of 5+ years and is regularly updated with security patches and fixes through Cumulative Updates.
- Migrate to Citrix Virtual Apps and Desktops service. The Citrix Virtual Apps and Desktops service offers full support for public cloud and on-premises workloads and the latest integration enhancements.
The Citrix Virtual Apps and Desktops service is regularly updated with the latest integration and performance optimizations with our key public cloud vendors, including Azure, AWS, and GCP. Reference the release matrix for more information.
How is this change enforced in CVAD 2003?
There is no technical enforcement in Citrix Virtual Apps and Desktops 2003; however, a Citrix Virtual Apps and Desktops 2003 site with public cloud workloads will be treated as an unsupported configuration. A future Current Release will enforce this change.
To ensure continuity, we recommended that customers with workloads in public clouds do not upgrade to CVAD 2003 and instead remain on CVAD 1912 or move to the Citrix Virtual Apps and Desktops service.
No, VMWare Cloud on AWS is a public cloud component. Customers who wish to use VMWare Cloud on AWS should use the Citrix Virtual Apps and Desktops Service, or remain on LTSR 1912.When will Citrix technically enforce this change?
Citrix plans to remove cloud-hosted workload functionality in a future Current Release. These upcoming changes will include multiple enforcement mechanisms including changes in meta-installer, Studio and VDA registration processes.
Are Controllers running in a public cloud supported with on-premises workloads?
When product enforcement is in place, it will focus on VDA workloads and does not impact controllers. A customer may run their Citrix Virtual Apps and Desktops infrastructure in public clouds and connect to on-prem workloads if they choose.
Can you run a 2003 Current Release VDA with a 1912 LTSR Controller?
The LTSR program requires all baseline components to be on the LTSR version. Using 1912 Controllers to provision CR VDAs in public clouds is not supported. Reference the LTSR FAQ for more information.
This forward-looking indication of plans for products is preliminary and all future release dates are tentative and are subject to change.
The development, release and timing of any features or functionality described for our products remains at our sole discretion and are subject to change without notice or consultation. The information provided is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making purchasing decisions or incorporated into any contract.
In this post I wanted to discuss the use of Citrix Enlighted Data Transport with Citrix Gateway Service. This is a feature that has been available with Citrix ADC for quite some time but it is a new feature for Gateway Service. I wanted to take you through step by step on how to configure EDT and Adaptive Transport with Gateway Service, as well as discuss any system requirements that are needed to get you up and running.
What is Adaptive Transport
Adaptive transport is a proprietary transport protocol that functions well on highly latent networks, which TCP alone finds challenging. This protocol is adaptive and can switch to TCP or UDP based on network conditions in order to ensure the best user experience for users using HDX.
Enlighted Data Transport System requirements
- VDA 1912 or later
- Rendezvous protocol must be enabled and working ( We cover this next)
- Ports UDP 443 and TCP must be open outbound from VDA to the Internet
- Adaptive Transport must be enabled
- EDT is supported with all supported OS’s. Citrix do recommend the use of Windows 10 and Windows 2019 when running EDT with Citrix Gateway Service
- Latest Workspace App Version ( 1908 or above for Parallel connections)
Configuring Rendezvous Protocol
When you are configuring Rendezvous protocol for use with Citrix CVAD Service the following is required.
- VDA 1912 or later
- Enable the Rendezvous protocol in the Citrix policies in Studio
- The Cloud Connectors must obtain the VDA’s FQDN when brokering a session. This can be achieved by using the the following commands in Powershell:
- asnp citrix*
- Get- XDAuthentication
Set the DNS Resolution to True
Set-Brokersite -DNSResolutionEnabled $True
To check that the DNS Settings are configured correctly – Type Get-Brokersite
The DNS Resolution should now be set to True.
Citrix Policy Requirements
Now that the DNS settings are complete, we need to ensure the Citrix Policies are also set for Rendezvous protocol. (The Rendezvous protocol allows HDX sessions to bypass the Citrix Cloud Connector and connect directly and securely to the Citrix Gateway service.)
Please see more detail here: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops-service/hdx/rendezvous-protocol.html
To set the Citrix policy, Open Citrix Studio and create a new policy for Rendezvous protocol. How to clear pc ram cache.
Click enable , and also enable Adaptive transport.
Lets also set up Session Reliability setting, as our final policy requirement. Enabling Session Reliability will allow users to automatically reconnect to Citrix sessions after a disruption.
Now that Rendezvous protocol is setup, lets move on to complete the setup to allow for the use of EDT.
Open Microsoft Group Policy Manager, and create a policy that will allow for you to set the Cipher Suite for the VDA workloads. Choose Computer configuration, Network, SSL Configuration, SSL Cipher Suite Order.
Lets now check if the settings are working as expected
Citrix Cloud Connectivity
Within the HDX session, launch a desktop and open powershell
Citrix Cloud Console
The transport protocols used are displayed as below when successfully using EDT
Citrix Cloud Gcps
It is also possible to check via Director