Known issues

The following issues are known at this release:

  • 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-premise Citrix Virtual Apps and Desktops.
    • In the Citrix Virtual Apps and Desktops Setup Wizard, enter the IP address for the Citrix Cloud connector when it prompts for the Citrix Virtual Apps and Desktops Controller Address.
  • 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.
  • For Windows 10 1709, you must apply the OS update KB4093105, or later, before installing Citrix Provisioning components.
  • In the Provisioning Console, the Citrix Virtual Apps and 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.
  • Citrix Provisioning supports Windows 10 Fall Creator v1709 with the following known issues:
    • Windows 10 32 bit v1709 cannot boot from a vDisk in private image mode. [LCM-3224]
  • After performing a silent install of a Citrix Provisioning client, subsequent upgrades using the Upgrade Wizard fail because the client fails to reboot. [#PVS-2264]
  • Existing Citrix Provisioning target devices cannot be added to an existing Citrix Virtual Apps and Desktop catalog using the Machine Creation Services catalog in Studio. However, new target devices created using the Citrix Virtual Apps and Desktop Setup Wizard can be added to the existing catalog from the Provisioning server. [#DNA-53806]
  • When using the Citrix Provisioning 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”. This 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]
  • The Citrix Virtual Apps and Desktop Setup Wizard creates targets then boots them to format the cache drive. This process occurs quickly. Sometimes, a VDA may reach a state where it fails to shut down correctly because it’s initializing while the Citrix Provisioning Device Service simultaneously finishes formatting the cache drive then shuts down the target. To resolve this issue, in the vDisk registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices, create a DWORD called “RebootDelaySec”. Set an arbitrary value, delay-to-shutdown, in seconds using a decimal value. [#HDX-14474]
  • The MCS IO driver may cause a system to crash. To resolve this issue, Citrix recommends disabling the driver in Studio. [#PMCS-2941]

Known issues

In this article