-
-
WebSocket communication between VDA and Delivery Controller
-
-
Migrate workloads between resource locations using Image Portability Service
-
-
-
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 VDA and Delivery Controller
This article describes how to set up a WebSocket connection for communication between VDAs and Delivery controllers as an alternative to using WCF communication. It provides the benefit that only the TLS port 443 for communication from the VDA to the Delivery Controller.
Currently this is only available for MCS provisioned machines.
How it works
The following section describes the workflow for the WebSocket connection between a Delivery Controller and a VDA:
- The admins initiate the process by provisioning VDAs using the Machine Creation Service (MCS).
- During the MCS provisioning process, MCS generates public-private key pairs for each VDA and registers the public keys with the FMA trust service on the Delivery Controller. MCS saves the public-private key pair as a file under the identity disk on the VDAs.
- When the VDA machine boots up, the MCS agent installed on the VDA machine reads the key pair from the identity disk and writes this information to the VDA registry location.
- The broker agent installed on the VDA reads the key pairs from the registry and generates an SSL-enabled WebSocket request to the Delivery Controller with a service key authentication header signed by the private key.
- The delivery controller verifies the signed service key authentication header with the public key from the FMA trust service.
- Once the verification is complete, the system establishes the WebSocket connection between the VDA and the Delivery Controller.
WebSocket support
Procedure
Follow the instructions to set up a WebSocket connection:
- Create a machine catalog for AD-joined VDAs with MCS provisioning. For more information, see Create machine catalog.
- Create a delivery group and add your VDA to it. For more information, see Create delivery groups.
-
Enable a WebSocket connection on the VDA. Run the following PowerShell command on the VDA:
New-ItemProperty "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CitrixBrokerAgent\WebSocket" -Name "Enabled" -PropertyType "DWord" -Value 1 -Force <!--NeedCopy-->
-
To check if WebSocket is enabled, check the following registry key value. The value of
Enabled
must be 1.Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CitrixBrokerAgent\WebSocket <!--NeedCopy-->
Name: Enabled
Type: REG_DWORD
Value: 1
-
Share
Share
In this article
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.