Zero Client Firmware 5.2.1 Release Notes

Release Overview

PCoIP Zero Client Firmware 5.2.1 is a firmware for Tera2 Zero Clients only (not Remote Workstation Cards). This article provides a summary of key feature additions, compatibility notes, resolved issues, and known issues for this firmware release. This release is a maintenance update with bug fixes to version 5.2.

Important Notes and Requirements

  • PCoIP Management Console 2.x cannot detect or manage devices on firmware versions prior to version 5.0. If upgrading from firmware 4.x, then either the zero client AWI or PCoIP Management Console 1.10.3-1.10.7 must be used to upgrade the zero client to firmware 5.x.
  • Zero clients on firmware 5.2 can only be managed by PCoIP Management Console 2.0 or higher. PCoIP Management Console 1.x cannot detect or manage devices on firmware higher than 4.8.
  • Either zero client firmware 4.7.x or 4.8 must be used as the staging firmware prior to upgrading to firmware 5.2 and above.
  • This download includes a file identified by the .all extension specifically for use by the Administrative Web Interface (AWI) and a file identified by the .pcoip extension specifically for use by PCoIP Management Console 2.x.
  • This .pcoip file contains zero client firmware 5.2.1 for Tera2 zero clients only.

Release History

5.2.1 August 2016 Maintenance update
5.2 July 2016 Update to SHA-256 AWI certificate




Compatibility NotesProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon WorkSpacesTeradici Pervasive Computing Platform
This PCoIP firmware is compatible with the release of VMware Horizon that was generally available when this firmware was released. It is also compatible with one major release of Horizon prior to this. Other versions of Horizon may also be compatible, but will need to be verified in your specific deployment environment.
The version of Horizon available at the time of this firmware release was Horizon 7.0.
PCoIP Zero Client Firmware 5.0 and higher requires PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA or higher in order to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.
Deployments using the PCoIP Management Console to manage Tera2 Zero Clients on firmware 5.2 and above must use PCoIP Management Console release 2.0 or newer. Using the latest release of the PCoIP Management Console is recommended.
While mixed firmware release operation is not generally supported, firmware 5.2 has been tested to work with Remote Workstation Cards on Remote Workstation Card firmware 4.7.4.
Note: Using zero clients on firmware 5.2 to connect to Remote Workstation Cards may require you to use both versions of PCoIP Management Console: version 2 to manage the zero clients, and version 1.x to manage Remote Workstation Cards until such time as there is a Remote Workstation Card firmware release that is supported by PCoIP Management Console 2.0 or higher.
PCoIP Zero Client Firmware 5.2 has been tested against Imprivata OneSign 5.1 with VMware Horizon 7.0.
PCoIP Zero Client Firmware 5.2 has been tested with the Leostream Connection Broker version 8. It is not compatible with earlier versions of the Leostream Connection Broker.
Note: After upgrading to PCoIP Zero Client Firmware 5.2, the session connection type for the zero client must be changed to PCoIP Connection Manager, with the address of the Leostream Connection Broker. Also ensure the Leostream Connection Broker has had 'Enable TLSv1.1 protocol' enabled in the Connection Broker Security Options section of the Connection Broker > System > Settings page.
Supported browsers are Firefox 46, Chrome 50, Internet Explorer 11, and Microsoft Edge 25.
Web browsers must support TLS 1.1 or higher to connect to the administrative web interface (AWI).


Resolved IssuesProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon WorkSpacesTeradici Pervasive Computing Platform
49077. Samsung NC241 Zero Client no longer fails to boot. The Samsung NC241 Zero Client did not boot in this scenario:
  1. Disconnect an active PCoIP session using the Auto hardware button on the NC241
  2. Power down the zero client using the hardware power button
  3. Attempt to power up the zero client using the hardware power button

    After step 3 the NC241 fails to boot successfully and remains at a black screen.

This issue has been fixed.

48667. Preferred Resolution Override no longer causes VMware View connection failures. Previously, a zero client might fail to establish a PCoIP session with a VMware Horizon View PCoIP host when Preferred Resolution Override was enabled. After selecting a desktop, the zero client display(s) went black for 30 seconds followed by a message saying "You have been disconnected". The VMware Horizon View agent log contained "Assert at function get_native_dmt". This issue has been fixed.


Known Issues and Workarounds

Security scanners may report that the zero client is susceptible to CVE-2004-0230. This CVE exists in TCP stacks in devices that implement the Border Gateway Protocol. While this is a significant issue for routers that implement the Border Gateway Protocol it is not a significant issue for zero clients.


The zero client may reboot when attempting to connect to a PCoIP Management Console that is not responding to TLS handshake requests in a timely manner.


Mouse wheel scroll-down doesn't work while in a PCoIP session. This occurs when the mouse is connected to a zero client through a Belkin Advanced Secure Keyboard/Mouse (KM) Switch. This problem has been observed while using KM models F1DN102K, F1DN104K and F1DN108K. Workaround: On TERA2 zero clients bridge the KM and enable the "Force Local Cursor Visible" feature on the zero client Configuration->USB Administrative Web Interface.


Zero client will not resolve an FQDN that begins or ends with the underscore character (for example, _myhost.teradici.local).


Proximity Card Reader is treated as Locally connected when connecting to OneSign Win 2008R2 with Restrict Proximity Cards option disabled. The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled.


Passport HD- 450 GB plugged over the hubs failing to be enumerated in HHT2 season. Western Digital Passport external portable hard drives connected to a zero client internal hub may fail to enumerate.

  1. Connect the drive to a zero client root hub port then restart the PCoIP session and disconnect/reconnect the drive.
  2. Connect the drive to an external hub that is connected to the zero client then restart the PCoIP session and disconnect/reconnect the drive.

Manual DHCPv6 gateway address gets overwritten/cleared on reset. The IPv6 Gateway address is displayed as an editable field on the Zero Client Administrative Web Interface. Changes to this field are not respected by the Zero Client firmware. Instead, the IPv6 gateway is determined using IPv6 Router Advertisement.


AWI inaccessible when IPv6 Link Local Address is entered in the IPv6 Manual Address field. Configuring a Zero Client in IPv6 mode to manual addresses and setting the IPv6 Manual Address to the same value as the Link Local Address will make the Zero Client Administrative Web Interface unreachable. Workaround: Use the On-Screen Display to reconfigure the IPv6 address settings.


The Evoluent VerticalMouse 4 device does not work if the device is bridged and the user connects the device to a zero client behind a hub (external or built-in hub port) while a session is active. Workaround: Avoid plugging the device into a hub port while a session is active or connect the device to a zero client root port, or disconnect and reconnect the session after plugging the mouse into a zero client behind a hub.


Elo Touch monitor may lose calibration settings. An Elo Touch monitor connected to a zero client may lose its calibration settings and be unstable in the On-Screen Display when the zero client connects to a PCoIP host running certain versions of the Elo MultiTouch driver and the monitor is calibrated using the MultiTouch driver on the host. Workaround: This issue has not been observed with version 5.5.3 of the Elo MultiTouch driver.


Zero clients disconnect after 20 hours of session. When View 6.x connection server is configured to "never" time out clients, zero clients are disconnected by the host after 20 hours of session. Workaround: Set the View 6.x connection client time out from "never" to a large number.


Gemalto IDCore 3020 PIV 2.0 smart card needs to be bridged to get correct driver in Windows 7. By default, Gemalto IDCore 3020 smart cards work in pre-session. However, the card does not work while in-session for Windows 7 virtual desktops. Workaround: Install the correct driver from a default Windows 7 installation by following these steps:
1. From the zero client administrative web interface, bridge the smart card reader.
2. Without the smart card inserted, log in to the virtual desktop with username/password.
3. Insert the smart card. Windows 7 should recognize the smart card and reader and automatically install the correct drivers.
4. Log off Windows to disconnect the session.
5. From the zero client administrative web interface, remove the bridge configuration for the smart card reader.
6. Log in with the smart card. The smart card should be fully accessible.


OneSign login fails to continue after switching from VCS + Kiosk connection type. After changing a zero client's Session Connection Type from View Connection Server + Kiosk to View Connection Server + OneSign, the zero client is unable to negotiate a PCoIP session with VMware View using OneSign authentication. Workaround: Restart the zero client.


OSD cursor stops to move. The OSD cursor will stop responding to mouse input for a few seconds after pressing the Apply button on the AWI USB Permissions page or while loading the AWI Attached Devices page.


Disconnecting a session with Auto-reconnect enabled causes an Alert dialog. With the auto-reconnect feature enabled, users may see an alert dialog briefly on screen before the PCoIP session is reconnected. The message shown is "Unable to connect (0x1001). Please contact your IT administrator." This message can be safely ignored.


Switching connections between DVI and DP causes HP Z27i to go blank at times. HP Z27i displays connected to a zero client's DisplayPort connectors may not show the remote desktop content when the zero client starts a PCoIP session to a workstation access card when the previous session that card was a from a zero client with displays attached to its DVI ports.


Zero clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled.


AWI and OSD limit passwords to 20 characters. When a zero client is configured with a password length greater than 20 characters then the AWI is unable to accept the password. Workaround: Use the On-Screen Display to set a password no more than 20 characters long.


Requesting SCEP certs with long passwords using the server FQDN will fail. AWI does not support more than 239 characters for the combined length of the SCEP server URL and challenge password. Workaround: If a shorter FQDN is not available, use the IP address of the server or configure SCEP from the OSD.