PCoIP Zero Client firmware 6.0.0 is now available

Question

We’re pleased to announce the release of PCoIP Zero Client firmware 6.0.0, which introduces support for Amazon Workspaces MFA on Tera2 Zero Clients, and other features and improvements.

Release of Teradici PCoIP® Zero Client Firmware 6.0.0 is now available and provides feature updates. This release introduces the following key features:

Amazon WorkSpaces session connection type with Multi-Factor Authentication now available
Removal of CounterPath Unified Communications - Unified Communications is no longer supported on Tera 2
TLS 1.1 is the minimum requirement for initiating PCoIP sessions
TLS 1.0 is no longer available to initiate PCoIP sessions. TLS 1.1 must be used as the minimum version to initiate PCoIP sessions. - This also means that if using host initiated wake with a Remote Workstation Card, the minimum firmware on the Remote Workstation Card must now be firmware 4.9.0 and VMware Horizon must be on release 6.2.1 or higher.
TLS 1.2 is the minimum requirement for establishing an Administrative Web Interface (AWI) session
The zero client Administrative Web Interface now requires web browsers that support TLS 1.2 - customers can download the software package and associated documentation free of charge from our Tech Support site at the links provided below.

IMPORTANT NOTE: Release 6.0.0 is the first release that is exclusive to our All Access customers. The firmware is available for download only for customers with an existing All Access license.

We recommend that you migrate to this version to experience all of its benefits. For complete details of this release, visit KB15134-3211.

If you have any questions or feedback, please reply to this post.

Answer 1

Answer by Chris · May 14, 2018 at 11:10 PM

@Patrick Mauro do you NEED to use MFA in order to directly connect to AWS Workspaces using the new 6.0 firmware? Is it possible to use standard username and password?

0 · Share

Answer 2

Answer by Team Orion · May 15, 2018 at 08:38 PM

The presence of the MFA field is driven by the AWS connection server. It instructs the zero client to display the field and require a value in it.

I haven't checked recently on it, but last time I looked, if you did not configure MFA for your WorkSpaces, then the AWS connection server would not verify the content. So you could enter anything into it. But you must enter something because the zero client has been instructed by that server to require a value.

Whether or not MFA is required is determined by AWS.

cheers,

Patrick

0 · Share

Answer 3

Answer by Chris · May 16, 2018 at 12:11 AM

Thanks - that worked. This should be in the release notes.

0 · Share

Answer 4

Answer by Raymond Tang · Jul 02, 2018 at 07:28 PM

Does 6.0 firmware support wildcard certs? I just upgraded my clients to 6.0 and they all error out that the cert does not match the cert on the server. Downgraded back to 5.5.1 and its fine again.

0 Show 1 · Share

Raymond Tang · Jul 02, 2018 at 08:26 PM 0

Share

Disregard...i figured it out. I had to set NTP on the 6.0. On 5.5.1, it never checked the time.

PCoIP Zero Client firmware 6.0.0 is now available

4 Replies

Your answer

Welcome to the PCoIP Community Forum!