Friday, 1 February 2013

CPVS61016 for PVS 6.1 - How important is it?

Well, Citrix recently released hotfix 016 for PVS 6.1 and as opposed to the usual updates consisting of of bare binarys to be dropped onto the server this has the feel (and install) of a rollup. We can see from the notes that accompany 016 that the list of bug fixes and PVS tweaks is comprehensive to say the least. In fact all Citrix Support cases now start with the line "Have you installed Hotfix 016?". If the answer is no, then you already have your first step. So what has been addressed in this super-fix?

Well first and foremost, this Hotfix can and should be used as the installer for a new installation. It includes all previous fixes plus those below. The installers do not rely on a previous install of the server / console or target device. Handy!

Personally, I'd recommend removing the components from an existing install too and reinstalling using the Hotfix installers.
  • In VMware ESX deployments, the XenDesktop Setup wizard can throw an exception, preventing users from setting up templates and machines properly.
  • Selecting the Streamed image with Personal Vdisk option of the XenDesktop Setup wizard results in the creation of a fixed disk rather than a dynamic disk.
  • 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.
  • Stopping the license server causes target devices to attempt to fail over after about five minutes, rendering the Stream Service unresponsive in the process.
  • The Stream Process (StreamProcess.exe) can exit unexpectedly when many target devices reconnect at the same time due to HA failover or rebalancing.
  • Using Multiple Activation Key (MAK) activation, attempts to activate a target device from the Provisioning Services Console can fail with the following error: "Error IPC ---- Command timeout. Error 0xE0070102." The issue occurs if the local host name of the Provisioning Server contains lowercase letters.
  • 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.
  • Target devices can randomly become unresponsive during shutdown. Memory dump indicate that the issue occurs while trying to obtain performance counters.
  • 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.
  • 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.
  • 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.

No comments:

Post a Comment