Release Notes
Remote Workstation Card Firmware 21.07.3
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
Release Overview
Remote Workstation Card Firmware 21.07.3 is a firmware release for Remote Workstation Cards (not PCoIP Zero Clients).
This is a maintenance release with no new features. These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.
Note: only Cloud Access subscribers are eligible to receive this release.
What's New in 21.07
This release contains bug fixes and security updates.
SCEP
Remote Workstation Cards now can perform SCEP certificate requests for AWI and 802.1X certificates.
Security Updates
Removed support for TLS 1.1.
Compatibility
Management Console
This firmware is supported with Management Console 20.01 or newer.
Zero Client
- Remote Workstation Card firmware 21.07 has been tested with Zero Client 21.07.
- Other Zero Client firmware may be compatible, but are not supported.
PCoIP Software Client
- USB devices connected to the host computer running the Software Client are not supported when connecting to Remote Workstation Cards or Remote Workstation Card Agents.
- Direct connections require PCoIP Software Client 20.04.2 or newer.
- Remote Workstation Card firmware 21.07 has been tested with PCoIP Software Client 21.07. Other Software Client versions may be compatible with this release, but are not supported.
VMware Horizon
-
Remote Workstation Card has been tested with VMWare Horizon 8.2 2103.
- Remote Workstation Card is compatible with PCoIP Secure Gateway.
- If using Horizon 7.7 or newer, see KB 5309
SCEP issued certificates in FW 21.03 or earlier are retained after upgrading to FW 21.07.3 or newer
After upgrading to FW 21.07.3 or newer, SCEP certificates acquired in firmware 21.03 or earlier are retained in the endpoint certificate store and won't be replaced by those in the Management Console profile.
Remote Workstation Card crashes when Horizon View client disconnects
Remote Workstation Card crashes when Horizon View client disconnects
'Direct-to-Host + SLP Host discovery' connections intermittently reset device after changing network segments
If the Zero Client and Remote Workstation Card are configured to connect via 'Direct-to-Host + SLP Host Discovery', and then placed on a different subnet/network, the first connection may result in a reset of the Zero Client or Remote Workstation Card resetting.
Subsequent connections on the new network/subnet will not have this issue.
Use the 'Direct-to-Host' option when connecting from Zero Client to Remote Workstation Card.
View Horizon brokered connection to Remote Workstation Card fails in Horizon 7.7.0 and newer
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.
Re-enable the legacy mode wherein the embedded self-signed certificate is used.
- Navigate to the HKEYLOCALMACHINE\SOFTWARE\Teradici\SecurityGateway registry key.
- Add a new String (REG_SZ) value, SSLCertPresentLegacyCertificate, to this registry key.
- Set the SSLCertPresentLegacyCertificate value to 1.
- Restart the VMware Horizon View PCoIP Security Gateway service
Local cursor corruption is observed when DPI other that 100% is used, for Zero Client to Remote Workstation Card connections.
Cursor corruption observed if Windows DPI is greater than 100% on Remote Workstation Card connections
Set Windows DPI scaling to 100%. Logout of windows, log back in, then change the DPI scaling to desired value.
Note: the mouse will not scale, but the corruption will not occur.
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.