PCoIP Zero Client Firmware 6.2.0 Release Notes¶
PCoIP Zero Client Firmware 6.2.0 is a firmware release for PCoIP Zero Clients (not PCoIP Remote Workstation Cards).
This release is a feature release with functional changes and bug fixes over release 6.1.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.
What's New in Release 6.2¶
Local termination for Wacom Intuos Pro Medium PTH-660, Intuos Pro Large PTH-860, Cintiq 22HDT, and Cintiq DTH-1300 tablets
Improves tablet performance in higher latency networks when connecting to any of the following hosts:
|Zero Client Local Termination||Remote Workstation Card Windows||Remote Workstation Card Linux||Cloud Access Software 2.15 for Windows
|Cloud Access Software 2.15 for Linux
|Intuos Pro Medium PTH-660||X||✔||✔||✔|
|Intuos Pro Large PTH-860||X||✔||✔||✔|
|Cintiq DTH-1300||X||✔||X||Not Tested|
Custom certificate support for direct connections to Remote Workstation Card
Peer-to-peer connections between Zero Client and Remote Workstation Card can be secured with a user provided certificate.
Important Notes and Requirements¶
- Zero clients with firmware 5.x or 6.x can only be managed by PCoIP Management Console 2.0 or higher.
- If you are upgrading your Tera2 firmware from a 4.x release:
- Use PCoIP Management Console 1.10.3 through 1.10.8 or the the zero client's AWI to upgrade the zero client to firmware 5.0 or higher.
If you are upgrading directly to a 6.x release, you must upgrade from firmware version 4.7 or 4.8.
This download includes an .all file for use by the Administrative Web Interface (AWI) and a .pcoip file for use by PCoIP Management Console 2.0 and higher.
- The .pcoip file contains zero client firmware 6.2.0 for PCoIP Zero Clients only.
Related Documents and Software¶
- Open-source and third-party components
|6.2.0 GA||March 5, 2019||General Availability|
|6.1.1 GA||November 22, 2018||<General Availability, bug fixes and security updates|
|6.1 GA||July 4, 2018||General Availability|
|Compatibility Notes||Workstation||VMware Horizon||Amazon WorkSpaces||Teradici Cloud Access Platform|
|Release 6.2.0 is verified with VMware Horizon 7.7. 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.||X|
|PCoIP Connection Manager for Amazon WorkSpaces 1.0.7 or higher is required in order to connect to Amazon WorkSpaces using the PCoIP Connection Manager session type.||X|
|Management requires a compatible endpoint manager such as PCoIP Management Console release 2.0 or higher. However, PCoIP Management Console 3.2 or higher is recommended.|
|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 5.1.0.||X||X|
|Release 6.2 is compatible 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.||X
|Supported browsers are Firefox, Chrome, 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).|
Cannot connect through VMWare UAG with MFA (80406)¶
When the following combination is used, users cannot establish a session:
Connections through active Unified Access Gateway (UAG)
View Disclaimer is turned on
Multi-Factor Authentication (MFA) is used
When user enters their MFA credentials, Zero Client prompts user to re-enter Horizon login credentials.
If any one of the following are disabled, there are no issues.
Unified Access Gateway (UAG)
Multi-Factor Authentication (MFA)
VMware pool names are blank if they are too long (76282)¶
The VMware pool names will be populated as blank if they exceed 65 characters.
Certificates with unreadable DNs are not logged (75044)¶
Certificates with unreadable Domain Names (DN) will not be logged if the firmware is unable to match any certificates against known CAs.
Stylus cannot wake up display. (74801)¶
If the display goes to sleep, the stylus on a Wacom tablet cannot be used to wake it up.
Use mouse or keyboard to wake up display.
VCS Communication error with SC650 BLADE and Horizon 7.5 (72839)¶
VCS Communication Error is encountered when an SC650 blade smartcard is used to authenticate with a VCS Horizon 7.5.0. This is not an issue with Horizon 7.4 or earlier.
Recommendation is to not upgrade to Horizon 7.5 at this time.
Zero client in Auto Detect crashes upon receipt of invalid certificate chain (71136)¶
The zero client may crash with the error:
0d,00:00:00.00> LVL:1 RC: 0 MGMT_SYS :*** CRITICAL ERROR CONTEXT DUMP *** 0d,00:00:00.00> LVL:1 RC: 0 MGMT_SYS :Reset cause: SOFTWARE
Verify and correct the certificate chain.
Mouse and keyboard briefly unresponsive after session launch with Wacom tablet connected (71111)¶
Mouse and keyboard devices may be unresponsive when launching a session from the Zero Client if a PTH-660 or PTH-860 Wacom tablet is connected. The mouse and keyboard will become responsive after a few seconds.
Internet Explorer 11 does not trust the Administrative Web Interface certificate (71084)¶
Internet Explorer 11 does not trust the Administrative Web Interface certificate if the AWI is accessed via IP address (it will trust the certificate when using the FQDN).
802.1x not disabled after all certificates removed (70037)¶
Removing the certificates set to be used for 802.1x will not disable 802.1x.
After removing the 802.1x certificates, manually disable 802.1x.
Certificates with long subject names populated using the Cyrillic alphabet cannot be parsed by the zero client. (68434)¶
Certificates with long subject names populated using the Cyrillic alphabet cannot be parsed by the zero client.
Use a shorter subject name in the certificate.
USB Isochronous devices need to be on a root port in order to work. (68340)¶
USB Isochronous devices (such as audio or video devices) need to be on a root port in order to work.
Availability of the root port varies from manufacturer to manufacturer, and they should be engaged to determine if they have a root port available on their zero client model. If available, use the root port for Isochronous device types.
Zero Client cannot establish a PCoIP session after Qualys scan (65940)¶
Zero Client is unable to establish a PCoIP session after some Qualys scans.
Power cycle the Zero Client
Zero client attempts to resume session when Amazon WorkSpaces host initiates disconnect (65214)¶
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.
Ensure Enable Session Disconnect Hotkey is set to on for the zero client so that the zero client manages the disconnect.
Incorrect error presented when certificate uploaded via AWI (65165)¶
When uploading a certificate via AWI, even though the certificate is uploaded into the certificate store the following error may be displayed: Error. The upload did not complete. Please try again.
Verify the certificate is in the certificate store. If it is, ignore the error.
Zero clients may reboot if a Nessus scan is performed while SNMP is enabled. (62970)¶
Zero clients may reboot if a Nessus scan is performed while SNMP is enabled.
Disable SNMP on the zero client.
Setting timezone to UTC in Management Console results in UTC+0 Europe/Dublin (62959)¶
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.
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 (62201)¶
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.
Ensure that the card has no more than two certificates.
Change in button timing for entering manual recovery (61350)¶
Beginning with firmware 5.2.1, the power button sequence to boot a zero client from powered down into the recovery image is:
Press power button once to turn on the client
Wait for one second
Triple tap power button
Zero client boots into the recovery image
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.
Mouse cursor briefly unresponsive after zero client reboot (60568)¶
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.
Zero Client is unable to use IPv6 VMware Horizon View when DHCPv6 is not available (47650)¶
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...'
Security scanners may report zero client to be susceptible to CVE-2004-0230 (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.
Mouse wheel problem occurs with Belkin Advanced Secure Keyboard/Mouse Switch (42387)¶
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.
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 (40824)¶
A zero client will not resolve an FQDN that begins or ends with the underscore character (for example, _myhost.teradici.local).
Restrict Proximity Card setting does not work with VMware Horizon RDSH (40754)¶
The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled.
Enumeration failures with Western Digital portable hard drives (39419)¶
Western Digital Passport external portable hard drives connected to a zero client internal hub may fail to enumerate.
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 (34901)¶
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.
Zero client AWI cannot be accessed when IPv6 Link Local Address is entered in the IPv6 Manual address field (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 (AWI) unreachable.
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 (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.
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 (30150)¶
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.
Use version 5.5.3 of the Elo Multi-Touch driver. This issue has not been observed with this driver version.
RDR-7L82AKU smart card reader does not work with OneSign 4.9 SP1 HF11 and newer (22448)¶
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.
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 (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.
Install the correct driver from a default Windows 7 installation:
- From the zero client administrative web interface, bridge the smart card reader.
- Without the smart card inserted, log in to the virtual desktop with username/password.
- Insert the smart card. Windows 7 should recognize the smart card and reader and automatically install the correct drivers.
- Log off Windows to disconnect the session.
- From the zero client administrative web interface, remove the bridge configuration for the smart card reader.
- Log in with the smart card. The smart card should be fully accessible.
OneSign cannot authenticate after changing Session Connection Type (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.
Restart the zero client.
After display is turned off, screen does not wake up by pushing zero client button (21484)¶
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.
OSD cursor briefly stops responding to mouse input (21382)¶
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.
Disconnecting a session with auto-reconnect enabled causes an alert dialog (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.
Switching between DVI and DisplayPort connectors may cause screen to go blank on HP Z27i displays (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, and the card's previous session was from a zero client with displays attached to its DVI ports.
Temporary IPv6 addressing causes failure when connecting zero clients to any soft host (15923)¶
Zero Clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled.