Zero Client Firmware 5.4.0 Release Notes


Release Overview

PCoIP Zero Client Firmware 5.4 is a firmware for Tera2 PCoIP Zero Clients (not PCoIP Remote Workstation Cards). This release is a feature release with functional changes and bug fixes over release 5.3.0. These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.

What’s New in This Release

Token smart card authentication

Enhanced BasicCard, Payflex, and Open Platform Smart Cards can be used for single sign-on authentication. They have been verified against Gemalto PC-TWIN and Rocketek RT-SCR1 card readers when the connection is brokered by a PCoIP Broker Protocol-compliant broker with Cloud Access Software or Cloud Access Platform hosts.

If there is no USB for the session, the session will disconnect upon card removal.

Configurable SCEP CA Identifier

To increase compatibility with more SCEP servers, the CA Identifier is now configurable from the OSD and AWI to send values other than the default ‘CAIdentifier’ value to the SCEP server during the GetCACert request.

3440x1440 and 2560x1440 display support

3440x1440 and 2560x1440 display resolutions are now supported as native resolutions. These resolutions are only available as native resolutions and are not explicitly select-able from the resolution override or display topology options.

OMNIKEY 5127-mini smart card support

Added support for the OMNIKEY 5127-mini when used in Imprivata OneSign environments.

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.8 must be used to upgrade the zero client to firmware 5.x.
  • Zero clients on firmware 5.x can only be managed by PCoIP Management Console 2.0 or higher. PCoIP Management Console 1.x cannot detect or manage devices on firmware 5.0 or higher.
  • Zero clients being upgraded to firmware 5.x from a 4.x release must first be upgraded to firmware 4.7 or 4.8.
  • 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.4.0 for Tera2 PCoIP Zero Clients only.
Related Documents and Software

Release History

VersionDateDescription
5.4 January 2017 Initial release

Compatibility

Compatibility NotesHost Platforms
Workstation VMware Horizon Amazon WorkSpaces Teradici Cloud Access Platform
This release is compatible with VMware Horizon 7.0. 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.
PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 or higher is required in order to connect to Amazon WorkSpaces.

Use of Amazon WorkSpaces with hourly billing requires the PCoIP Connection Manager for Amazon WorkSpaces 1.0.5 or higher.

Management requires a compatible endpoint manager such as PCoIP Management Console release 2.0 or higher.
While mixed firmware release operation is not generally supported, this firmware release has been tested to work with Remote Workstation Cards on Remote Workstation Card firmware 4.9.0.
Note: Using zero clients on this firmware release 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.
This release has been tested against Imprivata OneSign 5.2 with VMware Horizon 7.0.
This release 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 from PCoIP Zero Client Firmware 4.x to 5.x, 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, Chrome, Internet Explorer 11, and Microsoft Edge. Versions of the browsers tested are those that were available prior to release.
Web browsers must support TLS 1.1 or higher to connect to the administrative web interface (AWI).

Known Issues and Workarounds

Nessus warns on SNMP community name

The Nessus Vulnerability Scanner reports that the zero clients default SNMP community name, public, is a high severity issue. (57407)
Workaround: Change the SNMP community name or disable SNMP.

Zero client is unable to use IPv6 VMware Horizon View when DHCPv6 is not available

When IPv6 is enabled on a zero client but it is unable to contact a DHCPv6 server, the zero client will not be able to broker a session using an IPv6 VMware Horizon View connection server. The zero client displays the message ‘CONFIGURATION_ERROR - IPv6 capability required: Your VMware Horizon View Client addressing configuration is not compatible with this View Server…’ (47650)

Security scanners may report zero client to be susceptible to CVE-2004-0230

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. (45883)

Mouse wheel problem occurs with Belkin Advanced Secure Keyboard/Mouse Switch

Mouse wheel scroll-down does not 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. (42387)
Workaround: On Tera2 Zero Clients, bridge the KM and enable the Force Local Cursor Visible on the zero client Configuration > USB Administrative Web Interface.

Zero client fails to resolve FQDN with a label that starts or ends with an underscore

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

Restrict Proximity Card setting does not work with VMware Horizon RDSH

The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled. (40754)

Enumeration failures with Western Digital portable hard drives

Western Digital Passport external portable hard drives connected to a zero client internal hub may fail to enumerate. (39419)
Workaround: Connect the drive to a zero client root hub port, or 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 IPv6 gateway address is overwritten on reset

Although the IPv6 Gateway address is displayed as an editable field on the zero client Administrative Web Interface (AWI), changes to this field are not respected by the zero client firmware. Instead, the IPv6 gateway is determined using IPv6 Router Advertisement. (34901)

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 (AWI) unreachable. (33783)
Workaround: Use the On-Screen Display (OSD) to reconfigure the IPv6 address settings.

Evoluent VerticalMouse 4 does not work when connected behind a hub during active session

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. (33706)
Workaround: Avoid plugging the device into a hub port while a session is active or connect the device to a zero client root port. Alternatively, disconnect and reconnect the session after plugging the mouse into a zero client behind a hub.

Elo Touch monitor may lose calibration in OSD after used in bridged mode with certain Elo Multi-Touch drivers

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

Disconnecting one display resets Preferred Resolution Override on all displays

When multiple displays have Preferred Resolution Override applied to them, disconnecting one display will clear the override for all displays. (28122)

Gemalto IDCore 3020 smart cards is missing 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. (22315)
Workaround: Install the correct driver from a default Windows 7 installation:

  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 cannot authenticate after changing Session 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. (21653)
Workaround: Restart the zero client.

After display is turned off, screen does not wake up by pushing zero client button

When the On-Screen Display (OSD) Screensaver timeout expires, it will turn off the display after the end of a PCoIP session brokered by a PCoIP Connection Manager. Clicking the zero client’s physical button does not wake the display. (21484)

OSD cursor briefly stops responding to mouse input

The On-Screen Display (OSD) cursor stops 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. It will behave as expected shortly after. (21382)

Switching between DVI and DisplayPort connectors may cause screen to go blank on HP Z27i displays

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, and the card’s previous session was from a zero client with displays attached to its DVI ports. (19353)

Temporary IPv6 addressing causes failure when connecting zero clients to any soft host

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

Resolved Issues

Reverted UPN handling on password dialog for VMware Horizon View connections

UPN (user@domain) user name formats no longer passing the domain portion of the UPN to the View Connection Server in Horizon View connections is now resolved.
As of firmware 5.4, Horizon connections will send the user@domain UPN as the user name to the VCS, and the selected domain from the dropdown as the domain.
For PCoIP Connection Manager connection types, the user name sent to the broker will be the user portion of user@domain, and the domain sent will be the domain portion of user@domain. (57885)

PCoIP Zero Client is now discoverable through SLP

The zero client firmware fails to respond to SLP discovery queries received more than five minutes after the zero client boots. This is now fixed. (54536)

Video now appears when two displays have no serial number

Previously, when two displays attached to the zero client had no serial number in their Extended Display Identification Data (EDID) blocks, the zero client displayed no video. This issue is now fixed. (53617)

USB scanners can now scan documents and pictures

Previously, some USB scanners failed to scan or bridge to the host. This issue is fixed. (52412)