dell wyse pcoip firmware release 5.2.2 release notes · dell wyse pcoip firmware release 5.2.2...

Dell Wyse PCoIP Firmware Release 5.2.2Release NotesNew releases are created to support new hardware platforms, correct defects, make enhancements, or add new features. These releases are tested and supported on current, actively shipping hardware platforms, and those hardware platforms that are within their first year after their official End-of-Life date, as applicable. After the one year time period, new software releases are no longer certified for use with the earlier version of the hardware, even though it is possible that they may still work. This allows us to advance our product with features and functions that might not have been supported by the previous hardware, with previous generation CPUs and supporting components.

Release Date: 2016-11

Contents

Release overview................................................................................................................................................................ 1Supported platforms..........................................................................................................................................................2Upgrade scenarios............................................................................................................................................................. 2Scenario 1: Upgrading from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDM.................................................2Deploying certificate to ThreadX 4.x devices.................................................................................................................3Deploying Teradici image version 5.x...............................................................................................................................3Compatibility notes............................................................................................................................................................ 4New features..................................................................................................................................................................... 11Key resolved issues.......................................................................................................................................................... 14Useful links........................................................................................................................................................................26

Release overviewPColP Zero Client Firmware 5.2.2 is firmware for Tera2 Zero Clients only and not for Remote Workstation Cards. This document provides a summary of upgrade scenarios, key feature additions, compatibility notes, and upgrade paths for 5.2.2 firmware release.

NOTE:

WDM related:

• WDM v5.7.1 supports 4.x, 5.2.1, and 5.2.2 versions of firmware.

• Earlier versions of WDM support only 4.x. If you are using earlier versions of WDM, then upgrade the WDM to version 5.7.1, and proceed with the firmware update.

Teradici console related:

• PColP Management Console 2.x cannot detect or manage devices on firmware versions prior to version 5.0. If upgrading from firmware 4.x, then either the zero client AWI or PColP Management Console 1.10.3-1.10.7 must be used to upgrade the zero client to firmware 5.x.

• Zero clients on firmware 5.x can only be managed by PColP Management Console 2.0 or later. PColP Management Console 1.x cannot detect or manage devices on firmware 5.x.

2016 - 11

Dell Wyse PCoIP Firmware Release 5.2.2Release Notes

1

• Either zero client firmware 4.7.x or 4.8 must be used as the staging firmware before upgrading to firmware 5.2 and later.

Supported platformsThis release supports the following platforms:

• Wyse 5030 zero client for VMware

• Wyse 5050 AIO thin client with PCoIP

• Wyse 7030 zero client for VMware

Upgrade scenariosThe following are the different upgrade scenarios for this product:

1 Upgrade path from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDM

For more information on this scenario, see Upgrade path from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDM.

2 Upgrade path from earlier version 4.x versions to 5.2. using WDM

Customer who have earlier version of the Dell Wyse Teradici products should first upgrade their clients to version 4.8, and then follow the instructions explained in scenario 1.

3 Upgrade path from 5.x to 5.2.2 using Teradici Console

Customers who are using Teradici Console need to follow the Teradici instructions available at Teradici Knowledge Base.

Scenario 1: Upgrading from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDMPrerequisites

The following are the prerequisites for upgrading from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDM:

• Wyse Device Manager (WDM) 5.7.1

• Windows Server 2012/2012 R2

Scenario

• New installed WDM 5.7.1 in the Windows server 2012 R2

• ThreadX services installed

• Availability of existing ThreadX4 devices firmware version 4.8.0

• All the required DNS SRV records, and PCoIP Endpoint Vender Class for DHCP are already set up – For more information, see WDM 5.7.1 Admin Guide, section, Upgrading the ThreadX 4.x devices to ThreadX 5.x from WDM.

NOTE: A new DHCP Endpoint Vendor class, and Endpoint Bootstrap Manager URI (EBM URI) are available which must be implemented for WDM 5.7.1 to manage Teradici.

For more information on upgrading from 4.8 (ThreadX 4.x) to 5.2.2 (ThreadX 5.x) using WDM, see WDM 5.7.1 Administrator’s Guide sections—Management of ThreadX 5.X devices using WDM web UI and Upgrading the ThreadX 4.x devices to ThreadX 5.x from WDM.

2 Dell Wyse PCoIP Firmware Release 5.2.2Release Notes

HTTPS://TECHSUPPORT.TERADICI.COM/LINK/PORTAL/15134/15164/ARTICLE/2936/-ZERO-CLIENTS-5-2-2-AND-PCOIP-SOFTWARE-CLIENTS-1-9GUID-CFE3FF16-69DA-4F96-97B6-DACB9785B70A

Steps

For upgrading the ThreadX4 device from firmware 4.8.0 to 5.x version, a certificate should be pushed in to the device. The certificate is named cert.pem, and is located in the folder C:\Program Files (x86)\Wyse\WDM\TeraDici.

NOTE:

This certificate is unique to every WDM installation.

Deploying certificate to ThreadX 4.x devicesTo deploy the certificate on ThreadX 4.x devices, do the following:

1 Start the WDM GUI and log in to WDM with administrator privileges.

2 Go to Applications > PCoIP Configuration Packages.

3 Click +, and download the PCoIP configuration manager utility.

4 Start the downloaded utility, and select Version 4.x.

5 Click the Security, and enable certificate check box.

6 Copy the cert.pem certificate contents including the first and last line (Begin certificate and End certificate).

By default, the cert.pem certificate is located in the folder C:\Program Files(x86)\Wyse\WDM\TeraDici.

7 Paste the cert.pem contents in the text box displayed.

8 Enter the name and the description for the package in the respective text box.

9 Click Register, and save the configuration.

10 Go to the Devices page in WDM web UI, and select the desired device using the check box.

11 Click Update, and select the created configuration package from the PCoIP Configuration Packages category, and then click Save.

12 Go to the Jobs page and confirm that the package deployment is successfully completed.

Deploying Teradici image version 5.xPre-requisites

The Teradici firmware update Repository Support Package (RSP) must be created with the new OS type TDC5.To deploy Teradici image version 5.x, do the following:

1 Launch the WDM web UI, and log in as administrator.

2 Go to Applications > Images, and click + to download the package registration utility.

3 Click RSP from the package registration utility.

4 Click Browse, and upload ThreadX 5.x firmware package to WDM.

5 Go to the Devices page in WDM web UI.

6 Select the devices which have to be upgraded using the check box.

7 Click Update, and select the registered package from the Imagescategory.

8 Click Save to schedule package deployment. The package should get deployed.

9 Go to the Jobs page, and confirm whether the package deployment is successfully completed. The device should get rebooted and discovered to WDM automatically as ThreadX_5x devices.

Scripting example for ThreadX 5 for building the Teradici image package for WDM 5.7.1.

[Version][email protected]=PCoIP Tera2 Firmware Release 5.2.2 for P25, P45, and 5050 AIOOS=TDC5ImageSize=0ImageType=merlinCategory=Images[Script]RB


3

Compatibility notesThe following table contains compatibility notes for 5.0 - 5.2.2 firmware updates:

Table 1. Compatibility notes

Version Description Tera2 Zero Client Workstation Vmware

Horizon

Amazon WorkSpaces

Teradici Pervasive Computing Platform

5.0.0

The PCoIP firmware is compatible with release of the VMware Horizon View that is 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 you must verify in your specific deployment environment. The version of Horizon View available at the time of the PCoIP firmware release was Horizon 6.1.1 and 6.2.

X X

5.0.0

This PCoIP Zero Client Firmware 5.0 and higher requires PCoIP Connection Manager for the Amazon WorkSpaces version 1.0.2 (/techsupport.teradici.com/ics/support/KBAnswer.asp? questionID=2237) or higher to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

X X

5.0.0

Deployments using the PCoIP Management Console to manage Tera2 zero clients on Firmware 5.0 must use the PCoIP MC release 2.0 or later. Using of the latest release of the PCoIP Management Console is recommended.

X

5.0.0

While mixed firmware release operation is not supported, Zero Client Firmware 5.0 is tested to work with the Workstation Access Cards on Workstation Access Card Firmware 4.7.2

NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.0. The Management Console 2.0 to manage the zero clients, and Management Console 1.x to manage Remote Workstation Cards until as there is a Remote Workstation Card firmware release that is supported by Management Console 2.0

X X

5.0.0Client Firmware 5.0 has been tested against Imprivata OneSign 5.0 with VMware Horizon View 6.1.1.

X X

5.0.0

Zero Client Firmware 5.0 is tested with the Leostream Connection Broker version 8. The Zero Client Firmware 5.0 is not compatible with earlier versions of the Leostream Connection Broker.

X X X X


HTTPS://TECHSUPPORT.TERADICI.COM/ICS/SUPPORT/KBANSWER.ASP? QUESTIONID=2237




Horizon

Amazon WorkSpaces


NOTE: After upgrading to Zero Client Firmware 5.0, the session connection type for the zero client must be changed to PCoIP Connection Manager, with the address of the Leostream Connection Broker. Also ensure that the Leostream Connection Broker has Enable TLSv1.1 protocol enabled in the Connection Broker Security Options section of the Connection Broker > System > Settings page.

5.0.2

This PCoIP firmware is compatible with the release of VMware Horizon View that is generally available when this firmware is 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 needs to be verified in your specific deployment environment. The version of Horizon View available at the time of this firmware release was Horizon 6.2.

X X

5.0.2

This PCoIP Zero Client Firmware 5.0 and higher requires Teradici PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA (https://techsupport.teradici.com/link/portal/15134/15164/Article/2733) or higher to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

X X

5.0.2

Deployments using the PCoIP Management Console to manage Tera2 zero clients on Firmware 5.0 must use the PCoIP MC release 2.0 or newer. Using the latest release of the PCoIP Management Console is recommended.

X

5.0.2

While mixed firmware release operation is not supported, Zero Client Firmware 5.0 has been tested to work with Workstation Access Cards on Workstation Access Card Firmware 4.7.2.

NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.0. The Management Console 2.0 is used to manage the zero clients, and Management Console 1.x to manage Remote Workstation Cards until there is a Remote Workstation Card firmware release that is supported by Management Console 2.0.

X X X


5

HTTPS://TECHSUPPORT.TERADICI.COM/LINK/PORTAL/15134/15164/ARTICLE/2733




Horizon

Amazon WorkSpaces


5.0.2Zero Client Firmware 5.0 has been tested against Imprivata OneSign 5.0 with VMware Horizon View 6.1.1.

X X

5.0.2

Zero Client Firmware 5.0 is tested with the Leostream Connection Broker version 8. Zero Client Firmware 5.0 is not compatible with earlier versions of the Leostream Connection Broker.


.

X X X X

5.1.1

This PCoIP firmware is compatible with the release of VMware Horizon that was generally available when this firmware was released. It is also compatible with one major release of Horizon prior to this. Other versions of Horizon may also be compatible, but needs to be verified in your specific deployment environment. The version of Horizon available at the time of this firmware release was Horizon 7.0.

X X

5.1.1

PCoIP zero client firmware 5.0 and later requires Teradici PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA (https://techsupport.teradici.com/link/portal/15134/15164/Article/2733) or later to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

X X

5.1.1

Deployments using the PCoIP Management Console to manage Tera2 zero clients on firmware 5.1 must use the PCoIP MC release 2.0 or newer. Using of the latest release of the PCoIP Management Console is recommended.

X

5.1.1

While mixed firmware release operation is not supported, zero client firmware 5.1 is tested to work with Remote Workstation Cards on the Remote Workstation Card firmware 4.7.2.

X X X






Horizon

Amazon WorkSpaces


NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.1. The Management Console 2 is used to manage the zero clients, and Management Console 1.x is used to manage Remote Workstation Cards until there is a Remote Workstation Card firmware release that is supported by Management Console 2.0 or higher.

5.1.1Zero client firmware 5.1 is tested against Imprivata OneSign 5.1 with VMware Horizon 6.2.

X X

5.1.1

Zero Client Firmware 5.1 is tested with the Leostream Connection Broker version 8. Zero Client Firmware 5.1 is not compatible with earlier versions of the Leostream Connection Broker.


X X X X

5.1.1

Web browsers must support TLS 1.1 or later to connect to the Administrative Web Interface (AWI). The recommended browsers are Firefox 45, Chrome 47, and Internet Explorer 11. Internet Explorer 8, 9, and 10 require TLS 1.1 or 1.2 to be enabled in the Internet Options dialog box, Advanced tab to connect to the AWI Internet Explorer 7 and earlier cannot connect to the AWI.

X

5.2.0


X X

5.2.0PCoIP zero client firmware 5.0 and higher requires Teradici PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA (https://

X X


7



Horizon

Amazon WorkSpaces


techsupport.teradici.com/link/portal/15134/15164/Article/2733) or higher to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

5.2.0

Deployments using the PCoIP Management Console to manage Tera2 zero clients on firmware 5.2 must use the PCoIP MC release 2.0 or later. Use of latest release of the PCoIP Management Console is recommended.

X

5.2.0

While mixed firmware release operation is not supported, zero client firmware 5.2 has been tested to work with Remote Workstation Cards on the Remote Workstation Card firmware 4.7.4.

NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.2. The Management Console 2 is used to manage the zero clients, and Management Console 1.x is used to manage Remote Workstation Cards until there is a Remote Workstation Card firmware release that is supported by Management Console 2.0 or higher.

X X X

5.2.0 Zero client firmware 5.2 has been tested against Imprivata OneSign 5.1 with VMware Horizon 7.0. X X

5.2.0

Zero client firmware 5.2 is tested with the Leostream Connection Broker version 8. Zero client firmware 5.2 is not compatible with earlier versions of the Leostream Connection Broker.

NOTE: After upgrading to zero client firmware 5.2, the session connection type for the zero client must be changed to PCoIP Connection Manager, with the address of the Leostream Connection Broker. Also ensure that the Leostream Connection Broker has Enable TLSv1.1 protocol enabled in the Connection Broker Security Options section of the Connection Broker > System > Settings page.

X X X X

5.2.0

Supported browsers are Firefox 46, Chrome 50, Internet Explorer 11, and Microsoft Edge 25. Web browsers must support TLS 1.1 or later to connect to the Administrative Web Interface (AWI).

X

5.2.1

This PCoIP firmware is compatible with the release of VMware Horizon that was generally available when this firmware was released. It is also compatible with one major release of Horizon prior to this. Other versions of Horizon may also

X X





Horizon

Amazon WorkSpaces


be compatible, but needs to be verified in your specific deployment environment. The version of Horizon available at the time of this firmware release was Horizon 7.0.

5.2.1

PCoIP Zero Client Firmware 5.0 and later requires PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA or later to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

X X

5.2.1

Deployments using the PCoIP Management Console to manage Tera2 Zero Clients on firmware 5.2 and above must use the PCoIP Management Console release 2.0 or newer. Use of the latest release of the PCoIP Management Console is recommended.

X

5.2.1

While mixed firmware release operation is not supported, firmware 5.2 has been tested to work with Remote Workstation Cards on the Remote Workstation Card firmware 4.7.4.

NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.2. The version 2 to manage the zero clients, and version 1.x to manage Remote Workstation Cards until there is a Remote Workstation Card firmware release that is supported by PCoIP Management Console 2.0 or later.

X X X

5.2.1 PCoIP Zero Client Firmware 5.2 is tested against Imprivata OneSign 5.1 with VMware Horizon 7.0. X X

5.2.1

PCoIP Zero Client Firmware 5.2 is tested with the Leostream Connection Broker version 8. It is not compatible with earlier versions of the Leostream Connection Broker.

NOTE: After upgrading to PCoIP Zero Client Firmware 5.2, the session connection type for the zero client must be changed to PCoIP Connection Manager, with the address of the Leostream Connection Broker. Also ensure that the Leostream Connection Broker has Enable TLSv1.1 protocol enabled in the Connection Broker Security Options section of the Connection Broker > System > Settings page.

X X X X

5.2.1Supported browsers are Firefox 46, Chrome 50, Internet Explorer 11, and Microsoft Edge 25.Web browsers must support TLS 1.1 or later to

X


9


Horizon

Amazon WorkSpaces


connect to the administrative web interface (AWI).

5.2.2


X X

5.2.2

PCoIP Zero Client Firmware 5.0 and later requires PCoIP Connection Manager for Amazon WorkSpaces 1.0.2 GA or later to connect to Amazon WorkSpaces. It is not compatible with earlier versions of the PCoIP Connection Manager for Amazon WorkSpaces.

X X

5.2.2

Deployments using the PCoIP Management Console to manage Tera2 Zero Clients on firmware 5.2 and above must use the PCoIP Management Console release 2.0 or newer. Use of the latest release of PCoIP Management Console is recommended.

X

5.2.2

While mixed firmware release operation is not supported, firmware 5.2 has been tested to work with Remote Workstation Cards on the Remote Workstation Card firmware 4.7.5.

NOTE: You may require to use both the versions of Management Console to connect Remote Workstation Cards using Zero Client on Firmware 5.2. The Management Console 2 is used to manage the zero clients, and version 1.x is used to manage Remote Workstation Cards until there is a Remote Workstation Card firmware release that is supported by PCoIP Management Console 2.0 or higher.

X X X

5.2.2 PCoIP Zero Client Firmware 5.2 is tested against Imprivata OneSign 5.1 with VMware Horizon 7.0. X X

5.2.2

PCoIP Zero Client Firmware 5.2 is tested with the Leostream Connection Broker version 8. It is not compatible with earlier versions of the Leostream Connection Broker.

X X X X



Horizon

Amazon WorkSpaces


NOTE: After upgrading to PCoIP Zero Client Firmware 5.2, the session connection type for the zero client must be changed to PCoIP Connection Manager, with the address of the Leostream Connection Broker. Also ensure that the Leostream Connection Broker has Enable TLSv1.1 protocol enabled in the Connection Broker Security Options section of the Connection Broker > System > Settings page.

5.2.2

Compatible browsers: Firefox, Internet Explorer 11, Chrome, Edge.

Tera2 Zero Client firmware is tested against the browser version available prior to release.

X

New featuresThe following table contains the new features:

Table 2.

Version Description Tera2 Zero Client Workstation

Vmware Horizon

Amazon WorkSpaces


5.0.0

12885. Added support for Management Console 2.0. Introduced new management protocol for improved management scalability and performance. The old management protocol CMI is removed, and there is no support to connect to older versions of Management Console.

X

5.0.0

12885. Added support for Management Console 2.0. Introduced new management protocol for improved management scalability and performance. The old management protocol CMI is removed, and there is no support to connect to older versions of Management Console.

X

5.0.0

28663. Relocated the language and keyboard layout controls from the OnScreen Display's Configuration dialog box to the User Settings dialog box. In addition, the Zero Client's time zone can now be configured from the User Settings dialog box. Configuration of language, keyboard layout, and time zone in the OSD can be disabled using the PCoIP Management Console.

X

5.0.0

28240 & 23205. Administrative Web Interface (AWI) and the PCoIP Connection Manager connections updated to more modern ciphers. The following ciphers are added: TLS_RSA_WITH_AES_256_GCM_SHA384

X X X X


11


Vmware Horizon

Amazon WorkSpaces


TLS_RSA_WITH_AES_128_GCM_SHA256

TLS_RSA_WITH_AES_256_CBC_SHA256


TLS_RSA_WITH_AES_256_CBC_SHA

The following ciphers were removed:

TLS_RSA_WITH_RC4_128_SHA

TLS_RSA_WITH_3DES_EDE_CBC_SHA

The complete cipher suite list (in order of preference) is: TLS_RSA_WITH_AES_256_GCM_SHA384

TLS_RSA_WITH_AES_128_GCM_SHA256





NOTE: Internet Explorer 7 is no longer supported as a result of this change.

28138. Zero Clients enable both the AES-128-GCM and AES-256-GCM session encryption algorithms for all sessions. Administrators that wish to disable one of the two algorithms can do so in the Security Gateway and/or PCoIP host components.

X

5.0.0

27059. The Administrative Web Interface setting Session Negotiation Cipher has been renamed to "Session Negotiation Cipher Suites". The setting option Disable SHA-1 introduced in FW 4.8.0 has been removed. Clients configured to use this setting uses Maximum Compatibility: TLS 1.0 or higher with RSA keys instead. The TLS cipher suites used for the Maximum Compatibility: TLS 1.0 or higher with RSA keys option is expanded to include ciphers that use the SHA-256 and SHA-384 HMAC algorithms and support Perfect Forward Secrecy.

X

5.0.0

10058. Added support for the VMware custom keyboard layout codes to enable synchronization of more keyboard layouts between the zero client and Horizon when connected using PCoIP.

X X

5.0.0

29962. Added support for the following Wacom tablets:

• | Product ID | Description|• | 0x00B0 | Wacom Intuos3 4x5 |• | 0x00B1 | Wacom Intuos3 6x8 |

X X



Vmware Horizon

Amazon WorkSpaces


• | 0x00B2 | Wacom Intuos3 9x12 |







• | 0x00BA | Wacom Intuos4 8x13 |

• | 0x00BB | Wacom Intuos4 12x19 |

• | 0x00BC | Wacom Intuos4 WL |

• | 0x0026 | Wacom Intuos5 touch S |

• | 0x0027 | Wacom Intuos5 touch M |

• | 0x0028 | Wacom Intuos5 touch L |

• | 0x0029 | Wacom Intuos5 S |

• | 0x002A | Wacom Intuos5 M |

• | 0x0314 | Wacom Intuos Pro S |

• | 0x0315 | Wacom Intuos Pro M |

• | 0x0317 | Wacom Intuos Pro L |

• | 0x00F4 | Wacom Cintiq 24HD |

• | 0x00F8 | Wacom Cintiq 24HD touch |

• | 0x003F | Wacom Cintiq 21UX |

• | 0x00C5 | Wacom Cintiq 20WSX |

• | 0x00C6 | Wacom Cintiq 12WX |

• | 0x0304 | Wacom Cintiq 13HD |

• | 0x0057 | Wacom DTK2241 |

• | 0x0059 | Wacom DTK2242 |

• | 0x00CC | Wacom Cintiq 21UX2 |

• | 0x00FA | Wacom Cintiq 22HD |

• | 0x005B | Wacom Cintiq 22HDT |

5.1.142141. Added support for pre-session authentication using the SafeNet eToken 4100 smart card with VMware Horizon.

X X

5.1.135614. Extended SafeNet AT SC650 smart card with VMware Horizon to include to support for BLADE in addition to PKI.

X X

5.1.1

39323. Additional SHA-256 cipher suites are added for connection to VMware Horizon (View) Connection servers: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA


X X


13


Vmware Horizon

Amazon WorkSpaces


5.1.1

40562. Additional SHA-256 cipher suites are added for TLS connections to the Imprivata OneSign servers: ECDHE-RSA-AES128-GCM-SHA256 AES128-GCM-SHA256 AES128-SHA256 AES256-SHA256

X X

5.1.1

36467. Out-of-band password changes of the OneSign users now supported. OneSign users who have their passwords changed outside of OneSign can now enter their new password into the zero client when authenticating against a OneSign server.

X X

5.1.1

33130. Multi-question input based authentication when zero clients are connected using PCoIP Connection Manager sessions. Brokers can now request information from the user of the zero client to satisfy authentication methods such as security questions or multi-factor authentication.

X X

5.1.1

35973. The zero client AWI now requires a minimum of TLS 1.1 for connections. Browsers that do not support TLS 1.1 or higher are no longer supported. Recommended web browsers are Firefox, Chrome, and Internet Explorer 11. Internet Explorer 8, 9, and 10 require TLS 1.1 or 1.2 to be enabled in the Internet Options dialog's Advanced tab to connect to the AWI Internet Explorer 7 can no longer connect to the AWI.

X

5.2.0The certificate for the Administrative Web Interface (AWI) is updated to a SHA-256 certificate

X

Key resolved issues

Table 3. Key resolved issues

Version Issue Tera2 Zero Client Workstation Vmware Horizon Amazon WorkSpaces


5.0.0

33229. When using Swiss-German keyboard layouts, Strg + Alt key combination does not generate the correct character.

X

5.0.0

32825. Evoluent Vertical Mouse 4 fails to work on a Linux workstation.

X X




5.0.0

30928. If you are using Bloomberg keyboard and Auto Power-Off Timeout is set, Wake-on-USB may fail if the zero client is put to sleep using the power button.

X

5.0.0

30480. Unable to access some characters from the German keyboards using Strg+Alt key combination in the OSD

X

5.0.0

30104. Stylus used with Intuos CTH-680 behaves erratically while in the OSD.

X

5.0.0

30009. Some keyboard models have LEDs that would not toggle from within the zero client OSD.

X

5.0.0

29675. When downgrading from firmware 5.0.0 to 4.x, the timezone defaults to UTC.

X

5.0.0

29194. Unable to enter some accent keys using the Swiss-German keyboard.

X

5.0.0

28964. Network Connection Loss message may be displayed on zero clients connected to Horizon 6 if Enable Peer Loss Overlay is configured and the zero client is power cycled.

X


15



5.0.0

28958. If a smart card is removed and inserted again, when using with the Gemalto middleware software and Windows 7, web browser may not be able to read certificates from the card.

X X

5.0.0

28601. A Zero Client can occasionally become nonresponsive with a black screen on session tear-down.

X X X X X

5.0.0

26382. The wake on USB capable devices may fail to wake the Zero Client from standby power state.

X X

5.0.0

26361. Cursor movement on a device that has more than one HID interface, demonstrates erratic behavior in the OSD.

X

5.0.025499. VisionX Cheque Scanner fails to operate.

X X X

5.0.0

21157. From the AWI, user will be prompted to reset the zero client after submitting changes to the session configuration advanced options while it is configured for the Direct to Host + SLP Host Discovery type. The reset is not necessary if the only changes are mode to the advanced options

X




and if the session type is unchanged.

5.0.2

38500. The Tera2 Zero Client VMware recovery image always boots the ZC to the standby state, regardless of settings declined by the manufacturer. This is known to impact Amulet Hotkey DXZ4 zero clients, causing a lock up of the zero client that requires it to be returned to the factory for repair when the DXZ4 is booting the recovery image. It does not occur when the DXZ4 is booting the primary image.

X

5.0.2

36515. When the card belonging to the current user is tapped on a RFIDeas proximity card reader connected to the front USB ports of an Atrust w100 zero client to end a OneSign-brokered PCoIP session the zero client may immediately start another PCoIP session for that user

X X

5.0.2

36416. The zero client does not retrieve the VCS address provisioned in the DNS _PCoIP-VCS SRV record.

X X

5.0.236407. Sometimes, the zero client may

X


17



stop communicating with the Management Console. This appears as a client that never shows that it is online from within the Management Console, even when it is.

5.0.2

34957. The Zero Client On-Screen Display and Administrative Web Interface offer the Connection Manager Interface Session Connection Type after upgrading to Tera2 Zero Client firmware 5.0.0. This mode is nonfunctional. Firmware 5.0.0 does not support brokering sessions using the Connection Management Interface.

X

5.0.2

34896. A PCoIP Management Console 2.0 Enterprise Edition profile that configures the Trap NMS Address field as a hostname fails to apply to the Tera2 Zero Client.

X

5.0.2

25083. When applying a Management Console 2.0 Enterprise Edition profile that contains certificates totaling more than 84,386 bytes, the zero client may enter a state where the AWI is

X




nonresponsive and the zero client is unable to connect to the Management Console. Rebooting the zero client resolves the issue.

5.1.1

44965. The zero client may reboot when attempting to connect to a PCoIP Management Console that is not responding to TLS handshake requests in a timely manner

X

5.1.1

43869. Zero clients fail automated smart card login to VMware View Windows 2012 RDSH sessions because Windows 2012 sends an unexpected smart card control message to the zero client.

X

5.1.1

42108. Zero clients can repeatedly reboot if the DHCP option for Management Console (MC) 2.x server certificate fingerprint has exactly one more character than expected or if DNS TXT record for MC 2.x server certificate fingerprint string is longer than expected. Workaround: Format the certificate fingerprint string in DHCP/DNS server as per MC 2.0 manual.

X


19



5.1.1

40953. Some smart card authentication using a PIV card against VMware Horizon may fail if the Card Capabilities Container identifier is an unexpected length.

X X

5.1.1

40729. Removing a smart card from a reader during a PCoIP session while the smart card is being accessed may cause the zero client to restart.

X X

5.1.1

40629. Smart card authentication using a PIV card against VMware Horizon may fail if the certificate contains a compressed certificate.

X X

5.1.1

38541. The Management Console cannot reboot a zero client after resetting it to the factory defaults. Workaround: Reboot the zero client manually.

X

5.1.1

37709. The zero client required a DNS reverse lookup record (PTR) for the FQDN used in DNS pcoip-bootstrap SRV record for MC 2.x address to find the MC 2.x certificate fingerprint TXT record. When the PTR record does not exist, the zero client is unable to

X




authenticate its Endpoint Manager using the TXT record.

5.1.1

36051. Some zero client time zones are not pushed across to software PCoIP servers during session negotiation. The resulting session uses UTC time on the PCoIP server host. The affected time zones are: Australia/Eucla Australia/Lord_Howe Pacific/Chatham Pacific/Kiritimati Pacific/Marquesas Pacific/Norfolk America/Adak America/Metlakatla Pacific/Pitcairn Pacific/Gambier Pacific/Easter America/Miquelon Antarctica/Troll America/Atikokan America/Argentina/Catamarca America/Argentina/Cordoba Atlantic/Faroe Asia/Gaza Asia/Hebron Asia/Istanbul Europe/Nicosia Africa/Asmara Asia/Kolkata Pacific/Chuuk Pacific/Pohnpei

X X X X

5.1.1

38975. The ID_box scanner from ICAR does not bridge to the VMware Horizon host.

X X

5.1.133494. If the management server provides a

X


21



certificate without a Common Name (CN), the zero client may reboot.

5.1.1

10339. Smart card authentication using a PIV card against VMware Horizon may fail if the card capabilities container has multiple CardApplicationURLs.

X X

5.1.1

42211. The zero client fails to pick up the DHCP option value for Management Console 2.x fingerprint information from certain non-Windows DHCP server products (like InfoBlox) because the DHCP data string from the DHCP server is not null terminated. Workaround: Use DNS record option to provide MC 2.x address and certificate fingerprint information

X

5.2.0

43050. In the zero client OSD, some accent characters on the Swiss-French keyboard may be incorrect depending on the order in which the keys are held and released.

X

5.2.0

42570. The zero client may occasionally crash when the connection to the host is put under

X X




severe network impairment and video content is changing.

5.2.0

41963. The zero client may crash when trying to simultaneously connect to Management Console and View Connection Server (by having Auto Connect to VCS feature enabled) if the Management Console and View Connection Server certificate both have an Online Certificate Status Protocol (OCSP) responder.

X

5.2.0

40702. The zero client does not reboot after completing a Reset to Factory Defaults command initiated by an Endpoint Manager such as the PCoIP Management Console. Workaround: Follow the Reset to the Factory Defaults command with a Power Reset command or reboot the Zero Client manually.

X

5.2.0

36497. The Promethean electronic whiteboard is not accessible by the PCoIP host when connected to a zero client.

X X

5.2.0

45722. A zero client configured for Wake-on-USB will stay powered

X X


23



after being connected to DC power instead of going to sleep.

5.2.0

44949. Smart card authentication using a Gemalto access client card against VMware View may fail for certain card configurations

X

5.2.0

10079. The zero client may stop updating display content after a network interruption caused by a spanning tree-driven network change.

X X X X X

5.2.0

42211. The zero client fails to pick up the DHCP option value for Management Console 2.x fingerprint information from certain non-Windows DHCP server products (like InfoBlox) because the DHCP data string from the DHCP server is not null terminated.

X

5.2.1

49077. Samsung NC241 Zero Client no longer fails to boot. The Samsung NC241 Zero Client did not boot in this scenario: Disconnect an active PCoIP session using the Auto hardware button on the NC241 Power down the zero client using the hardware power button Attempt




to power up the zero client using the hardware power button After step 3 the NC241 fails to boot successfully and remains at a black screen. This issue is fixed.

5.2.1

48667. Preferred Resolution Override no longer causes the VMware View connection failures. Previously, a zero client might fail to establish a PCoIP session with a VMware Horizon View PCoIP host when Preferred Resolution Override was enabled. After selecting a desktop, the zero client display(s) went black for 30 seconds followed by a message saying "You have been disconnected". The VMware Horizon View agent log contained "Assert at function get_native_dmt". This issue has been fixed.

5.2.2

53400: Recovery image now correctly starts when manufacturer has set a default non-US keyboard Previously, recovery image failed to start when manufacturer defined default keyboard was not a US keyboard. The recovery image now


25



correctly starts when the zero client manufacturer has set the default keyboard to a non-US keyboard.

Useful linksThe following is the list of important links:

• WDM links: downloads.dell.com/wyse/wdm/.

• Teradici PCoIP® Zero Client Administrator's Guide: www.teradici.com/web-help/PCoIP_ZC_Config_HTML5/TER1504003_PCoIP_ZC_Config.htm.

• PColP® Management Console 2.2: techsupport.teradici.com/ics/support/kbanswer.asp?deptID=15164&task=knowledge&questionID=2905&languageID=.

Copyright © 2016 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.


HTTPS://DOWNLOADS.DELL.COM/WYSE/WDM/

HTTP://WWW.TERADICI.COM/WEB-HELP/PCOIP_ZC_CONFIG_HTML5/TER1504003_PCOIP_ZC_CONFIG.HTM

HTTP://WWW.TERADICI.COM/WEB-HELP/PCOIP_ZC_CONFIG_HTML5/TER1504003_PCOIP_ZC_CONFIG.HTM

HTTPS://TECHSUPPORT.TERADICI.COM/ICS/SUPPORT/KBANSWER.ASP?DEPTID=15164&TASK=KNOWLEDGE&QUESTIONID=2905&LANGUAGEID=

HTTPS://TECHSUPPORT.TERADICI.COM/ICS/SUPPORT/KBANSWER.ASP?DEPTID=15164&TASK=KNOWLEDGE&QUESTIONID=2905&LANGUAGEID=

dell wyse pcoip firmware release 5.2.2 release notes · dell wyse pcoip firmware release 5.2.2...

Documents