Hotfix PVS710ServerConsoleWX64004 for PVS Server and Console 7.1 x64

Hotfix PVS710ServerConsoleWX64004 for PVS Server and Console 7.1 x64

book

Article ID: CTX142406

calendar_today

Updated On:

Description

Filename: PVS710ServerConsoleWX64004.zip
For: Provisioning Services 7.1. For additional information, including operating system requirements, see Requirements for Provisioning Services 7.1 on the Citrix Product Documentation site.
Replaces: CPVS71003
Date: July, 2015
Languages supported: English (US), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.01

Readme Revision History

VersionDateChange Description
1.01August, 2015Update installation instructions and documentation links
1.00July, 2015Initial release

Important Note(s)

  • This is a full release of the Server and Console components of Provisioning Services 7.1. You can use it to perform a new installation of each component in addition to upgrading an existing installation of the component.
  • Caution! This release may require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

Where to Find Documentation

This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, including supported operating systems and system requirements, see Provisioning Services 7.1 on the Citrix Product Documentation site.

New Fixes in This Release

The following issues are fixed since the release of Provisioning Services 7.1.

Console Issues
Server Issues

Console Issues

  1. After completing the XenDesktop wizard, the Machine Catalog in Studio is empty and the streaming IP address appears instead of the management IP address, which is incorrect. To use the management IP address, set the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices
    Name: UseManagementIpInCatalog
    Type: DWORD
    Value: 1

    [From PVS710ServerConsoleWX64004][#LC0125]

  2. In Version 7.1 of Provisioning Services, attempts to set a subnet mask of 0.0.0.0 when configuring bootstrap to use the Gateway/DHCP settings to set the subnet mask value at runtime fail and the following error message appears

    "Invalid Subnet mask."

    [From PVS710ServerConsoleWX64004][#LC0312]

  3. When running the Streamed VM Setup Wizard to add VMs to a Device Collection and if a hosting entry uses a different case format, the following error message appears:

    "To avoid creating a duplicate key, the Add or Set command was cancelled"
    Details:-
    Cannot insert duplicate key row in object 'dbo.VirtualHostingPool' with unique index 'IDX_VirtualHostingPoolSiteIdName'. The duplicate key value is (18df503c-c745-452a-89aa-3bbf431c7b33, livsvmv01.livdc.local).
    The statement has been terminated.

    [From PVS710ServerConsoleWX64004][#LC0348]

  4. The Xen Desktop Setup Wizard does not use the template boot properties when creating targets. To fix this, create the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices
    Name: UseTemplateBootOrder
    Type:REG_DWORD
    Data: 1

    [From PVS710ServerConsoleWX64004][#LC0382]

  5. When running the Streamed VM Setup Wizard, some Active Directory organizational units (OUs) might not appear in the wizard if the OU name contains special characters.

    [From PVS710ServerConsoleWX64004][#LC0393]

  6. Attempts to map a disk on the Provisioning Service server by using either MCLI.exe or the command "mcli-runwithreturn mapdisk -p disklocatorName=MyDiskLocatorName, sitename=MySiteName, storeName=MyStoreName" fail and the following error message appears:

    Object Reference not set to an instance of an object (MCLI command)

    Attempts to run the command "mcli-run unmapdisk" fails and shows the error message "An unexpected MAPI error occurred."

    [From PVS710ServerConsoleWX64004][#LC0786]

  7. When trying to create machines by using the XenDesktop Setup Wizard, the hard drive and the virtual DVD drives are placed in difference storage volumes, even though the hosting unit can only access one volume.

    [From PVS710ServerConsoleWX64004][#LC0918]

  8. The Notifier.exe process might experience an access violation and exit unexpectedly at random.

    [From PVS710ServerConsoleWX64004][#LC1199]

  9. If the Desktop Delivery Controller contains a port number in the uniform resource identifier (URI), when the XenDesktop Setup Wizard runs, the Microsoft Management Console (MMC) stops responding.

    [From PVS710ServerConsoleWX64004][#LC1248]

  10. The XenDesktop Setup Wizard fails when one of the Cluster Shared Volumes does not contain the StorageDisk location.

    [From PVS710ServerConsoleWX64004][#LC1807]

  11. If the account used to log on to the Provisioning Services console is not the same account used to install Provisioning Services, running the XenDesktop Setup Wizard fails with the following error:

    "Cannot connect to the XenDesktop controller at <address>. Some or all identity references could not be translated."

    [From PVS710ServerConsoleWX64004][#LC1952]

  12. In a Microsoft SCVMM environment, the XenDesktop Setup wizard does not assign a static MAC address to a non-streaming network adapter when the MAC address type in the template is static.

    [From PVS710ServerConsoleWX64004][#LC2459]

Server Issues

  1. The SOAP Service might exit unexpectedly while changing the vDisk license mode to Key Management Service (KMS).

    [From PVS710ServerConsoleWX64004][#LC0265]

  2. Attempts to use MAK activation for Microsoft Windows can fail and the following error message appears:

    "Confirmation ID not retrieved, check internet access."

    The issue occurs in scenarios where Microsoft Office is installed on the vDisk and the record of the Office product exists in the VAMT database. During activation, the Install-VamtproductKey command attempts to install the Windows product key for both Windows and Office and returns the error above. With his fix, there is  no more attempt to include Office in the MAK activation.

    Note: This fix does not provide support for Microsoft Office MAK. Provisioning Services still does not support MAK for Office. The only supported way of having Office on a PVS image is to use KMS for both Windows and Office.

    [From PVS710ServerConsoleWX64004][#LC0277]

  3. In Version 7.1 of Provisioning Services, attempts to set a subnet mask of 0.0.0.0 when configuring bootstrap to use the Gateway/DHCP settings to set the subnet mask value at runtime fail and the following error message appears

    "Invalid Subnet mask."

    [From PVS710ServerConsoleWX64004][#LC0312]

  4. The Target device might return broadcasted ARP reply packets during the bootstrap process, causing excessive network traffic.

    [From PVS710ServerConsoleWX64004][#LC0451]

  5. If there are five or more network adapters attached to the server, the following error messages appear:

    • Message processor timed out. Error number 0XE0070003.
    • No response received for successful send. Error number 0xA0070002.

    [From PVS710ServerConsoleWX64004][#LC0455]

  6. When using the network settings of the DHCP in bootstrap configuration, if the "Router" option in DHCP is not configured, a false default gateway IP address might appear in the Provisioning Services Target device.

    [From PVS710ServerConsoleWX64004][#LC0688]

  7. When installing the XenApp Enterprise and PVS Datacenter licenses on the Citrix License Server and starting the XenApp Target device from the vDisk, the PVS Datacenter licenses are not consumed in the License Management Console.

    [From PVS710ServerConsoleWX64004][#LC0707]

  8. With this release, the vhdUtil tool can rename a virtual disk chain and prepare the chain to be imported as a new disk. During renaming, the following actions occur:

    • Updates the disk header, footer, and timestamp.
    • Renames the PVP file, if it exists.
    • Creates an XML file based on the renamed chain that allows the renamed disk to be imported by the Provisioning Services console.

    [From PVS710ServerConsoleWX64004][#LC0722]

  9. Attempts to map a disk on the Provisioning Service server by using either MCLI.exe or the command "mcli-runwithreturn mapdisk -p disklocatorName=MyDiskLocatorName, sitename=MySiteName, storeName=MyStoreName" fail and the following error message appears:

    Object Reference not set to an instance of an object (MCLI command)

    Attempts to run the command "mcli-run unmapdisk" fails and shows the error message "An unexpected MAPI error occurred."

    [From PVS710ServerConsoleWX64004][#LC0786]

  10. After upgrading to Provisioning Services 7.1, if there are a large number of VDAs, it can take four to five hours to restart all VDAs.

    [From PVS710ServerConsoleWX64004][#LC0941]

  11. Target devices shows the correct number of retries, however the Provisioning Services console always shows zero retries.

    [From PVS710ServerConsoleWX64004][#LC1427]

  12. When adding Dynamic vDisks to stores, the server reports an incorrect Replication Status after adding the Dynamic vDisk to the second store.

    [From PVS710ServerConsoleWX64004][#LC1428]

  13. When copying and pasting properties between two virtual disks, the load balancing settings are not pasted on the second disk.

    [From PVS710ServerConsoleWX64004][#LC1498]

  14. The Stream Service fails when starting and stopping the service.

    [From PVS710ServerConsoleWX64004][#LC1664]

  15. The Powershell MCLI command ""Mcli-Get DeviceInfo" returns an empty value in the "Status" field.

    [From PVS710ServerConsoleWX64004][#LC1790]

  16. After installing Provisioning Services Console version 7.1.3, many .NET applications fail on Windows Server 2008 R2 and on Windows 7.

    [From PVS710ServerConsoleWX64004][#LC1838]

  17. When configuring VMware PXE Manager for vCenter, if a default gateway IP address is not provided as part of the DHCP options, the bootstrap protocol incorrectly sets the gateway IP address (GIADDR) to the Relay Agent IP address.

    [From PVS710ServerConsoleWX64004][#LC1966]

  18. The target device can experience delays on Microsoft Hyper-V when any key is pressed in the disk menu.

    [From PVS710ServerConsoleWX64004][#LC1997]

  19. When the number of target devices increase on Microsoft Hyper-V, some targets fail to start and stop responding at the "Starting Windows" screen.

    [From PVS710ServerConsoleWX64004][#LC2011]

  20. Occasionally, the Stream Service process stops responding when multiple target devices shut down.

    [From PVS710ServerConsoleWX64004][#LC2141]

  21. If there are unresponsive threads, the Stream Service process cannot recover after automatically restarting.

    [From PVS710ServerConsoleWX64004][#LC2227]

  22. If there are two Provisioning Servers configured to use the TFTP Service option and if NetScaler load balances the servers, if you increase the frequency of monitor probes to run faster than the default time of five seconds, memory consumption on bntftp.exe can increase to 7.5 gigabytes.

    [From PVS710ServerConsoleWX64004][#LC2314]

  23. If a static IP address is assigned when running Boot Device Manager, after saving the .iso image the first time and then incrementing the IP address, subsequent attempts to save a new image overwrites the existing file.

    [From PVS710ServerConsoleWX64004][#LC2619]

Fixes from Replaced Hotfixes

The following issues were fixed in an earlier release of Provisioning Services 7.1.

Console Issues
Server Issues

Console Issues

  1. The XenDesktop Setup Wizard might not create or start the target virtual machines on the correct home server in XenServer. The issue occurs if the templates specify the second server as the home server in the template properties. If the XenDesktop Setup Wizard is run by using this template, the target device might boot on the first server.

    [From CPVS71003][#LA4756]

  2. The XenDesktop Setup Wizard fails to create Hyper-V virtual machines when the option "Network sites within this logical network are not connected" is selected for the logical network.

    [From CPVS71003][#LA4837]

  3. If there is more than one login server and the first login server contacted by a target device does not respond, the virtual machine fails to start and becomes unresponsive instead of attempting to contact another login serverin the boot strap list. As a result, starting the target device by using the Boot Device Manager (BDM) fails with a "No ARP Reply" message.

    [From CPVS71003][#LA5029]

  4. The virtual machine created by using the Streamed VM Setup Wizard from the template on the VMware ESX server might not have the correct boot order. In the BIOS setting, the boot order should be CD-ROM and then Network. Instead, Network is first in the boot order.

    [From CPVS71003][#LA5379]

  5. When a Soap Server starts, it might fail to retrieve the domain name associated with the system on which it is running. The issue occurs because the Soap Server starts before all the network interfaces on the system are initialized and the Soap Server fails to contact the domain controller.

    [From CPVS71003][#LA5459]

  6. The Streamed Virtual Machine Setup Wizard does not honor the template boot properties when creating targets.

    To fix this, create the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices
    Name: UseTemplateBootOrder
    Type: DWORD
    Value: 1

    [From CPVS71003][#LA5463]

  7. This feature enhancement adds the ability to assign a Personal vDisk (PvD) to a PvD target device.

    Warning: Unless the vDisk is of the same lineage as the PvD target, the PvD software will erase all data of that PvD target at boot time, resulting in a complete loss of all data on that PvD target. It is your responsibility to ensure that the lineage is correct before assigning the new vDisk to a PvD target.

    [From CPVS71003][#LA5661]

  8. Creating virtual machines by using the Provisioning Services XenDesktop Setup Wizard fails on VMware vSphere when vDisk Cache type is set to "Cache on server" or "Cache on the device RAM".

    [From CPVS71003][#LA5787]

  9. The Provisioning Services Console might exit unexpectedly when opening the "Site" property.

    [From CPVS71003][#LA5802]

  10. The Provisioning Services Console might exit unexpectedly when creating a view.

    [From CPVS71003][#LC0075]

  11. The XenDesktop Setup Wizard fails to create virtual machines by using System Center Virtual Machine Manager (SCVMM) and the template does not have a logical network set. When this occurs, the console log file shows a failure.

    [From CPVS71003][#LC0080]

  12. If users who log on to windows that do not have domain rights and a different user account is used to log on to Provisioning Services Console that has full Active Directory rights, trying to create, delete, or reset Active Directory accounts fails. The Windows-based user accounts are honored instead of the Provisioning Services Console user account.

    [From CPVS71003][#LC0163]

  13. When running the XenDesktop Setup Wizard to create virtual machines on XenServer by using a template with an ISO file attached, the provisioned VMs do not have the ISO attached.

    [From CPVS71003][#LC0209]

  14. The Remote Desktop Services (RDS) catalog provisioned by Provisioning Services contains different properties (Allocation Type: Random, User data: Discard) when compared to the catalogs provisioned by Machine Creation Services (MCS).

    [From CPVS71003][#LC0210]

Server Issues

  1. A newly formatted drive might not be accessible through the vDisk store creation utility when adding a new drive to the Provisioning Server that is later partitioned and formatted. This drive is inaccessible in the vDisk store creator until either an object is created in the drive or the properties of the drive are opened and the Security tab is selected. The issue occurs when using the browse option in the Paths tab.

    [From CPVS71003][#LA4577]

  2. If a target device has 10 or more operating system available memory areas in the memory map, the device might exit unexpectedly while the Preboot Execution Environment (PXE) starts. The device might also fail with a RAM-cache mode error of "Not enough RAM."

    [From CPVS71003][#LA4646]

  3. The XenDesktop Setup Wizard might not create or start the target virtual machines on the correct home server in XenServer. The issue occurs if the templates specify the second server as the home server in the template properties. If the XenDesktop Setup Wizard is run by using this template, the target device might boot on the first server.

    [From CPVS71003][#LA4756]

  4. The XenDesktop Setup Wizard fails to create Hyper-V virtual machines when the option "Network sites within this logical network are not connected" is selected for the logical network.

    [From CPVS71003][#LA4837]

  5. The Citrix PVS Trivial File Transfer Protocol (TFTP) Service and Citrix PVS Two-Stage Boot Service might fail to start when the Provisioning Services Server restarts.

    To enable the fix, you must create the following registry keys:

    For Citrix PVS TFTP Service:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BNTFTP\Parameters
    Name: InitTimeoutSec
    Type: DWORD
    Data: 1 to 4 seconds (default is 1 second) 
    Name: MaxBindRetry 
    Type: DWORD
    Data: 5 to 20 retries (default is 5)

    For Citrix PVS Two-Stage Boot Service:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PVSTSB\Parameters
    Name: InitTimeoutSec
    Type: DWORD
    Data: 1 to 4 seconds (default is 1 second) 
    Name: MaxBindRetry 
    Type: DWORD
    Data: 5 to 20 retries (default is 5)

    [From CPVS71003][#LA4927]

  6. If the vDisk and associated files are exported and imported from a store in Farm A to a store in Farm B, the Stream Process (StreamProcess.exe) might query the UNC path of Farm A instead of Farm B while starting a target device from the vDisk in Farm B. As a result, the target device might start slowly.

    [From CPVS71003][#LA4930]

  7. When checking the replication status of the vDisk for the entire site, servers from the different sites show that the server is not reachable.

    [From CPVS71003][#LA4998]

  8. If there is more than one login server and the first login server contacted by a target device does not respond, the virtual machine fails to start and becomes unresponsive instead of attempting to contact another login serverin the boot strap list. As a result, starting the target device by using the Boot Device Manager (BDM) fails with a "No ARP Reply" message.

    [From CPVS71003][#LA5029]

  9. When merging vDisks, the absolute path for the virtual hard disk (VHD) and automatic virtual hard disk (AVHD) files might be used first instead of using the relative path. This can cause a merge failure or might result in a corrupted merged disk. The issue occurs if the absolute path points to a wrong location after moving the vDisk around.

    [From CPVS71003][#LA5316]

  10. When starting targets from a missing vDisk, the incorrect error message of "vDisk file access permission denied. error: 0x2" appears instead of a "File not found" error.

    [From CPVS71003][#LA5327]

  11. The virtual machine created by using the Streamed VM Setup Wizard from the template on the VMware ESX server might not have the correct boot order. In the BIOS setting, the boot order should be CD-ROM and then Network. Instead, Network is first in the boot order.

    [From CPVS71003][#LA5379]

  12. The Soap Service might exhibit poor performance when accessing the database. The Soap Service must be restarted for the Provisioning Services Console to work. This fix improves performance.

    [From CPVS71003][#LA5418]

  13. When a Soap Server starts, it might fail to retrieve the domain name associated with the system on which it is running. The issue occurs because the Soap Server starts before all the network interfaces on the system are initialized and the Soap Server fails to contact the domain controller.

    [From CPVS71003][#LA5459]

  14. The Streamed Virtual Machine Setup Wizard does not honor the template boot properties when creating targets.

    To fix this, create the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices
    Name: UseTemplateBootOrder
    Type: DWORD
    Value: 1

    [From CPVS71003][#LA5463]

  15. The replication status shows that the vDisk is not available on some Provisioning Service until you restart the stream service on the remote servers.

    [From CPVS71003][#LA5514]

  16. This feature enhancement adds the ability to assign a Personal vDisk (PvD) to a PvD target device.

    Warning: Unless the vDisk is of the same lineage as the PvD target, the PvD software will erase all data of that PvD target at boot time, resulting in a complete loss of all data on that PvD target. It is your responsibility to ensure that the lineage is correct before assigning the new vDisk to a PvD target.

    [From CPVS71003][#LA5661]

  17. The Stream Process (StreamProcess.exe) might exit unexpectedly due to the socket error when sending packets.

    [From CPVS71003][#LA5686]

  18. The Citrix Provisioning Services console shows incorrect vDisk replication status until the Stream Service is restarted.

    [From CPVS71003][#LA5762]

  19. When using the Streamed Virtual Machine Setup Wizard, Provisioning Services can fail when attempting to retrieve template information from the stores of the hosts within a cluster and the following error message appears:

    "Object reference not set to an instance of an object"

    [From CPVS71003][#LA5783]

  20. When replicating vDisks from one store to another on all Provisioning Servers, the replication status does not appear correctly in the logs.

    [From CPVS71003][#LA5818]

  21. Merging vDisk versions fails with the following error message while using Network File System (NFS) storage:

    "There is not enough space on the disk. Error number 0xE0000070."

    [From CPVS71003][#LA5906]

  22. Enabling "Auto Rebalance" to rebalance the target device that has a fixed Subnet Affinity setting might fail to honor the correct Subnet Affinity setting. As a result, target devices are rebalanced to servers that are not in the same subnet.

    [From CPVS71003][#LA5917]

  23. In multi-homed PVS server environments where the management and streaming networks are configured as separate networks, sending a message or a reboot request from the PVS console fails.

    [From CPVS71003][#LC0074]

  24. The Provisioning Services server might fail to capture the newly assigned machine account Active Directory password if the initial password change request to the domain server times out. As a result, targets fail to be able to log on to the domain.

    [From CPVS71003][#LC0078]

  25. Microsoft Windows is not activated on the target device after restart if the vDisk is configured to use Microsoft Multiple Activation Key (MAK) licensing.

    [From CPVS71003][#LC0079]

  26. With RAM cache enabled, target devices can fail to start and a BlInitializeLibrary error appears.

    [From CPVS71003][#LC0179]

  27. Attempts to merge vDisk might result in a corrupted vDisk.

    [From CPVS71003][#LC0239]

Installing This Release

Console Component:

For information about installing the Console component of this hotfix, see Installing Provisioning Services Console Software on the Citrix Product Documentation site.

If it does not exist already, this will add a new entry, Citrix Provisioning Services Console (x64), to the Programs and Features list.

Server Component:

For information about installing the Server component of this hotfix, see see Installing and Configuring Provisioning Services on the Citrix Product Documentation site.

If it does not exist already, this will add a new entry, Citrix Provisioning Services (x64), to the Programs and Features list.