Tera2 PCoIP Zero Client Firmware Release Notes¶
PCoIP Zero Client Firmware 5.5.1 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.4.1. 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¶
Gemalto IDPrime MD Smart Card Support¶
The following Gemalto IDPrime MD smart cards are now supported for VMware Horizon View session authentication:
- IDPrime MD 830 (up to Level2)
- IDPrime MD 840
- IDPrime MD 3810
PIVKEY Smart Card¶
PIVKey C980 Smartcards are now supported on Zero Clients for VMware Horizon View authentication.
HID OMNIKEY 5421 Card Reader¶
The HID OMNIKEY 5421 smart card reader is supported for VMware Horizon View pre-session authentication.
X.509 User Name Hints¶
The Zero Client supports the VMware Horizon View smart card user name hint feature. This feature was added to Horizon View in version 7.0.2 and permits a user with multiple accounts to be able to specify which account they wish to use when logging in using a smart card. More information on the feature is available from VMware: http://pubs.vmware.com/Release_Notes/en/horizon-7-view/horizon-702-view-release-notes.html.
SNMP sysName Provides FQDN¶
When querying the zero client using SNMP, the sysName.0 MIB object defined in SNMPv2-MIB now returns the zero client's FQDN.
Updated Time Zones¶
The IANA time zone database included in the zero client firmware has been updated to 2016j. This ensures time zones used on the zero client match current international standards.
Zero Clients no longer send their event logs to the Management Console¶
The zero client no longer pushes its event log content to the Endpoint Manager. As a result, users of Management Console 2.4.0 and older will see static log information in the log viewer accessed from the Endpoint Details page. This is to line up with Management Console 2.5.0 no longer having the event log viewer.
Administrative Web Interface Certificate is now a 3072-bit RSA key¶
The certificate presented by the Administrative Web Interface now uses a 3072-bit RSA key
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.5.1 for Tera2 PCoIP Zero Clients only
Related Documents and Software¶
- Tera2 PCoIP Zero Client Firmware 5.5.1 Administrators Guide
- PCoIP Management Console 3.0.1 Release Notes
- Open Source and Third-Party Licenses
|5.5.1||May 2017||General availability release|
|Teradici Cloud Access Platform|
|This release is compatible with VMware Horizon 7.1, 7.3, 7.4, 7.7 and 7.8. 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. Certification status of zero clients should be obtained from VMware’s HCL. See KB 1618 for more information on VMware Horizon certification and compatibility.||X|
|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.||X|
|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: Remote Workstation Cards: 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.1.|
|This release has been tested with the Leostream Connection Broker version 8. It is not compatible with earlier versions of the Leostream Connection Broker.
Session Connection Type: 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).
SIPR token authentication may fail with multiple certificates on card¶
The zero client will fail to complete SIPR token smart card authentication against VMware Horizon View when the smart card contains more than two certificates. (62201)
Workaround: Ensure that the card has no more than two certificates.
Change in button timing for entering manual recovery¶
Beginning with firmware 5.2.1, the power button sequence to boot a zero client from powered down into the recovery image is:
- Press power button once to turn on the client
- Wait for one second
- Triple tap power button
- Zero client boots into the recovery image.
From firmware 5.0.0 to 5.2.0 it was possible to triple tap the power button immediately after turning on the zero client. This is no longer supported. (61350)
Mouse cursor briefly unresponsive after zero client reboot¶
The On-Screen Display's mouse cursor may be unresponsive for a few seconds after a zero client reboot when a web browser is connected to the zero client's Administrative Web Interface. (60568)
Zero Client is unable to use IPv6 VMware Horizon View when DHCPv6 is not available¶
If the zero client is configured for IPv6, and it cannot connect a DHCPv6 server, it will be unable to connect to a desktop when brokered by 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¶
A 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)
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.
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 unstable 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)
RDR-7L82AKU smart card reader does not work with OneSign 4.9 SP1 HF11 and newer¶
RFIDeas RDR-7L82AKU proximity card readers do not detect cards after logging in to a virtual desktop running Imprivata OneSign 4.9 SP1 HF11 or newer. (22448)
Workaround: Revert Imprivata OneSign installation to a version older than 4.9 SP1 HF11.
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)
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.
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)
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. (21082)
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)
Zero Client connect VMware Horizon View Connection Server after resolution of VMSA-2017-0008.2¶
VMware changes to Horizon View to resolve VMware Security Advisory ID VMSA-2017-0008.2 resulted in a "View Connection Server error" when the zero client attempted to connect to a desktop. Zero client firmware has been updated to support the changes introduced by VMware into Horizon View 6.2.4 and newer. (62797)
Upgrading firmware 5.4.x with AWI open no longer causes zero client to freeze¶
The zero client will no longer freeze if upgrading from firmware 5.5 or higher. The issue was present only in firmware 5.4.x. (62772)
In OneSign mode the zero client will abort pre-session authentication when the View Connection Server session times out¶
A zero client in OneSign mode may receive more than one View Connection Server address from the OneSign server. When a zero client is left at the desktop selection dialog for longer than the View Connection Server's Forcibly Disconnect User setting value (default 600 minutes) and then a desktop selection is made, the zero client will abort to the Connect dialog. (62425)
Increased smart card transaction timeout¶
The zero client smart card remoting feature's idle timeout has been increased from five to 20 seconds to improve compatibility with versions of Windows older than Windows 8. (62192)
Zero client event log flooded with messages in 802.1x and PoE environments¶
Prevously, the zero client event log may have become flooded with messages that began with "RDMA2 :src_mac" when the zero client is operating in PoE (Power over Ethernet) mode or is configured to use 802.1x. This is now resolved. (59523)
SNMP disabled by default¶
SNMP is now disabled by default. Zero clients where the Enable SNMP setting is not explicitly configured will now have SNMP disabled and must have SNMP re-enabled by the administrator if it is to be used after firmware upgrade. (57407)
Enabled USB audio no longer causes zero client reboots¶
Previously, a zero client with USB audio enabled may infrequently reboot, even when audio was not playing. This issue has been fixed. (49418)