PCoIP Zero Client Firmware 6.0.0 is a firmware release 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.5.1. These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
Note: only All Access subscribers are eligible to receive this release.
Amazon WorkSpaces session connection type with Multi-Factor Authentication now available
Migration of zero client endpoints to cloud desktops has been made easier by adding support for Amazon WorkSpaces as a session type from with in the zero client OSD and AWI. This removes the need to deploy and manage the PCoIP Connection Manager for Amazon WorkSpaces in order to connect zero clients to Amazon WorkSpaces. Additionally, if Multi-Factor Authentication is configured for Amazon WorkSpaces, then the zero client will always require Multi-Factor Authentication for the user.
Removal of CounterPath Unified Communications
Unified Communications is no longer supported on Tera 2
TLS 1.1 is the minimum requirement for initiating PCoIP sessions
TLS 1.0 is no longer available to initiate PCoIP sessions. TLS 1.1 must be used as the minimum version to initiate PCoIP sessions.
This also means that if using host initiated wake with a Remote Workstation Card, the minimum firmware on the Remote Workstation Card must now be firmware 4.9.0 and VMware Horizon must be on release 6.2.1 or higher.
TLS 1.2 is the minimum requirement for establishing an Administrative Web Interface (AWI) session
The zero client Administrative Web Interface now requires web browsers that support TLS 1.2.
|Compatibility Notes||Workstation||VMware Horizon||Amazon WorkSpaces||Teradici Cloud Access Platform|
This release is verified with VMware Horizon 7.4, 7.3 and 7.2. 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.
VMware Horizon 6.2.1 is now the minimum release required to connect with zero clients on this firmware release.
PCoIP Connection Manager for Amazon WorkSpaces 1.0.5 or higher is required in order to connect to Amazon WorkSpaces using the PCoIP Connection Manager session type.
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.
Remote Workstation Card firmware 4.9.0 is now the minimum requirement in order to connect to zero clients on this firmware release.
Note: 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.4 with VMware Horizon 7.2.
This release has been tested with the Leostream Connection Broker version 8. It is not compatible with earlier versions of the Leostream Connection Broker.
Note: After upgrading from PCoIP Zero Client Firmware 4.x to 5.0 or higher, 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.2 or higher to connect to the administrative web interface (AWI).
Zero client attempts to resume session when Amazon WorkSpaces host initiates disconnect
Amazon WorkSpaces can support Ctrl+Alt+F12 as a means to cause the connection to disconnect. If the zero client is configured to have Enable Session Disconnect HotKey turned off, then when the user enters Ctrl+Alt+F12, the Amazon WorkSpace will catch the command and initiate a disconnect. When this disconnect occurs the zero client will attempt to resume the session. (65214)
Workaround: Ensure Enable Session Disconnect Hotkey is set to on for the zero client so that the zero client manages the disconnect.
Zero clients may reboot if a Nessus scan is performed while SNMP is enabled.
Zero clients may reboot if a Nessus scan is performed while SNMP is enabled. (62970)
Workaround: Disable SNMP on the zero client.
Setting timezone to UTC in Management Console results in UTC+0 Europe/Dublin
If the Management Console is configured to push the timezone setting of (UTC+0:00) UTC to the zero client, the zero client will set itself to (UTC+0:00) Europe/Dublin or (UTC+0:00) Europe/London. This timezone makes use of daylight savings time. There is no option in the zero client for (UTC+0:00) UTC. (62959)
Workaround: There is no option in the zero client for (UTC+0:00) UTC. However, if UTC+0:00 without daylight savings is required, then (UTC+0:00) Atlantic/Reykjavik can be used instead.
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:
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:
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)
Scrolling using an Emerson KVM now behaves as expected
Scrolling using an Emerson KVM scroll wheel now behaves as expected (62767)
Crestron KVM properly uses absolute coordinates when other devices are configured for absolute coordinates
When other devices connected to the zero client are configured to use absolute coordinates, Crestron KVMs now use absolute coordinates as expected. (62766)