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!
Known issues
Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) has the following known issues:
- The Hybrid Azure AD VDA session fails to launch. [BRK-19284]
- After you create a backup and navigate to the Components tab for that selected backup, you see empty data for a component that has a resource after you click View component members. [STUD-31195]
- When trying to restore AWS, Azure, GCP, and XenServer hosting connections, the Restore count on the Restore Progress page is 1 and displays only the restore action result of XenServer. [STUD-31337]
- After you create a backup, the Hosting Connections component count on the Backup progress page is displayed as 0. [STUD-31950]
- In a VMware environment hosted on AWS, the MCS machine catalog creation fails if the master image is vTPM enabled. This issue affects all Citrix Virtual Apps and Desktops versions and is due to a problem in the VMware environment. For assistance, contact VMware support. [PMCS-38514]
- If you use Azure AD Domain Services: Workspace (or StoreFront) logon UPNs must contain the domain name that was specified when enabling Azure AD Domain Services. Logons cannot use UPNs for a custom domain you create, even if that custom domain is designated as primary.
For issues related to current VDAs, see Known issues.
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.