Known issues and considerations
This Citrix Provisioning release includes the following new issues and considerations:
- While moving Citrix Provisioning Servers to a new or existing farm, if you move the last server out of the old farm (example, farm A) to another farm (example, farm B), then farm A’s database becomes inaccessible. You cannot use this farm (farm A in this case) again in the future. As a workaround, back up the
HKLM\Software\Citrix\ProvisioningServicesregistry key before moving the last server. [PVS-13371]
Previously reported issues
- If an admin is a member of multiple groups configured as Citrix Provisioning admins, then if any group is made Read-only, then all admins in that group become Read-only admins even if they are members of other groups that are not set to Read-only. [PVS-12930]
- Citrix Provisioning does not currently support IPv6 on Nutanix. However, while running the Citrix Virtual Desktops Setup Wizard to create VMs on Nutanix, you incorrectly get the option to select Targets use IPv6 checkbox on the Virtual machines page. [PVS-13060].
- The Citrix Virtual Apps and Desktops Setup Wizard sometimes fails to provision targets on Nutanix if the Auto-Add feature is enabled on the Citrix Provisioning console. [PVS-11745]
-
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:
- If you use IPv6-based streaming, then the streamed target acquires two IPv6 addresses from DHCP, out of which, one of the addresses shows up as a statically assigned address in Windows. You can also see an auto-configured address if IPv6 auto-configuration is enabled on the network. This auto-configured address also shows up as a statically assigned address in Windows. In addition to these, the streamed target is also allocated a link local address in Windows. [PVS-11858]
- 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 checkbox.
- Enter an FQDN longer than 15 characters in the Server FQDN field.
- Clear the Target Device is UEFI firmware checkbox.
- 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]
-
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 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]