Zero Client Firmware 5.1.1 Release Notes

Release Status: General Availability

Release Overview:

  • PCoIP® zero client firmware 5.1.1 is firmware for Tera2 zero clients only (not Remote Workstation Cards). 
  • This article will provide a summary of compatibility notes, key feature additions, resolved issues and known issues for this firmware release.

Important 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.5 must be used to upgrade the zero client to firmware 5.x.
  • Zero clients on firmware 5.1 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.1

Important Notes:

  • 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.1.1 for Tera2 zero clients only.

Compatibility Notes:ProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon WorkSpacesTeradici 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 Teradici 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.1 must use PCoIP MC 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, zero client firmware 5.1 has been tested to work with Remote Workstation Cards on Remote Workstation Card firmware 4.7.2.
Note: Using zero clients on firmware 5.1 to connect to Remote Workstation Cards may require you to use both version of Management Console. Management Console 2 to manage the zero clients, and Management Console 1.x to manage Remote Workstation Cards until such time as there is a Remote Workstation Card firmware release that is supported by Management Console 2.0 or higher.
Zero client firmware 5.1 has been tested against Imprivata OneSign 5.1 with VMware Horizon 6.2.
Zero client firmware 5.1 has been tested with the Leostream Connection Broker version 8. zero client firmware 5.1 is not compatible with earlier versions of the Leostream Connection Broker.
Note: After upgrading to zero client firmware 5.1, 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.

Web browsers must support TLS 1.1 or higher to connect to the Administrative Web Interface (AWI). Recommended browsers are Firefox 45, Chrome 47, and Internet Explorer 11.

Internet Explorer 8,9, and 10 require TLS 1.1 or 1.2 to be enabled in the Internet Options dialog's Advanced tab in order to connect to the AWI

Internet Explorer 7 and earlier cannot connect to the AWI.

Key New Features:ProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon
WorkSpaces
Teradici Pervasive Computing Platform
42141. Added support for pre-session authentication using the SafeNet eToken 4100 smart card with VMware Horizon.
35614. Extended SafeNet AT SC650 smart card with VMware Horizon to include to support for BLADE in addition to PKI.

39323. Additional SHA-256 cipher suites added for connection to VMware Horizon (View) Connection servers:

  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA

40562. Additional SHA-256 cipher suites added for TLS connections to Imprivata OneSign servers:

  • ECDHE-RSA-AES128-GCM-SHA256
  • AES128-GCM-SHA256
  • AES128-SHA256
  • AES256-SHA256
36467. Out-of-band password changes of OneSign users now supported. OneSign users who have their passwords changed outside of OneSign can now enter their new password into the zero client when authenticating against a OneSign server.
33130. Multi-question input based authentication when zero clients are connected using PCoIP Connection Manager sessions.  Brokers can now request information from the user of the zero client to satisfy authentication methods such as security questions or multi-factor authentication.

35973. The zero client AWI now requires a minimum of TLS 1.1 for connections. Browsers that do not support TLS 1.1 or higher are no longer supported.

Recommended web browsers are Firefox, Chrome, and Internet Explorer 11.

Internet Explorer 8,9, and 10 require TLS 1.1 or 1.2 to be enabled in the Internet Options dialog's Advanced tab in order to connect to the AWI

Internet Explorer 7 can no longer connect to the AWI.

Key Resolved Issues:ProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon WorkSpacesTeradici Pervasive Computing Platform
44965. The zero client may reboot when attempting to connect to a PCoIP Management Console that is not responding to TLS handshake requests in a timely manner.        
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.
42108. Zero clients can repeatedly reboot if the DHCP option for Management Console (MC) 2.x server certificate fingerprint has exactly one more character than expected or if DNS TXT record for MC 2.x server certificate fingerprint string is longer than expected. Workaround: Correctly format the certificate fingerprint string in DHCP/DNS server as per MC 2.0 manual.
40953. Some smart card authentication using a PIV card against VMware Horizon may fail if the Card Capabilities Container identifier is an unexpected length.      
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.      
40629. Smart card authentication using a PIV card against VMware Horizon may fail if the certificate contains a compressed certificate.      
38541. The Management Console cannot reboot a zero client after resetting it to the factory defaults. Workaround: Reboot the zero client manually.        
37709. The zero client required a DNS reverse lookup record (PTR) for the FQDN used in DNS pcoip-bootstrap SRV record for MC 2.x address to find the MC 2.x certificate fingerprint TXT record. When the PTR record does not exist the zero client will be unable to authenticate its Endpoint Manager using the TXT record.        
36051. Some zero client time zones are not pushed across to software PCoIP servers during session negotiation. The resulting session uses UTC time on the PCoIP server host. The affected time zones are:
  • Australia/Eucla
  • Australia/Lord_Howe
  • Pacific/Chatham
  • Pacific/Kiritimati
  • Pacific/Marquesas
  • Pacific/Norfolk
  • America/Adak
  • America/Metlakatla
  • Pacific/Pitcairn
  • Pacific/Gambier
  • Pacific/Easter
  • America/Miquelon
  • Antarctica/Troll
  • America/Atikokan
  • America/Argentina/Catamarca
  • America/Argentina/Cordoba
  • Atlantic/Faroe
  • Asia/Gaza
  • Asia/Hebron
  • Asia/Istanbul
  • Europe/Nicosia
  • Africa/Asmara
  • Asia/Kolkata
  • Pacific/Chuuk
  • Pacific/Pohnpei
 
38975. The ID_box scanner from ICAR does not bridge to the VMware Horizon host.      
33494. If the management server provides a certificate without a Common Name (CN) the zero client may reboot.        
10339. Smart card authentication using a PIV card against VMware Horizon may fail if the card capabilities container has multiple CardApplicationURLs.    
42211. The zero client fails to pick up the DHCP option value for Management Console 2.x fingerprint information from certain non-Windows DHCP server products (like InfoBlox) because the DHCP data string from the DHCP server is not null terminated. Workaround: Use DNS record option to provide MC 2.x address and certificate fingerprint information

Key Known Issues:ProductsPlatforms
Tera2 Zero ClientWorkstationVMware HorizonAmazon WorkSpacesTeradici Pervasive Computing Platform
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.
42387. Mouse wheel scroll-down doesn't 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. Workaround: On TERA2 zero clients, bridge the KM and enable the "Force Local Cursor Visible" feature on the zero client AWI (Configuration->USB).
41963. The zero client may crash when trying to simultaneously connect to Management Console and View Connection Server (by having Auto Connect to VCS feature enabled) if Management Console & View Connection Server certificate both have an Online Certificate Status Protocol (OCSP) responder.
40824. The zero client will not resolve an FQDN that begins or ends with the underscore character (e.g. _myhost.teradici.local).
40754. The "Restrict Proximity Card" setting does not work with VMware Horizon RDSH sessions when set to disabled.
40702. The zero client does not reboot after completing a Reset to Factory Defaults command initiated by an Endpoint Manager such as the PCoIP Management Console. Workaround: Follow the Reset to Factory Defaults command with a Power Reset command or reboot the Zero Client manually.
39419. Western Digital Passport external portable hard drives connected to a zero client internal hub may fail to enumerate. Workaround: 1) Connect the drive to a zero client root hub port. ) Connect the drive to an external hub that is connected to the zero client.
then restart the PCoIP session and disconnect/reconnect the drive.
   
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.        
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. Workaround: Use the On-Screen Display to reconfigure the IPv6 address settings.        
33706. 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. Workaround: Avoid plugging the device into a hub port while a session is active or connect the device to a zero client root port, or disconnect and reconnect the session after plugging the mouse into a zero client behind a hub.    
30150. An Elo Touch monitor connected to a zero client may lose its calibration settings and be unsable in the On-Screen Display 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. Workaround: This issue has not been observed with version 5.5.3 of the Elo MultiTouch driver.    
23116. When a Horizon 6(+) Connection Server is configured to "never" time out clients, zero clients are disconnected by the host after 20 hours of session. Workaround: Set the Horizon 6(+) Connection Server client time out from "never" to a large number.      
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.
     

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 Horizon using OneSign authentication. Workaround: Restart the zero client.

     
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.        
15923. Zero clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled.  
10267. When a zero client is configured with a password length greater than 20 characters then the AWI is unable to accept the password. Workaround: Use the On-Screen Display to set a password no more than 20 characters long.        
9992. AWI does not support more than 239 characters for the combined length of the SCEP server URL and challenge password. Workaround: If a shorter FQDN is not available, use the IP address of the server or configure SCEP from the OSD.      

The above known issues are newly identified as of this release and are under investigation. Please subscribe to this knowledge base item to receive updates.

PCoIP® zero client firmware 5.1 is firmware for Tera2 zero clients only.