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:
-
In a VMware environment hosted on AWS, the MCS machine catalog creation fails if the master image is vTPM enabled. For VMware support, see Get Support. [PMCS-37603]
-
Monitor screens might not load if the Pendo URL,
https://citrix-cloud-content.customer.pendo.io/
is blocked. [DIR-18482] -
You get an error if you run a command with
XDHyp:\
in the remote PowerShell SDK. To resolve this issue:- Run a command with
Hyp
. For example:Get-HypServiceStatus
- Run a command with
XDHyp:\
. For example:Get-ChildItem XDHyp:\Connections\
[BRK-13723]
- Run a command with
-
After changes in the Citrix DaaS architecture in version 2209, the default icons for Windows desktops and for applications deployed before this release have changed to generic PC desktop icons. This change is only applicable to desktops and applications that are pointing to the default icon. If you want to change icons back to the Windows application default icon, run the following script using the Remote PowerShell SDK:
Get-BrokerApplication -IconUid 1 | Set-BrokerApplication -IconUid 0
. -
In Manage > Full Configuration, attempts to change the OS type for Azure catalogs fail with an error message. Changing the OS type for Azure catalogs is no longer supported even if you use PowerShell. [STUD-19819]
-
In Microsoft Azure environments, enabling Azure ephemeral OS disk and MCS I/O at the same time fails to create a machine catalog. However, for existing machine catalogs, you can still update a machine catalog, add or delete VMs, and delete a machine catalog. [PMCS-21698]
-
The drop-down arrow icon for the Average IOPS, Session Control, and Power Control buttons might not appear on the User Details and the Machine Details pages. However, the functionality works as expected. To view all the items on the menu, click anywhere on the button. [DIR-11875]
-
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.
-
When deploying to Azure and creating an MCS catalog version 7.9 or later with write-back cache enabled and the VDA installed on the master image is 1811 or earlier, an error occurs. Also, you cannot create anything related to Personal vDisk for Microsoft Azure. As a workaround, select a different catalog version to deploy to Azure, or disable the write-back cache. To disable write-back cache when you create a catalog, clear the Memory allocated to cache and Disk cache size checkboxes on the Machines page.
-
The Console link on Monitor > Machine Details does not launch the Machine Console in the Microsoft Edge 44 and Firefox 68 ESR browsers. [DIR-8160]
-
When you try to use the ‘Restart’ option in the Workspace App web or desktop, the ‘Restarting’ dialogue never closes and never reports success. The hypervisor shows that the machine has shut down but has not started. As a workaround, after some time the user can close the ‘Restarting’ dialogue and launch the desktop and the desktop must start. [BRK-5564]
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.