Known issues and considerations

Known issues in 2203 LTSR CU4

• P2PVS cannot create a vDisk when the VM being imaged is booted with UEFI. As a workaround, use Imaging Wizard. For example, run c:\\Program Files\\Citrix\\Provisioning Services\\ImagingWizard.exe P2vhdx win10 c:\\test to create a VHDX file named win10 in c:\\test .
  When you use UEFI imaging, consider the following:
  • You cannot specify individual volumes. UEFI imaging operates on the entire boot disk.
  • UEFI imaging does not support multiple disks. The system images only a single boot disk configuration.
• Attempt to upgrade Citrix Provisioning™ version 2203 LTSR to version CU4 might fail. As a workaround, upgrade Citrix Provisioning to version CU3 and then to version CU4.

Known issues in 2203 LTSR CU3

Known issues in 2203 LTSR CU2

• In Azure and GCP environments, you cannot set the authentication for the initial target device login process.
• In Citrix Provisioning on Azure 2112 and later, some of the VMs fail to release vDisk lock even after shutting down the VMs.

Known issues in 2203 LTSR CU1

Known issues in 2203 LTSR

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

Previously reported issues

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

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