PCoIP Zero Client Firmware 4.8.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 4.8.1 and is recommended for all users of older releases.
|4.8.2||September 2016||Security update|
|4.8.1||June 2016||Update to SHA-256 AWI certificate, maintenance update|
|4.8||April 2015||Feature enhancements and additions|
|Tera2||Workstation||VMware Horizon||Amazon WorkSpaces|
|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 7.0.||✔||✔|
|This firmware has been tested with PCoIP Management Console 1.10.7. It is compatible with PCoIP Management Console 1.10.x (starting with 1.10.3).
Using the latest release 1.x of the PCoIP Management Console is recommended.
|This firmware was tested with Remote Workstation Card Firmware 4.7.5 and, while not tested, should be compatible with older firmware versions down to 4.0.x.||✔||✔||✔|
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.
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)
Zero clients fail the automated smart card login to VMware View Windows 2012 RDSH sessions because Windows 2012 sends an unexpected smart card control message to the zero client. (43869)
Some accent characters on the Swiss-French keyboard may be incorrect in the zero client On-Screen Display (OSD), depending on the order in which the keys are held and released. (43050)
Zero client may occasionally crash when the connection to the host is put under severe network impairment and video content is changing. (42570)
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)
Removing a smart card from a reader during a PCoIP session while the smart card is being accessed may cause the zero client to restart. (40729)
Smart card authentication using a PIV card against VMware View may fail if the certificate contains a compressed certificate. (40629)
Adding an Imprivata OneSign server to an existing OneSign enterprise may cause the zero client to restart. (37884)
When the card belonging to the current user is tapped on a RFIDeas proximity card reader connected to the front USB ports of an Atrust w100 zero client to end a OneSign-brokered PCoIP session, the zero client may immediately start another PCoIP session for that user. (36515)
Workaround: Connect the RFIDeas reader to the rear USB ports.
The Promethean electronic whiteboard is not accessible by the PCoIP host when connected to a zero client. (36497)
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.
If using a Bloomberg keyboard and Auto Power-Off Timeout is set, Wake-on-USB may fail if the zero client is put to sleep by using the power button. (30928)
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.
Some keyboard models have LEDs that will not toggle from within the zero client On-Screen Display (OSD). (30009)
Tera2 Zero Clients using unified communications with Bria VE are unable to initiate calls when the SIP invite contains uppercase content. (29754)
A Network Connection Loss message may be displayed on zero clients connected to Horizon 6 if Enable Peer Loss Overlay is configured and the zero client is power cycled. (28964)
If a smart card is removed and inserted again when using with Gemalto middleware software and Windows 7, a web browser may not be able to read certificates from the card. (28958)
When multiple displays have Preferred Resolution Override applied to them, disconnecting one display will clear the override for all displays. (28122)
Cursor movement on a device that has more than one HID interface demonstrates erratic behavior in the On-Screen Display (OSD). (26361)
Previously, Panini Vision X Check Scanner failed to operate due to URB transfer size. (25499)
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:
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)
On the AWI, users will be prompted to reset the zero client after submitting changes to the session configuration advanced options while it is configured for the Direct to Host + SLP Host Discovery type. The reset is not necessary if the only changes is made to the advanced options and if the session type is unchanged. (21157)
Workaround: Click the Continue button to skip the reset.
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)
Smart card authentication using a PIV card against VMware View may fail if the card capabilities container has multiple Application Card URLs. (10339)
The zero client may stop updating display content after a network interruption caused by a spanning tree-driven network change. (10079)
Note: This release contains a security update and is recommended over previous releases.
The zero client no longer reboots when an impaired network condition caused substantial imaging packet loss. (53154)