Known issues and considerations
This Citrix Provisioning™ release includes the following known issue:
-
There can be issues with internal communications between provisioning servers during an upgrade, when some servers have been upgraded and some have not. This is due to the transition to an improved internal communications protocol between servers.
If you have targets booting from virtual disks in private image mode, or targets booting in maintenance mode, they may not connect or reconnect properly. Citrix recommends not having any of these targets streaming during the upgrade. The Configuration Wizard can display a warning about these targets when you run it the first time after upgrading.
Additionally, some management commands may fail with communication errors during the upgrade.
When all the servers have been upgraded, there are no longer any communication issues expected. [PVS-13608]
-
Non-elevated processes cannot run Citrix Provisioning PowerShell commands on the Citrix Provisioning Server. [PVS-15020]
Previously reported issues
-
P2PVS cannot create a vDisk when the VM being imaged is booted with UEFI. As a workaround, use Imaging Wizard. For example, run
c:\\Program Files\\Citrix\\Provisioning Services\\ImagingWizard.exe P2vhdx win10 c:\\testto create a VHDX file namedwin10inc:\\test.When you use UEFI imaging, consider the following:
- You cannot specify individual volumes. UEFI imaging operates on the entire boot disk.
- UEFI imaging does not support multiple disks. The system images only a single boot disk configuration.
[PVS-14851]
-
When using the Configuration Wizard to create a new farm in an existing, empty database that is provided by Azure SQL Database, there are unexpected errors and the configuration step fails. The errors, found in the log file, say User does not have permission to alter database
database, the database does not exist, or the database is not in a state that allows access checks.These errors occur even when the database exists, is in a normal state, and the user has the necessary permissions.
There are no known issues when creating a new database for a new farm. If the permissions needed to create a database are a concern, use
DbScript.exe.[PVS-14672]
-
The Stream and SOAP services crash and do not start after installing Microsoft updates. To resolve the issue, check the event log in the Event Viewer > Application. If the log mentions about forest trust relationship information, do the following:
- 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]
- Set a DWORD registry value named
- From Citrix Provisioning version 2503.1, the support for running the Citrix Provisioning Services as Network Service is deprecated. This is because the following Citrix Provisioning features don’t work if you choose to run Citrix Provisioning Services as the Network Service account.
- KMS Activation Support
- Cached secrets clearing: Removes certain secrets from the vDisk when it is promoted to production
- Daylight Savings support: Ensures that domain trust is not lost when the daylight savings state changes
[PVS-13857]
- The Target Device Update BDM dialog doesn’t work if you select more than one NIC on the same Citrix Provisioning Server. [PVS-13647]
- 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] -
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]
-
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 CVAD Setup Wizard with a XenServer host, the provisioned VMs will not be bootable if the number of vCPUs chosen is not a multiple of the “Cores per socket” setting in the chosen VM template. You must pick a template that reflects the desired cores per socket and then choose a number of vCPUs that is a multiple of this. [PVS-1126]