Known issues and considerations
This Citrix Provisioning release includes the following new issues and considerations:
-
You can attempt to downgrade to an earlier Citrix Provisioning version without uninstalling the current version. The installer does not reject this action, however, this action isn’t supported. To downgrade to an earlier version, you must first uninstall the current version, restore the database, and then install the earlier version. [PVS-11294]
-
You can have read-only access to your Citrix Provisioning deployment if you enable the feature flag
ReadOnlyAdmin. To enable the feature flag:- Add a DWORD registry value named
ReadOnlyAdminunderHKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices\Features. - Set the value to
1.
[PVS-10872]
- Add a DWORD registry value named
Previously reported issues
-
Sometimes the Citrix Provisioning console might crash if you assign a user to a read-only administrator role and a device operator role (for example, read-only admin for a site and device operator for a collection under this site), and then try to add or modify data in the Target Device Properties.
To resolve this issue, do not assign a user to both read-only administrator role and device operator role. [PVS-10872]
-
In Azure and GCP environments, you can’t 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-10372]
-
When configuring boot devices using the Boot Device Management utility, you cannot proceed beyond the Specify the Login Server page if you:
- Select Use DNS to find the server.
- Select the Target Device is UEFI firmware check box.
- Enter an FQDN longer than 15 characters in the Server FQDN field.
- Clear the Target Device is UEFI firmware check box.
- Select Use static IP address for the Server.
You can continue to the next page if you clear the FQDN field or reduce the number of characters to fewer than 15. [PVS-9954]
-
In GCP environments, the Citrix Virtual Apps and Desktops Setup Wizard fails to remove server-side write cache files that are in the
WriteCachedirectory of the Citrix Provisioning store. The write cache files are used to format the write cache when you first start the VMs. Therefore, the files must be removed even if provisioning fails to avoid wasting disk space. To resolve this issue, do one or both of the following:- Ensure that the number of threads has a value of 20. Do one of the following:
- Set the value in the registry setting key:
Computer\HKEY_CURRENT_USER\Software\Citrix\ProvisioningServices\VdiWizard\MAX_VM_CREATE_THREADS_PER_HYPERVISOR <!--NeedCopy-->- Remove the registry setting key.
- Ensure that the store used for write cache files uses an SSD persistent disk instead of a Standard disk. [PVS-9870]
- Ensure that the number of threads has a value of 20. Do one of the following:
-
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:
- In the virtual disk registry key,
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices, create a DWORD calledRebootDelaySec. - Assign a value to
RebootDelaySec. This delays the time for shutdown by the value set in seconds. [HDX-14474]
- In the virtual disk registry key,
-
When using the Streamed VM Setup Wizard to create VMs on a Citrix Hypervisor 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]