Release Notes

Remote Workstation Card Firmware 5.1.0

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


Custom certificate support for direct connections to Remote Workstation Card

PCoIP Zero Clients can be paired to PCoIP Remote Workstation Cards using custom certificates to establish a secure PCoIP peer-to-peer connection.

Note: Best security practice

Teradici highly recommends using this new feature to create a more secure environment. Contact your IT department to ensure your deployment is in accordance with your Company's security policy.

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.2.0.
Zero Client firmware 6.2 is now the minimum requirement in order to connect to Remote Workstation Cards on this firmware release.

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

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

This release cannot be brokered in use with the Teradici Cloud Access Software.

This release cannot be brokered using the CMI brokering protocol.

       

 

Resolved Issues

None

Known Issues

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.