Release Notes

The Zero Client's Preferred Resolution Override feature in the OSD does not show resolutions greater than 2048x1152 (including 4K UHD) if Enable Attached Display Override is active.

Occasionally, AWI pages are slow to load and appear with missing menu items, especially the home page.

When connecting to a VMware Horizon resource that is in use or unavailable, the OSD message "Connecting to desktop" is being displayed instead of messages that indicate the desktop is being in use or is unavailable.

When the EAP TLS server has a CA signed certificate, the PCoIP endpoint 802.1X will fail authentication when the Root CA is not in the certificate store.

802.1X setups with a self-signed certificate in the EAP TLS server is not affected.

Firmware 21.07.0 and later does not store the Root CA certificate during a SCEP request.

After launching a PCoIP session RHEL/CentOS host with Cintiq 22HDT bridged, the session may get disconnected and the system becomes unresponsive.

When establishing a PCoIP session with the Zero Client and Wacom Cintiq Pro 24, and connecting to the Remote Workstation Card, the Zero Client will reset.

Starting with Horizon 7.7.0, PCoIP session can no longer be established to a View brokered Remote Workstation Card via PCoIP security gateway. Horizon 7.6.0 is fine.

If a Certificate Authority (CA) issued certificate has an OCSP responder, the PCoIP Zero Client checks if it is revoked. However, for certificates (with an OCSP responder) that are issued by a root CA, the PCoIP Zero Client would report that the OCSP responder is unreachable.

When connecting to VMWare Horizon using SafeNet SC650 Blade smart card, the Zero Client fails to authenticate with the View Connection Server and an Alert message is displayed in the OSD "Alert! View Connection Server communication error."

This issue affects firmware 5.5.0 and higher.

Zero Client crashes after IDPrime .NET smart card PIN and username hint are submitted

When using Chrome, performing frequently or fast webpage reloading can result in portions of an AWI page that are not normally visible to become visible. This has not been observed on Firefox or Edge.

The VMware pool names will be populated as blank if they exceed 65 characters.

Certificates with unreadable Domain Names (DN) will not be logged if the firmware is unable to match any certificates against known CAs.

If the display goes to sleep, the stylus on a Wacom tablet cannot be used to wake it up.

When connecting to a Windows 10 Horizon VM using CAC or PIV smart card, the session fails Single Sign-On (SSO) and the Windows password login screen is displayed. If the user clicks on Sign-in options, and selects the smart card icon, the login screen shows the smart card login with PIN field.

After the user is logged in and the session is disconnected without logging off from OS, then when the user reconnects, the user is logged into the OS. However, if the user logs out from the OS and connects the session or uses a different card, SSO will not work.

The zero client may crash with the error: {quote}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 {quote} when it is is configured for either one of the VMware Horizon connection types, or Auto Detect, and is presented with an invalid certificate chain (such as one containing duplicate entries).

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 if the AWI is accessed via IP address (it will trust the certificate when using the FQDN).

Removing the certificates set to be used for 802.1x will not disable 802.1x.

Certificates with long subject names populated using the Cyrillic alphabet cannot be parsed by the zero client.

USB Isochronous devices (such as audio or video devices) need to be on a root port in order to work.

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.

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.

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.

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.

Beginning with firmware 5.2.1, the power button sequence to boot a zero client from powered down into the recovery image is:

1. Press power button once to turn on the client
2. Wait for one second
3. Triple tap power button
4. 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.

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.

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

A zero client will not resolve an FQDN that begins or ends with the underscore character (for example, _myhost.teradici.local).

The Restrict Proximity Card setting does not work with VMware Horizon RDSH sessions when set to disabled.

Western Digital Passport external portable hard drives connected to a zero client internal hub may fail to enumerate.

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.

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.

SLAAC address is not populated when IPv6 and SLAAC are enabled on Remote Workstation Card.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Zero clients cannot establish a connection to any soft host that has temporary IPv6 addressing enabled.