Citrix DaaS

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, is blocked. [DIR-18482]

  • You get an error if you run a command with XDHyp:\ in the remote PowerShell SDK. To resolve this issue:

    1. Run a command with Hyp. For example: Get-HypServiceStatus
    2. Run a command with XDHyp:\. For example: Get-ChildItem XDHyp:\Connections\


  • 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.

Known issues

In this article