Known issues and considerations
This Citrix Provisioning release includes the following new issues and considerations:
- The help text displayed using
Get-Help -examples New-BootDeviceManagerdoes not include information on the new parameters added to support IPv6 addresses. [PVS-13369] - 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].
- If you want to create VMware target VMs, that stream using IPV6, from a template that was created from a VM that was run previously, then all the target VMs get the same DHCP Unique Identifier (DUID) value. To resolve the issue, use a template that’s created from a VM that was never run before. This action ensures that the VMware target VMs get a unique DUID value each time the target VMs are run. [PVS-11891]
- In Citrix Provisioning version 2311 and earlier, IPv6 in Citrix Provisioning streamed Windows targets that use IPv4 streaming is not supported. [PVS-12578]
- Upgrade from Citrix Provisioning version 2308 to Citrix Provisioning version 2311 is not supported on Azure. If you try to upgrade, the Citrix Provisioning console and server are left in a broken state that can only be cleaned up using a tool like MSIZap. [PVS-12137]
- When your farm is joined to a Citrix Virtual Apps and Desktops site, the Configuration Wizard might not properly validate that the user has sufficient privileges on the Delivery Controller that is selected. You might get the privilege errors only during the finish step. Therefore, always ensure that you have Machine Catalog Administrator or higher privileges in the Citrix Virtual Apps and Desktops site. [PVS-12155]
- 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]
- While running the Configuration Wizard to create a new farm, if you provide database administrator credentials that do not have dbcreator privileges, you are repeatedly prompted to provide different credentials without any message explaining the reason. To exit this condition, provide the required credentials or click Cancel on the Database Administrator Credentials dialog. [PVS-12032]
- Auto add field in the Options tab of the Farm Properties dialog doesn’t work for the targets configured to boot using UEFI even though the field is available on the UI. [PVS-12392]
Previously reported issues
-
The Stream and SOAP services crash and do not start after installing Microsoft January 2022 updates. To resolve the issue, check the event log in the Event Viewer > Application. If the log mentions about forest trust relationship information, do one of the followings:
- Apply the Microsoft fix based on your OS, Citrix Provisioning version, and version of the
.NETframework. For more information, see CTX338544. - Set a DWORD registry value named
SkipForestLevelTruststo1underHKLM\Software\Citrix\ProvisioningServiceson the Citrix Provisioning Server and restart the SOAP Server. With this workaround, Citrix Provisioning stops supporting multiple forest deployments.
[PVS-11591]
- Apply the Microsoft fix based on your OS, Citrix Provisioning version, and version of the
-
When running a BDM update in the Citrix Provisioning Console, an incorrect message The task cannot be performed on active Devices. Shut down the Devices before attempting to perform the task is displayed when the hypervisor is not accessible. [PVS-11587]
-
The Citrix Virtual Apps and Desktops Setup Wizard sometimes fails to provision BIOS targets on Nutanix if the Auto-Add feature is enabled on the Citrix Provisioning console. [PVS-11745]
-
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]
-
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 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]