Fixed issues 编辑

Provisioning Services 7.15 CU9 (7.15.45)

Server

• Removing or marking down two vDisks in the Citrix Provisioning Console fails, with an error message A database error occurred. This error condition appears when you convert a character string to an unique identifier. [CVADHELP-18484]

• The stream process stalls. This issue occurs in environments where the SNMP server randomly sends a request packet, containing no data, to stream process ports. [CVADHELP-18600]

Provisioning Services 7.15 CU8 (7.15.39)

Server

• The TFTP service configured on a Provisioning Server might consume high memory. [CVADHELP-15299]

• With this fix, you can install Citrix Provisioning target devices by using Microsoft System Center Configuration Manager (SCCM). [CVADHELP-15749]

• The stream process (StreamProcess.exe) might fail to recover from hung threads. [CVADHELP-15775]

• With this fix, Citrix Provisioning adds NVMe controller support for target devices using ESX. The presence of the controller is determined on the Citrix Virtual Apps and Desktops Setup Wizard template. It is used when creating the write cache disk and the BDM disk. For BDM Update scenarios, Citrix Provisioning determines whether the controller exists on the provisioned VM and then updates the disk using the controller. [CVADHELP-15788]

• The Citrix Provisioning virtual disk might be forced to reconnect intermittently by the server. [CVADHELP-16457]

• After upgrading Citrix Provisioning Services from version 7.15 LTSR to version 1912 LTSR CU2, the available network interfaces might be missing from the TFTP configuration tool (Tftpcpl.cpl). [CVADHELP-16888]

• Attempts to merge the vDisk versions to a base image might fail causing this error message to appear:

  The parameter is incorrect. Error number 0xE00000057.

  [CVADHELP-16921]

Target Device

• The imaging wizard and P2pvs cannot fully image UEFI windows if the partition layout is customized. [CVADHELP-14553]

• The PVS Device Service (BNDevice.exe) might consume a high percentage of CPU usage. [CVADHELP-14870]

• When you configure UEFI PXE with DHCP Option 17 through a custom port, a target device might fail to start. [CVADHELP-16036]

Provisioning Services 7.15 CU7 (7.15.33)

Console

• Attempts to create virtual machines using the XenDesktop setup wizard might fail. [CVADHELP-13752]

• In the Citrix Provisioning console, attempts to copy and paste target device properties by using a mouse might fail. [CVADHELP-15568]

Server

• In a multi-homed PVS server environment, attempts to download the tsbbdm.bin file might fail. [CVADHELP-13948]

• Debug logs associated with target devices are not included in Always-on Tracing (AOT) or CDF traces sent to the Citrix Provisioning server. [CVADHELP-14829]

• You cannot view the Farm is already configured option when you run the Configuration wizard. The issue occurs after you upgrade Provisioning Services. [CVADHELP-14860]

• Attempts to open the Provisioning Services Console after restarting the Provisioning Server might fail with this error message:

  An unexpected MAPI error occurred

  [CVADHELP-15141]

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

• When you configure the Streamprocess parameters using the StreamProcess.cfg file, the stream process (StreamProcess.exe) might fail to start. [CVADHELP-15295]

• The TFTP service in the Provisioning server consumes large amounts of RAM. [CVADHELP-15299]

• VDAs fail to start in scenarios where DNS name resolution and BDM are used with Infoblox DNS and DHCP. [CVADHELP-15724]

• With this fix, you can install Citrix Provisioning target devices by using Microsoft System Center Configuration Manager (SCCM). [CVADHELP-15749]

• With this fix, Citrix Provisioning adds NVMe controller support for target devices using ESX. The presence of the controller is determined on the Citrix Virtual Apps and Desktops Setup Wizard template. It is used when creating the write cache disk and the BDM disk. For BDM Update scenarios, Citrix Provisioning determines whether the controller exists on the provisioned VM and then updates the disk using the controller. [CVADHELP-15788]

• Changes to scheduled updates you make through vDisk Update Management do not take effect until you restart the Citrix PVS Soap Server service. [CVADHELP-16410]

Target Device

• The imaging wizard and P2pvs cannot fully image UEFI windows if the partition layout is customized. [CVADHELP-14553]

• The PVS Device Service (BNDevice.exe) might consume a high percentage of CPU usage. [CVADHELP-14870]

• With this fix, Citrix Provisioning target devices can be installed using Microsoft System Center Configuration Manager (SCCM). [CVADHELP-15590]

• With this fix, you can install Citrix Provisioning target devices by using Microsoft System Center Configuration Manager (SCCM). [CVADHELP-15749]

Provisioning Services 7.15 CU6 (7.15.27)

Console

• Permission problems associated with site administrator and device administrator roles. [CVADHELP-13302]

• In the Citrix Provisioning console, attempts to copy and paste the target device properties by using a mouse might fail. [CVADHELP-13361]

• The XenDesktop setup wizard might fail with an error when the Microsoft SCVMM server and the Hyper-V cluster are present on different domains. [CVADHELP-13762]

Server

• Target devices might become unresponsive on XenServer. The issue occurs when the CPU usage is high. [CVADHELP-11365]

• Registry hive file in the virtual disk version (AVHD) was corrupted when KMS restore was performed as a remote operation. [CVADHELP-12690]

• Permission problems associated with site administrator and device administrator roles. [CVADHELP-13302]

• When you use a PowerShell command to create a bootable ISO file (boot.iso), the option to set the network interface index might not be present in the BDM PowershellSDK. [CVADHELP-14362]

• Adding a machine resource using Studio results in an error message indicating that the provisioning server cannot connect to the specified port number. [CVADHELP-13348]

Target Device

• Registry hive file in the virtual disk version (AVHD) was corrupted when KMS restore was performed as a remote operation. [CVADHELP-12690]

Provisioning Services 7.15 CU5 (7.15.21)

Console

• The UEFI devices that are configured for BDM are unable to use a non-default custom network port range. [LD0706]

• Citrix Virtual Apps and Desktops setup wizard fails on GEN2 target devices when useTemplateCache is enabled. [LD0900]

• The LimitCPUForMigration template setting is ignored. [LD1071]

• When streaming target devices with Generation 2 virtual machines, Provisioning Servers might not be load balanced correctly. [LD1241]

• Attempts to access the farm from the console might fail. The issue occurs when the user is a member of the provisioning administrative group in a domain that is different from the user’s domain. [LD1371]

Server

• Attempts to access the farm from the console might fail. The issue occurs when the user is a member of the provisioning administrative group in a domain that is different from the user’s domain. [LD1371]

• Merging virtual disk versions that reside on the Resilient File System (ReFS) might take a long time on Windows Server 2016. [LD1783]

• The Configuration wizard might fail to complete when the SQL mode1DB is greater than the default database. [LD1957]

• The stream process (StreamProcess.exe) might exit unexpectedly when you switch the database from offline to online. [LD1958]

Target Device

• Some target devices repeat the Citrix Provisioning reconnect login process after SQL server failover. [LD1822]

Provisioning Services 7.15 CU4 (7.15.15)

Console

• The System Center Virtual Machine Manager (VMM) was set up to manage multiple top level host groups. If you run the Citrix Virtual Apps and Desktops Setup Wizard and connect to a Hyper-V environment, this error message might appear:

  Cannot connect to the hypervisor - An item with the same key has already been added. [LD0047]

• With this fix, the New-PvsSite command might not contain -VirtualHostingPoolId, -VirtualHostingPoolName, and -XsPvsSiteUuid as mandatory parameters. [LD1209]

Server

• When an additional virtual hard disk (VHD) footer is assigned to a merged VHD, the file size of the merged base might increase. [LC9837]

• The BNTFTP.exe process might exit unexpectedly. The issue occurs when there is a security check failure or a stack buffer overrun. [LD0250]

• A Citrix Provisioning server installed on Windows Server 2012 and earlier might experience issues when merging an existing virtual disk version to a new merged base on a virtual disk with VHDX format. This issue occurs when a virtual disk is stored on a Resilient File System (ReFS) on a Windows Server 2016 or newer and accessed over Server Message Block (SMB). Merging virtual disk versions to a new merged base fails. The following error message might appear:

  The parameter is incorrect. Error number 0xE00000057. [LD0437]

• After upgrading Provisioning Services from Version 7.6 CU2 to Version 7.15 CU2, the target device might experience a fatal exception and display a blue screen. The issue occurs due to null pointer pointing to a personality string. [LD0546]

• The UEFI devices that are configured for BDM are unable to use a non-default custom network port range. [LD0706]

Target Device

• The Enable auto update controller policy might fail to take effect on a Citrix Provisioning Windows target VDA. The issue is due to the lack of network service permission, causing the Broker Agent service’s failure to access SavedListOfDdcsSids.xml in the persistent data location (d:\pvsvm). [LD0450]

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]

• 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 size is 512 MB and the physical storage size is 4,096 MB. [LC8430]

• When applying Microsoft Hotfix KB3186539 on servers running Japanese and Chinese versions of Windows, 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, 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 PVS 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. 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 bytes 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. Sometimes, login times can become excessively long (for example, greater than 2 minutes). This lapse can cause server timeout issues between the PVS Console and the Soap Server. 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 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. There is a 30 second timeout applied each time an attempt to connect to an unreachable domain is made. These connection attempts 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 later. Although the domain is gone, it is still reported by Active Directory when enumerating domains or authorization groups.

  Unreachable domains are 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. Check these traces 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 are excluded from domain and group enumeration. After the file is updated, you must restart the Soap Server and any running consoles to load the updated values. [LC6249]

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