Zero Client Firmware 5.2.2 Release Notes¶
PCoIP Zero Client Firmware 5.2.2 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 security update with bug fixes to version 5.2.1 and is recommended for all users of older releases.
- 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 and above 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 then 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.
- Teradici PCoIP® Zero Client Administrator’s Guide
- PCoIP® Management Console 2.2
- Open-source and third-party components
|5.2.2||September 2016||Security update|
|5.2.1||August 2016||Maintenance update|
|5.2||July 2016||Update to SHA-256 AWI certificate|
|Tera2 Zero Client||Workstation||VMware Horizon||Amazon WorkSpaces||Teradici 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.5.
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.
Zero clients may fail to authenticate with a View 6.2.2 connection server via a Citrix Netscaler load balancer when the load balancer is configured for SSL offloading mode. When the error occurs, the message ‘View Connection Server communication error’ is shown, or the zero client may reboot. (50735)
Workaround: Configure the Netscaler load balancer to use SSL bridging instead of SSL offloading.
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 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 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 will not resolve an FQDN that begins or ends with the underscore character (for example, _myhost.teradici.local). (40824)
The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled. (40754)
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.
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)
Zero client AWI cannot be accessed 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 (AWI) unreachable. (33783)
Workaround: Use the On-Screen Display (OSD) 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. (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.
When multiple displays have Preferred Resolution Override applied to them, disconnecting one display will clear the override for all displays. (28122)
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:
- From the zero client administrative web interface, bridge the smart card reader.
- Without the smart card inserted, log in to the virtual desktop with username/password.
- Insert the smart card. Windows 7 should recognize the smart card and reader and automatically install the correct drivers.
- Log off Windows to disconnect the session.
- From the zero client administrative web interface, remove the bridge configuration for the smart card reader.
- Log in with the smart card. The smart card should be fully accessible.
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.
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)
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)
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)
Zero clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled. (15923)
Note: This release contains a security update and is recommended over previous releases.
Previously, recovery image failed to start when manufacturer defined default keyboard was not a US keyboard. The recovery image now correctly starts when the zero client manufacturer has set the default keyboard to a non-US keyboard. (53400)