Zero Client Firmware 4.0.3 Release Notes

Release Status: General Availability Release

Release Overview: PCoIP Firmware 4.0.3 is a firmware patch release for Tera2 PCoIP zero clients and PCoIP host cards. Note this release does not include Tera1 end-points.

Important notes:

  • Deployments using the PCoIP Management Console to manage Tera2 endpoints must use PCoIP MC release 1.8.1 or newer.
  • After updating devices to firmware 4.0.3 on Tera2 devices, downgrading firmware will be not possible.

Key Release Details:

  • No new features are included in this release.

Compatibility Notes:

Workstation and VDI:

  • Deployments using the PCoIP Management Console to manage Tera2 endpoints must use PCoIP MC release 1.8.1 or newer.
  • Deployments using the PCoIP Management Console to manage Tera1 endpoints must use PCoIP MC release 1.7.0 or newer; it is recommended to use the latest release of the PCoIP Management Console.

VDI Specific:

  • This PCoIP firmware is compatible with the release of VMware View that was generally available when this firmware was released. It is also compatible with one major release of View prior to this. Other versions of View may also be compatible, but will need to be verified in your specific deployment environment. The version of View available at the time of this firmware release was View 5.1.
  • The firmware on Tera2 PCoIP zero clients must be updated to FW 4.0.3.
  • Virtual desktops using View 5.x should install firmware 4.0.3 on PCoIP zero client devices to meet VMware client certification requirements.
  • Tera2 zero clients support client caching in firmware 4.0.3, but requires support in the host VM that is coming in a future version of VMware View

Workstation Specific:

  • The firmware on both Tera2 PCoIP host cards and Tera2 PCoIP zero clients must be updated to FW 4.0.3
  • While mixed firmware release operation is not tested, firmware 4.0.3 is compatible with 3.5.x, 3.4.x, 3.3.x 3.2.x and 3.1.x releases.
  • Firmware 4.0.3 is not interoperable with firmware releases: 3.0, 2.x, 1.x or 0.x.

Key Resolved Issues:

  • Resolved an issue where Tera2 clients managed by MC 1.8.0 could become non-functional and unrecoverable when applying profiles.
  • Resolved a communication error with the View Connection Server when the OCSP server is unresponsive.
  • Improved system reliability with Tera2 host cards.
  • Resolved “Source signal on other port” error on video port 2 (only applies to environments deploying View 4.6 and Windows XP)

Key Known Issues:

Workstation and VDI:

  • Connecting a zero client to both PCoIP host cards and VMware View desktops may result in USB peripheral connectivity issues when connecting to the VMware View virtual desktop. Workaround: After ending a session with a PCoIP host card, reset the zero client before establishing a session with a VMware View virtual desktop.
  • The PCoIP Management Console cannot be used to configure the IPv6 Gateway Address field. Workaround: Enable and configure DHCPv6 or SLAAC to set this field or configure the field statically using the device Administrative Web Interface.
  • Dell 3008WF display may not work correctly when connected to the Tera2 zero client through VGA. Workaround: Connect via DVI or DP.
  • Greek keyboard mapping in the OSD is not supported.
  • Romanian keyboard in the OSD incorrectly maps the "/" key to the "-" key.
  • The OSD Configuration> Display tab describes the behaviour of unplug and re-plug incorrectly. The actual behaviour is that a display reverts to its native resolution (rather than previous) when unplugged and re-plugged.
  • The enable display override does not work as intended. Enabling this feature has no effect.

Workstation Specific Issues:

  • Disconnecting a session while a transfer is in progress from a Scan Disk Cruzer flash drive may result in USB devices not working. Workaround: Unplug and re-plug the Scan Disk Cruzer device.
  • The desktop display resolution may change when a user resizes the software client window while a session is active with a PCoIP host card. This occurs if the client window becomes smaller than the current desktop or a larger resolution will fit within the client window. Sometimes when this change occurs, the graphics driver scales the image resulting in the desktop not fitting within the client window. Workaround: Resize the client window or configure the graphics driver to use the monitor’s built in scaling feature.

VDI Specific Issues:

  • Ironkey USB drives do not work in a View 5.1 environment.
  • Zero clients always connect to port 443 of the Imprivata OneSign server. Users cannot override the port by configuring the port number in the Bootstrap URL field
  • Zero clients may fail to establish Imprivata OneSign sessions when the OneSign Appliance Verification setting equals no verification. This happens when the zero client trust store contains a certificate that does not match the certificate used by the OneSign server. Workaround: Ensure that the zero client trust store match the certificates used by the OneSign server.
  • Zero clients cannot disable the beep behaviour for the following proximity RFIDeas readers when connecting to virtual desktops using Imprivata OneSign: Air ID ( RDR-7L82AKU ), Wave ID ( RDR-80582AKU ), pcProx Plus ( RDR-80_81AKU ).
  • Zero clients connecting to VMware View 5.1 virtual desktops running Windows XP-32 may experience brief audio outages while using USB speakers or headsets. Workaround: Use analog speakers or headsets.
  • Zero clients connecting to VMware View 5.0.1 (or earlier) virtual desktops may experience USB device connectivity problems. Workaround: Unplug and re-plug the USB device.
  • Samsung Galaxy tablet may not function correctly in VDI sessions. There is no current workaround for this issue.
  • Disabling proximity reader beeps does not work for the Wave ID proximity card reader or the HID pcProx Plus RDR-80_81 card reader.

The above known issues are under investigation. Please subscribe to this knowledge base item to receive updates.