Teradici Remote Workstation Card Firmware 4.2.0 Release Notes¶
Release Status: General Available GA
Release Overview: PCoIP Firmware 4.2.0 GA is a feature firmware release for Tera1 and Tera2 zero clients and host cards.
Individual releases are provided for Tera1 and Tera2 processor-based products, and a combined format for PCoIP Management Console. For complete descriptions see the Release Notes contained within the downloadable zip file.
|Key Release Details||Products||Platforms|
|Boot-up Splash Screen
If enabled in the factory, a splash screen is displayed briefly while the zero client is powering on and before the user connection screen appears.
|PCoIP Utility Bar Support
A GUI drop-down bar can now be used to disconnect a session or to shut down a remote workstation. When enabled, administrators can optionally pin this bar, and users can drag it to the left or right. This Utility Bar is disabled by default.
PCoIP Utility Bar Mode can be configured for all Tera2 zero clients Configuration> Session > Advanced Options page using the MC or AWI.
|Local USB Audio Support
USB audio devices attached to Tera2 zero clients may now be terminated locally, improving performance and interoperability. This feature is enabled by default. New options are also available for configuring the preferred USB audio input and output device to use when more than one device is connected to a zero client.
Zero client and host card AWI Audio pages have been moved from the Permissions menu to the Configuration menu.
|New Imprivata Features
The View Connection Server + Imprivata OneSign session type now has two new Imprivata options—Invert Wiegand Data and Restrict Proximity Cards.
|Unique Naming of SCEP Certificates
SCEP certificates are now configured with the requested certificate “Subject” as the PCoIP Device Name and the “Subject Alternative” as the device MAC address (all in lower case and with no dashes). Previously, the requested certificate "Subject" was hard-coded to "PCoIP Endpoint" and the “Subject Alternative” was left blank. This change makes the requested certificates traceable back to the original zero client.
This naming convention for SCEP certificates is not configurable.
|PCoIP Device Name Label Enhancement
The PCoIP Device Name label has been extended to allow the underscore character inside a device name. It cannot be the first or last letter.
|Event Log Filter Mode Enhancement
Administrators can now disable event logging on a device.
|RSA 2-factor Authentication Support
In addition to traditional smart card and username/password authentication, this feature enables the user to add RSA SecurID for user authentication as the second authenticator.
Note: This feature is not configurable in firmware.
|RADIUS 2-factor Authentication Support
In addition to the traditional smart card and username/password authentication, this feature enables the user to add a second authenticator (i.e., RADIUS username/password, RSA SecurID) for user authentication.
Note: This feature is not configurable in firmware.
|Key Resolved Details||Products||Platforms|
|10672 - Resolved an issue where PCoIP zero clients may reset when using PCoIP Management Console 1.9.0.||✔||✔||✔||✔|
|10652 - Smart cards that are provisioned using SafeNet 2.10 software can now be used for pre-session authentication on zero clients.||✔||✔|
|10504 - For users who authenticate using Proximity Card plus Password, if the user types the wrong password, typing the correct password on retry triggers Password authentication only rather than Proximity Card plus Password authentication. This prevents tap-out from working correctly, and does not start the grace period timer (if enabled). This is resolved.||✔||✔||✔|
|10464 - When a View Connection Server is configured for RADIUS mode, user passwords are no longer limited to 16 characters.||✔||✔||✔||✔|
|10419 - If a display was unplugged from a Tera2 client while in session with a hard host, when the session disconnects, the OSD sometimes does not display correctly until the zero client is rebooted. This is resolved.||✔||✔|
|10381 - A zero client in CMI mode is unable to remotely power on a workstation containing a PCoIP remote workstation card using Wake-on-LAN under the following conditions:
Requirements: Two workstations (A & B), one zero client and a CMI connection broker.
The PCoIP connection attempt times out and host B does not power on.
This is now resolved.
|10390 - Resolved an issue where the zero client resets when trying to connect to a host while a USB hub is connected to a zero client root port and two or more hubs are connected to this hub.||✔||✔||✔||✔|
|10276 - Server certificates that use Subject Alternative Names (SANs) to identify the server without having a Common Name in their Subject field are now accepted by zero clients.||✔||✔||✔||✔|
|10244 - Workstation hosts no longer remain in a state where they cannot be discovered via SLP after being powered off from a zero client and subsequently powered on directly from the workstation's power switch. Previously, only the zero client from where the host was powered off is able to reconnect to the host; other zero clients fail to find that host through SLP discovery.||✔||✔||✔|
|10212 - Resolved an issue where banner logo images could be corrupted by moving OSD dialog boxes containing the banner logo images around the OSD screen.||✔||✔||✔||✔|
|10042 - In the OSD, if you press Tab and Caps Lock at the same time, the keyboard Caps Lock indicator light now correctly shows the Caps Lock state.||✔||✔||✔||✔|
|10010 - When the zero client is configured to use the German language the VMware View desktop selection dialog's Reset VM button now fits the German text. This button has always functioned properly. Now, the first and last letter of the button text are not cut off.||✔||✔||✔||✔|
|10004 - Resolved an issue where microphone recording in sessions between zero clients, Linux, and Windows workstations can have a low signal-to-noise ratio. This occurs when the workstation is using the Realtek audio driver to control a Realtek audio codec chip. The recorded audio quality is normal during the first PCoIP session after the workstation boots up and noisy in the following PCoIP sessions.||✔||✔||✔|
|9761 - Resolved an issue where the Permissions->USB web page fails to load properly when using the IE 10 web browser to access the Administrative Web Interface (AWI) of a zero client or host card, where the user typically sees a partially populated web page.||✔||✔||✔||✔|
|9648 - Resolved an issue with Tera2 dual display clients where the second display may not work if the first display is dual-link and preferred resolution override is enabled.||
|This PCoIP firmware is compatible with the release of VMware Horizon View that was generally available when this firmware was released. It is also compatible with one major release of Horizon View prior to this. Other versions of Horizon View may also be compatible, but will need to be verified in your specific deployment environment.
The version of Horizon View available at the time of this firmware release was Horizon View 5.2.
|Deployments using the PCoIP Management Console to manage Tera2 endpoints must use PCoIP MC release 1.8.1 or newer.||✔||✔||✔|
|Deployments using the PCoIP Management Console to manage Tera1 endpoints must use PCoIP MC release 1.7.0 or newer.
Using the latest release of the PCoIP Management Console is recommended.
|While mixed firmware release operation is not tested, firmware 4.2.0 is compatible with 4.1.x, 4.0.x, 3.5.x, 3.4.x, 3.3.x 3.2.x and 3.1.x releases.||✔||✔||✔|
|Firmware 4.2.0 is not interoperable with firmware releases 3.0, 2.x, 1.x or 0.x.||✔||✔||✔|