Product Documentation

Fixed issues

Dec 28, 2015

Compared to: Provisioning Services 7.7

Provisioning Services 7.8 contains all fixes that were included in Provisioning Services 7, 7.1, 7.6, and 7.7, plus the following, new fixes:

Console Issues

  • When a help desk administrator creates new virtual machines (VMs) from a standalone Provisioning Services Console through the XenDesktop Setup wizard, attempts to start a target device from a BDM partition can fail and cause an incorrect IP address for the logon server to appear.

    [#LC3911]

  • Installing the Provisioning Services Console sets the following registry key to " 1." This can cause other .NET applications to try to use the wrong version of the Framework and possibly fail:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
    Name: OnlyUseLatestCLR
    Type: REG_DWORD
    Data: 1

    [#LC4197]

  • Attempts to create virtual machines (VMs) by using the XenDesktop Setup wizard or the Streamed VM Setup wizard might fail in a Microsoft System Center Virtual Machine Manager (SCVMM) environment. With this fix, the fully qualified domain name (FQDN) of the host is used in the commands instead of short name.

    [#LC4230]

  • The XenDesktop Setup wizard might fail to create Provisioning Services target devices in System Center Virtual Machine Manager (SCVMM) 2012 environments.

    [#LC4256]

  • Attempts to connect to VMware Vsphere Hypervisor 5.1 by using the Streamed VM Setup wizard or the XenDesktop Setup wizard fail if User1 and User2 are configured to use different ports.

    To use a different port to connect to the VMware ESX server, you must create the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices\PlatformEsx
    Name: Port
    Type: DWORD
    Value: <port_number>

    [#LC4283]

  • SSL connections between the XenDesktop Setup wizard and XenServer fail.

    [#LC4377] 

Server Issues

  • After installing the server and the target device, there is a significant increase in the Write Cache usage.

    [#LC1001]

  • Attempts to mount a vDisk on a Provisioning Server fail unless the server has logical access to the vDisk.

    [#LC3835]

  • When a help desk administrator creates new virtual machines (VMs) from a standalone Provisioning Services Console through the XenDesktop Setup wizard, attempts to start a target device from a BDM partition can fail and cause an incorrect IP address for the logon server to appear.

    [#LC3911]

  • Machine creation fails with the XenDesktop Setup wizard in SCVMM environments if there is a trailing backslash (\) at the end of the VM storage path.

    [#LC4418]

Target Device Issues

  • After installing the server and the target device, there is a significant increase in the Write Cache usage.

    [#LC1001]

  • When using a BDM partition, target devices running on VMware do no attempt to log on to all servers in the list if the top-most server is unreachable.

    [#LC3805]

  • Automatic vDisk Updates do not run inventory updates on PvD enabled vDisks.

    [#LC3997]

  • ESX target devices utilizing a VMXnet3 network driver can experience a fatal exception, displaying a blue screen when using jumbo frames (frames with more than 1500 bytes of payload per frame).

    [LC4238]