Citrix Provisioning

Known issues and considerations

This Citrix Provisioning release includes the following new issues and considerations:

  • When you report a problem using the Citrix Provsioning Console, the SOAP Service must be run as an administrative user. [PVS-9429]

  • When running the configuration wizard silently (using the /a parameter), the wizard could fail to properly configure permissions on URLs that are used by the SOAP server and the Citrix Provisioning API server. This issue occurs in situations where the account requires the addition of permissions to the URL. In such cases the servers fail to start. This issue does not occur when running the configuration wizard interactively. To resolve this issue, run the configuration wizard again. [PVS-9443]

  • When running the configuration wizard silently (using the /a parameter), the wizard fails to properly configure the number of days between Active Directory computer account password updates. It continues to use the default value. This issue does not occur when running the configuration wizard interactively. [PVS-9460]

  • When running the configuration wizard silently (using the /a parameter), all of the credentials necessary for Service Principal authentication are not applied, and an error results, indicating that the tenant ID was not provided. A similar problem occurs with user-assigned Managed Identity authentication, resulting in an error indicating that the client ID was not provided. Other authentication modes are not impacted. The resolve this issue, use the configuration wizard interactively. [PVS-9513]

  • When provisioning workloads with Azure Cloud utilizing Azure SQL Database or Azure SQL Managed Instance, running the configuration wizard and using the Join existing farm option may result in an issue with selecting the database you wish to join. In such cases the provided credentials are valid on the database server, but there is no access to the database you want to join. As a result, the desired farm is not visible in the list of farms you can join. If this issue occurs, remove the credential’s principle from the database server. After removing the credential’s principle, subsequently running the configuration wizard prompts you for the database administrator credentials to complete the wizard process. You can then join the farm. This restores the principal to the database server. [PVS-9498]

Previously reported issues

  • Windows 11 is only supported on VMWare ESX 7.0 Update 2 (and later). [PVS-9057]

  • Windows 2022 HyperV Gen 1 (BIOS) VMs are not supported as targets. [PVS-9079]

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

  • (Release 2109 and earlier) When streaming to Linux target devices, if the firewall is enabled on the OS, 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:

  1. In the virtual disk registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices, create a DWORD called RebootDelaySec.
  2. Set a value, delay-to-shutdown, in seconds using a decimal or hexidecimal value. [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]

Citrix Cloud

When using the Citrix Cloud feature, consider the following:

  • To install the remote PowerShell SDK on the Provisioning server, you must uninstall the 5 Citrix Virtual Apps and Desktop snap-ins from the server, then install the remote PowerShell SDK.


This does not apply to workloads provisioned using Azure. For provisioned workloads on Azure, Citrix Provisioning automatically installs the remote PoSH SDK and not the 5 snap-ins.

Known issues and considerations