Zero Client Firmware 5.0.2 Release Notes

Release Status: General Availability (GA)

Release Overview:

PCoIP® Zero Client firmware 5.0.2 for Tera2 zero clients (not Remote Workstation Cards) is a maintenance release containing bug fixes and no additional features. New features introduced in firmware 5.x can be seen in the Zero Client Firmware 5.0.0 Release Details: (15134-2737). This article will provide a summary of compatibility notes, key feature additions, resolved issues and known issues for this firmware release. Currently certified for use with Horizon View 6.2.

Important Requirements:

  • Either the zero client AWI or PCoIP Management Console 1.10.3-1.10.5 must be used to upgrade zero clients to firmware 5.0. PCoIP Management Console 2.0 cannot detect or manage devices on firmware versions prior to version 5.0.
  • Zero Clients on firmware 5.0 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 than 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.0.

Important Notes:

  • An individual release is provided for Tera2 zero clients, and a combined format for PCoIP Management Console.
  • The combined file format is to be used with PCoIP Management Console 1.10.3 or higher, it is not supported in earlier PCoIP Management Console releases.
  • The combined file format contains zero client firmware 5.0 for Tera2 zero clients only.

Compatibility Notes:
Products Platforms
Tera2 Zero Client
Workstation
VMware Horizon Amazon WorkSpaces Teradici Pervasive Computing Platform
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 6.2.
This 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.0 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.0 has been tested to work with Workstation Access Cards on Workstation Access Card Firmware 4.7.2.
Note: Using Zero Client on Firmware 5.0 to connect to Remote Workstation Cards may require you to use both version of Management Console. Management Console 2.0 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.
Zero Client Firmware 5.0 has been tested against Imprivata OneSign 5.0 with VMware Horizon View 6.1.1.
Zero Client Firmware 5.0 has been tested with the Leostream Connection Broker version 8. Zero Client Firmware 5.0 is not compatible with earlier versions of the Leostream Connection Broker.
Note: After upgrading to Zero Client Firmware 5.0, 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.

New Features:
Products Platforms
Tera2 Zero Client
Workstation VMware Horizon Amazon
WorkSpaces
Teradici Pervasive Computing Platform
This is a maintenance release containing bug fixes.

Key Resolved Issues: Products Platforms
Tera2 Zero Client
Workstation VMware
Horizon
Amazon
WorkSpaces
Teradici Pervasive Computing Platform
38500. The Tera2 Zero Client firmware recovery image always boots the ZC to the standby state, regardless of settings defined by the manufacturer. This is known to impact Amulet Hotkey DXZ4 zero clients, causing a lock up of the zero client that requires it to be returned to the factory for repair when the DXZ4 is booting the recovery image. It does not occur when the DXZ4 is booting the primary image.  
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.    
36416. The zero client does not retrieve the VCS address provisioned in the DNS _pcoip-vcs SRV record.     
36407. In rare cases, the zero client may stop communicating with the Management Console. This will appear as a client that never shows that it is online from within the Management Console, even when it is.
34957. The Zero Client On-Screen Display and Administrative Web Interface offer the Connection Manager Interface Session Connection Type after upgrading to Tera2 Zero Client firmware 5.0.0. This mode is non-functional. Firmware 5.0.0 does not support brokering sessions using the Connection Management Interface.  
34896. A PCoIP Management Console 2.0 Enterprise Edition profile that configures the Trap NMS Address field as a hostname will fail to apply to the Tera2 Zero Client.
25083. When applying a Management Console 2.0 Enterprise Edition profile that contains certificates totaling more than 84386 bytes, the zero client may enter a state where the AWI is non-responsive and the zero client is unable to connect to the Management Console. Rebooting the zero client resolves the issue. 

Key Known Issues:
Products Platforms
Tera2 Zero Client
Workstation VMware Horizon  Amazon
WorkSpaces
 
Teradici Pervasive Computing Platform
35204. Tera2 Zero Client firmware 5.0.0 fails to connect to Amazon WorkSpaces through a PCoIP Connection Manager for Amazon WorkSpaces version 1.0.1 or lower with the error message: "Command failed. Please report this failure to your system administrator. Error: 6603". Workaround: Replace the PCoIP Connection Manager for Amazon WorkSpaces with version 1.0.2 or higher.
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.
33910. Management Console 1.x is unable to manage zero clients that have been upgraded to firmware 5.0.
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.
33494. If the management server provides a certificate without a Common Name (CN) the zero client may reboot.
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. Workaround: Restart the Zero Client.
15923. Zero Clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled.

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.0 is firmware for Tera2 zero clients