-
-
Install Linux Virtual Delivery Agent for Amazon Linux 2, CentOS, and RHEL manually
-
Configure Delivery Controllers for XenDesktop 7.6 and earlier versions
-
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!
Configure Delivery Controllers for XenDesktop 7.6 and earlier versions
XenDesktop 7.6 and earlier versions require changes to support the Linux VDA. For those versions, a hotfix or update script is required. The installation and verification instructions are provided in this article.
Update Delivery Controller configuration
For XenDesktop 7.6 SP2, apply Hotfix Update 2 to update the Broker for Linux Virtual Desktops. Hotfix Update 2 is available here:
CTX142438: Hotfix Update 2 - For Delivery Controller 7.6 (32-bit) – English
For versions earlier than XenDesktop 7.6 SP2, you can use the PowerShell script named Update-BrokerServiceConfig.ps1 to update the Broker Service configuration. This script is available in the following package:
- citrix-linuxvda-scripts.zip
Repeat the following steps on every Delivery Controller in the farm:
- Copy the Update-BrokerServiceConfig.ps1 script to the Delivery Controller machine.
- Open a Windows PowerShell console in the context of the local administrator.
- Browse to the folder containing the Update-BrokerServiceConfig.ps1 script.
-
Run the Update-BrokerServiceConfig.ps1 script:
.\Update-BrokerServiceConfig.ps1 <!--NeedCopy-->
Tip:
By default, PowerShell is configured to prevent the execution of PowerShell scripts. If the script fails to run, change the PowerShell execution policy before trying again:
Set-ExecutionPolicy Unrestricted <!--NeedCopy-->
The Update-BrokerServiceConfig.ps1 script updates the Broker Service configuration file by using new WCF endpoints required by the Linux VDA and restarts the Broker Service. The script determines the location of the Broker Service configuration file automatically. A backup of the original configuration file is created in the same directory, with .prelinux appended to the file name.
These changes have no impact on the brokering of Windows VDAs configured to use the same Delivery Controller farm. A single Controller farm can manage and broker sessions for both Windows and Linux VDAs seamlessly.
Verify Delivery Controller configuration
When the required configuration changes have been applied to a Delivery Controller, the EndpointLinux string appears five times in the %PROGRAMFILES%\Citrix\Broker\Service\BrokerService.exe.config file.
From the Windows command prompt, log on as a local administrator to check:
cd "%PROGRAMFILES%"\Citrix\Broker\Service\
findstr EndpointLinux BrokerService.exe.config
<!--NeedCopy-->
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.