Citrix DaaS

Known issues

Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) has the following known issues:

  • AWS preparation identity disk is available even after the machine creation process deletes the preparation VM. This issue is resolved. You can, however, delete any available preparation identity disk if there is no ongoing catalog creation or image update task. [PMCS-34500]

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


  • MCS machine catalog creation fails if you use Ephemeral OS disk to create a catalog using an image from a different subscription in Azure environment. [CCVADHELP-2600]

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

  • If you don’t upgrade to the latest Remote SDK before introducing Citrix Virtual Apps and Desktops version 2206 VDAs to the DaaS environment, you get the following error when running the cmdlets: Invalid enum value L7_34 cannot be deserialized into Citrix.Broker.Admin.SDK.FunctionalLevel. [PMCS-27248]

  • When creating a machine catalog, the volume worker bootstrapper VM (XenDesktop Temp) is not terminated correctly. As a result, an error occurs and the VM leaks. This occurs when Machine Creation Services (MCS) fails to recognize a device name associated with the HVM Linux bootstrapper. To resolve this issue, manually delete the volume worker bootstrapper (XenDesktop Temp) and its associated network interface. [PMCS-20277]

  • 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 current hypervisor communication implementation, Remote HCL, might throw exceptions by the target hypervisor platform. As a result, the connection between the cloud controller and the cloud connector fails and is then recreated. If any other Remote HCL operations are in progress and using the same connection, those connections can also fail. This causes machine power and registration states to fall out of sync. Other problems can arise as a result because the issue affects all types of Remote HCL operations, not just power states. Azure and GCP hypervisors hosting connections are not affected. These connections do not use Remote HCL. [CCVADHELP-483]

  • VMware machines fail to restart and cannot be forcefully restarted. This issue applies to all versions of VMware, including VMC on AWS. The problem occurs in machine catalogs that have persistent (dedicated) VMs, or, VMs that are power managed. To resolve this issue, use the New-Brokerhostingpoweraction cmdlet to restart or force restart your machines. [PMCS-15797]

  • 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 write-back cache. To disable write-back cache when you create a catalog, clear the Memory allocated to cache and Disk cache size check boxes 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]

  • Changing the name of an AWS Virtual Private Cloud (VPC) in the AWS console breaks the existing hosting unit in Citrix Cloud. When the hosting unit is broken, you cannot create catalogs or add machines to existing catalogs. [PMCS-7701]

  • When you try to use the ‘Restart’ option in 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]

  • When you deploy machines in an MCS catalog, the provisioning task can fail and the following error message appears: “Terminating Error: Desktop Studio closed.” The error details might show that no AD accounts were created. The catalog might complete successfully later without intervention. The issue is seen in large, complex deployments. [PMCS-8869]

  • Cloud Library cannot be used to assign resources in deployments that include on-premises StoreFront. [CCVADHELP-625]

For issues related to current VDAs, see Known issues.

Known issues

In this article