Known issues and considerations
This Citrix Provisioning release includes the following new issues and considerations:
-
DbScript.exe fails to upgrade the database when you try to upgrade to Citrix Provisioning PVS 2206 or later. To resolve this issue, you must manually add the following lines between lines 2376 and 2377 of the DbScript.exe. Replace [YOUR_DATABASE_NAME] with your database name.
END GO DECLARE @ErrorVar INT SET @ErrorVar = @@ERROR if @ErrorVar != 0 BEGIN DECLARE @errVersion smallint SELECT @errVersion = version FROM DatabaseVersion PRINT N'Error updating from Version ' + CAST(@errVersion AS NVARCHAR(8)); PRINT N'Error = ' + CAST(@ErrorVar AS NVARCHAR(8)); SET NOEXEC ON return END USE [YOUR_DATABASE_NAME] DECLARE @version smallint SELECT @version = version FROM DatabaseVersion if @version < 172 BEGIN <!--NeedCopy-->[PVS-11063]
-
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 proceed 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, Citrix Virtual Apps and Desktops Setup Wizard fails to remove server-side write cache files that are located in the
WriteCachedirectory of 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 :
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.
-
When you try to delete an empty collection in Citrix Provisioning in Azure and on-premises environment, the Citrix Provisioning console displays the Azure VM deletion screen. [PVS-9746]
-
Citrix Provisioning does not support accelerated network in an Azure target device. [PVS-8871]
-
In Release 2109 and earlier, if the firewall is enabled on the OS, when you stream to Linux target devices, the UDP ports 6901-6902,6910-6930 must be opened manually on the target device. [PVS-9162]
-
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]
- 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]