-
-
-
WebSocket communication between VDAs and Delivery Controllers
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
WebSocket communication between VDAs and Delivery Controllers
This article outlines the steps to establish WebSocket communication between VDAs and Delivery Controllers, as an alternative to Windows Communication Foundation (WCF).
Step 1: Enable WebSocket on Delivery Controllers
-
Configure your site. For more information, see Create a site.
-
Install TLS certificates on each Delivery Controller present on your site. For more information, see Install TLS server certificates on Controllers.
-
Enable WebSocket Communication on each Delivery Controller by using the following command:
New-ItemProperty "HKLM:\SOFTWARE\Citrix\DesktopServer\WorkerProxy" -Name "WebSocket_Enabled" -PropertyType "DWord" -Value 1 -Force <!--NeedCopy-->
Note:
Ensure that you restart the Delivery Controllers after enabling WebSocket.
Step 2: Enable WebSocket on VDAs
-
Install the root and intermediate Certificate Authorities (CAs) on the VDAs to trust the Delivery Controllers.
-
Enable WebSocket communication for VDAs based on the VDA creation method:
-
Non-domain-Joined VDAs:
WebSocket communication is enabled by default. No additional configuration is required.
-
Domain-joined VDAs created using easy install:
Enable WebSocket by setting the following environment variables in
/opt/Citrix/VDA/sbin/ctxinstall.conf
before running the easy install script (ctxinstall.sh) initially.-
**CTX_XDL_DJ_ENROLLMENT_TOKEN_FILE= ‘ ’** – Controls WebSocket enablement and specifies the token file for VDA registration. The default value is **‘ ’**, meaning that WebSocket is disabled. To enable WebSocket on a domain-joined VDA, enter the path to the token file. -
**CTX_XDL_ENROLLMENT_TOOL_USING_LDAPS=’y n’** – Configures the enrollment tool to query either LDAP or LDAPS. By default, it queries LDAP (‘n’). To use LDAPS, set the value to ‘y’.
-
-
Domain-joined VDAs created using Machine Creation Services (MCS):
On the template machine, open
/etc/xdl/mcs/mcs_local_setting.reg
and add a command line similar to the following for WebSocket enablement:create -k "HKLM\Software\Citrix\VirtualDesktopAgent" -t "REG_DWORD" -v "CbpTransportVersion2" -d "0x00000001" --force <!--NeedCopy-->
This command creates or modifies the CbpTransportVersion2 registry key. By default, the value is 0 (WCF communication). To enable WebSocket communication on domain-joined VDAs, set the value to any non-zero value. After modifying the registry, restart the ctxvda service to apply the changes.
Tip:
On any domain-joined VDA, regardless of its creation method, you can use the CbpTransportVersion2 registry key to switch between WCF and WebSocket.
-
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation 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 Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.