Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide for 3.3.1_327

Transcription

1 Cisco Virtualization Experience Client 2111/2211 PCoIP Administration Guide for 3.3.1_327 April 27, 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number:

2 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. 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: 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) 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 Systems, Inc. All rights reserved.

3 CONTENTS Preface vii Overview vii Audience vii Organization vii Related Documentation viii Obtaining Documentation, Obtaining Support, and Security Guidelines Document Conventions viii viii CHAPTER 1 Introduction 1-1 Menu and Page Overview 1-1 CHAPTER 2 Administrative Web Interface Overview 2-1 About the Page Layout 2-1 Supported Web Browsers 2-2 Administrative Web Interface IP Address 2-2 Administrative Web Interface Security 2-3 Installing the CA Root Certificate 2-3 Installing the CA Root Certificate in Internet Explorer 2-3 Installing the CA Root Certificate in Firefox 2-3 Logging In 2-4 Viewing the Home Page 2-5 About the Administrative Web Interface Menus 2-6 CHAPTER 3 Working with the On Screen Display 3-1 About the Connect Screen 3-1 Connect Button 3-2 About the OSD Options Menu 3-3 CHAPTER Configuring the Device 4-1 Initial Setup Web Page 4-1 Step 1: Audio 4-2 Step 2: Network 4-3 iii

4 Contents Step 3: Session 4-3 Step 4: Apply Changes 4-3 Configuring the Network Parameters 4-3 Adding Custom Information to the Device 4-6 Enabling or Disabling Connection Management 4-7 Configuring for Use with a VMware View Connection Server 4-9 Configuring the VMware View Advanced Parameters 4-11 Configuring the VMware View Kiosk Mode Parameters 4-14 Configuring the Discovery Mechanism 4-15 Configuring the SNMP Agent 4-16 Configuring the Connections 4-17 Identify Peer By 4-19 Controlling Bandwidth for PCoIP Sessions 4-19 Configuring Device Parameters for RDP 4-21 Setting the User Interface Language 4-23 Configuring the OSD Screen-Save Timeout 4-24 Adjusting the Image Quality 4-25 Enabling Monitor Emulation 4-27 Enabling the Host Driver Function 4-28 Configuring the NTP Parameters 4-28 Updating the Password for a Device 4-29 Password Reset Window 4-30 Resetting the Parameters to Factory Defaults 4-31 Configuring the EDID Override Mode 4-31 Setting up User Permissions 4-32 Specifying USB Devices 4-33 Configuring the Audio Parameters 4-35 Setting up the Client Power-off Permissions 4-36 Using the Diagnostic Tools 4-36 Viewing and Clearing Event Log Messages 4-36 Session Control 4-37 Viewing PCoIP Protocol Statistics 4-38 Working with the Host CPU web page 4-40 Generating an Audio Test Tone from the Client 4-41 Viewing a Test Pattern on the Client Display 4-41 Resetting the Device Processor 4-42 Determining if a Device is Reachable 4-43 Viewing Device Information 4-44 Viewing the Version Information 4-44 iv

5 Contents Viewing the Attached Devices 4-46 Uploading to the device 4-47 Uploading the Firmware to the Device 4-47 Uploading a Logo to the Device 4-48 Configuring the User Settings 4-49 Configuring the Mouse Settings 4-49 Changing the Keyboard Repeat Settings 4-49 Image Tab 4-50 Configuring the Display Topology 4-50 CHAPTER 5 About the Overlay Pages 5-1 Network Connection Lost Overlay 5-1 USB Device Not Authorized Overlay 5-1 USB Over Current Notice Overlay 5-2 Half-Duplex Overlay 5-2 Video Source Overlays 5-2 APPENDIX A Usage Examples A-1 Bandwidth and Image Configuration Example A-1 Configuring the Client Bandwidth Limit to 25 Mbps A-2 Configuring Image Properties A-4 Configuring the Client Bandwidth Limit to 0 Mbps (No Limit) A-6 USB Permissions Example A-7 Authorizing USB Device By Class A-7 Authorizing USB Device By Vendor ID and Product ID A-8 APPENDIX B Client Language and Keyboard Support B-1 APPENDIX C Cisco VXC 2111/2211 Power Considerations C-1 Available Power on USB Ports C-1 USB Hub Support C-1 PoE Power Negotiation C-2 Cisco VXC 2111 Power Support C-2 Cisco VXC 2211 Power Support C-3 Cisco VXC 2211 Base LED Behavior C-3 Power Consumption C-4 v

6 Contents vi

7 Preface Overview Cisco Virtualization Experience Clients (VXC) 2111 and 2211 run PC over IP (PCoIP) firmware for operation in PCoIP networks. The Cisco VXC clients are highly optimized zero clients that provide ultra-fast access to applications, files, and network resources available on machines hosted by a PCoIP infrastructure. Note Cisco VXC 2111/2211 clients provide Remote Desktop Protocol (RDP) configuration options. However, Cisco does not provide support for RDP network implementations for the Cisco VXC 2111/2211. Audience This guide is intended for administrators of Cisco VXC running PCoIP. It provides information and detailed system configurations to help you design and manage a PCoIP environment. Organization This manual is organized as described in the following table. Chapter Chapter 1, Introduction Chapter 2, Administrative Web Interface Overview Description Describes the manual. Provides an overview of the Administrative Web Interface. Chapter 3, Working with the On Screen Display Provides an overview of the On Screen Display (OSD). Chapter 4, Chapter 5, About the Overlay Pages Appendix A, Usage Examples Describes the Cisco VXC client configuration using PCoIP Administrative Web Interface and On Screen Display. Describes the user message Overlay Windows. Describes examples of setting up clients. vii

8 Preface Chapter Appendix B, Client Language and Keyboard Support Appendix C, Cisco VXC 2111/2211 Power Considerations Description Describes the languages and keyboards supported by the clients. Describes the Power over Ethernet (PoE) support for the Cisco VXC client. Related Documentation For more information, see the documents available at the following URLs: Cisco Virtualization Experience Client 2000 Series Cisco Virtualization Experience Client Manager Obtaining Documentation, Obtaining Support, and Security Guidelines For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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. Document Conventions This document uses the following conventions: Convention Description boldface font Commands and keywords are in boldface. italic font Arguments for which you supply values are in italics. [ ] Elements in square brackets are optional. { x y z } Alternative keywords are grouped in braces and separated by vertical bars. [ x y z ] Optional alternative keywords are grouped in brackets and separated by vertical bars. string A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. screen font Terminal sessions and information the system displays are in screen font. viii

9 Preface Convention Description boldface screen font Information you must enter is in boldface screen font. italic screen font Arguments for which you supply values are in italic screen font. ^ The symbol ^ represents the key labeled Control for example, the key combination ^D in a screen display means hold down the Control key while you press the D key. < > Nonprinting characters, such as passwords are in angle brackets. Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication. Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Warnings use the following convention: Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071 SAVE THESE INSTRUCTIONS ix

10 Preface x

11 CHAPTER 1 Introduction As a user or administrator you can interact with your Cisco VXC clients through the embedded HTTPS web interface (the Administrative Web Interface) and On Screen Display (OSD). To minimize the total learning curve and maximize the accessibility, the web interface and OSD are organized as similarly as possible and are structured in a task-oriented fashion. The Administrative Web Interface and the OSD let you configure the client through the GUI. With the OSD, messages appear overlaid on the user display as required. Note This document describes the interface for Cisco VXC Clients running PCoIP. This document does not describe the Administrative Web Interface for PCoIP software integrated into products such as VMware View. The configuration features are also available through some connection brokers and the Cisco VXC Manager console (web-based tool used to manage multiple PCoIP endpoints). These features are not described in this guide. For more information on the Cisco VXC Manager, see the Administration Guide for Cisco VXC Manager. This document has four main sections: Administrative Web Interface Overview provides on overview of the Administrative Web Interface. Working with the On Screen Display provides an introduction to the On Screen Display (OSD). details the Cisco VXC client configuration using the PCoIP Administrative Web Interface and the On Screen Display (OSD). About the Overlay Pages discusses the user message overlay windows. The Appendix contains: Appendix A, Usage Examples Appendix B, Client Language and Keyboard Support Appendix C, Cisco VXC 2111/2211 Power Considerations This document is intended to give administrators and users a working understanding of a PCoIP system. Menu and Page Overview The Administrative Web Interface and OSD have various menus and pages. The following tables list each the pages according to their menus as well as if they are available in the Administrative Web Interface, OSD, or both. 1-1

12 Menu and Page Overview Chapter 1 Introduction Note Many of the pages available from the OSD include a subset of parameters that are available in the Administrative Web Interface. Note The pages marked with an asterisk (*) are not applicable to Cisco VXC. Table 1-1 Configuration Menu Page Name Initial Setup Network Label Connection Management VMware View VMware View Advanced (in OSD, this page is available from the VMware View page) VMware View Kiosk Mode (in OSD, this page is available from the VMware View page) Discover SNMP Sessions Bandwidth RDP Language OSD Image (The Web Image page is available form the User Settings menu.) Monitor Emulation* Host Driver Function* Time Password Reset Parameters Display USB Audio Power Web, OSD, or Both Web Both Both Both Both Both Both Both Web Both Web Both Both Both Web Web Web Web Web Both OSD Web Web Web 1-2

13 Chapter 1 Introduction Menu and Page Overview Table 1-2 Permissions Menu Page Name USB Audio Power Web, OSD, or Both Web Web Web Table 1-3 Diagnostics Menu Page Name EventLog Session Control Session Statistics Host CPU* Audio Display PCoIP Ping Web, OSD, or Both Both Web Both Web Web Both Both OSD Table 1-4 Info Menu Page Name Version Attached Devices Web, OSD, or Both Both Web Table 1-5 Upload Menu Page Name Firmware OSD Logo Web, OSD, or Both Web Web Table 1-6 User Settings Menu Page Name Mouse Keyboard Image Display Topology Web, OSD, or Both OSD OSD OSD OSD 1-3

14 Menu and Page Overview Chapter 1 Introduction 1-4

15 CHAPTER 2 Administrative Web Interface Overview The PCoIP Administrative Web Interface lets you interact with the device remotely using an Internet browser. About the Page Layout Figure 2-1 shows an example of the client page. It has seven basic regions: Log Out Log out of the Administrative Web Interface PCoIP Zero Client Displays Cisco VXC PCoIP endpoint information Home Click to navigate to the Home web page Drop-down menus The toolbar at the top part of the page lets you easily find pages through its menus: Configuration, Permissions, Diagnostics, Info, and Upload Web page information Displays the title and summary of the current web page Data field A configurable or read-only parameter (inline help appears when appropriate) Apply/Cancel Each web page that includes editable parameters has these two buttons: Apply Store the edited parameters in flash Cancel Reset the edited parameters to the values currently stored in flash 2-1

16 Chapter 2 Administrative Web Interface Overview Figure 2-1 Administrative Web Interface Home Page Supported Web Browsers The web page servers have been tested and are compatible with the following web browsers: Firefox 1.5, 2.0, 3.0, 3.5, 3.6 Internet Explorer 6.0, 7.0, and 8.0 Note Other browsers may also be compatible. We strongly recommend you install the CA root certificate in the browser you use to avoid warning messages from occurring when you log in to the Administrative Web Interface (see Installing the CA Root Certificate, page 2-3). Administrative Web Interface IP Address To access the Administrative Web Interface: Procedure Step 1 Step 2 Browse to the IP address of the client. The IP address used depends on how the IP addresses are determined within your IP network: Static IP Address: the IP address is hard-coded and must be known Dynamic IP Address: the IP address is dynamically assigned by the Dynamic Host Configuration Protocol (DHCP) server and can be obtained from the DHCP server Enter the IP address into the browser (for example, 2-2

17 Chapter 2 Administrative Web Interface Overview Note Some networks using DHCP may be able to also access the Administrative Web Interface using the PCoIP Device Name. See Adding Custom Information to the Device, page 4-6 for more information. Administrative Web Interface Security The Administrative Web Interface uses HTTP over an SSL socket (HTTPS). You cannot access it without an administrative password. The HTTPS connection is secured using a Teradici self-signed certificate. Note Some PCoIP devices have password protection disabled and do not require a password to log in. You can enable or disable the password protection through the Cisco VXC Manager. Installing the CA Root Certificate You can install a Certificate Authorities (CA) root certificate in the Internet browser to avoid the browser security warnings. Steps for installing the certificate on Internet Explorer 7 and Firefox are described in the following sections. Installing the CA Root Certificate in Internet Explorer Procedure Step 1 Step 2 Step 3 Step 4 Open the Tools menu and select Internet Options. Click on the Content tab, and select Certificates. On the Trusted Root Certification Authorities tab, select Import. Follow the on-screen directions to import the certificate. The certificate file is part of the firmware release. The file is called cacert.pem. Ensure you use the Trusted Root Certification Authorities certificate store. Installing the CA Root Certificate in Firefox Procedure Step 1 Step 2 Step 3 Step 4 Open the Tools menu and select Options. Select the Advanced icon at the top of the page. On the Encryption tab, select View Certificates. On the Authorities tab, select Import. 2-3

18 Logging In Chapter 2 Administrative Web Interface Overview Step 5 Follow the on-screen directions to import the certificate. The certificate file is part of the firmware release. The file is called cacert.pem. Check the option labeled Trust this CA to identify web sites. Logging In To log in to the Administrative Web Interface: Procedure Step 1 From the Log In page, enter your password. The default value is blank ( ). Figure 2-2 Log In Web Page (Client) Step 2 Step 3 To change the time after which the device is automatically logged out, set the Idle Timeout field to one of the following values: 1 minute 5 minutes 15 minutes 30 minutes Never Click Log In. When you first log in to a device, the home page appears. It provides an overview of the device status. If configured in the firmware defaults, the Initial Setup page optionally appears the first time you log in. Note Some PCoIP devices have password protection disabled by default and do not require a password to login. Password protection for the Log In page can be enabled or disabled using the Cisco VXC Manager. See the Administration Guide for Cisco VXC Manager document for more information. If a warning message appears when you try to log in, a session is already in progress on that device. Only one administrator can log in to a device at one time. Logging in to a session already in progress terminates that session. 2-4

19 Chapter 2 Administrative Web Interface Overview Viewing the Home Page See Updating the Password for a Device, page 4-29 for information on changing the password. Viewing the Home Page The home page displays a summary of the client. The first time you log into the Administrative Web Interface, the Initial Setup page appears. The home page appears for each subsequent session. To display it, click the Home link at the top left section of the menu bar. Note When you click the Reset Statistics button, the statistics reported in the home page are also reset. For details about resetting the statistics, see Viewing PCoIP Protocol Statistics, page Figure 2-3 Home Page The information fields shown on the home page are summarized in Table 2-1. Table 2-1 Home Page Parameters Parameter Time since boot Connection State Packet Statistics Comments Length of time that the PCoIP processor has been running (see Resetting the Device Processor, page 4-42) Possible states: Disconnected, Connection Pending, Connected (see Viewing PCoIP Protocol Statistics, page 4-38) Packets sent (see Viewing PCoIP Protocol Statistics, page 4-38) Packets received (see Viewing PCoIP Protocol Statistics, page 4-38) Packets lost (see Viewing PCoIP Protocol Statistics, page 4-38) 2-5

20 About the Administrative Web Interface Menus Chapter 2 Administrative Web Interface Overview Table 2-1 Home Page Parameters (continued) Parameter Byte Statistics Round Trip Latency Bandwidth Stats Display Frame Rates Session Encryption Type PCoIP Device Name Comments Bytes sent (see Viewing PCoIP Protocol Statistics, page 4-38) Bytes received Approximate network minimum, average, and maximum round trip latency; for example, client to virtual machine and back to client (see Viewing PCoIP Protocol Statistics, page 4-38) Active bandwidth Limit is bandwidth PCoIP processors may generate (see Viewing PCoIP Protocol Statistics, page 4-38) Transmit Bandwidth is minimum, average, and maximum traffic transmitted (see Viewing PCoIP Protocol Statistics, page 4-38) Receive Bandwidth is minimum, average, and maximum traffic received see Viewing PCoIP Protocol Statistics, page 4-38) Display Rate for video content through PCoIP protocol; for example, if nothing changed, Frame Rate is 0 fps (see Viewing PCoIP Protocol Statistics, page 4-38) The type of encryption configured for the device. Options include AES-128-GCM, and SALSA Round 12 (see Configuring the Connections, page 4-17) The logical name for the device. This field is the name the client registers with the DNS server if DHCP is enabled and the system is configured to support registering the host name with the DNS server. About the Administrative Web Interface Menus The Administrative Web Interface has five menus that link to the various configuration and status pages. Configuration: The items on this menu let you configure the various aspects for the device, such as network settings, language, session parameters, and so on. Permissions: The items on this menu let you set up the client permissions for the USB, audio, and power. Diagnostics: The items on this menu help you troubleshoot the device. Info: The items on this menu let you view firmware information and the devices currently attached to the device. Upload: The items on this menu let you upload new a firmware version as well as an OSD logo to the device. 2-6

21 Chapter 2 Administrative Web Interface Overview About the Administrative Web Interface Menus Figure 2-4 shows the web pages available in the Administrative Web Interface. Note The pages marked with an asterisk (*) are not applicable to Cisco VXC. Figure 2-4 Administrative Web Interface Overview 2-7

22 About the Administrative Web Interface Menus Chapter 2 Administrative Web Interface Overview 2-8

23 CHAPTER 3 Working with the On Screen Display The On Screen Display (OSD) local GUI appears on the client when the device is powered on and a PCoIP session is not in progress. The OSD provides a way for the user to connect to a virtual machine through the Connect screen. The Connect screen also lets the user access the Options page which provides a subset of the functionality provided by the Administrative Web Interface. You can access the Options page by clicking the Options menu on the Connect screen. About the Connect Screen The Connect screen appears during the startup except when the client is configured for a managed startup or auto-reconnect. You can change the logo that appears above the Connect button by uploading a replacement image through the Administrative Web Interface. See Uploading a Logo to the Device, page 4-48 for information on updating the Connect Screen logo. The Network icon at the bottom right of the Connect screen shows the status of the network connection. Users must wait until the network icon appears as shown in Figure 3-1: 3-1

24 Chapter 3 Working with the On Screen Display Figure 3-1 OSD Connect Screen A red X over the network icon means that either the network is not properly connected or the connection is still being initialized (that is, during client bootup). Figure 3-2 Network Not Ready (detail) Figure 3-3 shows the network icon when ready. Figure 3-3 Network Ready (detail) Connect Button Click the Connect button to initiate a PCoIP session or RDP session (depending on the session settings). While the PCoIP connection is pending, the OSD local GUI displays a Connecting, please wait message. When the connection is established, the OSD local GUI disappears and is replaced with the session image. 3-2

25 Chapter 3 Working with the On Screen Display About the OSD Options Menu Figure 3-4 OSD Connect Screen (Connecting) About the OSD Options Menu There are five pages available from the Options menu: Configuration: This option lets you configure various aspects for the device, such as the network settings, peer connection, session parameters, and so on. Diagnostics: This option helps you troubleshoot the device. Information: This option lets you view details about the device. User Settings: This option lets the user define mouse and keyboard settings, as well as the PCoIP protocol image quality. Password: This option lets you update the administrative password for the device. 3-3

26 About the OSD Options Menu Chapter 3 Working with the On Screen Display Figure 3-5 OSD Options Menu 3-4

27 CHAPTER 4 As a user or administrator you can interact with your Cisco VXC clients through the embedded HTTPS web interface (the Administrative Web Interface) and On Screen Display (OSD). Users can connect or disconnect a session, view diagnostics, and configure user parameters. Administrators can view and change configuration settings and user permissions, upload data to the PCoIP device, view session diagnostics information, and view product information. To minimize the total learning curve and maximize the accessibility, the web interface and OSD are organized as similarly as possible and are structured in a task-oriented fashion. Configuring the Device The Configuration option on the Administrative Web Interface and OSD let you configure various aspects for the device. This section walks you through the full set of configuration options. Note The OSD configuration options are a subset of the options available in the Administrative Web Interface. To make changes to the configuration settings you need an administrative password. You do not need a password to view the Diagnostic and Information menus. Note The Cisco VXC firmware lets you disable the OSD and Administrative Web Interface from the Cisco VXC Manager. Initial Setup Web Page If configured in the firmware defaults, the Initial Setup web page optionally appears the first time you log in. For subsequent sessions, the home page appears unless the firmware parameters are reset. Note This page is not generally used to configure Cisco VXC connections. To set up a connection with a VMware View Connection Server, see Configuring for Use with a VMware View Connection Server, page

28 Configuring the Device Chapter 4 The Initial Setup web page contains the configuration parameters that the administrator must first set when using the client. The web page simplifies the out-of-box experiences and reduces the time for initial users to establish sessions between a Cisco VXC client and a remote virtual machine. More complex environments that use connection management systems require further configuration. After you update the settings on this page, click Apply. Figure 4-1 Initial Setup Client Web Page Step 1: Audio Step 1: Audio allows the administrator to configure the audio parameters. Table 4-1 summarizes the applicable parameters. For details on the full set of Audio parameters, see Generating an Audio Test Tone from the Client, page Table 4-1 Step 1: Audio Parameters Parameter Enable HD Audio Comments Enables audio support on the client 4-2

29 Chapter 4 Configuring the Device Step 2: Network Step 2: Network allows the administrator to configure the network parameters. Table 4-2 summarizes the applicable parameters. For details on the full set of Network parameters, see Configuring the Network Parameters, page 4-3 Table 4-2 Step 2: Network Parameters Parameter Enable DHCP IP Address Subnet Mask Gateway Primary DNS Server Secondary DNS Server Comments Enables DHCP rather than manual configuration The device IP address The device subnet mask The device gateway IP address The device primary DNS IP address The device secondary DNS IP address Step 3: Session Step 3: Session allows the administrator to configure the session parameters. Table 4-3 shows the client parameters. For details on configuring the full set of Session parameters, see Configuring the Connections, page Table 4-3 Step 3: Session Parameters (Client) Parameter Session Type Identify Host by Host IP Address Host MAC Address Comments Specifies the PCoIP protocol or RDP Specifies the host identify method Note In this context, host refers to the server that hosts the virtual machine. Specifies the host IP address Specifies the host MAC address Step 4: Apply Changes Step 4: Apply Changes allows the administrator to apply the parameter updates made in the preceding steps. Parameters will not be updated until Apply is selected. Configuring the Network Parameters You can configure the client network Parameters from the Initial Setup web page or Network page. After you update the Parameters on this page, click Apply to save your changes. 4-3

30 Configuring the Device Chapter 4 Figure 4-2 Network Configuration Web Page Figure 4-3 OSD: Network Configuration Table 4-4 Parameter Enable DHCP IP Address Network Parameters Description When enabled: The device contacts a DHCP server to be assigned an IP address, subnet mask, gateway IP address, and DNS servers. The firmware requests a domain name (option 15), host name (option 12), and client FQDN (option 81). When disabled: You must set these parameters manually. The device IP address. If DHCP is disabled, you must set this field to a valid IP address. If DHCP is enabled, you cannot edit this field. 4-4

31 Chapter 4 Configuring the Device Table 4-4 Parameter Subnet Mask Network Parameters (continued) Description The device subnet mask. If DHCP is disabled, you must set this field to a valid subnet mask. If DHCP is enabled, you cannot edit this field. Warning It is possible to configure an illegal IP Address/Subnet Mask combination (for example, invalid mask) that leaves the device unreachable. Take care when setting the Subnet Mask. Gateway Primary DNS Server Secondary DNS Server Domain Name FQDN The device gateway IP address. If DHCP is disabled, this field is required. If DHCP is enabled, you cannot edit this field. The device primary DNS IP address. This field is optional. If the DNS server IP address is configured when using a Connection Manager, the Connection Manager address may be set as an FQDN instead of an IP address The device secondary DNS IP address. This field is optional. If the DNS server IP address is configured when using a Connection Manager, the Connection Manager address may be set as an FQDN instead of an IP address. The domain named used (for example, domain.local). This field is optional. This field specifies the client domain. The Fully Qualified Domain Name for the client. The default is pcoip-portal-<mac> where <MAC> is the client MAC address. If used, the Domain Name is appended (for example, pcoip-portal-<mac>.domain.local). This field is read-only on this page. Note To use the FQDN feature, the DNS server with DHCP option 81 must be available and properly configured. 4-5

32 Configuring the Device Chapter 4 Table 4-4 Network Parameters (continued) Parameter Ethernet Mode Maximum MTU Size Description Lets you configure the Ethernet mode of the client as: Auto 10 Mbps Full-Duplex 100 Mbps Full-Duplex When you choose 10 Mbps Full Duplex or 100 Mbps Full-Duplex and then click Apply, this warning message appears: Warning: When Auto-Negotiation is disabled on the PCoIP device, it must also be disabled on the switch. Additionally, the PCoIP device and switch must be configured to use the same speed and duplex parameters. Different parameters may result in a loss of network connectivity. Are you sure you want to continue? Click OK to change the parameter. Note Always set the Ethernet Mode to Auto and use only 10 Mbps full-duplex or 100 Mbps full-duplex when the other network equipment (for example, switch) is also configured to operate at 10 Mbps full-duplex or 100 Mbps full-duplex. An improperly set Ethernet Mode may result in the network operating at half-duplex (which is not supported by the PCoIP protocol). The session will be severely degraded and eventually dropped. Lets you configure the Maximum Transfer Unit packet size. A smaller MTU may be needed for situations such as VPN tunneling because PCoIP packets cannot be fragmented. Set the Maximum MTU Size to a value smaller than the network path MTU for the end-to-end connection between the virtual machine and client. The Maximum MTU Size range is 500 to 1500 bytes. Note The default MTU is 1300 for sessions with the remote virtual machine. Adding Custom Information to the Device The Label page allows an administrator to add custom information for the client. 4-6

33 Chapter 4 Configuring the Device Figure 4-4 Label Configuration Web Page Figure 4-5 OSD: Label Configuration Table 4-5 Label Parameters Parameter PCoIP Device Name PCoIP Device Description Generic Tag Description Lets you give the client a logical name. The default is or pcoip-portal-<mac> where <MAC> is the device MAC address. This field is the name the client registers with the DNS server if DHCP is enabled and the system is configured to support registering the host name with the DNS server. It is important to ensure that the PCoIP Device Name is unique for each endpoint in the network. A description or other information (such as the location of the endpoint) for the device. The firmware does not use this field. It is provided for administrator use. Generic tag information about the device. The firmware does not use this field. It is provided for administrator use. Enabling or Disabling Connection Management The Connection Management page allows you to enable or disable connection management and to specify the IP address of the connection manager that is not VMware View. 4-7

34 Configuring the Device Chapter 4 VMware View connection management settings are in dedicated pages. See Configuring for Use with a VMware View Connection Server, page 4-9. In a managed connection, an external Connection Manager Server does the following: Communicates with and can remotely control and configure the device Can locate an appropriate peer for the device to connect to and initiate the connection Can simplify the administration effort for a large, complex system Figure 4-6 Connection Management Configuration Web Page (IP Address) Figure 4-7 Connection Management Configuration Web Page (FQDN) 4-8

35 Chapter 4 Configuring the Device Figure 4-8 OSD: Connection Management Configuration Table 4-6 Connection Management Parameters Parameter Enable Connection Management Identify Connection Manager By Enable Event Log Notification Enable Diagnostic Log Description When enabled, you can configure and control the device by using an external connection manager. Lets you choose whether the connection manager is identified by an IP address or by an FQDN. If Connection Management is disabled, this field is not required and not editable. Controls whether the client devices send the contents of their event logs to the connection management server. Controls whether connection-management-specific debug messages are written to the event log of the client devices. Configuring for Use with a VMware View Connection Server The VMware View page allows configuration for use with a VMware View Connection Server. 4-9

36 Configuring the Device Chapter 4 Figure 4-9 VMware View Configuration Web Page Figure 4-10 OSD: VMware View Configuration Table 4-7 VMware View Parameters Parameter Enable VMware View Identify Connection Server by Description When enabled, you can configure the client for use with a VMware View Connection Server. Note To enable the VMware View feature, the Enable Connection Management check box on the Connection Management page must be unchecked. If VMware View is disabled, the remaining fields are not required and are not editable. Choose how the connection manager is identified: IP Address FQDN 4-10

37 Chapter 4 Configuring the Device Table 4-7 VMware View Parameters (continued) Parameter Connection Server FQDN Port SSL Auto connect Connection Server Cache Mode Description When FQDN is enabled, you can enter the URI used to specify the VMware View Connection Server. Some examples of valid URL formats include: myconnectionserver.cisco.com Specify the port used to communicate to the VMware View Connection Server Specify whether you want the client to communicate with the VMware View Connection server over a secure connection using SSL. Specify whether the client always connects with the VMware View Connection server at startup. Set this field to: Last five servers used These appear on the Connection Server entry box on the OSD VMware View Connect screen Read-only The Cisco VXC Manager can be used to prepopulate the list of available connection servers. Configuring the VMware View Advanced Parameters The Advanced button from the VMware View page lets you set advanced VMware View parameters for the Cisco VXC client. To display the Advanced Settings page from the Administrative Web Interface: Procedure From the Configuration menu, click VMware View (Advanced). The Advanced Settings page appears. 4-11

38 Configuring the Device Chapter 4 To display the Advanced Settings page from the OSD: Procedure Step 1 Step 2 From the Configuration menu, click the VMware View tab. The VMware View page appears. Click the Advanced button. 4-12

39 Chapter 4 Configuring the Device Table 4-8 VMware View Advanced Settings Parameters Parameter Auto Launch If Only One Desktop Login Username Caching Use OSD Logo for View banner Prefer GSC-IS Enable Auto-Logon Logon Username Logon Password Logon Domain Name Description When enabled and the user credentials are entered, users are automatically connected to their desktop VM. Note This feature is for users who are entitled to a single desktop. It does not apply to users entitled to multiple virtual desktops When enabled, the username text box automatically populates with the last username entered. When enabled, the Cisco VXC Client OSD logo is used for login. Administrators can upload a custom OSD logo through the Cisco VXC client web interface. When selected, the CAC GSC interface is used if a smart card supports more than one interface such as CAC (GSC-IS) and PIV endpoint. If a smart card supports only one interface, such as either CAC or PIV endpoint, then only the CAC or PIV endpoint interface is used regardless of the Prefer GSC-IS setting. This affects only smart card access performed outside of PCoIP sessions. Prefer GSC-IS is selected by default. When enabled, the login information is automatically entered. The user does not need to enter a username or password when connecting to the device. The name of the user. The user password. The domain name for the client being configured. Desktop Name to Select Enter the pool/desktop name used by a Cisco VXC client when starting a session. 4-13

40 Configuring the Device Chapter 4 Configuring the VMware View Kiosk Mode Parameters Kiosk mode is used with VXC clients when you want to provide access to Virtual Machines (VM) to multiple users in a public place (such as airports, bus stations, and stadiums). Such users use the zero client to obtain information that is not specific to any individual, such as bus schedules, sightseeing information, public phone numbers, and so on. In addition, if there are concerns that a guest user might damage a VM by using it in an inappropriate way, you can configure the VM as non-persistent in the datacenter. In this case, the VM does not save any persistent information after it is powered down, and will restart in its original state when it is powered up again. You can configure Kiosk Mode through the OSD or the Administrative Web Interface. Kiosk mode requires a properly configured VMware View environment. See VMware View documentation for more information. To access the Kiosk Mode settings from the Administrative Web Interface: Procedure Step 1 Step 2 Log in to the Administrative Web Interface for the client. From the Configuration menu, click VMware View (Kiosk Mode). The Kiosk Mode Configuration page appears. To configure the kiosk mode settings from the OSD: Procedure Step 1 Step 2 From the Configuration menu, click the VMware View tab. Click Kiosk Mode. The Kiosk Mode window appears. 4-14

41 Chapter 4 Configuring the Device Table 4-9 VMware View Kiosk Mode Parameters Parameter Enable Kiosk Mode Zero Client MAC Option Custom Option Password Description When enabled, the Cisco VXC client automatically logs in at startup to a predefined virtual desktop. Users do not need to enter their credentials. If the Zero Client MAC option is selected, the username is automatically entered based on the unique MAC address of the Cisco VXC client. If the Custom option is selected, the username is set to CM and the username is entered. The system uses the contents of the Password field as the session password when Kiosk Mode automatically logs the Cisco VXC client in to the predefined virtual desktop. Configuring the Discovery Mechanism Note The Discovery Configuration page is not applicable to Cisco VXC clients. 4-15

42 Configuring the Device Chapter 4 Figure 4-11 Discovery Configuration Web Page Figure 4-12 OSD: Discovery Configuration Configuring the SNMP Agent The Cisco VXC includes an SNMP agent that supports reporting of management information to an SNMP manager. The SNMP page lets you enable or disable the Cisco VXC SNMP agent. The Cisco VXC uses public as the SNMP community string. Figure 4-13 SNMP Configuration Web Page Table 4-10 Parameter Enable SNMP SNMP Parameters Description When enabled, the client enables the PCoIP SNMP agent. Disabling the SNMP agent ensures that the PCoIP SNMP MIB cannot be accessed. 4-16

43 Chapter 4 Configuring the Device Configuring the Connections Note This page is not generally used to configure Cisco VXC connections. To set up a connection with a VMware View Connection Server, see Configuring for Use with a VMware View Connection Server, page 4-9. The Session page lets you configure how the client device connects to or accepts connections from peer devices. Figure 4-14 Session Configuration Web Page Figure 4-15 OSD: Session Configuration Note If Accept Any Peer is disabled the user must enter the peer (client) MAC address and the IP address will be non-editable. 4-17

44 Configuring the Device Chapter 4 Table 4-11 Session Parameters Parameter Description Accept Any Peer Note This field is not applicable to Cisco VXC. Session Type You can choose a PCoIP session or an RDP session. Note Cisco does not provide support for RDP network implementations for the Cisco VXC 2111/2211. Identify Peer By Choose whether the device is identified by its IP and MAC address or by the FQDN. Identify Peer By, page 4-19 shows the peer identify parameters available for either method. If you enter an invalid IP address or DNS name, the web interface prompts you to correct it. You can set the Peer MAC address equal to on a Cisco VXC client and the field is ignored. Peer IP Address Specify the peer IP address. Peer MAC Address Specify the peer MAC address. Enable Auto-Reconnect Lets the client automatically reconnect with the last connected broker server when a session is lost. Enable Peer Loss Overlay Enable AES-128-GCM When enabled, the Network Connection Lost overlay appears on the displays when a loss of network connectivity is detected. It also appears in the case of a virtual desktop such as VMware View. Normal hypervisor scheduling delays can falsely trigger this message. This option is disabled by default. Note Desktop applications that require the peer loss notification should renewable the feature through the OSD, Administrative Web Interface, or Cisco VXC Manager. Configure the AES-128-GCM encryption for the client. AES-128-GCM is an encryption method implemented in the TERA1x100 processor that allows best performance between hardware endpoints. Note The enabled encryption must match on the virtual machine and client for a session to be established. If both modes are enabled, the firmware selects: Enable SALSA Round 12 VM 4.5 and later to client: SALSA Round12 for the PCoIP session Configure SALSA Round 12 encryption for the client. SALSA Round12 is a lighter encryption method implemented in firmware that may offer improved performance when connecting to VMware View 4 or later when there is more than about 7 Mbps available on the network. Note The enabled encryption must match on the virtual machine and client for a session to be established. If both modes are enabled, the firmware selects: VM 4.5 and later to client: SALSA Round12 for the PCoIP session 4-18

45 Chapter 4 Configuring the Device Identify Peer By The Identify Peer By selector allows you to choose whether the peer device is identified by IP and MAC address or by Fully Qualified Domain Name (FQDN). If Accept Any Peer is enabled, these fields are not required and are not editable. Table 4-12 shows the peer identify parameters available when either method is chosen. If an invalid IP address or DNS name is entered, the web interface will prompt the administrator to correct it. Table 4-12 Peer Identify Methods Peer Identify Method Data Fields Comment Peer IP/MAC Peer IP Address PCoIP client or RDP client Peer MAC Address PCoIP client Peer FQDN Peer DNS Name PCoIP client or RDP client Peer MAC Address PCoIP client Controlling Bandwidth for PCoIP Sessions The Bandwidth page lets you control the bandwidth used by the device during a PCoIP session. This applies to sessions between Cisco VXC clients and the remote virtual machine. The parameters in this page are applied after you click Apply. To configure the bandwidth used with a VMware View virtual desktop, adjust the PCoIP GPO session variables Figure 4-16 Bandwidth Configuration Web Page 4-19

46 Configuring the Device Chapter 4 Table 4-13 Bandwidth Parameters Parameter Device Bandwidth Limit Description Defines the maximum bandwidth peak for the PCoIP system. The bandwidth setting defines the bandwidth based on which side is sending data: On the virtual machine side: from the virtual machine to the client (for example, graphics data) On the client side: from the client to the virtual machine (for example, USB data) The usable range of the device bandwidth is 1000 to 220,000 kbps. The PCoIP processor uses only the required bandwidth up to the Device Bandwidth Limit maximum. The PCoIP processor dynamically adjusts the bandwidth in response to network congestion. Setting the Device Bandwidth Limit to 0 configures the PCoIP processor to adjust the bandwidth depending on network congestion. If there is no congestion, there is no limit on bandwidth. That is, the processor uses the maximum rate available. We recommend setting this field to the limit of the network connected to the client and virtual machine. Note The setting in this field is applied immediately after you click Apply. See Bandwidth and Image Configuration Example, page A-1 for an example of setting the Device Bandwidth Limit. 4-20

47 Chapter 4 Configuring the Device Table 4-13 Bandwidth Parameters (continued) Parameter Device Bandwidth Target Device Bandwidth Floor Description Defines the temporary limit on the network bandwidth during periods of congestion (packet loss). When the network experiences congestion, the device bandwidth is reduced rapidly to the target value and more slowly below this value. This allows for a more even distribution of bandwidth between users sharing a congested network link. After the congestion is alleviated, the bandwidth used increases depending on the available network resources up to the Device Bandwidth Limit. You must have a good understanding of the network topology before setting this to a non-zero value. Lets you configure the bandwidth floor used by the firmware when congestion is present and when bandwidth is required. This lets you optimize performance for a network with understood congestion or packet loss. If the bandwidth is not required, the bandwidth used drops below the floor. A setting of 0 lets the firmware reduce bandwidth to 1000 kbps for these network impairments. You must have a good understanding of the network topology before setting this to a non-zero value. Note The firmware implements a Slow Start Algorithm that: Increases the bandwidth used until the bandwidth required is reached, network congestion is detected, or the Device Bandwidth Limit is reached Begins at the lesser of the Device Bandwidth Limit and 8000 kbps Increases the bandwidth used within seconds Allows a graceful session startup for low bandwidth scenarios (for example, WAN) After initiating a PCoIP session, users may temporarily notice low bandwidth video artifacts while the algorithm ramps up bandwidth use. Configuring Device Parameters for RDP The RDP web page allows you to configure device parameters specific to the Remote Desktop Protocol (RDP). Note Cisco VXC PCoIP firmware is bundled with, and provides configuration options for, the RDP 5.2 client. However, Cisco does not provide support for RDP network implementations with the Cisco VXC 2111/2211 and recommends that you do not use the bundled RDP client. 4-21

48 Configuring the Device Chapter 4 Figure 4-17 RDP Configuration Web Page Figure 4-18 OSD: RDP Configuration 4-22

49 Chapter 4 Configuring the Device Table 4-14 RDP Parameters Parameter Resolution Bit Depth Terminal Server Port Audio Mode Enable Wallpaper Enable Themes Description The RDP screen resolution. Options include: Native Resolution 800x x x x x x x x x1200 The RDP session color bit depth. Options include: 8 bpp (bits per pixel) 16 bpp 24 bpp The port number to which the RDP client connects. The location where the audio playback occurs for the RDP session. Options include: Do not play Play on client Play on host (indicates play on the virtual machine) Enable the use of wallpaper with the RDP session. Enable the use of desktop themes with the RDP session. Setting the User Interface Language The Language page allows the administrator to change the user interface language. Note This setting affects the local OSD GUI. 4-23

50 Configuring the Device Chapter 4 Figure 4-19 Language Configuration Web Page Figure 4-20 OSD: Language Configuration Table 4-15 Language Parameters Parameter Language Keyboard Layout Description Configure the OSD language. This setting determines the language for the OSD only. It does not affect the language setting for the actual user session. See Appendix B, Client Language and Keyboard Support for supported languages. Change the layout of the keyboard. When the user starts a session, this setting is pushed to the virtual machine. If the Windows GPO is set to allow the keyboard layout setting, it is used during the user session. If the Windows GPO is not set to allow the setting, it is dropped. See Table B-2 in Appendix B, Client Language and Keyboard Support for supported keyboard layouts. Configuring the OSD Screen-Save Timeout The OSD page allows you to modify the On Screen Display (OSD) parameters. 4-24

51 Chapter 4 Configuring the Device Figure 4-21 OSD Configuration Web Page Figure 4-22 OSD: OSD Configuration Table 4-16 OSD Parameters Parameter Screen-saver Timeout Description Configure the screen-saver timeout before the client puts the attached displays into low-power mode. You can configure the timeout mode in seconds, up to 9999 seconds. A setting of 0 seconds disables the screen-saver. Note After the OSD screen Timeout period expires, the attached displays are dimmed. To bring the displays up again (within 5 seconds) move the attached mouse. (No password is required.) Adjusting the Image Quality The Image page lets you make changes to the image quality of the PCoIP session. This applies to sessions between Cisco VXC clients and the virtual machine. To configure the image quality settings with a VMware View virtual desktop, adjust the PCoIP session variables. 4-25

52 Configuring the Device Chapter 4 Figure 4-23 Image Configuration Web Page Figure 4-24 OSD: Image 4-26

53 Chapter 4 Configuring the Device Table 4-17 Image Parameters Parameter Minimum Image Quality Maximum Initial Image Quality Description Lets you compromise between image quality and frame rate when network bandwidth is limited. Some use cases may require lower-quality images at a higher frame rate while others need higher-quality images at a lower frame rate. In environments where the network bandwidth is constrained, moving the slider towards Reduced allows higher frame rates. Moving the slider towards Perception-Free allows for higher image quality. When network bandwidth is not constrained, the PCoIP system maintains perception-free quality regardless of the Minimum Image Quality parameter. Note The Minimum Image Quality must be less than or equal to the Maximum Initial Image Quality. See Bandwidth and Image Configuration Example, page A-1 for an example of setting the Minimum Image Quality. Use the slider to reduce the network bandwidth peaks caused by screen content changes. This parameter limits the initial quality on the first display frame of a screen change. Unchanged regions of the image are built to a loss-less state regardless of this parameter. Note The Maximum Image Quality: Must be greater than or equal to the Minimum Image Qualified Does not have a corresponding parameter on the OSD because it is intended as an administrator-only parameter Enabling Monitor Emulation Note The Monitor Emulation page is not applicable to Cisco VXC clients. Figure 4-25 Monitor Emulation Configuration Web Page 4-27

54 Configuring the Device Chapter 4 Enabling the Host Driver Function Note The Host Driver Function page is not applicable to Cisco VXC clients. Figure 4-26 Host Driver Function Configuration Web Page Configuring the NTP Parameters The Time web page configures the Network Time Protocol (NTP) settings to allow the event logs (see Viewing and Clearing Event Log Messages, page 4-36) of the client to be time-stamped based on NTP time. Note To simplify system troubleshooting, set the NTP parameters to allow correlation of user events to the relevant diagnostic event log entries. Figure 4-27 Time Configuration Web Page Table 4-18 Parameter Current Time Enable NTP Time Parameters Description Displays the time based on the NTP. Enable or disable the NTP feature. 4-28

55 Chapter 4 Configuring the Device Table 4-18 Time Parameters (continued) Parameter Identify NTP Host By NTP Host Port NTP Query Interval Time Zone Enable Daylight Savings Time Description Choose if the NTP Host (that is, the NTP server) is identified by IP address or by FQDN. If NTP is disabled, this field is not required and is not editable. If you enter an invalid IP address or DNS name, a message appears to prompt you to correct it. The parameter depends on which method you choose: IP Address: Shows the NTP server IP address FQDN: Shows the NTP server DNS name Lets you configure the NTP port number. Lets you configure the query interval. The first field is for the interval period and the second field is for the time unit in Minute(s), Hour(s), Day(s), and Week(s). Lets you select the local time zone. Enable or disable the automatic adjustment for daylight savings time. Updating the Password for a Device The Password page lets you update the local administrative password for the device. The password can be a maximum of 20 characters. Some PCoIP devices have password protection disabled by default. The Password page is not available on these devices. Password protection can be enabled through the Cisco VXC Manager for these devices. Note This parameter affects the web interface and the local OSD GUI. Take care when updating the client password because the client may become unusable if the password is lost. If a device is set up to have password protection disabled, the Password page on the OSD is not available. You can enable the password protection through the Cisco VXC Manager for these devices. 4-29

56 Configuring the Device Chapter 4 Figure 4-28 Password Configuration Web Page Figure 4-29 OSD: Change Password Table 4-19 Password Parameters Parameter Old Password New Password Confirm New Password Reset Description This field must match the current administrative password before you can update the password. The new administrative password for both the web interface and the local OSD GUI. This field must match the New Password field for the change to take place. If the client password is lost, you can click the Reset button to request a response code from their client vendor. The challenge code can be sent to the vendor. The vendor qualifies the request and returns a response code if authorized. When the response code is correctly entered, the client password is reset to an empty string. You must enter a new password. Note Contact the client vendor for more information when an authorized password reset is required. This option is not available through the Administrative Web Interface. It is available only through the OSD. Password Reset Window Figure 4-30 shows the Authorized Password Reset window. 4-30

57 Chapter 4 Configuring the Device Figure 4-30 OSD: Authorized Password Reset Resetting the Parameters to Factory Defaults The Reset web page lets you reset configuration and permissions to factory default values stored in flash. When you click the Reset Parameters button, a prompt appears for confirmation. This is to prevent accidental resets. Figure 4-31 Reset Parameters Web Page Figure 4-32 OSD: Reset Table 4-20 Reset Parameters Parameter Reset Parameters Description The Reset Parameters button resets all configuration and permissions to factory default values. When this button is selected, the web interface will prompt the administrator for confirmation to prevent accidental resets. Configuring the EDID Override Mode The Display page lets you enable the Extended Display Identification Data (EDID) override mode. 4-31

58 Setting up User Permissions Chapter 4 Note The EDID override mode can be enabled only from the OSD. Under normal operation, the GPU in the virtual machine queries the monitor to determine the monitor's capabilities. These are reported in the EDID information. In some situations, a monitor may be connected to a client in a way that prevents the client from reading the EDID information such as connecting through some KVM devices. In this case, configure the client to report default EDID information to the virtual machine by enabling the display override mode. When this feature is enabled, the client provides EDID information to the user s virtual machine display properties that indicates the following resolutions are supported: Hz Hz Hz Hz (native resolution advertised) Hz Hz Hz Hz Warning Enabling display override forces default-monitor display information that may not comply with the connected monitor and result in a blank monitor. Enable display override only when there is no valid EDID information and when monitor display characteristics are understood. Figure 4-33 OSD: Display Configuration Setting up User Permissions The Permissions option on the Administrative Web Interface lets you configure parameters for the USB, Audio, and Power for the device. 4-32

59 Chapter 4 Setting up User Permissions Note There are no corresponding Permissions options for the OSD. Specifying USB Devices Note Certain USB-powered devices require sufficient power to be available on the client to power them. If the client does not have sufficient power for a USB device, the USB device cannot function, regardless of the configurations on these screens. The USB page lets you specify authorized and unauthorized USB devices. It is divided into two sections: Authorized Devices ( white list ) and Unauthorized Devices ( black list ). Devices are authorized or unauthorized based on ID or Class. You can use wildcards (or specify any ) to reduce the number of entries needed to define all devices. See USB Permissions Example, page A-7 in Appendix A, Usage Examples for more details on USB configuration. USB plug events are blocked in the Cisco VXC client hardware for unauthorized USB devices. The virtual machine cannot see or access the device for an additional layer of security. The factory defaults for the client USB permissions are any, any, any (that is, authorized USB devices). Note The USB permissions are updated only at the start of a PCoIP session. They are authorized in the following order of priority (highest to lowest): 1. Unauthorized Vendor ID/Product ID 2. Authorized Vendor ID/Product ID 3. Unauthorized Device Class/Sub Class/Protocol 4. Authorized Device Class/Sub Class/Protocol 4-33

60 Setting up User Permissions Chapter 4 Figure 4-34 USB Permissions Web Page Table 4-21 USB Parameters Parameter Authorized Devices Unauthorized Devices Bridged Devices Description Specify the authorized USB devices for the client. Two buttons let you customize this white list : Add New: Add a new device or device group to the list. This allows USB authorization by ID or Class: ID: The USB device is authorized by Vendor ID and Product ID Class: The USB device is authorized by Device Class, Sub Class, and Protocol Remove: Delete a rule for a device or device group from the list. Specify the unauthorized USB devices for the client. Add New: Add a new device or device group to the list. This allows USB devices to be unauthorized by ID or Class: ID: The USB device is unauthorized by Vendor ID and Product ID Class: The USB device is unauthorized by Device Class, Sub Class, and Protocol Remove: Delete a rule for a device or device group from the list. Cisco VXC clients locally terminate HID devices when connecting to VMware View virtual desktops, however, some devices advertise as HID but use different drivers. These devices may need to be bridged to the virtual machine rather than locally terminated. This setting lets you force the client to bridge specific USB devices so that they use the drivers on the virtual desktop. This rule only affects sessions between a client and a virtual machine running VMware View 4.6 or later. Add New: Add a new device or device group to the list. This allows USB devices to be bridged by Vendor ID and Product ID. Remove: Delete a rule for a device or device group from the list. 4-34

61 Chapter 4 Setting up User Permissions Table 4-22 summarizes the USB authorization entry type and the associated data fields. Two buttons let you customize this white list : Table 4-22 USB Device Authorized/Unauthorized Entry Types Entry Type Required Fields Hexadecimal Value Comments ID VID 0-FFFF PID 0-FFFF Class Device Class 0-FF; asterisk (*) indicates any device class Sub Class Protocol 0-FF; asterisk (*) indicates any device subclass 0-FF; asterisk (*) indicates any protocol authorized Drop-down menu provides translations of the known device classes Drop-down menu provides translations of the known device subclasses Drop-down menu provides translations of the known protocols Configuring the Audio Parameters You can configure the audio parameters from the Initial Setup page when you start your first session. For subsequent sessions, use the Audio page to configure the audio permissions for the device. After you update the options on this page, click Apply to save your changes. To display the Audio page from the Administrative Web Interface, select the Permissions menu, and then click Audio. Figure 4-35 Audio Web Page Table 4-23 Audio Parameters Parameter Enable HD Audio Description Enables audio support on the client. If the Enable HD Audio option is disabled on the virtual machine, the audio hardware is not available for the OS to enumerate. 4-35

62 Using the Diagnostic Tools Chapter 4 Setting up the Client Power-off Permissions The Power page lets you configure the power-off permissions of the client. Figure 4-36 Power Web Page Table 4-24 Power Parameters Parameter Client Power Button Description The pull-down menu lets you configure the client power button functionality. Options include: Power-off not permitted Soft power-off only soft limit Hard power-off only Soft and hard power-off Using the Diagnostic Tools The Diagnostics menu contains links to pages with run-time information and functions that may be useful for troubleshooting. Note The diagnostic options in the OSD are a subset of those available through the Administrative Web Interface. Viewing and Clearing Event Log Messages The Event Log page lets you view and clear event log messages from the client. The web interface lets you change the log filter setting on the device, which controls which messages are put in the log. When you set the filter to terse, the device logs terse messages. 4-36

63 Chapter 4 Using the Diagnostic Tools Figure 4-37 Event Log Web Page Figure 4-38 OSD: Event Log Table 4-25 Event Log Parameters Parameter Event log Message Event log filter mode Description View: Click View to open a browser page that displays all the event log messages (with time-stamp information) stored on the device. Press F5 to refresh the browser page log information. Clear: Click Clear to delete all stored event log messages stored on the device. Click the drop-down menu to filter the event logs. Options are: Verbose Terse Session Control The Session Control web page allows control of the device session. 4-37

64 Using the Diagnostic Tools Chapter 4 Figure 4-39 Session Control Web Page Table 4-26 Session Control Parameters Parameter Connection State Peer IP/MAC Address Description This field displays the current state for the session. Options include: Disconnected Connection Pending Connected Two buttons appear below the Connection State field: Connect: If the connection state is Disconnected, click this button to initiate a PCoIP session between the client and its peer device. If the connection state is Connection Pending or Connected, this button is disabled. Disconnect: If the connection state is Connected or Connection Pending, click this button to end the PCoIP session for the device. If the connection state is Disconnected, this button is disabled. Peer IP Address: Displays the IP address for the peer device. When not in session, this field is blank. Peer MAC Address: Displays the MAC address of the peer device. When not in session, this field is blank. Viewing PCoIP Protocol Statistics The Session Statistics page on the Administrative Web Interface and OSD lets you view current statistics when a session is active. If a session is not active, you can view the statistics from the last session. 4-38

65 Chapter 4 Using the Diagnostic Tools Figure 4-40 Session Statistics Web Page Figure 4-41 OSD: Session Statistics 4-39

66 Using the Diagnostic Tools Chapter 4 Table 4-27 Session Statistics Parameters Parameter Connection State PCoIP Packets Statistics Bytes Statistics Round Trip Latency Bandwidth Statistics Display Frame Rate Reset Statistics Description The current (or last) state of the PCoIP session. Values include: Asleep Canceling Connected Connection Pending Disconnected Waking PCoIP Packets Sent: The total number of PCoIP packets sent in the current/last session. PCoIP Packets Received: The total number of PCoIP packets received in the current/last session. PCoIP Packets Lost: The total number of PCoIP packets lost in the current/last session. Bytes Sent: The total number of bytes sent in the current/last session. Bytes Received: The total number of bytes received in the current/last session. The minimum, average, and maximum round-trip PCoIP system (for example, virtual machine to client and then back to the virtual machine) and network latency in milliseconds (+/- 1 ms). Active Bandwidth Limit: The maximum amount of network traffic the processor may currently generate. The value is derived from the configured bandwidth parameters and the current (or last) network congestion levels. Transmit Bandwidth: The minimum, average, and maximum traffic transmitted by the processor. Receive Bandwidth: The minimum, average, and maximum traffic received by the processor. Display 1 Frame Rate: The frame rate for Display 1, reported in frames per second. Display 2 Frame Rate: The frame rate for Display 2, reported in frames per second. Click this button to reset the statistic information on this page. Note This button also resets the statistics reported in the home page. Working with the Host CPU web page Note The Host CPU page is not applicable to Cisco VXC clients. 4-40

67 Chapter 4 Using the Diagnostic Tools Figure 4-42 Host CPU Web Page Generating an Audio Test Tone from the Client The Audio web page allows you to generate an audio test tone from the client. To verify the audio test, you must first connect speakers or headphones to the client. Caution Cisco recommends that you do not wear the headphones during the audio test. Instead, hold them approximately two feet away from your ears because the volume level is loud and cannot be adjusted. To generate an audio test tone, click Start to start the test tone. Click Stop to stop the test. Note The Audio web page functionality is available on a client only when not in a PCoIP session. Figure 4-43 Audio Diagnostics Web Page Viewing a Test Pattern on the Client Display The Display web page lets you initiate and view a test pattern on the client display. Note The test pattern only appears on the Display page when the client is not in a PCoIP session. If you click Start when the client is in session, an error message appears. 4-41

68 Using the Diagnostic Tools Chapter 4 Figure 4-44 Display Web Page Table 4-28 Parameter Test mode Test resolution Start/Stop Display Parameters Description Set the type of test pattern for the attached monitor(s) as: Video Test Pattern Generator Pseudo Random Bitstream Set the test pattern resolution as: 1024x x x x1200 Click Start to begin the test pattern. Click Stop to stop the test. Resetting the Device Processor The PCoIP Processor page lets you reset the client and view the amount of time that has elapsed since the client PCoIP processor last booted. 4-42

69 Chapter 4 Using the Diagnostic Tools Figure 4-45 PCoIP Processor Web Page Figure 4-46 OSD: PCoIP Processor Table 4-29 PCoIP Process Parameters Parameter Current Time Time Since Boot (Uptime) Reset PCoIP Processor Description The current time. This feature requires that the NTP be enabled and configured. For details about configuring the NTP settings, see Configuring the NTP Parameters, page View the time that has elapsed since the PCoIP processor last booted. Click this button to reset the client. Determining if a Device is Reachable The Ping page lets you ping a device to see if it is reachable across the IP network. This may help you determine if a broker server is reachable. Because the firmware forces the do not fragment flag in the ping command, you can also use this feature to determine the maximum MTU size. Note The Ping tab has no matching menu in the Administrative Web Interface. 4-43

70 Viewing Device Information Chapter 4 Figure 4-47 OSD: Ping Figure 4-48 Ping Parameters Parameter Destination Interval Packet Size Packets Sent Packets Received Description IP Address or FQDN to ping Interval between ping packets Size of ping packet Number of ping packets transmitted Number of ping packets received Viewing Device Information The Information page lets you see details about the device. The Administrative Web Interface shows version, vital product data (VPD), and attached device information. The OSD lets you view the device version information. Viewing the Version Information The Version page allows you to view hardware and firmware version details. 4-44

71 Chapter 4 Viewing Device Information Figure 4-49 Version Web Page Figure 4-50 OSD: Version Table 4-30 Version Parameters Parameter VPD Information Firmware Information Description This is vital product information provisioned by the factory to uniquely identify each client. MAC Address: Client unique MAC address Unique Identifier: Client unique identifier Serial Number: Client unique serial number Firmware Part Number: Part number of the current firmware Hardware Version: Client hardware version number This information reflects the current firmware details. Firmware Version: Version of the current firmware Firmware Build ID: Revision code of the current firmware Firmware Build Date: Build date for the current firmware 4-45

72 Viewing Device Information Chapter 4 Table 4-30 Version Parameters (continued) Parameter PCoIP Processor Revision Bootloader Information Description The silicon revision of the PCoIP processor. Revision B of the silicon is denoted by a 1.0. This information reflects the current firmware bootloader details: Bootloader Version: Version of the current bootloader Bootloader Build ID: Revision code of the current bootloader Bootloader Build Date: Build date of the current bootloader Viewing the Attached Devices The Attached Devices page lets you see the type and status of the monitor and USB hardware currently attached to the client. Figure 4-51 Attached Devices Web Page Table 4-31 Attached Devices Parameters Parameter Monitors USB Devices USB Device Status Description This section displays the name, serial number, vendor identification (VID), product identification (PID), date, and status of the monitor attached to each port. The first line is for monitor 1. The second line is for monitor 2. This section displays the name, serial number, vendor identification (VID), product identification (PID), device class, sub class, protocol, and status of the USB device attached to each port. The first line is for the first USB port. The second line is for the second port, and so on. The possible status options include: Not Connected: No device is connected. Standalone: The device is detected outside of a PCoIP session. Not Initialized: The device is detected in a PCoIP session but the virtual machine has not initialized the device. Failed Authorized: The device is detected in a PCoIP session but is not authorized. (For more information, see USB Permissions Example, page A-7.) Locally Connected: The device is detected and authorized but locally terminated in a PCoIP session (for example, a local cursor). Connected: The device is detected and authorized in a PCoIP session. 4-46

73 Chapter 4 Uploading to the device Uploading to the device You can use the options in this menu to upload new firmware to a device or to upload an OSD logo to a device. These options are not available through the OSD. Uploading the Firmware to the Device The Firmware web page allows you to upload a new firmware build to the client. Figure 4-52 Firmware Upload Web Page Table 4-32 Parameter Firmware build filename Upload Firmware Upload Parameters Description The filename of the firmware image to be uploaded. You can browse to the file using the Browse button. The file must be accessible to the web browser (that is, on a local or accessible network drive). The firmware image must be an.all file. Click the Upload button to transfer the specified file to the device. The web interface prompts you to confirm this action to avoid accidental uploads. Firmware Upload Process Example Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Ensure the client is disconnected from the virtual machine. Log in to the client Administrative Web Interface (using a password if enabled). From the Firmware Upload web page, browse to the firmware.all file (for example, tera1x00_rel1-9-v175.all). Click Open. Click Upload. Click OK to confirm that you want to proceed with the upload. When the firmware upload completes, the message Success Flash successfully programmed! You must reset the device for the changes to take effect appears. Click Reset. The message The PCoIP processor will reset on the next host system restart; your changes will take effect then. Are you sure you want to proceed? appears. Click OK. If the client does not automatically reset itself, reset the client manually. 4-47

74 Uploading to the device Chapter 4 Step 10 Start the PCoIP session as usual. Uploading a Logo to the Device The OSD Logo page allows you to upload an image to the device. This image is displayed on the Connect window of the local GUI On Screen Display (OSD) logo. The VMware View Advanced page includes an option Use OSD Logo for View Banner, which lets you configure if the OSD logo appears on the View login screen instead of the View banner. For more information, see Configuring the VMware View Advanced Parameters, page Figure 4-53 OSD Logo Upload Web Page Table 4-33 OSD Logo Parameters Parameter OSD logo filename Upload Description Specify the filename of the logo image you want to upload. You can browse to the target file using the Browse button. The file must be accessible to the web browser (that is, on a local or accessible network drive). The 24-bits-per-pixel image must be in BMP format and its dimensions cannot exceed 256 pixels in width, 64 pixels in height. If the file extension is incorrect, an error message appears. Click Upload to transfer the specified image file to the client. A message to confirm the upload appears. OSD Logo Upload Process Example Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 From the OSD Logo web page, click Browse to locate the target logo file. Click Open. Click Upload. The message Are you sure? This will upload a new logo for the local GUI. This operation may take a few minutes appears. Click OK. Wait for the OSD Logo upload to finish. A message appears to advise if the upload was successful. Reset the client. 4-48

75 Chapter 4 Configuring the User Settings Configuring the User Settings The User Settings page lets you access tabs to define the mouse and keyboard settings, PCoIP protocol image quality, as well as the display topology. Configuring the Mouse Settings The Mouse page lets you change the mouse cursor speed settings for the OSD and RDP sessions. Figure 4-54 OSD: Mouse Table 4-34 Parameter Mouse Speed Mouse Parameters Description Configure the speed of the mouse cursor. Note You can also configure the mouse speed through the virtual machine. Changing the Keyboard Repeat Settings The Keyboard page lets you change the keyboard repeat settings for the OSD and RDP sessions. Note The Keyboard tab has no corresponding menu in the Administrative Web Interface. 4-49

76 Configuring the User Settings Chapter 4 Figure 4-55 Keyboard Table 4-35 Keyboard Parameters Parameter Keyboard Repeat Delay Keyboard Repeat Rate Repeat Settings Test Box Description Lets users configure the client keyboard repeat delay. Lets users configure the client keyboard repeat rate. Lets users test the chosen keyboard settings. Image Tab For information about adjusting the image quality, see Adjusting the Image Quality, page Configuring the Display Topology The Display Topology page lets users change a display position, rotation, and resolution for a PCoIP session. To apply the display topology feature to a PCoIP session between a client and a Virtual Machine (VM), you must have VMware View 4.5 or later. Note Be aware of the following: The Display Topology tab has no corresponding menu in the Administration Interface. Always change the display topology settings using the Display Topology tab on the client (OSD > Options > User Settings). Do not try to change these settings using the Windows Display Settings in a virtual machine when using VMware View. To view the Display Topology page: Procedure Step 1 Step 2 From the OSD, click Options, and then click User Settings. Click the Display Topology tab. 4-50