Citrix Provisioning

Known issues

This release of Citrix Provisioning contains no new issues.

Previously reported issues

The following issues were reported in previous Citrix Provisioning releases and are applicable to the current release:

  • The MCSIO v1 CtxMcsWbc.sys driver causes a system to crash. To resolve this issue, Citrix recommends disabling the driver in Studio. [PMCS-2941]

Note:

This issue only occus with MCSIO v1. The CtxMcsWbc.sys driver was replaced in this version of Citrix Provisioning.

  • If Asynchronous I/O is selected for the virtual disk in environments using a VDA before version 2006, persistence of VDA metadata is lost. This includes updates to the Delivery Controller. [PMCS-11355]

  • A published image can crash when booting earlier versions of Citrix App Layering. This issue occurs in environments using Citrix Hypervisor.[UNI-79222]

  • 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 value. [HDX-14474]
  • When importing VHDX files published using App Layering into a Citrix Provisioning disk store, the operation may mistakenly report that an invalid disk is being used. This is due to additional period characters used in the date/time format embedded in the published file’s name. You can resolve this issue by renaming the file so that it contains only one period at the very end for the .VHDX file extension. In this case, the provisioned disk store successfully imports the disk file. [UNI-75902]

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

  • When using the Citrix Virtual Desktops Setup Wizard, the default VDA level is 7_9 even though there is a 7_20 VDA level. This behavior is the same in the Machine Creation Wizard in Studio. Also, the VDA level 7_20 in Citrix Virtual Desktops Setup Wizard is the same as the VDA level in Studio version 1811.

  • UEFI target devices do not support the List local hard disk in boot menu option. If you select this option in the boot menu, the system does not boot to hard disk for UEFI target devices. Instead, the system shows the boot menu again after timing out.

  • Before upgrading from version 7.17 to this version of Citrix Provisioning, you must manually uninstall CDF on the Provisioning Server, Console, and target devices.

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.

  • Once a Console is installed with the remote PowerShell SDK and is used for provisioning, it no longer functions with on-premises Citrix Virtual Apps and Desktops.

  • In the Citrix Virtual Desktops Setup Wizard, enter the IP address for the Citrix Cloud Connector when it prompts for the Citrix Virtual Apps and Desktops Controller Address.

  • In the Provisioning Console, the Citrix Virtual Desktops Setup Wizard cannot be used to connect twice in a row. Once the Wizard tries to connect to the Cloud Delivery controller once, regardless of connection success or failure, you must exit and close the Provisioning Console.

Known issues