Release Notes
Remote Workstation Card Firmware 5.0.1
Management Requirements
- Remote Workstation Cards with firmware 17.05, 20.01.x or newer is supported when managed by PCoIP Management Console 20.01 or newer.
- 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 an enabled administrative web interface (AWI).
- Some features require the Remote Workstation Card Software installed to work.
Upgrade Path Information
If you are upgrading your Tera2 firmware:
- Use PCoIP Management Console 20.01 or newer to upgrade to firmware 20.01 or newer.
- Use PCoIP Management Console 1.10.3 through 1.10.8 to upgrade to firmware 5.x from firmware 4.9 or older.
- The AWI can be used to upgrade a single Remote Workstation Card firmware to any firmware version.
- See Knowledge Base article KB 1144
Download Contents
This download includes an .all file for use by the Administrative Web Interface (AWI) and a .pcoip file for use by PCoIP Management Console version 2.0 and higher.
The .pcoip file is used by the PCoIP Management Console and contains the Remote Workstation Card firmware release.
Related Product Resource Locations
What's New
Support for Management Console 3.1+
The Remote Workstation Card is now compatible with PCoIP Management Console 3.1 and higher. This permits the use of a single management tool for both remote workstation cards and zero clients when using modern firmware.
Removal of Connection Management Interface (CMI)
CMI is no longer available in the Remote Workstation Card. As a result of the removal of CMI, the Remote Workstation Card is no longer compatible with PCoIP Management Console 1.x but maintains brokering with Horizon View. Brokering by way of the PCoIP Broker Protocol is planned for a future release
Security Updates
The Remote Workstation Card Firmware session security mode has been improved.
The minimum TLS version required for establishing a PCoIP session is now TLS 1.1. The minimum TLS version required to access the Administrative Web Interface (AWI) is now TLS 1.2.
The Administrative Web Interface certificate is now a SHA-256 certificate with 3072-bit RSA encryption.
SNMP sysName
Now reports the endpoint FQDN instead of "Teradici Corp"
Time Zone Database update
GMT time zones have been replaced with the 2016j IANA time zone database.
Compatibility
| Compatibility Notes | Platforms | Platforms | Clients | Clients |
| VMware Horizon |
Teradici Cloud Access Software |
PCoIP Zero Client |
PCoIP Software Clients |
|
|
This firmware release is supported when connected to PCoIP Zero Clients on firmware 6.0.0. Note: Other zero client firmware may be compatible with this release, but are not supported. |
X | |||
|
This firmware release is supported when connected to PCoIP Software Client 3.5.0. Note: Other client versions may be compatible with this release, but are not supported. |
X | |||
|
Management requires a compatible endpoint manager such as PCoIP Management Console release 3.1 or higher. |
X | |||
| This firmware release is supported with the VMware broker and security gateway available in Horizon View 7.3 and 7.4. | X | |||
|
This release cannot be brokered in use with the Teradici Cloud Access Software. This release cannot be brokered using the CMI brokering protocol. |
|
|||
|
USB devices (other than basic Mouse and Keyboard) are supported when used with Tera2 PCoIP Zero Clients on firmware 5.5.1 or higher. |
X |
|
||
|
Wacom Tablet local termination is supported when used with Tera2 PCoIP Zero Clients on firmware 5.5.1 or higher, and the Host Software for Linux 4.7.0 or higher. See the Local Tablet Driver section of the Host Software for Linux Administrators' Guide for more details on versions and tablet compatibility. Not all tablets are compatible with all versions of zero client firmware and host software. |
X |
|
Recent versions of Google Chrome now trust the PCoIP certificate
Google Chrome now trusts the zero client and remote workstation card certificate. Verified with version 65.0.3325.181.
AWI no longer references TLS 1.0
When setting the Session Negotiation Cipher Suite for the endpoint, Maximum Compatibility references now references TLS 1.1 and higher.
CVE-2014-8730 TLS Padding Vulnerability has been resolved
CVE-2014-8730 TLS Padding Vulnerability has been resolved
Zero client no longer crashes under severe network impairment
Previously, zero client might occasionally crash when the connection to the host was put under severe network impairment and video content was changing. This issue is now fixed.
SLAAC address is now populated when IPv6 and SLAAC are enabled on Remote Workstation Card.
SLAAC address is now populated when IPv6 and SLAAC are enabled on Remote Workstation Card.
Frequent webpage reloading shows different content in Chrome
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.
Internet Explorer 11 does not trust the Administrative Web Interface certificate
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).
Profile application to a Remote Workstation Card fails when Enable Audio has not been enabled
Applying a Profile to a Remote Workstation Card from PCoIP Management Console will be unsuccessful if the Enable Audio setting on the Remote Workstation Card has never been enabled (default is disabled) or the Remote Workstation Card has not had the Enable Audio setting enabled since the last Reset Parameters setting has been applied.
In either case, after attempting to apply the profile, the PCoIP Management Console may display incorrect statuses of the endpoint. For example, if the profile attempted to peer the Remote Workstation Card to a PCoIP Zero Client, the status will display as peered when the Remote Workstation Card may be in a state ready to accept any connection.
To make sure your profile is applied to the Remote Workstation Card correctly, ensure the Enable Audio setting has been enabled in the profile you are applying or ensure the setting has been enabled once prior to applying a new profile.