Release Notes for Cisco Virtualization Experience Client 2111/2211 PCoIP Firmware Release 4.2.0
The Cisco Virtualization Experience Client (VXC) 2111 and 2211 are workstation-class virtualization clients for use with PC-over-IP (PCoIP). The PCoIP protocol is designed to deliver a user desktop from a centralized host server across standard IP networks, enabling you to use applications and desktop peripherals as if you were using them locally.This release supports the following Cisco Virtualization Experience Client (VXC) clients using PCoIP Zero Client firmware:
The Cisco VXC 2111 attaches to, and obtains its power from, the Cisco Unified IP Phone 8961, 9951, or 9971 through a spine connector cable. The phone is powered by either an AC adapter (CP-PWR-CUBE-4) or by Power over Ethernet (PoE) capable Cisco Switches. The Cisco Unified IP Phone 8961, 9951, or 9971 must run Firmware Release 9.1(2) or later.
The Cisco VXC 2211 operates independently and is powered by either an AC adapter (CP-PWR-CUBE-4) or by Power over Ethernet (PoE) capable Cisco Switches.
Cisco Virtualization Experience Client 2000 Serieshttp://www.cisco.com/en/US/products/ps11499/tsd_products_support_series_home.html
Cisco Virtualization Experience Client Managerhttp://www.cisco.com/en/US/products/ps11582/tsd_products_support_series_home.html
New and Changed Features
The zero client AWI Audio page has been moved from the Permissions menu to the Configuration menu.
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.
RADIUS 2-Factor Authentication Support
In addition to traditional smart card and username/password authentication, this feature enables the user to add a second authenticator (RADIUS username/password, RSA SecurID) for user authentication as the second authenticator.
This feature is not configurable in firmware.
Install Firmware Release 4.2.0Procedure
To download and install the Cisco VXC 2111/2211 PCoIP firmware, follow these steps:
Changes in PCoIP firmware 3.4.0 onwards resulted in Default Device Configuration (DDC) not being supported for these releases in Cisco VXC Manager 4.8.5. With Cisco VXC Manager 4.8.5, the recommendation is to use Drag and Drop. To use DDC, use Cisco VXC Manager 4.9 or 4.9.1 and the 4.9.x-based packages.
Additional Recommended Upgrade ProcedureProcedure
To avoid connection issues after the upgrade, Cisco recommends that you push the View connection settings to the Cisco VXC 2111/2211 devices using the Cisco VXC Manager ThreadX configuration package for all upgraded Cisco VXC 2111/2211 devices.
Step 1 In the tree pane of the Administrator Console, expand . Step 2 In the details pane, right-click the VMware View package and choose View Package Script to open the Package Script dialog box displaying the script of the Cisco VXC Manager package. Step 3 Check the Edit and Save Script to Database ONLY check box, specify the IP address of the View server in the IP= parameter, and make any other changes to the script as required for your setup (for example, to enable SSL, you can set the SSL parameter to SSL=1.)
Caution To include the Port= parameter in the script, you must set a valid value for it. If the Port= parameter is blank, delete it from the script to avoid errors. You only need to specify the Port= parameter if you are using a port other than the default value of 80 for HTTP or 443 for HTTPS. Step 4 After completing your changes, click OK. Step 5 Schedule the package update using Drag and Drop (supported on Release 4.8.5 and 4.9.x of Cisco VXC Manager) or DDC (supported on Cisco VXC Manager 4.9.x only). See the Administration Guide for Cisco Virtualization Experience Client Manager for details.
DVI to VGA Adapter Requirements
If you use a DVI to VGA adapter to connect a VGA monitor to the Cisco VXC client, use only the adapter that your device supports. Do not use an adapter that is shipped with a different Cisco VXC model because doing so can cause display issues, such as a blank monitor.
The following table shows the Cisco DVI to VGA adapters supported by each Cisco VXC model:
USB Device Operation
The following tables describe the mode in which USB devices operate based on device type, session type, and device configuration.
Table 2 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. —
Table 3 EHCI Enabled (USB 2.0 support is enabled) Root Port Behind USB 1.1 Hub Behind USB 2.0 Hub View Desktop All devices operate in their native mode (USB 1.1 or USB 2.0 isochronous devices, [for example, audio devices, and 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).
USB Transfer Speed
LLDP Required for Cisco VXC 2211 Power Negotiation
Analog Audio Support
The following are the system requirements for support of the analog audio driver.
Support for Analog Audio Input
The Cisco VXC 2111/2211 supports analog audio input in PCoIP connections with View 4.5 and later. To support analog audio input, you must install a Teradici audio driver in the virtual desktop. This driver is not installed by the View Agent installer and is not officially supported by VMware. To obtain the audio driver or for any technical support issues, see the Teradici support page.
Installing the Analog Audio Driver
To install the analog audio driver:
- In the View virtual machine, run the PCoIP Component installer.
- Follow the instructions in the Teradici PCoIP Component Installer Setup dialog.
- If you agree to the license, choose Install (the Teradici Audio Driver is automatically selected). After the installation completes, verify under Control Panel (Sounds) that the Teradici Virtual Audio Driver is the default playback and recording device.
- Restart the virtual machine.
Uninstalling the Analog Audio Driver
To uninstall the Teradici Virtual Audio Driver, open the Windows Device Manager and under Sound, Video and Game Controllers, delete the Teradici Audio Driver.
Secure Connection Troubleshooting
This section provides information for troubleshooting secure connections to the View Connection Server (VCS).
Issue: Connection to the VCS is failing after removing the VCS certificate with the certificate security set to the default, warn only
This is the expected behavior because the zero client keeps a cached list of the trusted View connection servers when the security mode is set to Warn if the connection may be insecure (Default).
If you remove the issuing certificate and attempt to connect to the same VCS, this compromises View client security. To establish a connection after you remove the certificate, you must also clear your trusted VCS address cache list.
To clear your trusted VCS address cache and confirm the expected connection behavior:
- From the Administrative Web Interface, select .
- Click the Show Advanced Options button.
- Click the Clear button beside Trusted View Connection Servers.
- Click Apply.
- From the OSD select .
- Confirm the VCS Certificate Check Mode is set to Warn if Connection may be insecure (Default) and select this option if it is not selected.
- Click OK.
- Click the Connect button.
- Observe the warning message.
- Click the Continue button.
- Confirm there is a red strikethrough through the https in the VCS address field in the connection dialog box.
Alternatively, you can reset the zero client and reconfigure your parameters on the zero client. This clears both the Trusted View Connection Servers cache and the certificate store. Follow steps 5-10 above to confirm the expected connection behavior.
Issue: No VCS warning message displays when the VCS Certificate Check Mode is set to Warn if Connection may be insecure (Default)
This is the expected behavior for non-interactive session modes, which do not display VCS Warning messages in Warn if the connection may be insecure (Default) security mode.
The following are non-interactive session types:
- View Connection Server + Auto-Logon
- View Connection Server + Kiosk
- View Connection Server + Imprivata OneSign (not currently supported on Cisco VXC 2111/2211)
The following is the interactive session type:
Release 4.2.0 PCoIP firmware is compatible with the release of VMware Horizon View generally available when this firmware was released. The version of Horizon View available at the time of this firmware release was Horizon View 5.2. 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.
VMware Horizon View 5.0 or later deployments using zero client devices to connect to View virtual desktops should install release 4.2.0 on the zero client devices.
You can view the firmware version on theweb page for the device.
Cisco VXC Manager Compatibility
Release 4.2.0 is compatible with Cisco VXC Manager 4.8.5, 4.9, and 4.9.1.
To manage the Cisco VXC 2111/2211, you do not require the Cisco VXC Manager. As an alternative for device management, you can use the PCoIP Management Console from Teradici (release 1.7.0 or newer; it is recommended to use the latest release of the PCoIP Management Console).
Using Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
To use the Software Bug Toolkit, follow these steps:
- To access the Bug Toolkit, go to: http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
- Log in with your Cisco.com user ID and password.
To look for information about a specific problem, enter the bug ID number in the "Search for bug ID" field, then click Go.
The following table lists known limitations that will not be fixed.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Copyright © 2014, Cisco Systems, Inc. All rights reserved.