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.
-
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.
Provisioning Services 7.15 CU8 (7.15.39)
Target Device
-
The imaging wizard and P2pvs cannot fully image UEFI windows if the partition layout is customized.
-
The PVS Device Service (BNDevice.exe) might consume a high percentage of CPU usage.
-
When you configure UEFI PXE with DHCP Option 17 through a custom port, a target device might fail to start.
Provisioning Services 7.15 CU7 (7.15.33)
Console
-
Attempts to create virtual machines using the XenDesktop® setup wizard might fail.
-
In the Citrix Provisioning console, attempts to copy and paste target device properties by using a mouse might fail.
Target Device
-
The imaging wizard and P2pvs cannot fully image UEFI windows if the partition layout is customized.
-
The PVS Device Service (BNDevice.exe) might consume a high percentage of CPU usage.
-
With this fix, Citrix Provisioning target devices can be installed using Microsoft System Center Configuration Manager (SCCM).
-
With this fix, you can install Citrix Provisioning target devices by using Microsoft System Center Configuration Manager (SCCM).
Provisioning Services 7.15 CU6 (7.15.27)
Console
-
Permission problems associated with site administrator and device administrator roles.
-
In the Citrix Provisioning console, attempts to copy and paste the target device properties by using a mouse might fail.
-
The XenDesktop setup wizard might fail with an error when the Microsoft SCVMM server and the Hyper-V cluster are present on different domains.
Server
-
Target devices might become unresponsive on XenServer. The issue occurs when the CPU usage is high.
-
Registry hive file in the virtual disk version (AVHD) was corrupted when KMS restore was performed as a remote operation.
-
Permission problems associated with site administrator and device administrator roles.
-
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.
-
Adding a machine resource using Studio results in an error message indicating that the provisioning server cannot connect to the specified port number.
Target Device
-
Registry hive file in the virtual disk version (AVHD) was corrupted when KMS restore was performed as a remote operation.
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.
-
Citrix Virtual Apps and Desktops setup wizard fails on GEN2 target devices when
useTemplateCache is enabled.
-
The
LimitCPUForMigration template setting is ignored.
-
When streaming target devices with Generation 2 virtual machines, Provisioning Servers might not be load balanced correctly.
-
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.
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.
-
Merging virtual disk versions that reside on the Resilient File System (ReFS) might take a long time on Windows Server 2016.
-
The Configuration wizard might fail to complete when the SQL mode1DB is greater than the default database.
-
The stream process (StreamProcess.exe) might exit unexpectedly when you switch the database from offline to online.
Target Device
-
Some target devices repeat the Citrix Provisioning reconnect login process after SQL server failover.
Provisioning Services 7.15 CU4 (7.15.15)
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).
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.
-
The Boot Device Manager (BDM) might fail to update on the XenServer that is created on the slave XenServer.
-
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.
-
The Provisioning Services XIP library for VMware ESXi does not support TLS v1.2.
-
When you upgrade the Provisioning Services Server or the Console software, the PowerShell snap-ins might not be upgraded.
-
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.
-
When using the XenDesktop Setup Wizard, attempts to create the Boot Device Manager (BDM) partition fails when using the VMware ESX vSAN configuration.
Target device issues
-
Attempts to install a PVS Linux Target device might fail. The issue occurs when the required dependencies on Ubuntu are incorrect.
Provisioning Services 7.15 CU2 (7.15.3)
Target device issues
-
Target devices might become unresponsive.
-
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.
-
Target devices might become unresponsive.
-
Microsoft Windows 10 v1709 might experience a fatal exception, displaying a blue screen when present in private mode.
-
Microsoft Windows 10 v1709, 32 bit cannot start from a vDisk in private image mode.
-
Target devices that are running on Microsoft Windows 10 might become unresponsive at the Getting devices ready screen while restarting.
-
Target devices might become unresponsive at the Windows logo or the splash screen.
Provisioning Services 7.15 CU1 (7.15.1)
Console Issues
-
The XenDesktop Setup wizard might fail after creating a template virtual machine.
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.
Provisioning Services 7.15
Console Issues
-
Editing the partition size using the imaging wizard does not work in PVS 7.1x.
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.
-
Soap service crashes when adding a new store using the console.
