RWC 20.01.3

Release Overview

Remote Workstation Card Firmware 20.01.3 is a firmware release for Remote Workstation Cards (not PCoIP Zero Clients).

This release is a maintenance release comprised of security updates and bug fixes.. 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.

Important Notice

If you are using PCoIP Management Console to deploy firmware updates, you must upgrade to Management Console 20.01 or newer before deploying firmware 20.01 or newer.

Deploying endpoints from an earlier version of Management Console may cause endpoints to become unmanageable.

For further details see knowledge base article KB 3230

What's New in This Release

Use with Management Console version 20.01

This firmware should only be used with Management Console 20.01 or newer

4K Display Support

Support for 4K resolutions.

Security Updates

  • Remote Workstation Card cryptography library has been updated to the latest Mocana version.
  • PCoIP session encryption with AES-128-GCM has been removed, only AES-256-GCM can be used

Linux Brokering

Brokering of the Remote Workstation Card can now be done in Linux environments. See  Remote Workstation Card Agent for Linux.

Versioning Number Change

Remote Workstation Card firmware is on a new numbering scheme, where the first number is the release date year, and the second number is the release date month, and the third number is the number of maintenance releases.

Compatibility

Zero Client

  • Remote Workstation Card firmware 20.01 has been tested with Zero Client firmware 20.01 and 6.5.
  • Other Zero Client firmware may be compatible, but are not supported.

PCoIP Software Client

Management Console

  • PCoIP Management Console 20.01+ is required.

VMware Horizon

  • Tested with VMware Horizon View 7.10
  • Remote Workstation Card is compatible with PCoIP Secure Gateway 7.7 and older.

Resolved Issues

Image tearing has been removed.

62763

Image tearing has been eliminated when viewing moving content that is thin and vertical or diagonal in nature.

Known Issues

Local cursor corruption is observed when DPI other that 100% is used, for Zero Client to Remote Workstation Card connections.

90046

Cursor corruption observed if Windows DPI is greater than 100% on Remote Workstation Card connections

Workaround:

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

76283

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

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

Profile application to a Remote Workstation Card fails when Enable Audio has not been enabled

70793

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.

Workaround:

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.