Release Notes

Release Notes
Wyse P Class PCoIP Firmware
®
Release 4.x
Products: P20, P25, P45
Issue: 121912 Rev. D
General Release
®
Copyright Notices
© 2012, Wyse Technology Inc. All rights reserved.
This manual and the software and firmware described in it are copyrighted. You may not
reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or
computer language, in any form or by any means, electronic, mechanical, magnetic, optical,
chemical, manual or otherwise, any part of this publication without express written
permission.
Trademarks
The Wyse and PocketCloud logos and Wyse and PocketCloud are trademarks of Wyse
Technology Inc. Other product names mentioned herein are for identification purposes only
and may be trademarks and/or registered trademarks of their respective companies.
Specifications subject to change without notice.
PCoIP and PC-over-IP are registered trademarks of Teradici Corporation in the United
States and/or other countries.
About this Guide
This guide is intended for administrators of Wyse P class zero clients. This document is
updated periodically as more information becomes available.
Finding the Information You Need in this Guide
You can use either the Search window or Find toolbar to locate a word, series of words, or
partial word in an active PDF document. For detailed information on using these features,
refer to the Help in your PDF reader.
Wyse Technical Support
To access Wyse technical resources, visit http://www.wyse.com/support. If you still have
questions, you can submit your questions using the Wyse Self-Service Center at
http://support.wyse.com/selfservice.html or call Customer Support at 1-800-800-WYSE (toll
free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time,
Monday through Friday.
To access international support, visit http://www.wyse.com/global.
Wyse Online Community
Wyse maintains an online community where users of our products can seek and exchange
information on user forums. Visit the Wyse Online Community forums at:
http://community.wyse.com/forum.
Contents
Copyright Notices ii
Trademarks ii
About this Guide ii
Finding the Information You Need in this Guide
Wyse Technical Support ii
Wyse Online Community ii
1
ii
Introduction 1
Purpose 1
Definitions 1
2
Release 4.0.3 3
Compatibility 3
New Features 4
Fixes 4
Known Issues 4
Additional Collateral
3
Release 4.0.2 9
Compatibility 9
New Features 10
Fixes 10
Known Issues 10
Additional Collateral
4
7
13
Release 4.0.1 (not released) 15
New Features 15
Fixes 16
Known Issues 16
Additional Collateral 17
Supplemental Information 18
Configuration > Session Direct to Host Advanced Web Page 18
Configuration > SNMP Web Page 18
Configuration > Session VCS + Imprivata OneSign Advanced Web Page 19
5
Release 4.0.0 21
Compatibility 21
New Features 22
Fixes 23
Known Issues 24
Additional Collateral 25
Supplemental Information 26
Configuration > Session VCS Advanced Web Page
VCS Certificate Check Mode Options 26
Session Negotiation Cipher Options 27
26
iv
Contents
OSD User Settings > VMware View Options 27
OSD Configuration > Session Direct to Host Advanced Options 27
OSD Configuration > Session VCS Advanced Options 28
OSD Configuration > Session VCS + Auto-Logon Options 28
OSD Configuration > Session VCS + Auto-Logon Advanced Options 28
OSD Configuration > Display Options 29
OSD User Settings > Display Topology Options 29
Configuration > Session Direct to Host Advanced Web Page 30
1
Introduction
Purpose
This document contains new feature information for Tera1 and Tera2. A brief summary
describes the feature additions and issues resolved in each firmware release starting with
release 4.0. The sections in this document are organized according to release date with
the most recent releases listed first.
IMPORTANT: Wyse has leveraged Teradici release notes with permission by Teradici for
the creation of release notes for Wyse P class zero clients (P20, P25, and P45). Any
reference to Host Cards is not applicable to the Wyse P20, P25, or P45 zero client
products.
Definitions
CAC
Common Access Card (smart card technology used in the U.S.
Department of Defense)
CMI
Connection Management Interface - Interface provided by the
Zero Client or Host, used to communicate with an external
connection management server
CMS
Connection Management Server (also referred to as Connection
Broker)
EDID
Extended Display Identification Data - Information provided by a
monitor that describes the capabilities of the monitor. This
information is typically used by the graphics card in the host
computer.
FW
Firmware
GSC-IS
Government Smart Card Interoperability Specification
HPDET
Hot Plug Detect - HDMI signal used to sense when a display is
plugged in or unplugged
OCSP
Online Certificate Status Protocol - protocol used to determine
the status of an X.509 digital certificate (defined in RFC 2560).
OID
Object identifier - a numerical value used to identify objects in a
certificate.
OS
Operating System
2
Chapter 1
OSD
On Screen Display on the PCoIP Zero Client
OTP
One-Time Password - security system that requires a new
password every time a user is authenticated
PCoIP®
Personal Computer over Internet Protocol (PC-over-IP®)
PCoIP Host
Host side of PCoIP system
PCoIP MC
PCoIP Management Console - Tool provided by Teradici that
gives IT personnel the ability to access and to manage all
PCoIP Hosts and zero clients from a single location in a
deployment
PCoIP Zero Client
User or client side of PCoIP system in the form of a standalone
desktop device or integrated display based on a PCoIP
processor
PIV
Personal Identity Verification
SSO
Single Sign-On - Authentication process that lets a user enter
one username and password and grants access to multiple
applications
Software Client
VMware View™ software application that can establish a PCoIP
session with a PCoIP Host
Tera1 product
Wyse P20
Tera2 product
Wyse P25, Wyse P45
URI
Uniform Resource Identifier
USB
Universal Serial Bus
VCS
View Connection Server
WDM
Dell Wyse Device Manager software
2
Release 4.0.3
This chapter provides a brief summary of the feature additions and issues resolved in
release 4.0.3 versus release 4.0.2.
NOTE: Release 4.0.3 is only applicable to Tera2 zero clients (Wyse P25 and Wyse P45)
and host cards.
Compatibility
VMware View™ 5.0 or later deployments using TERA2xxx zero client devices to connect
to View virtual desktops should install release 4.0.3 on the zero client devices.
It is highly recommended that remote workstation deployments using TERA2xxx zero
clients with TERA2xxx PCoIP host cards install release 4.0.3 on both the host card and
client devices. Deployments using a mix of TERA1x00 and TERA2xxx endpoints should
install release 4.0.3 on TERA2xxx endpoints and release 4.0.2 on the TERA1x00
endpoints. While mixed firmware release operation, other than the previously mentioned
configuration, is not tested, firmware release 4.0.3 is compatible with 4.0.2, 4.0.1, 4.0.0,
3.5.x, 3.4.x, 3.3.x, 3.2.x and 3.1.x releases. Firmware 4.0.3 is not interoperable with
releases 3.0, 2.x, 1.x or 0.x. An “Unable to connect (0x1002). Please contact your IT
administrator.” error message appears on the display if trying to connect to a PCoIP host
card running an incompatible release.
Deployments using Dell Wyse Device Manager (WDM) to manage PCoIP endpoints must
use WDM 4.9.1 HF04091034412 or later with this firmware release.
Deployments using the PCoIP Management Console (MC) to manage PCoIP endpoints
must use PCoIP MC version 1.8.1 or later with this firmware release.
NOTE: This firmware release can only be installed on TERA2xxx PCoIP processors.
4
Chapter 2
New Features
None.
Fixes
Fixes
Resolved a flash memory issue that could cause a TERA2 device to
become inoperative and unrecoverable while updating configuration
settings using PCoIP MC version 1.8.0.
Zero Client used with:
VMware View
Host card
Tera2
Tera2
Resolved a potential memory corruption problem on TERA2xxx host
cards, which could cause sessions to disconnect or workstations to
crash..
Tera2
Set the minimum firmware version equal to 4.0.3 for TERA2 devices,
preventing downgrades.
Tera2
Tera2
Resolved a communication error with the View Connection Server
that prevented users from starting a session when Online Certificate
Status Protocol (OSCP) server is unresponsive.
Tera2
Resolved a “Source signal on other port” error on video port 2 that
affected deployments using View 4.6 and Windows XP.
Tera2
Known Issues
Zero Client used with:
Known Issues
VMware View
See the Knowledge Base on the Teradici support website
(http://techsupport.teradici.com) for known issues.
9
Imprivata: Proximity card gives enroll error message for a configured
card.
9
Session does not get logged off when Imprivata proximity card is
tapped second time with dual monitor setup
9
Tera2: Webcam does not get detected under OSD attached devices
9
Tera2: Unit reports manufacturing date of 1/1/1900 to WDM
9
Tera2 P25: DVI port monitor is always set as monitor 2 under User
Settings > Display Topology UI
9
Host card
9
5
Release 4.0.3
The following tables describe the operating mode of USB devices based on device type,
session type, and device configuration when connected to a zero client.
Table 1
Tera1 USB Device Modes (Wyse P20)
EHCI Disabled (Devices operate in USB 1.1 mode only)
Root Port
Behind USB 1.1 and 2.0 Hub
View Desktop
All devices operate in USB 1.1 mode.
PCoIP Host Card
All devices operate in USB 1.1 mode.
EHCI Enabled (USB 2.0 support is enabled) - Default
View Desktop
PCoIP Host Card
Root Port
Behind USB 1.1 Hub
Behind USB 2.0 Hub
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, WebCams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB 2.0)
All devices operate in USB 1.1 mode.
Isochronous devices
are not supported (a
warning overlay may
appear).
6
Chapter 2
Table 2
Tera2 USB Device Modes (Wyse P25 and Wyse P45)
EHCI Disabled (Devices operate in USB 1.1 mode only)
Root Port
View Desktop
PCoIP Host Card
Behind USB 1.1 and 2.0 Hub
All devices operate in USB 1.1 mode.
The EHCI disable flag does not apply to the PCoIP host card.
See the following section for PCoIP host card behaviour.
EHCI Enabled (USB 2.0 support is enabled) - Default
View Desktop
PCoIP Host Card
Root Port
Behind USB 1.1 Hub
Behind USB 2.0 Hub
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, WebCams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB 2.0)
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, WebCams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
Isochronous devices
are not supported (a
warning overlay may
appear).
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB 2.0)
Isochronous devices
are not supported (a
warning overlay may
appear).
7
Release 4.0.3
Additional Collateral
Additional Collateral
Zero Client used with:
VMware View
Refer to the latest VMware View to PCoIP Zero Client Optimization
Guide (TER1003001) document for optimization guidelines for
connecting PCoIP zero clients to VMware View virtual desktops.
9
Refer to the latest VMware View to PCoIP Zero Client WAN Network
Guidelines (TER1007002) document for network optimization
guidelines when connecting PCoIP zero clients to VMware View 4
virtual desktops over remote access WAN networks.
9
Refer to the Teradici support website
(http://techsupport.teradici.com) for additional collateral for PCoIP
zero client and PCoIP host card applications, implementation and
management.
9
Refer to the Wyse website (http://www.wyse.com) for information on
Wyse Device ManagerTM (WDM) network management services for
the PCoIP zero client (complete user-desktop control—with features
such as remote shadow, reboot, shutdown, boot rename, automatic
check-in support, Wake-On-LAN, change device properties, and so
on).
9
Host card
9
8
Chapter 2
This page intentionally blank.
3
Release 4.0.2
This chapter provides a brief summary of the feature additions and issues resolved in
release 4.0.2 versus release 4.0.1.
NOTE: The fixes and enhancements made to release 4.0.1 are also included in the 4.0.2
release.
Compatibility
VMware View™ 5.0 or later deployments using zero client devices to connect to View
virtual desktops should install release 4.0.2 on the zero client devices.
It is highly recommended that remote workstation deployments using zero clients with
PCoIP host cards install release 4.0.2 on both the host card and client devices. While
mixed firmware release operation is not tested, firmware release 4.0.2 is compatible with
4.0.1, 4.0.0, 3.5.x, 3.4.x, 3.3.x, 3.2.x and 3.1.x releases. Firmware 4.0.2 is not
interoperable with releases 3.0, 2.x, 1.x or 0.x. An “Unable to connect (0x1002). Please
contact your IT administrator.” error message appears on the display if trying to
connect to a PCoIP host card running an incompatible release.
Deployments using Dell Wyse Device Manager (WDM) to manage PCoIP endpoints must
use WDM 4.9.1 hotfix (HF) or later with this firmware release.
Deployments using the PCoIP Management Console (MC) to manage PCoIP endpoints
must use PCoIP MC version 1.7.0 or later with this firmware release.
NOTE: Applicable to Tera1 only, this firmware release can only be installed on TERA1x00
PCoIP processors running firmware release 1.4 or later. If the processor is loaded with a
firmware release prior to version 1.4, first download one or more intermediate firmware
releases. The following table lists the installation steps for each version of firmware that
may be installed on a PCoIP processor. To view the firmware version, go to the device
Info > Version web page.
NOTE: Tera2 products are factory installed with firmware version 4.0.2.
Installed Firmware Version
Upgrade process for Tera1 (Wyse P20)
0.1 through 0.17
1. Install firmware release 0.18.
2. Install a 1.x firmware release (1.4 or greater).
3. Install the new firmware (4.0.2).
0.18 through 1.3
1. Install a 1.x firmware release (1.4 or greater).
2. Install the new firmware (4.0.2).
1.4 through 4.0.1
Install the new firmware (4.0.2).
10
Chapter 3
New Features
New Features
Zero Client used with:
VMware View
Added support for using the zero client in Imprivata OneSign Single
Sign-On mode with the OMNIKEY 5427 proximity reader.
9
Added support for Wyse P25 and Wyse P45 zero clients.
9
Host card
Fixes
Fixes
Zero Client used with:
VMware View
Resolved an analog calibration issue with P25 zero clients.
9
Host card
9
Known Issues
Known Issues
Zero Client used with:
VMware View
See the Knowledge Base on the Teradici support website
(http://techsupport.teradici.com) for known issues.
9
Audio gets distorted with live Webcam session.
NOTE: Teradici supports one isochronous device per connection.
9
Incorrect Peer MAC Address on “Session Control” Page.
9
Display Resolution shows incorrect value under “Attached Device/
Current Resolution” field in the System Event log.
9
Alignment setting with dual monitors failing.
9
View5.1-Expired Certificate Connection failing Work In Progress
8/23/2012 3:43 PM PDT.
9
No connection and no feedback when Imprivata in lockdown mode.
9
Event Logs are not clearly depicting the secure session state.
9
Host card
9
11
Release 4.0.2
The following tables describe the operating mode of USB devices connected to a zero
client based on device type, session type, and device configuration.
Table 1
Tera1 USB Device Modes (Wyse P20)
EHCI Disabled (Devices operate in USB 1.1 mode only)
Root Port
Behind USB 1.1 and 2.0 Hub
View Desktop
All devices operate in USB 1.1 mode.
PCoIP Host Card
All devices operate in USB 1.1 mode.
EHCI Enabled (USB 2.0 support is enabled)
View Desktop
PCoIP Host Card
Root Port
Behind USB 1.1 Hub
Behind USB 2.0 Hub
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, web cams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB
2.0).
All devices operate in USB 1.1 mode.
Isochronous devices
are not supported
(a warning overlay
may appear).
12
Chapter 3
Table 2
Tera2 USB Device Modes (Wyse P25, Wyse P45)
EHCI Disabled (Devices operate in USB 1.1 mode only)
Root Port
View Desktop
PCoIP Host Card
Behind USB 1.1 and 2.0 Hub
All devices operate in USB 1.1 mode.
The EHCI disable flag does not apply to the PCoIP host card.
See following section for PCoIP host card behavior.
EHCI Enabled (USB 2.0 support is enabled) - Default
View Desktop
PCoIP Host Card
Root Port
Behind USB 1.1 Hub
Behind USB 2.0 Hub
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, web cams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB
2.0).
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, web cams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
Isochronous devices
are not supported
(a warning overlay
may appear).
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB
2.0).
Isochronous devices
are not supported
(a warning overlay
may appear).
13
Release 4.0.2
Additional Collateral
Additional Collateral
Zero Client used with:
VMware View
Refer to the latest VMware View to PCoIP Zero Client Optimization
Guide (TER1003001) document for optimization guidelines for
connecting PCoIP zero clients to VMware View virtual desktops.
9
Refer to the latest VMware View to PCoIP Zero Client WAN Network
Guidelines (TER1007002) document for network optimization
guidelines when connecting PCoIP zero clients to VMware View 4
virtual desktops over remote access WAN networks.
9
Refer to the Teradici support website
(http://techsupport.teradici.com) for additional collateral for PCoIP
zero client and PCoIP host card applications, implementation and
management.
9
Refer to the Wyse website (http://www.wyse.com) for information on
Wyse Device ManagerTM (WDM) network management services for
the PCoIP zero client (complete user-desktop control—with features
such as remote shadow, reboot, shutdown, boot rename, automatic
check-in support, Wake-On-LAN, change device properties, and so
on).
9
Host card
9
14
Chapter 3
This page intentionally blank.
4
Release 4.0.1 (not released)
This chapter provides a brief summary of the feature additions and issues resolved in
release 4.0.1 versus release 4.0.0.
IMPORTANT: Although it was not released to customers, Firmware 4.0.1 is included in
this document. The 4.0.1 new features and fixes have been rolled into the Firmware
Release 4.0.2.
New Features
New Features
Zero Client used with:
VMware View
Added support for using the zero client in Imprivata OneSign Single
Sign-On mode with the OMNIKEY 5127 proximity reader.
9
Added hotkey to disconnect support (Ctrl+Alt+F12). This feature is
enabled by default and is available in Workstation and View
deployments. NOTE: Workstation deployments require that the
PCoIP host software be installed with the local cursor feature
enabled.
9
Host card
9
The advanced options section of the session web page added a field
to enable/disable the feature (see Figure 1).
Added pre-session support for the eToken 5205 Pro Anywhere and a
eToken NG OTP.
9
Improved error indications in the View login flow. This change
includes in-line error messages for bad username or password and a
CAPS LOCK indicator.
9
Added support for configuring the SNMP community name (see
Figure 2).
9
9
Removed network icon in the OSD and improved status indication in
connect dialog.
9
9
Modified the View connection security text to match current View
clients.
9
Event log is cleared when a reset to factory defaults is applied.
9
Added support for “Desktop Name to Select” configuration in “View
Connection Server + Imprivata OneSign”. This field is available in the
advanced options under session configuration (see Figure 3).
9
9
16
Chapter 4
Fixes
Fixes
Zero Client used with:
VMware View
Zero client now trusts intermediate and leaf certificates.
9
Zero client does not require the View Connection Server certificate to
have the Server Authentication Enhanced Key Usage if the
certificate does not have any Enhanced Key Usage entries.
9
Certificate with RFC3280 GeneralizedTime four-digit years are now
supported.
9
Zero client can now handle any OID appearing in a certificate’s
subject or issuer fields. For example, Go Daddy certificates.
9
Improved robustness when accessing smart card readers from
applications on a virtual machine including RDP sessions.
9
Improved handling of certificates with Subject Alternative Name data.
9
Zero client now accepts certificates with a critical Certificate Policies
extension.
9
Improved Online Certificate Status Protocol (OCSP) error handling.
9
Zero client no longer generates duplicate keystrokes when typing
quickly. NOTE: For workstation deployments, this fix only applies to
systems running the PCoIP host software with the Local Cursor
feature enabled.
9
Zero client no longer loses the first character typed on bridged
keyboards.
9
Zero client no longer asserts when connecting to a disabled View
Connection Server.
9
Certificate store is now cleared when resetting to factory defaults
through the OSD, Web, and CMI interfaces (instead of only the Web
interface).
9
Host card
9
9
Known Issues
Known Issues
Zero Client used with:
VMware View
See the Knowledge Base on the Teradici support website
(http://techsupport.teradici.com) for known issues.
9
Host card
9
See Table 1 and Table 2 for the operating mode of USB devices connected to a zero
client based on device type, session type, and device configuration.
17
Release 4.0.1 (not released)
Additional Collateral
Additional Collateral
Zero Client used with:
VMware View
Refer to the latest VMware View to PCoIP Zero Client Optimization
Guide (TER1003001) document for optimization guidelines for
connecting PCoIP zero clients to VMware View virtual desktops.
9
Refer to the latest VMware View to PCoIP Zero Client WAN Network
Guidelines (TER1007002) document for network optimization
guidelines when connecting PCoIP zero clients to VMware View 4
virtual desktops over remote access WAN networks.
9
Refer to the Teradici support website
(http://techsupport.teradici.com) for additional collateral for PCoIP
zero client and PCoIP host card applications, implementation and
management.
9
Refer to the Wyse website (http://www.wyse.com) for information on
Wyse Device ManagerTM (WDM) network management services for
the PCoIP zero client (complete user-desktop control—with features
such as remote shadow, reboot, shutdown, boot rename, automatic
check-in support, Wake-On-LAN, change device properties, and so
on).
9
Host card
9
18
Chapter 4
Supplemental Information
Configuration > Session Direct to Host Advanced Web Page
Figure 1
Configuration > Session Direct to Host Advanced Web Page
Configuration > SNMP Web Page
Figure 2
Configuration > SNMP Web Page
Release 4.0.1 (not released)
19
Configuration > Session VCS + Imprivata OneSign Advanced Web Page
Figure 3
Configuration > Session VCS + Imprivata OneSign Advanced Web Page
20
Chapter 4
This page intentionally blank.
5
Release 4.0.0
This chapter provides a brief summary of the feature additions and issues resolved in
release 4.0.0 versus release 3.5.1.
NOTE: The 4.0.0 and prior releases are applicable to Tera1 only (Wyse P20).
Compatibility
VMware View™ 5.0 or later deployments using zero client devices to connect to View
virtual desktops should install release 4.0.0 on the zero client devices.
It is highly recommended that remote workstation deployments using zero clients with
PCoIP host cards install release 4.0.0 on both the host card and client devices. While
mixed firmware release operation is not tested, firmware release 4.0.0 is compatible with
3.5.x, 3.4.x, 3.3.x, 3.2.x and 3.1.x releases. Firmware 4.0.0 is not interoperable with
releases 3.0, 2.x, 1.x or 0.x. An “Unable to connect (0x1002). Please contact your IT
administrator.” error message appears on the display if trying to connect to a PCoIP host
card running an incompatible release.
Deployments using Dell Wyse Device Manager (WDM) to manage PCoIP endpoints must
use WDM 4.9.1 HF or later with this firmware release.
Deployments using the PCoIP Management Console (MC) to manage PCoIP endpoints
must use PCoIP MC version 1.7.0 or later with this firmware release.
NOTE: This firmware release can only be installed on TERA1x00 PCoIP processors
running firmware release 1.4 or later. If the processor is loaded with a firmware release
prior to version 1.4, first download one or more intermediate firmware releases. The
following table lists the installation steps for each version of firmware that may be installed
on a PCoIP processor. To view the firmware version, go to the device Info > Version web
page.
Installed Firmware Version
Upgrade process
0.1 through 0.17
1. Install firmware release 0.18.
2. Install a 1.x firmware release (1.4 or greater).
3. Install the new firmware (4.0.0).
0.18 through 1.3
1. Install a 1.x firmware release (1.4 or greater).
2. Install the new firmware (4.0.0).
1.4 through 3.5.1
Install the new firmware (4.0.0).
22
Chapter 5
New Features
New Features
Zero Client used with:
VMware View
Host card
Security enhancement: Add support for configuring the VCS
Certificate Check Mode and VCS Certificate Check Mode
Lockout settings on the Configuration > Session web page (see
Figures 4 and 5). Three modes are supported.
• Reject the unverifiable connection (Secure) - requires a trusted,
valid certificate.
• Warn if the connection may be insecure (Default) - warns when
unsigned (View default), expired certificates or when the
certificate is not self-signed and the zero client trust-store is
empty.
• Allow the unverifiable connection (Not Secure) - connects even if
the connection may be compromised
The VMware View tab on the OSD Options > User Settings screen
lets users view and potentially modify the VCS Certificate Check
Mode. Users cannot modify the mode when the VCS Certificate
Check Mode Lockout setting is checked (see Figure 7).
9
9
Security enhancement: Add support for configuring the Session
Negotiation Cipher setting on the Configuration >Session web
page. This setting applies to all session connection types (Direct to
Host, View Connection Server and Connection Management
System). Two cipher settings are supported. (See Figure 6.)
• Maximum Compatibility: TLS 1.0 with RSA keys and AES-256 or
AES-128 encryption.
• Suite B: TLS 1.2 with Suite B-compliant 192-bit elliptic curve
encryption (NOTE: At the time of writing this cipher setting is not
supported by View 5.1 and earlier virtual desktops).
9
9
Updated the OSD look and feel:
• Revised color scheme
• Revised logo placement
9
9
9
OSD enhancement: Remove Peer MAC Address and add Enable
Preparing Desktop Overlay settings on the Advanced Session
settings for Direct to Host connections (see Figure 8).
OSD enhancement: Add support for configuring the Desktop Name
to Select and Enable Preparing Desktop Overlay settings on the
Advanced Session settings for VCS connections (see Figure 9).
9
OSD enhancement: Add support for setting Session Connection
Type equal to View Connection Server + Auto-Logon using the
OSD. Previous releases support configuring this connection type
through the web interface or the PCoIP MC (see Figures 10 and 11).
9
9
OSD enhancement: Add support for configuring the native resolution
of each display when the display override feature is enabled (see
Figure 12).
9
9
OSD enhancement: Modified the display topology setting page (see
Figure 13).
9
9
OSD enhancement: Removed requirement to reboot zero client after
changing display topology Rotation setting (see Figure 13).
9
9
23
Release 4.0.0
New Features
Zero Client used with:
VMware View
Host card
Add support for a newly defined Teradici SNMP MIB which adds an
extensive set of read-only variables. See Knowledge Base
#15134-203 on the Teradici support site for details on the new MIB.
9
9
Add support for configuring the PCoIP endpoint session timeout
(from 5 to 60 seconds) using the CMI.
9
9
Changed default OSD screen saver timeout to 300 seconds.
Previous releases disabled the OSD screen saver by default.
9
9
9
Updated the zero client Wake-On-LAN session configuration settings
(see Figure 14). NOTE: This change affects deployments using
PCoIP host cards configured to wake workstations from a low power
state using Wake-On-LAN messages.
Fixes
Fixes
Zero Client used with:
VMware View
Host card
Resolved an issue where disabling Login Username
Caching has no effect when using Imprivata OneSign.
9
Resolved an issue where the PCoIP endpoint would reset if
DHCP Options 60 and 43 are not configured to identify the
PCoIP Management Console. See the latest PCoIP
Management Console User Manual (TER0812002) for
configuration information.
9
Resolved an issue where the Omnikey 5325CL proximity card
reader would not work with a zero client.
9
Resolved an issue where the zero client resets when logging
out of a session authenticated with a smart card reader that
uses an ALCOR AU9540A51-GBS-GR device.
9
9
Resolved an issue where the incorrect keyboard layout is
used after downgrading firmware to a release that does not
support the currently configured keyboard layout.
9
9
Resolved issues when using smart cards in-session with
applications and middleware that make use of the
SCardListReaders and SCardControl API functions.
9
9
9
24
Chapter 5
Known Issues
Known Issues
Zero Client used with:
VMware View
Host card
See the Knowledge Base on the Teradici support website
(http://techsupport.teradici.com) for known issues when PCoIP zero
clients are connected to VMware View virtual desktops.
9
Deployments using PCoIP MC releases earlier than 1.7.0 may
experience a problem where the PCoIP MC daemon resets while
communicating with a zero client running FW release 3.5.0 or later.
This occurs if the zero client has more than five VCS entries.
Workaround: Upgrade to PCoIP MC version 1.7.0 or later or limit
the maximum number of VCS entries to five.
9
The desktop display resolution may change when a user resizes the
software client window while a session is active with a PCoIP host
card. This occurs if the client window becomes smaller than the
current desktop or a larger resolution will fit within the client window.
Sometimes when this change occurs, the graphics driver scales the
image resulting in the desktop not fitting within the client window.
Workaround: Resize the client window or configure the graphics
driver to use the monitor's built in scaling feature.
9
The PCoIP MC cannot be used to configure the IPv6 Gateway
Address field.
Workaround: Enable and configure DHCPv6 or SLAAC to set this
field or configure the field statically using the device web interface.
9
9
Zero clients always connect to port 443 of the Imprivata OneSign
server. Users cannot override the port by configuring a port number
in the Bootstrap URL field.
9
9
Zero clients may fail to establish Imprivata OneSign sessions when
the OneSign Appliance Verification setting equals no verification.
This happens when the zero client trust store contains a certificate
issued by the OneSign server that does not match the certificate
used by the OneSign server.
Workaround: Ensure the zero client trust store does not contain
certificates issued by the OneSign server or ensure certificates in the
zero client trust store match the certificates used by the OneSign
server.
9
9
Zero clients in session with View 5.1 desktops running XP-32 may
experience brief audio outages while using USB speakers or
headsets.
9
Customers connecting a zero client to both PCoIP host cards and
View desktops may experience USB device connectivity problems
when connected to the View desktop.
Workaround: After ending a session with a PCoIP host card, reset
the zero client before establishing a session with a View desktop.
9
Customers connecting a zero client to a View 5.0.1 (or earlier)
desktop may experience USB device connectivity problems.
Workaround: Unplug and re-plug the USB device.
9
9
9
25
Release 4.0.0
The following table describes the operating mode of USB devices based on device type,
session type, and device configuration.
Table 3
Operating Mode of USB Devices
EHCI Disabled (Devices operate in USB 1.1 mode only)
Root Port
Behind USB 1.1 and 2.0 Hub
View Desktop
All devices operate in USB 1.1 mode.
PCoIP Host Card
All devices operate in USB 1.1 mode.
EHCI Enabled (USB 2.0 support is enabled)
View Desktop
PCoIP Host Card
Root Port
Behind USB 1.1 Hub
Behind USB 2.0 Hub
All devices operate in
their native mode
(USB 1.1 or USB 2.0)
with the exception of
USB 2.0 isochronous
devices (i.e., audio
devices, WebCams).
USB 2.0 isochronous
devices operate in
USB 1.1 mode.
All devices operate in
USB 1.1 mode.
All non-isochronous
devices operate in
their native mode
(USB 1.1 or USB 2.0)
Isochronous devices
are not supported (a
warning overlay may
appear).
All devices operate in USB 1.1 mode.
Additional Collateral
Additional Collateral
Zero Client used with:
VMware View
Refer to the latest VMware View to PCoIP Zero Client Optimization
Guide (TER1003001) document for optimization guidelines for
connecting PCoIP zero clients to VMware View virtual desktops.
9
Refer to the latest VMware View to PCoIP Zero Client WAN Network
Guidelines (TER1007002) document for network optimization
guidelines when connecting PCoIP zero clients to VMware View 4
virtual desktops over remote access WAN networks.
9
Refer to the Teradici support website
(http://techsupport.teradici.com) for additional collateral for PCoIP
zero client and PCoIP host card applications, implementation and
management.
9
Refer to the Wyse website (http://www.wyse.com) for information on
Wyse Device ManagerTM (WDM) network management services for
the PCoIP zero client (complete user-desktop control—with features
such as remote shadow, reboot, shutdown, boot rename, automatic
check-in support, Wake-On-LAN, change device properties, and so
on).
9
Host card
9
26
Chapter 5
Supplemental Information
Configuration > Session VCS Advanced Web Page
Figure 4
Configuration > Session VCS Advanced Web Page
VCS Certificate Check Mode Options
Figure 5
VCS Certificate Check Mode Options
Release 4.0.0
Session Negotiation Cipher Options
Figure 6
Session Negotiation Cipher Options
OSD User Settings > VMware View Options
Figure 7
OSD User Settings > VMware View Options
OSD Configuration > Session Direct to Host Advanced Options
Figure 8
OSD Configuration > Session Direct to Host Advanced Options
27
28
Chapter 5
OSD Configuration > Session VCS Advanced Options
Figure 9
OSD Configuration > Session VCS Advanced Options
OSD Configuration > Session VCS + Auto-Logon Options
Figure 10
OSD Configuration > Session VCS + Auto-Logon Options
OSD Configuration > Session VCS + Auto-Logon Advanced Options
Figure 11
OSD Configuration > Session VCS + Auto-Logon Advanced Options
Release 4.0.0
OSD Configuration > Display Options
Figure 12
OSD Configuration > Display Options
OSD User Settings > Display Topology Options
Figure 13
OSD User Settings > Display Topology Options
29
30
Chapter 5
Configuration > Session Direct to Host Advanced Web Page
Figure 14
Configuration > Session Direct to Host Advanced Web Page
31
Release 4.0.0
This page intentionally blank.
Release Notes
Wyse® PCoIP Firmware Release 4.x
Issue: 121912
Written and published by:
Wyse Technology Inc., December 2012
Created using FrameMaker® and Acrobat®
Download PDF