Fixed issues

Provisioning Services 7.15 contains all fixes that were included in Provisioning Services 77.17.67.77.87.97.117.127.13 and 7.14, plus the following, new fixes:

Provisioning Services 7.15 CU3 (7.15.9)

Console Issues

  • The XenDesktop Setup Wizard might attempt to connect to an incorrect Hyper-V Host. The issue occurs when there are multiple clusters managed by the same System Center Virtual Machine Manager (SCVMM) server. [LC8415]

  • After you apply the Microsoft Hotfix KB3186539 on the Provisioning Server on some Japanese and Chinese versions of the Microsoft Windows operating system, the Boot Device Manager (BDM) platform cannot be created. [LC8743]

  • The Boot Device Manager (BDM) might fail to update on the XenServer that is created on the slave XenServer. [LC8964]

  • The Provisioning Services audit trail might show an incorrect text description for some entries. The data saved in the database for the entries is correct, but the description shown in the audit trail window is incorrect. [LC9481]

  • The Provisioning Services XIP library for VMware ESXi does not support TLS v1.2. [LC9629]

  • When you upgrade the Provisioning Services Server or the Console software, the PowerShell snap-ins might not be upgraded. [LC9718]

  • The Provisioning Server Unified Extensible Firmware Interface (UEFI) bootstrap might not accept boot menu input if there are multiple vDisk versions to choose from. The keyboard input becomes unresponsive during the PXE or BDM boot process of a physical target device that is booting in Maintenance mode. [LC9815]

  • When using the XenDesktop Setup Wizard, attempts to create the Boot Device Manager (BDM) partition fails when using the VMware ESX vSAN configuration. [LD0029]

Server issues

  • After promoting a vDisk to production, the vDisk might remain mounted on the Provisioning Services Server. [LC8051]

  • KMS handling is not applied to vDisk versions. [LC8147]

  • The same disk identifier is erroneously assigned to the vDisk residing in different stores when the existing vDisk was added using the “MCLI Add DiskLocator” command. [LC8281]

  • Provisioning Services fails to mount a vDisk when the VHDX logical sector size is 512 MB and the storage physical sector size is 4096 MB. [LC8430]

  • After you apply the Microsoft Hotfix KB3186539 on the Provisioning Server on some Japanese and Chinese versions of the Microsoft Windows operating system, the Boot Device Manager (BDM) platform cannot be created. [LC8743]

  • The Boot Device Manager (BDM) might fail to update on the XenServer that is created on the slave XenServer. [LC8964]

  • When you merge two or more vDisks at the same time, the MgmtDaemon.exe process might exit unexpectedly. [LC9123]

  • When you create a merged base vDisk version, the MgmtDaemon.exe process might exit unexpectedly with an exception code 0xc0000005. [LC9143]

  • The Provisioning Services audit trail might show an incorrect text description for some entries. The data saved in the database for the entries is correct, but the description shown in the audit trail window is incorrect. [LC9481]

  • After upgrading XenApp and XenDesktop from Version 7.13 to Version 7.15 in certain Active Directory environments, the local users might not be able to log on to the Provisioning Services Console. A timeout error message appears. [LC9542]

  • The Provisioning Services XIP library for VMware ESXi does not support TLS v1.2. [LC9629]

  • When you upgrade the Provisioning Services Server or the Console software, the PowerShell snap-ins might not be upgraded. [LC9718]

  • On Provisioning Services 7.14 and later versions, the Configuration wizard might fail to configure a farm when you are not using Active Directory. The issue occurs when the Provisioning Services is installed in a Workgroup environment. [LC9844]

  • When using the XenDesktop Setup Wizard, attempts to create the Boot Device Manager (BDM) partition fails when using the VMware ESX vSAN configuration. [LD0029]

  • After you upgrade Provisioning Services from Version 7.6.x to 7.15 LTSR CU2 and attempt to open the Provisioning Services Console, this error message might appear:

    An unexpected MAPI error occurred [LD0092]

Target Device Issues

  • Attempts to install a PVS Linux Target device might fail. The issue occurs when the required dependencies on Ubuntu are incorrect. [LC9478]

Provisioning Services 7.15 CU2 (7.15.3)

Console Issues

  • When using a Provisioning Server with the Finnish locale installed, attempts to create virtual machines using the XenDesktop Setup Wizard might fail and the following error message appears:

    “The bdmCreated field is not formatted properly, the correct format is YYYY-MM-DD HH:MM.” [LC7866]

Server Issues

  • When using a Provisioning Server with the Finnish locale installed, attempts to create virtual machines using the XenDesktop Setup Wizard might fail and the following error message appears:

    “The bdmCreated field is not formatted properly, the correct format is YYYY-MM-DD HH:MM.” [LC7866]

  • When the Boot Device Manager (BDM) is configured for the DHCP Discover, Offer, Request and Acknowledge (DORA) process, the process might not complete. The issue occurs when the DHCP relay sends the “OFFER” packet as a UNICAST packet. [LC8130]

  • The trust relationship of the Linux target device might be lost with Active Directory, when the machine account password for the target device expires. [LC8331]

  • Target devices cannot start correctly and as a result keep on restarting. [LC8358]

  • A target device that is part of a Delivery Group fails to boot after upgrading from a previous PVS version. [LC8378]

  • The XenDesktop Setup Wizard might attempt to connect to an incorrect Hyper-V Host. The issue occurs when there are multiple clusters managed by the same System Center Virtual Machine Manager (SCVMM) server. [LC8415]

  • The response of the configuration wizard and Provisioning Services Console operations might be slow or the Console might time out in an Active Directory environment. [LC8692]

  • Target devices might randomly stop communicating with the Provisioning Server during the initial read operation from the personal vDisk (single I/O stage). [LC8745]

  • When you attempt to copy and paste the vDisk properties between two vDisks, the properties might not be pasted on the second vDisk. [LC8767]

  • This enhancement is a backport of functionality introduced in Provisioning Services 7.17. It is included in response to customer requests. For more information, see Enhanced multi-tier Active Directory group search. [LC9064]

  • This enhancement is a backport of functionality introduced in Provisioning Services 7.17. It is included in response to customer requests. For more information, see Enhanced multi-tier Active Directory group search. [LC9066]

  • The Stream Service might exit unexpectedly while the Provisioning Server appears to be down in the Servers node. [LC9138]

Target Device Issues

  • Target devices might become unresponsive. [LC7911]
  • A Unified Extensible Firmware Interface (UEFI) target device might experience a fatal exception, displaying a blue screen, on CVhdMp.sys with stop code 0x0000007E. This exception might occur when you start a UEFI target device from a vDisk configured with NIC teaming. [LC8548]

  • Target devices might become unresponsive. [LC8897]
  • Microsoft Windows 10 v1709 might experience a fatal exception, displaying a blue screen when present in private mode. [LC8979]

  • Microsoft Windows 10 v1709, 32 bit cannot start from a vDisk in private image mode. [LC8980]

  • Target devices that are running on Microsoft Windows 10 might become unresponsive at the Getting devices ready screen while restarting. [LC8844]

  • Target devices might become unresponsive at the Windows logo or the splash screen. [LC9104]

Provisioning Services 7.15 CU1 (7.15.1)

Console Issues

  • The XenDesktop Setup wizard might fail after creating a template virtual machine. [LC8018]

Server Issues

  • In a network environment where the MTU size is less than 1,500 bytes, the bootstrap file fails to download and target devices fail to start using the Boot Device Manager (BDM). This enhancement allows you to lower the MTU size to less than 1,500 byte by setting the following registry key. The enhancement is disabled by default:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PVSTSB\Parameters Name: MtuSize Type: DWORD Value: MTU size you want to configure in decimal. If the value is below 512, 512 bytes is used. If the value is larger than 1,500, 1,500 bytes (default) is used. The fix is disabled by default. If the value is set to 0, the fix is also disabled. [LC8474]

Provisioning Services 7.15

Console Issues

  • Editing the partition size using the imaging wizard does not work in PVS 7.1x. [#LC7967]

    The following Nutanix issues have been resolved in this release:

  • After provisioning an Acropolis hypervisor using the XenDesktop Setup Wizard, you cannot start the hosted machine using Boot Device… from the PVS Console.

  • PVS targets do not support Cache on Server and Cache in device RAM.

Server Issues

  • Server communication time out. In some cases, login times can become excessively long (for example, greater than 2 minutes). This can cause server timeout issues between the PVS Console and the SoapServer. By default, the timeout for such connections is 2 minutes. However, you can increase this value by modifying the registry value HOTKEY_LOCAL_MACHINE\Software\Citrix\ProvisioningServices ConnectionTimeout=<timeout in seconds>. If the login time is greater than approximately 4 minutes, users will also experience timeouts from the Microsoft MMC containing the PVS Console (these timeouts can be dismissed).

    One cause for this issue is unreachable domains in Active Directory, where there is a 30 second timeout applied each time an attempt to connect to an unreachable domain is made. This can quickly add up to several minutes if there are multiple unreachable domains. In general, unreachable domains are created by adding a test or experimental domain to Active Directory, then removing it at a later time. Although the domain is gone, it is still reported by Active Directory when enumerating domains or authorization groups.

    Unreachable domains can also be caused by a domain controller being temporarily shut down and disconnected from the network, so not all unreachable domains should be blacklisted.

    The best way to determine whether there are unreachable domains is by looking at the CDF trace for the PVS_DLL_ADSUPPORT module and checking for “Unreachable Domain” and “Server Referral” errors. If any of these are found, check the domains to ensure that they are not in use any more, and if not, add the domain names to the blacklist.

    The blacklist is a JSON format file called “%ProgramData\Citrix\Provisioning Services\blacklist.json”. For example:

    {

        ”Domains”:

        [

            ”sub.xs.local”,

            ”sb.xs.local”

        ]

    }

    where the two domains sub.xs.local and sb.xs.local will be excluded from domain and group enumeration. After the file is updated, you must restart the SoapServer and any running consoles in order to load the updated values. [LC6249]

  • Soap service crashes when adding a new store using the console. [LC8165]