Filename: CPVS60019.zip
For: Provisioning Services 6.0. For additional information, including operating system requirements, see Citrix eDocs, the Citrix Product Documentation Library.
Replaces: None
Date: March, 2013
Language: English (US), Japanese (JA)
Readme version: 1.01

Readme Revision History

Version	Date	Change Description
1.01	April, 2013	Modified installation instructions
1.00	March, 2013	Initial release

Important Note(s)

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 Citrix eDocs, the Citrix Product Documentation Library.

New Fixes and Enhancements in This Rollup

This rollup introduces the following fixes that have not been previously released:

Server

Target Device

Server Issues

1. When a NAS controller fails or a (temporary) network interruption occurs, target devices can take up to 20 minutes to recover. During that time, the target devices remain unresponsive.

   [#LA2360]

2. The Stream Process (StreamProcess.exe) can exit unexpectedly when many target devices reconnect at the same time due to HA failover or rebalancing.

   [#LA2576]

3. The StreamProcess can exit unexpectedly at random.

   [#LA2650]

4. Stopping the Stream Service on a given Provisioning Server can render some target devices connected to that server unresponsive as failover to other servers does not occur.

   [#LA2812]

Target Device Issues

1. Target devices can randomly become unresponsive with memory dumps indicating that the issue occurs while getting the performance timer.

   [#LA2398]

2. Target devices can become unresponsive or experience a fatal exception, displaying a blue screen. The issue occurs when attempts to open a socket fail because a network interface is not ready or misconfigured. If the defaults provided by this fix do not fully resolve the issue, you can manually configure the number of retries and the delay time by setting the following registry keys:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNIStack\Parameters
   Name: SocketOpenRetryLimit
   Type: REG_DWORD
   Data: <range of 5 (default) to 40>

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNIStack\Parameters
   Name: SocketOpenRetryIntervalMS
   Type: REG_DWORD
   Data: <range of 200 (default) to 2000 (milliseconds)>

   [#LA2483]

3. When the target device uses the local disk for its write cache and the disk is full, users can experience various application or system errors. The device can become unresponsive, even experience a fatal exception, displaying a blue screen. To enable this fix, you must set the following registry key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNIStack\Parameters
   Name: EnableFatalErrorBSOD
   Type: REG_DWORD
   Data: 1 (enable); 0 (disable)

   [#LA2546]

4. When a target is set to use a gateway IP address obtained through DHCP, which is blank by default, the Provisioning Services target device driver overwrites the blank IP address obtained through DHCP with an incorrect entry of "0.0.0.0". The same incorrect entry is also added to the routing table. As a result, various routing or connection issues for the services and applications hosted by the target device can occur.

   [#LA2669]

5. Stopping the Stream Service on a given Provisioning Server can render some target devices connected to that server unresponsive as failover to other servers does not occur.

   [#LA2812]

6. The automatic update feature of Windows Server Update Services (WSUS) might fail to work in Japanese deployments.

   [#LA3046]

7. When streaming multiple guests to a XS 6.1 host, Provisioning Services consumes one PVS target license per virtual machine instead of checking for available XenServer licensing options.

   Note: To enable this fix in its entirety, you must also install XenServer Hotfix Knowledge Center article XS61E010 or its replacement hotfix.

   [#LA3362]

Fixes from Replaced Hotfixes

No hotfixes were replaced by this release.

Installing This Release

Server Component:

Replace the following files with their namesakes included in this package and then run the Provisioning Services Configration wizard without changing the existing settings:

File Name	Folder Location
Manager.dll	%ProgramFiles%\Citrix\Provisioning Services
StreamProcess.exe	%ProgramFiles% \ Citrix\Provisioning Services

Target Device:

Replace the following files with their namesakes included in this package:

File Name	Folder Location
BNDevice.exe	%ProgramFiles%\Citrix\Provisioning Services
CIM.exe	%ProgramFiles%\Citrix\Provisioning Services
BNIStack.sys	%ProgramFiles%\Citrix\Provisioning Services\drivers, %systemroot%\system32\drivers (for Windows XP and Windows 2003)
BNIStack6.sys	%ProgramFiles%\Citrix\Provisioning Services\drivers, %systemroot%\system32\drivers (for Windows Vista, Windows 7, Windows 2008 and Windows 2008 R2)
CNicTeam.sys	%ProgramFiles%\Citrix\Provisioning Services\drivers
Xip.Client.WSUS.resources.dll	%ProgramFiles%\Citrix\Provisioning Services\ja

For additional information about installing Target Device hotfixes, see eDocs.