Zero Client Firmware 4.1.0 Release Notes

Release Status: General Availability (GA)

Release Overview: PCoIP Firmware 4.1.0 GA is a minor firmware release for Tera1 and Tera2 zero clients and host cards.

Important notes:

There are individual releases for Tera1 and Tera2 processor-based products, and a combined package that can be uploaded to the PCoIP Management Console. The Management Console will intelligently apply the firmware based on the managed device processor type.

Key Release Details:

Workstation and VDI:

  • Security features (for Tera1 and Tera2 zero clients): Support for SCEP (Simple Certificate Enrollment Protocol): zero clients may be configured to submit a request for a certificate to a SCEP server (for Tera2 zero clients)

  • Following 3 failed attempts to access the Administrative Web Interface or the On Screen Display, each subsequent failed attempt will require additional time to complete

  • Option to force the changing of the administrative password upon the next access of the Administrative Web Interface or On-Screen-Display (selected password may be blank)
  • Logging of failed access attempts to the Administrative Web Interface, On Screen Display, or management interface (e.g. PCoIP Management Console)
  • Added options to disable the Administrative Web Interface and/or the PCoIP zero client management tool interface (e.g. zero clients can lock out access by the PCoIP Management Console)

  • Auto-Power-Off: Option to power off PCoIP zero clients after a configurable period of idle time when users are out of session (for Tera2 zero clients)

  • Option to configure PCoIP zero clients such that an image on a primary display can be reproduced on the secondary video ports. The mouse pointer is reproduced on the secondary display (for dual-display Tera2 zero clients)
  • Added support for Brazilian ABNT2 keyboards (for Tera1 and Tera2 zero clients)
  • Added a new session type to configure the PCoIP Connection Manager (for Tera2 zero clients). The PCoIP Connection Manager can be used in the future to broker PCoIP sessions for Teradici solutions

VDI Specific:

  • Support for SafeNet SC650 smart cards with SafeNet PKI applet and SHAC middleware
  • Support for Atos CardOS smart cards (for Tera2 zero clients)
  • Support for eToken 72k Pro USB user authentication devices (for Tera2 zero clients)

Workstation Specific:

  • Added support for local termination of keyboards and mice behind USB hubs provided all devices attached to USB hub are HID keyboards and mice
  • Added ability to configure the Peer MAC address from the Session configuration dialog of the On-Screen Display

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 Horizon View that was generally available when this firmware was released. It is also compatible with one major release of Horizon View prior to this. Other versions of Horizon View may also be compatible, but will need to be verified in your specific deployment environment. The version of Horizon View available at the time of this firmware release was Horizon View 5.2.
  • Local image caching is supported in Tera2 zero clients when deployed with VMware View 5.2 or newer. This enables considerable bandwidth savings.

Workstation Specific:

  • While mixed firmware release operation is not tested, firmware 4.1.0 is compatible with 4.0.x, 3.5.x, 3.4.x, 3.3.x 3.2.x and 3.1.x releases
  • Firmware 4.1.0 is not inter operable with firmware releases: 3.0, 2.x, 1.x or 0.x

Key Resolved Issues:

Workstation and VDI:

  • Resolved an issue where the Display Override feature in the OSD does not function (for Tera1 and Tera2 zero clients)
  • Resolved an issue where Greek keyboards do not function correctly in the OSD (for Tera1 and Tera2 zero clients)
  • Resolved two issues where keys were not mapped correctly on a Japanese keyboard (for Tera1 and Tera2 zero clients)
  • Resolved an issue where syslog would disable itself when it was unable to send a syslog message to the configured server because of a network error (for Tera1 and Tera2 zero clients)
  • USB port numbers are referred to as “logical” references in device logs to avoid confusion with physical labeling of USB ports (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the Japanese 106 keyboard entered an incorrect character when the user presses the right-most character key in the upper row
  • Edited supported language translations in the OSD

VDI Specific:

  • Resolved an issue where supported smart cards may not be able to successfully complete their login process (for Tera1 and Tera2 zero clients)
  • Resolved an issue where IronKey USB devices do not function with PCoIP zero clients (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the BASYS2 breadboard device does not function correctly with PCoIP zero clients (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the USB certify scanner device fails to connect to a virtual machine when used with PCoIP zero clients (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the SeaI/O USB device may not function when the PCoIP zero client power is cycled off and back on while the device is connected (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the microphone gain was being incorrectly set (for Tera1 and Tera2 zero clients)
  • Resolved an issue where a CAPS lock warning message was not being displayed if a user had previously failed a login attempt due to a bad username/password (for Tera1 and Tera2 zero clients)
  • When Imprivata OneSign is in lockdown mode, a message indicating the reason for the failed connection is presented to the user (for Tera1 and Tera2 zero clients)
  • The secure session state is now included in device logs (for Tera1 and Tera2 zero clients)
  • Resolved a smart card issue where Atos CardOS cards were not functioning correctly (for Tera2 zero clients)

Workstation Specific:

  • Resolved an issue where the workstation host card may reset when processing a malformed audio packet (for Tera1 and Tera2 zero clients)
  • Resolved an issue where the incorrect bandwidth limit may be selected when connecting a Tera1 client to a Tera2 workstation host card. This issue only occurs when mixing both Tera1 and Tera2 clients to the same Tera2 workstation host card
  • Addressed an issue where Tera1 zero clients experienced audio issues when connecting to Tera2 host cards

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
  • Dell 3008WF display may not work correctly when connected to the Tera2 zero client through VGA. Workaround: Connect via DVI or DP
  • Romanian keyboard in the OSD incorrectly maps the "/" key to the "-" key

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.
  • After a workstation is awoken from sleep or hibernate and the PCoIP session is resumed the audio-video synchronization will be out of sync. Workaround: Restart audio/video content and do not use hibernate/sleep mode.

VDI Specific Issues:

  • Reports of lower window dragging performance.  Workaround: see knowledge base article : 15134-1608

  • 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 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
  • When connected to PCoIP zero clients in a VDI session, the Samsung Galaxy tablet may not function correctly. There is no current workaround for this issue

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