Citrix Provisioning

Known issues and considerations

Known issues in 2203 LTSR CU2

The following issues are known in this release:

  • In Azure and GCP environments, you cannot set the authentication for the initial target device login process. [PVS-10409]

  • In Citrix Provisioning on Azure 2112 and later, some of the VMs fail to release vDisk lock even after shutting down the VMs. [PVS-10420]

Known issues in 2203 LTSR CU1

No new known issues have been observed in Cumulative Update 1.

Known issues in 2203 LTSR

The following issues are known in this release:

  • The vDisk Properties dialog sometimes display the wrong cache type. To see the correct cache type, in the Citrix Provisioning Console tree, select the vDisk Pool, or select the store, where the vDisk exists, and check the vDisk row. [PVS-9638]

  • When you try to delete an empty collection in Citrix Provisioning in azure and on-premises environment, Citrix Provisioning console displays the Azure VM deletion screen. [PVS-9746]

Previously reported issues

  • Citrix Provisioning does not support BIOS boot for Windows Server 2022. [PVS-9079]

  • Windows 2022 HyperV Gen 1 (BIOS) VMs are not supported as targets. [PVS-9079]

  • Windows 2022 as a host has limitations. Microsoft SCVMM 2019 for Hyper-V does not support Windows Server 2022 as a host. The Citrix Virtual Apps and Desktops Setup wizards and Stream VM wizard cannot create targets when using Windows Server 2022 as the hypervisor.

  • The Citrix Virtual Desktops Setup Wizard creates targets then boots them to format the cache drive. This process occurs quickly. Sometimes, a VDA reaches a state where it fails to shut down correctly. This process occurs because the VDA is initializing while the Citrix Provisioning Service and the provisioned device service simultaneously finish formatting the cache drive, then shuts down. To resolve this issue:

  1. In the virtual disk registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices, create a DWORD called RebootDelaySec.
  2. Assign a value to RebootDelaySec. This delays the time for shutdown by the value set in seconds. [HDX-14474]
  • When using the Streamed VM Setup Wizard to create VMs on a XenServer host while specifying 1 vCPU, the VM is created with 1 vCPU and a topology of 2 cores per socket. Creating VMs in this fashion prevents the VM from booting, while displaying the following error message in XenCenter: “The value ‘VCPU_max must be a multiple of this field’ is invalid for field platforms:cores-per-socket. As a result, XenCenter fails to boot the VM because the topology and vCPU configuration are incompatible. [PVS-1126]
Known issues and considerations