Zero Client Firmware 4.8.1 Release Notes

Release Status: General Availability (GA)

Release Overview:

PCoIP® Firmware 4.8.1 is a maintenance update for Tera2 zero clients that includes the contents of Firmware 4.8.0, 4.8.0-p1, 4.8.0-p2, 4.8.0-p3 and additional bug fixes and general enhancements.This firmware upgrades the AWI certificate from SHA-1 to SHA-256, permitting compatibility with newer web browser releases. Further information regarding browser SHA-1 compatibility can be found from your browser vendor or from the Internet. This article will provide a summary of compatibility notes and key feature additions for this firmware release.

Important Notes:

  • Firmware 4.5.1 or 4.6.0 will be used as a minimum firmware required prior to moving to any newer release of PCoIP firmware on Tera2 zero clients and host cards.
  • This release contains both an .all file format for AWI management of Tera2 processor-based products, and a .pcoip combined file format for PCoIP Management Console 1.10.5 administration of multiple Tera2 processor-based products .
  • The .pcoip combined file format is to be used with PCoIP Management Console 1.10.3 and higher, and is not supported in earlier PCoIP Management Console releases.
  • The combined file format contains firmware 4.8.1 for Tera2 zero clients, and firmware 4.7.5 for Tera2 Remote Workstation Cards.

Compatibility Notes:
Products Platforms
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.5. It is compatible with PCoIP Management Console 1.10.3 & 1.10.4.

Using the latest release 1.x of the PCoIP Management Console is recommended.


PCoIP Zero Client Firmware 4.8.1 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.

New Features:
Products Platforms
Tera2 Workstation VMware Horizon  Amazon
The Platform
45397. The certificate for the Administrative Web Interface (AWI) has been updated to a SHA-256 certificate.  

Key Resolved Issues: Products Platforms
Tera2 Workstation VMware

48336. Under some scenarios, users may not be able to change expired Active Directory passwords from the Zero Client OSD when using OneSign.

48839. Some wake on USB capable devices may fail to wake the Zero Client from standby power state.
48841. In the zero client OSD, some accent characters on the Swiss-French keyboard may be incorrect depending on the order in which the keys are held and released.
48838. A Zero Client can occasionally become non-responsive with a black screen on session tear-down. 


Key Known Issues:
Products Platforms
Tera2 Workstation VMware Horizon  Amazon

25728. The OSD Logo Upload AWI page displays overlapping content when using Internet Explorer 9.

Workaround: Use Internet Explorer 11 or other web browser.

24954. The Philips Digital Pocket Memo device (VID/PID = 0911/1F40) is not supported on the Zero Client USB EHCI controller and may cause the Zero Client to restart.

Workaround: There are two solutions for the Philips Digital Pocket Memo. Users can either attach the device to the Zero Client behind a USB 1.1 hub or disable EHCI via the Zero Client AWI (this will reduce the transfer speed of other attached USB devices such as flash drives).

21639. After deleting a domain from the OneSign server, the domain remains visible on the zero client OneSign authentication dialog screen for a brief period.

Workaround: The zero client refreshes the OneSign domain list from the OneSign server once every ten minutes. The deleted domain name will be removed after ten minutes.

20830 If the virtual desktop is running Imprivata OneSign 4.9 SP1 HF11 or newer, unlocking the virtual desktop may fail if the zero client has Invert Wiegand Data disabled.

Workaround: Configure the zero client's Invert Wiegand Data setting to "Use Existing Setting" or "Enabled".

40824. Zero client will not resolve an FQDN that begins or ends with the underscore character (e.g. _myhost.teradici.local).
33783. 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.
34901. 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.
30150. An Elo Touch monitor connected to a Zero Client may lose its calibration settings and be unusable in the On-Screen Display (OSD). This occurs 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.
21082.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.
45883. 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.
36497. The Promethean electronic whiteboard is not accessible by the PCoIP host when connected to a zero client.
40754. The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled.
21653. 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.
10339.Smart card authentication using a PIV card against VMware View may fail if the card capabilities container has multiple CardApplicationURLs.
10267. When a Zero Client is configured with a password length greater than 20 characters the AWI is unable to accept the password.

21382. The OSD cursor will stop responding to mouse input for a few seconds when:

  • Pressing the Apply button on the AWI USB Permissions page
  • Loading the AWI Attached Devices page

19353. 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 to that card was a from a zero client with displays attached to its DVI ports.

40729. 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.
37884. Adding an Imprivata OneSign server to an existing OneSign enterprise may cause the zero client to restart.
36515. 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.
40629. Smart card authentication using a PIV card against VMware View may fail if the certificate contains a compressed certificate.
32825. Evoluent VerticalMouse 4 fails to work on a Linux workstation.
30104. Stylus used with Intuos CTH-680 behaves erratically while in the OSD.
29194. Unable to enter some accent keys using the Swiss-German keyboard.
25499. VisionX Cheque Scanner fails to operate.
23116. 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.
26382. Some wake on USB capable devices may fail to wake the Zero Client from standby power state. 
43869. Zero clients fail 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.
43050. In the zero client OSD, some accent characters on the Swiss-French keyboard may be incorrect depending on the order in which the keys are held and released.
42570. The zero client may occasionally crash when the connection to the host is put under severe network impairment and video content is changing.
10058. Added support for VMware custom keyboard layout codes to enable synchronization of more keyboard layouts between the zero client and Horizon when connected using PCoIP.
29754. Tera2 zero clients using unified communications with Bria VE are unable to initiate calls when the SIP invite contains uppercase content.  
45118. In the zero client OSD, some accent characters on the Swiss-French keyboard may be incorrect depending on the order in which the keys are held and released.
30480. Unable to access some characters from German keyboards using Strg+Alt in the OSD.
28964. Network Connection Loss message may be display on zero clients connected to Horizon 6 if Enable Peer Loss Overlay is configured and the zero client is power cycled.
10079. The zero client may stop updating display content after a network interruption caused by a spanning tree-driven network change.
9992. AWI does not support more than 239 characters for the combined length of the SCEP server URL and challenge password.
30928. 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.
30009. Some keyboard models have LEDs that would not toggle from within the zero client OSD.
26361. Cursor movement on a device that has more than one HID interface demonstrates erratic behaviour in the OSD.
28958.  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.

VMware Horizon View in RDS desktops or hosted apps do not support USB redirection when connecting with PCoIP zero clients.

Recommendation: Open a feature request with VMware if this capability is required.

25466 - The combined file containing firmware 4.8.0 for Tera2 Zero Clients, with file suffix .pcoip, is not compatible with MC 1.10.2 or older.

Workaround: To use this combined file upgrade to MC 1.10.3.

25355 - Under some scenarios, users may not be able to change expired Active Directory passwords from the Zero Client OSD when using OneSign.

Workaround: Log in via a Windows computer to update the password.

22761 - The first up arrow key press in the desktop selection dialog is not recognized.

22448 - RFIDeas RDR-7L82AKU proximity card readers do not detect cards after logging in to a virtual desktop running certain Imprivata versions such as OneSign 4.9 SP1 HF11.

Workaround: For information on compatible OneSign versions, contact Imprivata. Try alternative OneSign Agent versions. Customers have reported this issue does not occur with on new HF releases of OneSign for 5.0 and 4.9. 

22315 - 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.
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.

21135 - Configuring the transport type in Bria Virtualized Edition may cause the zero client to reset.

Workaround: Add to the DNS SRV record for the Zero Client a SIP TCP (_sip._tcp) entry.

18032 - Characters may be missed when using the Magtek USB Keyboard Emulation Swipe Reader.

Workaround: Refer to knowledge base #2396 for a resolution: MagTek USB Keyboard Emulation Card Swipe Reader (i.e. credit card reader) causes "stuck key".

14433 - Disclaimer dialog is not bypassed when using PCoIP Connection Manager + Auto-Logon session connection setting.


21157. On the AWI, the user 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 are made to the advanced options and if the session type is unchanged.

Workaround: Click the Continue button to skip the reset.