- What's new
- Fixed issues
- Known issues
- System requirements and compatibility
- Install Provisioning Services Software
- Device collections
- Target devices
- Using the Streamed VM Setup Wizard
- Deploying virtual desktops to VMs using the XenDesktop Setup Wizard
- Provisioning vGPU-enabled XenDesktop machines
- UEFI pre-boot environments
- Device collections
- Target devices
- Selecting the write cache destination for standard vDisk images
- Support for replicated vDisk storage
- Exporting and importing vDisks
- Releasing vDisk locks
- Copying and pasting vDisk properties
- Adding existing vDisks to a vDisk pool or store
- Backing up a vDisk
- Viewing vDisk usage
- Deleting cache on a difference disk
- Assigning vDisks and versions to target devices
- Updating vDisks
- Retiring or deleting vDisks
- Administrative roles
- Enable SQL Server Always On multi-subnet failover
- Managing for highly available implementations
July 2, 2018
The following issues are known at this release:
- When using the Citrix Cloud feature, consider the following:
- To install the remote PS SDK on the PVS server, you must uninstall the 5 XenDesktop snapins from the PVS server, then install the remote PS SDK.
- Once a Console is installed with the remote PS SDK and is used for provisioning, it no longer functions with on-premise XenDesktop.
- In the XenDeskop Setup Wizard, enter the IP address for the Citrix Cloud connector when it prompts for the XenDesktop Controller Address.
- Importing more than 150 devices for the Citrix Cloud Delivery Controller fails. [PVS-3655]
- For Windows 10 version 1803, the functionality cache in device RAM is not supported; a target device craches when it fails to use reserved memory from bootstrap. To resolve this issue, Citrix recommends using Cache in device RAM with overflow on hard disk.
- Before upgrading from PVS 7.17 to this version of PVS, you must manually uninstall CDF on the PVS Server, Console, and target devices.
- For Windows 10 1709, you must apply the OS update KB4093105, or later, before installing PVS components.
- In the PVS Console, the XenDesktop 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 PVS Console.
- Provisioning Services 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]
- BDM boot partition is not supported for VMWare vSAN configurations.
- After performing a silent install of a PVS client, subsequent upgrades using the Upgrade Wizard fail because the client fails to reboot. [PVS-2264]
- Existing Provisioning Services target devices cannot be added to an already existing XenDesktop catalog using the Machine Creation Services catalog in Studio. However, new PVS target devices created using the XenDesktop Setup Wizard can be added to the existing XenDesktop catalog from the PVS server. [DNA-53806]
- When using the PVS 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]
- In some localized environments (for example, Japanese) wrong characters are displayed when using the configuration image wizard. [PVS-1454]
- The XenDesktop Setup Wizard creates targets then boots them to format the cache drive; this process occurs quickly. In some cases, a VDA may reach a state where it fails to shutdown correctly because it’s initializing while the PVS service, Citrix PVS 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]