administration guide for cisco v irtualization experience ......figure 6: dhcp scope options: cisco...

Administration Guide for Cisco Virtualization Experience Client 6215Firmware Release 9.0First Published: April 02, 2013

Last Modified: June 18, 2013

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

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 LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE 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 versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, 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 OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE 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, networktopology 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 unintentionaland 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 partnershiprelationship between Cisco and any other company. (1110R)

© 2013 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

http://www.cisco.com/go/trademarks

C O N T E N T S

C H A P T E R 1 Preface 1

Overview 1

Supported Flash version 3

Audience 3

Organization 3

Related documentation 4

Documentation, support, and security guidelines 4

Document conventions 4

C H A P T E R 2 Cisco VXC 6215 Firmware Release 9.0 setup 7

High-level steps for initial setup 7

Best practices for Cisco VXC 6215 management using Cisco VXC Manager 8

Client discovery using Cisco VXC Manager 11

DHCP server configuration for device discovery 11

INI files 16

Create a wlx.ini file for client configuration 16

INI file examples 17

Mandatory INI parameters 17

Firefox browser configuration example 18

XenDesktop INI configuration example 18

XenApp INI configuration example 18

VMware View INI configuration example 19

RDP INI configuration example 19

Enable VNC configuration example 20

Time settings configuration example 20

Display and keyboard settings configuration example 20

Create a Cisco VXC Manager package for the wlx.ini file 20

Schedule device updates using Default Device Configuration 23

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.0 iii

Configure Default Device Configuration preferences 24

First-time Default Device Configuration 24

Existing Default Device Configuration 25

Cisco VXC 6215 deployment with a Cisco Virtual Office Router 26

Monitor resolution 26

SSH connections 27

C H A P T E R 3 Upgrading to Firmware Release 9.0 29

Cisco Virtualization Experience Media Engine 29

Disabled power management settings with Cisco VXME 30

Update the Cisco VXC 6215 firmware to Release 9.0 30

C H A P T E R 4 Cisco AnyConnect Secure Mobility Client 33

Feature support 33

Setup 34

Profile setup on Cisco ASA 35

Cisco AnyConnect setup on Cisco VXC 6215 using INI parameters 35

C H A P T E R 5 USB redirection 37

Recognizing USB cameras using HDX RealTime Webcam with Citrix 37

USB camera redirection not supported with Vmware View 37

USB redirection not supported for Logitech UC Keyboard with Cisco VXME 38

C H A P T E R 6 Desktop basics 39

Logging in 39

Using your desktop 40

Desktop keyboard shortcuts 41

Connecting to a monitor 42

Shutting down, restarting, and suspending 42

Installation update warning 43

Viewing system information 43

C H A P T E R 7 Accessing additional features with the Application Browser 45

Cisco AnyConnect Secure Mobility Client 46

Connect to a VPN 46

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.0iv

Contents

Connection Manager 46

Diagnostics 47

Diagnostics Log Viewer 48

VMware View client 49

Configure Cisco VXC Manager Agent 49

Volume Control 51

Firefox Web Browser 52

Cheese 52

Display Preferences 52

System Information 53

Take Screenshot 53

VNC Server 54

A P P E N D I X A Shadow or monitor a thin client 55

Shadow a thin client from a remote machine 55

INI configuration example for enabling VNC 56

VNC Server Preferences dialog box 57

A P P E N D I X B Cisco VXC Manager and Wyse Device Manager 59

Cisco VXC Manager with WDM 59

Set up Cisco VXC Manager 59

Set devices to use Cisco VXC Manager 60

A P P E N D I X C BIOS upgrade 61

Overview 61

Extract BIOS 62

Install BIOS 62

Limitations 63

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.0 v

Contents

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.0vi

Contents

C H A P T E R 1Preface

• Overview, page 1

• Audience, page 3

• Organization, page 3

• Related documentation, page 4

• Documentation, support, and security guidelines, page 4

• Document conventions, page 4

OverviewThe Cisco Virtualization Client 6215 (Cisco VXC 6215) delivers superior voice and video collaborationcapabilities in desktop virtualization. It unifies voice, video, and virtual desktop in one device.

The Cisco VXC 6215 provides workers with secure, real-time access to business applications and contentwithout compromising the collaborative user experience. The Cisco VXC 6215 supports the followingcapabilities:

• Combines virtual desktops with voice and video capabilities

• Supports processing capabilities that use network and data center CPU resources efficiently

• Supports high-quality, scalable voice and video, delivering an optimal user experience

The Cisco VXC 6215 provides support for the following hosted virtual desktop protocols:

• Citrix Independent Computing Architecture (ICA)

• PC over IP (PCoIP)

• Remote Desktop Protocol (RDP) (does not support the Cisco Virtualization Experience Media Engine[VXME] add-on)

By default, the firmware installed on the Cisco VXC 6215 supports desktop virtualization capabilities, butdoes not provide the additional voice and video functionality required for Unified Communications. To supportUnified Communications, you can enable Cisco Jabber on the Cisco VXC 6215 by purchasing the CiscoVirtualization Experience Media Engine (VXME).

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.0 1

For detailed information about CiscoVXME, see theDeployment Guide for Cisco Virtualization ExperienceMedia Engine for Cisco Virtualization Experience Client 6215.

Note

The following tables describe the virtual desktop protocols and applications that support the Cisco VXC 6215base firmware and those that support the Cisco VXME.

Table 1: Supported Virtual Desktop Protocols and Applications (Citrix)

Releases Supported with CiscoVXME

Releases Supported with BaseFirmware

Supported Virtual DesktopProtocols and Applications

5.0, 5.5, 5.6Release 5.0 requires thelatest VDA 5.5 pluginwith latest hotfix (hotfix100 minimum)

Note5.0, 5.5, 5.6

Release 5.0 requires thelatest VDA 5.5 pluginwith latest hotfix (hotfix100 minimum)

NoteCitrix XenDesktop

6.0 and 6.56.0 and 6.5Citrix XenApp (PublishedDesktoponly – no support for PublishedApplications)

12.1.2Supported with XenAppconnections only

12.1.2Supported with XenAppconnections only

Citrix ICA Client

12.1.212.1.2Citrix ICA Browser Plugin

5.0, 5.5, 5.65.0, 5.5, 5.6Citrix Virtual Desktop Agent

Table 2: Supported Virtual Desktop Protocols and Applications (VMware)




5.0 and 5.1, using VMware ViewClient 1.7

VMware View Client 1.7requires SSL forconnections to a ViewConnection Server

Note

5.0 and 5.1, using VMware ViewClient 1.7

VMware View Client 1.7requires SSL forconnections to a ViewConnection Server

Note

VMware View (PCoIP)

Table 3: Supported Virtual Desktop Protocols and Applications (RDP)




Not supported7.0 and 7.1, Using VMware ViewClient 1.7

RDP

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 9.02

PrefaceOverview

Supported Flash versionCisco VXC 6215 Release 9.0 includes Flash version 11.2.202.235-21.1+1. To ensure interoperability, installFlash 11.x on the hosted desktop. Cisco recommends you install the latest available 11.x version of FlashPlayer.

AudienceThis guide is intended for administrators of Cisco VXC 6215 clients. It provides information and detailedsystem configurations to help you design and manage your thin client environment.

OrganizationThis manual is organized as described in the following table.

DescriptionChapter

Describes how to set up and manage the thin clientusing Cisco VXC Manager.

Cisco VXC 6215 Firmware Release 9.0 setup, onpage 7

Describes how to upgrade devices to FirmwareRelease 9.0.

Upgrading to Firmware Release 9.0, on page 29

Provides information about configuring CiscoAnyConnect on devices to enable VPN connections.

Cisco AnyConnect Secure Mobility Client, on page33

Describes how to enable Flash redirection, USBredirection, and multimedia redirection on devices.

USB redirection, on page 37

Describes desktop basics.Desktop basics, on page 39

Describes how to use the Application Browser toaccess the applications, audio and video, and systemfeatures installed on the thin client.

Accessing additional features with the ApplicationBrowser, on page 45

Describes how to use VNC for remote access andmonitoring of the thin client.

Shadow or monitor a thin client, on page 55

Describes how to manage a network containing aCisco VXC Manager server and Cisco VXC 6215devices together with a Wyse Device Manager(WDM).

Cisco VXCManager andWyse Device Manager, onpage 59

Describes how to upgrade the BIOS for a BIOSpassword change.

BIOS upgrade, on page 61


PrefaceSupported Flash version

Related documentationFor more information, see the documents available at the following URLs:

Cisco Virtualization Experience Client 6000 Series

http://www.cisco.com/en/US/products/ps11976/tsd_products_support_series_home.html

Cisco Virtualization Experience Client Manager


Cisco Virtualization Experience Media Engine


Documentation, support, and security guidelinesFor information on obtaining documentation, obtaining support, providing documentation feedback, securityguidelines, and also recommended aliases and general Cisco documents, see the monthlyWhat's New in CiscoProduct Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to theWhat's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a freeservice and Cisco currently supports RSS Version 2.0.

Document conventionsThis document uses the following conventions:

Means reader take note. Notes contain helpful suggestions or references to material that is not covered inthe publication.

Note

Means reader be careful. In this situation, you might do something that could result in equipment damageor loss of data.

Caution

Warnings use the following convention:

Warning IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Beforeyou work on any equipment, be aware of the hazards involved with electrical circuitry and befamiliar with standard practices for preventing accidents. Use the statement number provided atthe end of each warning to locate its translation in the translated safety warnings that accompaniedthis device. Statement 1071

Warning


PrefaceRelated documentation




http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

SAVE THESE INSTRUCTIONS


PrefaceDocument conventions


PrefaceDocument conventions

C H A P T E R 2Cisco VXC 6215 Firmware Release 9.0 setup

Cisco thin clients are designed to be centrally managed and configured using INI files and the Cisco VXCManager. This chapter describes the Cisco VXCManager procedures required to apply client configurationson Cisco VXC 6215 devices running Firmware Release 9.0. For detailed information about using CiscoVXC Manager, see Administration Guide for Cisco Virtualization Experience Client Manager.

This chapter describes the steps required to manage devices that are already running Firmware Release9.0. For information about upgrading Cisco VXC 6215 devices from Release 8.6 or 8.7 to Release 9.0,see Upgrading to Firmware Release 9.0, on page 29.

Note

This chapter contains the following topics:

• High-level steps for initial setup, page 7

• Best practices for Cisco VXC 6215 management using Cisco VXC Manager, page 8

• Client discovery using Cisco VXC Manager, page 11

• INI files, page 16

• Create a wlx.ini file for client configuration, page 16

• INI file examples, page 17

• Create a Cisco VXC Manager package for the wlx.ini file, page 20

• Schedule device updates using Default Device Configuration, page 23

• Cisco VXC 6215 deployment with a Cisco Virtual Office Router, page 26

• Monitor resolution, page 26

• SSH connections, page 27

High-level steps for initial setupThe following are the high-level steps required to set up your Cisco VXC 6215 environment.


To interoperate with Cisco VXC 6215 Firmware Release 9.0, you must run Cisco VXC Manager 4.9.1.If you are running a previous release of Cisco VXC Manager, you can still discover and manage CiscoVXC 6215 devices running Firmware Release 9.0, but real-time commands are not supported.

For upgrades, Cisco recommends that you first upgrade your Cisco VXCManager management server torelease 4.9.1, and then upgrade your Cisco VXC 6215 devices to Firmware Release 9.0.

Note

Procedure

Step 1 Set up your virtualization server (see your virtualization server documentation).Step 2 Install or upgrade to Cisco VXC Manager 4.9.1 (see Installation Guide for Cisco Virtualization Experience

Client Manager).Step 3 Connect at least one Cisco VXC 6215 to your network and power it on.Step 4 Set up device discovery in Cisco VXC Manager (DHCP is the recommended method—see Client discovery

using Cisco VXC Manager, on page 11).Step 5 Create the INI files to centrally configure the thin clients (see Create a wlx.ini file for client configuration,

on page 16).Step 6 Set up a configuration package in Cisco VXCManager referencing the desired INI configuration (see Create

a Cisco VXC Manager package for the wlx.ini file, on page 20).Step 7 Push the configuration package to your thin clients (see Schedule device updates using Default Device

Configuration, on page 23 ).

Best practices for Cisco VXC 6215 management using CiscoVXC Manager

The following are best practices for management of Cisco VXC 6215 devices using Cisco VXC Manager.

HTTP and HTTPS with Cisco VXC Manager

•With Firmware Release 9.0, the Cisco VXC 6215 can support Cisco VXC Manager 4.9.1 using HTTPor HTTPS , but not FTP. Set the Cisco VXCManager to use HTTP or HTTPS for server communications(using a custom installation).

• If you enable HTTPS on Cisco VXCManager, it always uses HTTPS whether the Cisco VXC 6215 hascertificates installed or not. If you do not have a certificate on the device, the upgrade can still proceed.

• If you enable HTTPS on Cisco VXC Manager, and an upgrade for the Cisco VXC 6215 fails, CiscoVXC Manager does not fallback to attempting HTTP, unlike the standard HAgent process. Instead,Cisco VXC Manager returns an error after three attempts using HTTPS.

•When you configure the software repository, you can check the Secure (HTTPS) check box to enableHTTPS. However, the Validate Certificate with CA check box has no effect. Regardless of whether thelatter option is enabled, the certificates are used for encryption only, not authentication, and so they arenot validated against a trusted CA.


Cisco VXC 6215 Firmware Release 9.0 setupBest practices for Cisco VXC 6215 management using Cisco VXC Manager

• To upgrade to Firmware Release 9.0, you must first ensure HTTPS is disabled on Cisco VXCManager.The upgrade process supports HTTP only. After you perform the update to Firmware Release 9.0, youcan then re-enable HTTPS.

Drag-and-Drop not supported

With Firmware Release 9.0, DDC is the only supported method available to push packages. Drag-and-Dropis not supported. (Drag-and-Drop may function in small environments or for test purposes. However, it willnot function at all for thin clients behind a Cisco AnyConnect VPN.)

The benefits of using DDC are as follows:

• A specific configuration for your thin clients is always available for download (Drag-and-Drop is availableonly once, and in case of errors, the thin client cannot download the same configuration again).

• A specific configuration can be applied to multiple machines (all devices or sub-groups).

• A brand new device can download the correct package without the need to specify a new configuration(all new devices will use the same applied DDC configuration).

Single package deployment

Cisco recommends that you always deploy only one DDC package containing the base image, all the add-onsyou need, and the required INI file. If you must change anything inside the package, create a brand newpackage with a different name.

New INI and RSP files required for Firmware Release 9.0

The INI and RSP files required to upgrade to Firmware Release 9.0 are incompatible with those used inprevious releases and are also incompatible with those used to push updates to devices already runningFirmware Release 9.0. Do not try to re-use the Release 8.6 or 8.7 RSP and INI files with the new software.You must use the appropriate RSP and INI files for the Release 9.0 packages.

Required preserve changes setting

In order for the hostname on the device to be retained after a reboot, you must enable the preserve changesoption in the RSP file (set-preserve-changes yes) and in the INI file (Update.Preserve_changes=yes).If these parameters are not set correctly, your previous configurations will be lost after a reboot and thehostname on the thin client will revert to the device MAC address.

Editing INI and RSP files

Use only a plain text editor to edit INI and RSP files. Do not use word processing program such as Word orWordPad to edit these files, otherwise package deployment errors can occur.

INI caching

In the INI file, include the INIFileSource=cache parameter to ensure that devices use the local cached versionof the INI file if they cannot access the INI file from Cisco VXC Manager. This is particularly important fordevices running the Cisco AnyConnect VPN, so that they have a configuration to reference at bootup beforeconnecting to the network over VPN.



Cisco AnyConnect deployments

For devices running the Cisco AnyConnect VPN, before you provide the devices to your remote employees,you must first push the required configuration to the devices on your local network first. Once you haveupgraded the devices with the required parameters locally, you can then provide the preconfigured devicesto remote users to operate behind the Cisco AnyConnect VPN.

Deploying add-ons

•When you deploy an add-on to the device, include the base image in the DDC package. This ensuresthat the devices that apply the add-on are also running the required base image version. For devicesalready running the required base image, they will install the add-on only.

• To check which specific add-ons and RPMs are installed on the thin client, see the Application Info tabfor the device in Cisco VXC Manager (at the bottom of the details pane in Device Manager).

Package and file naming

• All Cisco VXCManager package names, filenames (including .rsp and .ini), folders, and so on must belower-case.

• Every time you push a new package, you must use a new name for the package. (You can copy thepackage, change the name, make the required changes, and then push the renamed package.) Do notmake changes to an existing package and push it again with the same name; otherwise, the clients maynot apply the latest changes. As a best practice, add the date to each package you create.

• If you downgrade a Cisco VXC 6215 thin client from a newer Image DDC (for example, DDC_10) toany older Image DDC (for example, DDC_09), and then try to re-apply the newer image DDC to theclient, the operation fails. To successfully re-apply the newer image DDC (DDC_10) to the thin clientafter a downgrade, youmust first rename the newer image DDC using Cisco VXCManager (for example,to DDC_10a).

Minimum checkin time

In the Device Manager preferences (Configuration Manager > Preferences > Device Manager), the minimumcheckin time must be no less than 5 minutes, otherwise devices will experience issues. For large deployments,the default value of 1 hour is appropriate.

Scheduled Packages error

If you deploy a package from Cisco VXC Manager and an error message appears in the Schedule Packages,delete this error. Any errors associated with a specific thin client prevent future package deployments to thethin client until the errors are deleted.

Device discovery using static configuration rather than DHCP

DHCP is the Cisco-recommended method for device discovery with Cisco VXC Manager. As an alternative,you can specify the Cisco VXC Manager address on the thin client statically in the INI file using theMgmtDiscoveryMethod=STATIC parameter together with the RapportServer and the RapportSecurePortparameters. For more information, see INI Files Reference Guide for Virtualization Experience Client 6215Firmware Release 9.0.



Execute command

In Device Manager, if you enter a command in the Execute Command dialog box (right-click the device andchoose Execute Command), always add an ampersand to the end of the command (for example,/etc/init.d/sshd start &). Otherwise, the command can leave the thin client unusable, requiring a manualreboot.

Log History tab

In the Log history tab (at the bottom of the details pane in Device Manager), if you list the logs by date, theentries are not listed in chronological order, but rather in alphabetical order.

Client discovery using Cisco VXC ManagerCisco VXC Manager is the standard tool for managing the Cisco VXC 6215. Cisco VXC Manager allowsyou to configure, upgrade, and administer your thin clients from a single interface. It also allows you to specifydefault configurations that are common to all of the thin clients in your environment. You can also use it toenable add-ons, which provide additional functionality in addition to the underlying firmware.

CiscoVXCManager can discover the CiscoVXC 6215 devices in your network using either dynamic discoveryor a manual process. After Cisco VXC Manager identifies the devices in the network, it stores informationabout them in the Cisco VXC Manager Database. You can then use Cisco VXC Manager to manage thedevices.

For the Cisco VXC 6215, the recommended discovery method uses a DHCP server. In this case, you mustconfigure DHCP Option Tags on your DHCP server to specify the IP address and port of the Cisco VXCManagerWeb Server. The Cisco VXCManager Agent (HAgent) on the Cisco VXC 6215 uses this informationto communicate with the Cisco VXC Manager Web Server, performing check-ins at boot up and at regularintervals. The Hagent provides the Cisco VXC Manager with device information including device name,hardware information, network information, and image version.

For detailed configuration steps for DHCP discovery, see DHCP server configuration for device discovery,on page 11.

For proper operation of the thin clients, you must also specify a value either for DHCPOption 15 (DomainName) or for DHCP Option 6 (Domain Server) in the DHCP server configuration. If you do not specifya standard domain name for DHCP Option 15, and you do not specify a standard domain server for DHCPOption 6, you must at minimum specify "none" for DHCP Option 15. This configuration is necessarywhether or not you are using DHCP to direct the thin clients to the central server.

Caution

For information about additional discovery methods with Cisco VXCManager, see Administration Guide forCisco Virtualization Experience Client Manager.

DHCP server configuration for device discoveryTo allow Cisco VXC Manager to discover the Cisco VXC 6215 devices, configure the following option tagvalues on your DHCP server:

• Option tag 186—IP address of your Cisco VXCManager server (for example, 192.168.1.10). The valueshould be in 4-byte IP address format.


Cisco VXC 6215 Firmware Release 9.0 setupClient discovery using Cisco VXC Manager

• Option tag 194—As an alternative to option tag 186, you can use option tag 194 to specify the FQDNof the Cisco VXC Manager server.

• Option tag 190—Secure port number to which Cisco VXC Manager server listens (for example, port443). The value should be in word format (value = 0x01bb) or 2-byte array format (value = 0x01 0xbb).

• Option tag 192—Non-secure port number to which Cisco VXC Manager server listens (for example,80). The value should be in either word format (value = 0x0050), or 2-byte array format (value= 0x000x50).

Do not run the Cisco VXC Manager server and the DHCP server on the same machine.Tip

To configure the Cisco VXC Manager server IP address and port option values on a Windows DHCP server:


Cisco VXC 6215 Firmware Release 9.0 setupDHCP server configuration for device discovery

Procedure

Step 1 Open the DHCP management wizard, choose the DHCP server to be configured, right-click the server name,and choose Set Predefined Options to open the Select Predefined Options and Values window.

Figure 1: DHCP Window

Figure 2: Select Predefined Options and Values

Step 2 On the Predefined Options and Values screen, click the Add button. The Option Type window appears.Step 3 In the Option Type window, enter the required information:

• Name—Cisco VXC Manager Server

• Data Type—IP Address

• Code—186



• Description (optional)—Enter desired information

Figure 3: Option Type: Server IP

Step 4 Click OK.Step 5 Repeat Steps 2 and 3 for the Cisco VXC Manager Server Secure port, with these changes:

• Name—Cisco VXC Manager Server Secure Port

• Data Type—Word

• Code—190

Step 6 Repeat Steps 2 and 3 for the Cisco VXC Manager Server port, with these changes:

• Name—Cisco VXC Manager Server Port

• Data Type—Byte or Word

• Code—192

Figure 4: Option Type: Cisco VXC Manager Server Port



Step 7 Click OK.

Figure 5: DHCP Scope Options: Cisco VXC Manager Server

Step 8 From the DHCP management wizard, right-click Scope Options (from the target DHCP Server Scope, asshown in Step 7) and choose Configure Options.

• In the list of Available Options, check option number 186, and enter the IP address of the Cisco VXCManager server.

• In the list of Available Options, check option number 190, and enter the port number at which yourCisco VXC Manager server listens for secure communication.

• In the list of Available Options, check option number 192, and enter the port number at which yourCisco VXC Manager server listens (Port 80 is shown below).

Figure 6: DHCP Scope Options: Cisco VXC Manager Server Port



Step 9 Click OK.

Figure 7: DHCP Scope Options List

Step 10 Confirm that options 186, 190 and 192 are listed with proper values under the target DHCP server and scope.

INI filesINI files are plain-text files that you can use to centrally manage and configure your thin clients on a globallevel. For example, you can use INI files to configure and save information about connection settings, displayoptions, and printer options. The INI files are maintained on the central Cisco VXC Manager server, and thethin client accesses the INI files from the server during the initialization process (using HTTP, or HTTPS).

INI files are employed as follows:

• wlx.ini—This is the global INI file. One wlx.ini file is available to all users. It contains global parametersfor all thin clients accessing the server.

• $MAC.ini—This file is used for device-specific configuration. It is stored in the same directory as thewlx.ini file. If the thin client locates this INI file on the server, the thin client uses the $MAC.ini file forits configuration rather than the wlx.ini file. In this case, the thin client does not access the wlx.ini fileunless you specify the include=wlx.ini parameter in the $MAC.ini file.

Create a wlx.ini file for client configurationThe most commonly used INI file, wlx.ini, contains the global parameters you want to apply to all thin clientsin your environment. (Cisco VXC Manager also allows you to specify a subset of thin clients to which aparticular wlx.ini configuration applies.)

The Cisco VXC 6215 supports a number of INI configuration parameters. See INI file examples, on page17 for some useful examples, including configurations required to create XenDesktop, VMware View, and


Cisco VXC 6215 Firmware Release 9.0 setupINI files

RDP connections. For a complete list of supported INI parameters, see INI Files Reference Guide for CiscoVirtualization Experience Client 6215 .

By default, administrator and root user credentials are specified on the thin client. The Cisco VXC 6215does not support the operation of the device using these credentials (the only supported mode of operationis using the thinuser credentials). However, Cisco strongly recommends that you change the passwordsfor these users to prevent unauthorized access to the client, using the following INI parameters.

INI parameter used to changepassword

Default passwordUsername

Caution

ChangeAdminPasswordadminadmin

ChangeRootPasswordadminroot

To create the wlx.ini file, perform the following procedure.

Procedure

Step 1 Open a text file.Step 2 Enter the INI parameters required in accordance with INI file examples, on page 17 or Cisco Virtualization

Experience Client 6215 INI Files Reference Guide.Step 3 Save the file as wlx.ini.Step 4 After you create the wlx.ini file, you must create a Cisco VXC Manager package to push the wlx.ini

configuration to your clients. See Create a Cisco VXC Manager package for the wlx.ini file, on page 20.

INI file examplesThis section contains sample INI files. For detailed information about INI parameters and definitions, see theINI Files Reference Guide for Cisco Virtualization Experience Client 6215.

Mandatory INI parametersTo push updates to Release 9.0 devices, you must include the following mandatory parameter in the INI file:IniFileSource=cache

To perform upgrades to Release 9.0 from a previous release, you must use different INI and RSP filesthan those used to push updates to Release 9.0 devices. For information about how to upgrade to Release9.0 from a previous release, see Upgrading to Firmware Release 9.0, on page 29.

Note


Cisco VXC 6215 Firmware Release 9.0 setupINI file examples

Static IP INI parameters for Cisco VXC Manager

If you are deploying using static Cisco VXC Manager IP configuration, also include the following:

MgmtDiscoveryMethod=STATICRapportServer=xxx.xxx.xxx.xxxRapportSecurePort=443

In the above, replace xxx.xxx.xxx.xxx and 443 with your Cisco VXC Manager IP address and secure portnumber.

Firefox browser configuration exampleThe following is a simple INI file that you can use to test the Cisco VXCManager client update process. Afterthe package process is successful using this file, the client will load the INI file, and launch the Firefox browserwith cisco.com as the home page.

Example:CONNECT=BROWSER \Description="Cisco Home Page" \URL=http://www.cisco.com \Resolution=FullScreen \Mode=Normal \autoconnect=yes

XenDesktop INI configuration exampleTo create XenDesktop server connections, use the Mozilla Firefox Connect options to specify the URL of theXenDesktop server to which users must connect. When the server URL is specified in the INI configuration,Firefox opens to this URL and the user can enter their credentials to initiate the connection to the HVD.

Example:CONNECT=BROWSER \Description="Windows Desktop" \URL=http://xd.company.com \Reconnect=yes \ReconnectSeconds=5 \AutoConnect=yes \mode=kiosk

In the above example, replace xd.company.com with the URL of your XenDesktop server.Caution

With the optional Autoconnect=yes parameter specified in the preceding example, the browser connects tothe specified URLwhen the client boots up. In addition, the optional Reconnect=yes and ReconnectSeconds=5parameters specify to reconnect a disconnected connection after 5 seconds. Finally, the optional mode=kioskparameter specifies to operate in kiosk mode, in which Firefox operates in full-screen mode with no accessto the address bar.

XenApp INI configuration exampleThe following is an example configuration for a Citrix XenApp connection.


Cisco VXC 6215 Firmware Release 9.0 setupFirefox browser configuration example

The Cisco VXC 6215 supports the ICAConnect Options only with XenApp connections. The ICAConnectOptions are not supported with XenDesktop connections.

Note

Example:CONNECT=ICA \BrowserIP=192.168.0.3 \Application="Desktop" \Description="ICA_Desktop " \AutoConnect=yes \Reconnect=yes \Encryption=128 \Colors=16m \Fullscreen=no \Resolution=800x600 \Username=$UN \Password=$PW \Domainname=$DN \Alternate=yes \LowBand=yes

In the above example, replace 192.168.0.3 with the IP address of the ICA browser.Caution

VMware View INI configuration exampleThe following is an example configuration for a VMware View connection.

Example:CONNECT=VMWARE_VIEWCLIENT \Description="VMview" \Host=192.168.0.2 \DomainName=$DN \Username=Administrator \Password=Password \DesktopSize=800x600 \Ping=yes \UseSSL=yes

In the above example, replace 192.168.0.2 with the IP address of your VMware View server.Caution

RDP INI configuration exampleThe following is an example configuration for an RDP connection.

Example:CONNECT=RDP \Host=x.x.x.x \Description="RDP_Server" \AutoConnect=yes \Colors=16m \Username=Administrator \Password=Password \Domainname=$DN \Resolution=800x600 \Reconnect=no \


Cisco VXC 6215 Firmware Release 9.0 setupVMware View INI configuration example

Drives=J=disk \Drives=k=floppy \Sound=off

In the above example, replace x.x.x.x with the IP address of your RDP server.Caution

Enable VNC configuration exampleThe following is an example configuration to enable VNC.

Example:DisableVnc=noVNCAuthTypes=noneVNCPrompt=no

Time settings configuration exampleThe following is an example configuration for time settings.

Example:Timeserver=yourntpserver.comTimeformat="24-hour format"TimeZone="US/Eastern"ManualOverride=1

Display and keyboard settings configuration exampleThe following is an example configuration for display and keyboard settings.

Example:DisplaySettings=MON1 rotate-normal 1440x900DesktopTaskBar=leftAutoHide=yesKeyboard.layouts=us

Create a Cisco VXC Manager package for the wlx.ini fileTo push a wlx.ini file to your clients, you must create a Cisco VXC Manager package, which you can thenschedule for distribution to your devices.

Required folder structure with Cisco VXC Manager

With Firmware Release 9.0, all Cisco VXC Manager package names, filenames (including .rsp and .inifiles), folders, and so on must be lower-case.

Note

With Cisco VXCManager, you must create and register specific packages to push upgrades and configurationsto your clients.


Cisco VXC 6215 Firmware Release 9.0 setupEnable VNC configuration example

To register the package with Cisco VXCManager, youmust create a unique RSP file and, in the same directory,a matching folder of the same name. This matching folder serves as the root directory for the remainingconfiguration files in the package.

For example, assuming <packagename>.rsp is the RSP file, the folder structure required to register the packageis as follows:

Table 4: Package Folder Structure

DescriptionDirectory

The unique RSP file, located in the same directory as the matching rootpackage directory.

~\<packagename>.rsp

The root package directory. It stores the wlx folder and the add-ons folder.It also stores the following files, which are used for imaging and updatingdevices:

• Latest-image.raw

• Latest-image.raw.info

~\<packagename>\

The main INI configuration folder. It stores the following:

• wlx.ini file and $MAC.ini file

• bitmap folder

• certs folder

~\<packagename>\wlx

The folder where you can place custom images you plan to use.~\<packagename>\wlx\bitmap

The folder where you can place the CA certificates that can be imported toa thin client.

Use the Certs and ImportCerts INI parameters in the wlx.ini fileto import the certificates to thin clients.

Note

~\<packagename>\wlx\certs

The folder where you can place the add-ons you want to use. It also storesthe directory file and the *.rpm packages available to be installed on thethin client. The directory file should list all available add-ons. The directoryfile is required in the add-ons folder to guarantee that add-ons are properlylocated.

~\<packagename>\addons

You can create this structure in any location on your Cisco VXC Manager server, as long as all required filesare in the appropriate folders.

If a folder does not contain a required file for the package, the folder can be omitted from the packagedirectory structure. For example, if the package contains no graphics, the \wlx\bitmap folder is not required.

Note

After you register the package, Cisco VXCManager stores the package files in the software repository underc:\inetpub\ftproot\Rapport\<packagename>.


Cisco VXC 6215 Firmware Release 9.0 setupCreate a Cisco VXC Manager package for the wlx.ini file

Do not attempt to modify a registered package located in the Rapport folder. To modify a package, youmust create and register a new package that includes the required changes.

Caution

Use the following procedure to create a Cisco VXC Manager package containing the wlx.ini file for CiscoVXC 6215 client configuration.

Procedure

Step 1 Create a folder to contain the client configurations, for example 6215-configs.Step 2 In the 6215-configs folder, create an RSP file, for example 6215-9.0-datetime-template.rsp, with the following

content (to create the RSP file, enter the required content in a text editor, and then save the file with a .rspextension):

This RSP script is provided as an example; you may need to reconfigure the parameters dependingon your environment. See the Administration Guide for Cisco Virtualization Experience ClientManager for details about configuring RSP files.

Note

[Version]Number=6215-9.0-datetime-template.rspDescription=6215 updateOS=SLXCategory=CiscoUSE_Pxe=NO

[Script]RP "<regroot>"EX "/usr/bin/perl /sbin/dhcp2registry"EX "/usr/sbin/thinclient-config --set-update-mode both"EX "/usr/sbin/thinclient-config --set-force-image-update no"EX "/usr/sbin/thinclient-config --set-preserve-changes yes"EX "sync"EX "(test -e /usr/sbin/imageupgrade && imageupgrade; exit 0)"EX "(! test -e /usr/sbin/imageupgrade && (sleep 10; /sbin/reboot)&)"

where the Number= segment must have the exact same value as the RSP file name.

This example RSP script is applicable only for devices already running Firmware Release 9.0. Fordetailed information to upgrade devices running Release 8.6 or 8.7 to Release 9.0, including therequired RSP script, see Upgrading to Firmware Release 9.0, on page 29.

Caution

Step 3 Create a matching folder to contain the remaining package files, in this example, 6215-9.0-datetime-template.Step 4 In the 6215-9.0-datetime-template folder, add the required package files to create the following folder structure:

C:\6215-configs\6215-9.0-datetime-template.rsp

C:\6215-configs\6215-9.0-datetime-template\latest-image.raw

C:\6215-configs\6215-9.0-datetime-template\latest-image.raw.info

C:\6215-configs\6215-9.0-datetime-template\wlx\wlx.ini

See the end of this procedure for the mandatory INI parameters with Firmware Release 9.0 deviceupdates.

Note

Step 5 To install an add-on, include the addons subfolder under the 6215-9.0-datetime-template folder, and copy theRPM and directory file to this folder:C:\6215-configs\6215-9.0-datetime-template\addons\add-on-name.rpm


Cisco VXC 6215 Firmware Release 9.0 setupCreate a Cisco VXC Manager package for the wlx.ini file

C:\6215-configs\6215-9.0-datetime-template\addons\directory

To install add-ons on devices running Firmware Release 9.0, you do not need to include theInstallAddons parameter in the wlx.ini file.

Note

Step 6 Register the package:a) In the tree pane of the Administrator Console, expand Package Manager.b) In the details pane, right-click Other Packages and choose New > Package.c) Choose Register a Package from a Script file (.RSP) and click Next.d) Click Browse and choose the RSP file you want to register and click Open.e) Click Next to display the Package Wizard summary.f) Click Next to see the Package Registration Progress screen.g) Click Next to create the package.h) After the package is created and registered, click Finish.

Step 7 To upgrade the Cisco VXC 6215, use the Default Device Configuration (DDC) method (see Schedule deviceupdates using Default Device Configuration, on page 23).

Mandatory INI parameters

To push updates to Release 9.0 devices, you must include the following mandatory parameter in the INI file:IniFileSource=cache


If you are deploying using static Cisco VXC Manager IP configuration, also include the following:



InstallAddon parameter not required

Unlike previous releases, to install add-ons on devices running Firmware Release 9.0, you do not need toinclude the InstallAddons parameter in the wlx.ini file. The thin client successfully installs the add-on as longas the /addons folder for the package contains the required add-on files and the accompanying directoryfile.

Schedule device updates using Default Device ConfigurationTo update a group of Cisco VXC 6215 devices, you can assign a Default Device Configuration (DDC). ADDC allows you to set default configurations for a group of devices and ensures that the devices conform toyour configurations. That is, if there is any deviation from your default configurations, Cisco VXC Managerreverts the devices to your specified configurations automatically (Cisco VXC Manager automatically sendsthe Cisco VXC Manager packages in the DDC to the devices according to your schedule and without yourintervention).

See the following sections to configure a DDC:

• Configure Default Device Configuration preferences, on page 24

• First-time Default Device Configuration, on page 24


Cisco VXC 6215 Firmware Release 9.0 setupSchedule device updates using Default Device Configuration

• Existing Default Device Configuration, on page 25

Configure Default Device Configuration preferencesBefore you create a Default Device Configuration, ensure to configure the DDC preferences as follows:

Procedure

Step 1 In the tree pane of the Administrator Console, choose Configuration Manager > Preferences.Step 2 In the details pane, click Device Manager Preferences.Step 3 In the tree pane of the Preferences dialog box, click DDC.Step 4 Under Default Device Configuration, check the Enable Default Device Configuration box.Step 5 Under Time to Schedule DDC Reconciliation, click Upon Checkin.Step 6 In the tree pane of the Preferences dialog box, click Scheduling.Step 7 Under Imaging Option, clickMerlin.Step 8 Click OK.

First-time Default Device ConfigurationPerform this procedure each time you create a new image package that you want to specify as the defaultimage for client upgrades.

Procedure

Step 1 Determine whether a Default Device Configuration already exists:a) In the tree pane of the Administrator Console, expandConfigurationManager and clickDefault Device

Configuration.


Cisco VXC 6215 Firmware Release 9.0 setupConfigure Default Device Configuration preferences

b) If a default configuration appears in the details pane, go to Existing Default Device Configuration, onpage 25. Otherwise, go to the next step.

Step 2 In the tree pane of the Administrator Console, expand Configuration Manager, right-click Default DeviceConfiguration, and chooseNew >Default Device Configuration to open the Default Device ConfigurationWizard.

Step 3 In the Operating System field, choose SUSE Linux.Step 4 In the Media Size field, choose 4000 MB.Step 5 In the Qualifying OS Image field, choose No Image.Step 6 In the Software Packages tab, check the required package for the upgrade to and click Add to add it to the

Selected column. (The packages listed in this tab match the packages that you have registered in the CiscoVXC Manager.)

Step 7 Click Next and under Execute DDC, chooseWhenever a device checks in.Step 8 Click Next and click Finish.Step 9 After a DDC has been configured for the Cisco VXC 6215, the clients are updated to the selected package

configuration automatically: either at their regularly scheduled checkin time or according to the update timeset in the Device Manager DDC preferences in Configuration Manager. You can also right-click the CiscoVXC 6215 you want to upgrade, and choose Reboot to perform a manual upgrade.

Step 10 After the devices are upgraded, click the top Refresh icon in Device Manager to see the changed softwarerevision.

To verify that Cisco VXC Manager has successfully pushed a package to a device, click Device Manager,and choose a target device. In the bottom right hand corner, of the details pane, click the plus icon (+) tomaximize the properties for the device, then click the Deployed Package tab to show all packages that areon the device.

Existing Default Device ConfigurationPerform this procedure when you want to specify an existing image package as the default image for clientupgrades.

Procedure

Step 1 In the tree pane of the Administrator Console, expand Configuration Manager, and click Default DeviceConfiguration.

Step 2 Right click SUSE Linux, and choose Properties.Step 3 In the Software Packages field, choose the package to upgrade to.Step 4 Click Finish.

After a DDC has been configured for the Cisco VXC 6215, the clients are updated to the selected packageconfiguration automatically: either at their regularly scheduled checkin time or according to the update timeset in the Device Manager DDC preferences in Configuration Manager. You can also right-click the CiscoVXC 6215 you want to upgrade, and choose Reboot to perform a manual upgrade.


Cisco VXC 6215 Firmware Release 9.0 setupExisting Default Device Configuration

Cisco VXC 6215 deployment with a Cisco Virtual Office RouterFor proper operation of the Cisco VXC 6215 behind a Cisco Virtual Office Router, you must configure thethin client with the Cisco VXC Manager IP address. To do so, you can first push the Cisco VXC Manager IPaddress to the thin client using INI settings on your local network, and then provide the pre-configured thinclient to the remote user. Alternatively, the remote user can manually enter the Cisco VXC Manager serverIP address using the following procedure.

This procedure is required only for the initial connection to the network from behind a Cisco Virtual Officerouter. The procedure assumes a factory new Cisco VXC 6215. Subsequent connections do not requirethese steps. The procedure also assumes that you have set up the thin client environment, including theconfiguration of connection parameters (Connect options) in the INI file to allow connection to avirtualization server.

Note

Procedure

Step 1 Connect the Cisco VXC 6215 to the Cisco Virtual Office router.Step 2 Power up the Cisco VXC 6215.Step 3 From the desktop, click Computer >More Applications > Firefox to launch the Firefox web browser.Step 4 If the Cisco Virtual Office router prompts you for a username and password, enter the required credentials.

Otherwise, if Firefox opens directly to the home page, proceed to the next step.Step 5 Click Computer >More Applications > VXC-M.Step 6 In the VXC-M Server field, enter the IP address of the Cisco VXC Manager.Step 7 In the Non-secure Port (HTTP) field, enter 80 (or a custom port for your Cisco VXC Manager setup, as

required).Step 8 In the Secure Port (HTTPS) field, enter 443 (or a custom port for your Cisco VXCManager setup, as required).Step 9 Click OK, and reboot the thin client.

At startup, the device appears in the Cisco VXC Manager as a new device with a green status, and theadministrator can configure it.

After the reboot the thin client downloads the wlx.ini file (the download can last a few minutes).

Step 10 After the download is complete, a shortcut icon appears on the desktop providing a connection to the hosteddesktop. Double-click the icon to connect to the hosted desktop.

If required, the administrator can push a firmware upgrade to the thinclient.

Note

Monitor resolutionFor most monitors, the thin client automatically obtains the correct resolution to display from the monitoritself.


Cisco VXC 6215 Firmware Release 9.0 setupCisco VXC 6215 deployment with a Cisco Virtual Office Router

For monitors that do not fully support the VESA standards (generally older models), the thin client may notbe able to display the monitor resolution correctly, resulting in a black screen. The workaround for this issueis to push an INI file containing the correct display settings to the thin client using Cisco VXC Manager.

The following is an example configuration using the DisplaySettings INI parameter to specify the resolutionfor monitor 1 to be 1024 x 768, with no rotation:DisplaySettings=MON1 rotate-normal 1024x768For more information about configuring this INI parameter, see INI Files Reference Guide for CiscoVirtualization Experience Client 6215.

SSH connectionsThe Cisco VXC 6215 can support remote connections to the thin client using SSH, however this functionalityis disabled by default to provide increased security.

To enable the SSH functionality on the Cisco VXC 6215 devices using Cisco VXCManager, in the DeviceManager, right-click the device and choose Execute Command. In the Execute Command dialog box,enter:

/etc/init.d/sshd start &

The default OpenSSH idle timeout is 30 minutes and the maximum timeout is 60 minutes. (These defaultSSH idle timeout values cannot be modified.)

Note


Cisco VXC 6215 Firmware Release 9.0 setupSSH connections


Cisco VXC 6215 Firmware Release 9.0 setupSSH connections

C H A P T E R 3Upgrading to Firmware Release 9.0

This chapter describes how to upgrade the Cisco VXC 6215 to Firmware Release 9.0.

The RSP and INI files that you use for upgrades to Firmware Release 9.0 are incompatible with thoseused in previous releases and are also incompatible with those used to update devices already runningFirmware Release 9.0 (as described in Cisco VXC 6215 Firmware Release 9.0 setup, on page 7). Whenyou perform the upgrade, be sure to use the correct RSP and INI files required for the upgrade, otherwiseerrors will occur.

Caution

• Cisco Virtualization Experience Media Engine, page 29

• Update the Cisco VXC 6215 firmware to Release 9.0, page 30

Cisco Virtualization Experience Media EngineTo support Unified Communications on the Cisco VXC 6215, you must purchase and install the CiscoVirtualization Experience Media Engine (VXME). Cisco VXME provides Unified Communicationsfunctionality on the Cisco VXC 6215 with Cisco Jabber.

Cisco Jabber integrates audio, video, presence, instant messaging (IM), web conferencing, and desktop sharinginto a single client. With Cisco VXME, users in a virtual environment can use Cisco Jabber from their thinclients.

WhenCisco Jabber is running in a virtual environment using CiscoVXME, desktop sharing is not supported.Note

You can install the Cisco VXME add-on on the Cisco VXC 6215 as part of the upgrade to Firmware Release9.0. For detailed deployment information about Cisco VXME, see the Deployment Guide for CiscoVirtualization Experience Media Engine for Cisco Virtualization Experience Client 6215.


Disabled power management settings with Cisco VXMEBy default, the Cisco VXC 6215 firmware supports a power management setting (EnergyWise) whereby theclients enter the sleep mode after a specified period of time. However, when the Cisco VXME add-on isenabled, this power management setting is disabled, and the clients do not enter the sleep mode.

Update the Cisco VXC 6215 firmware to Release 9.0Use the following procedure to update the firmware image on a Cisco VXC 6215 from Firmware Release 8.6or 8.7 to Firmware Release 9.0. You can also use this procedure to install the Cisco VXME add-on duringthe Firmware Release 9.0 upgrade.

Caution • To interoperate with Cisco VXC 6215 Firmware Release 9.0, you must run Cisco VXC Manager4.9.1. If you are running a previous release of Cisco VXCManager, you can still discover andmanageCisco VXC 6215 devices running Firmware Release 9.0, but real-time commands are not supported.

Cisco recommends that you first upgrade your Cisco VXC Manager management server to release4.9.1, and then upgrade your Cisco VXC 6215 devices to Firmware Release 9.0.

• To upgrade to Firmware Release 9.0, you must first ensure HTTPS is disabled on Cisco VXCManager. The upgrade process supports HTTP only. After you perform the update to FirmwareRelease 9.0, you can then re-enable HTTPS.

• Before you begin an upgrade, see Best practices for Cisco VXC 6215management using Cisco VXCManager, on page 8.

Procedure

Step 1 If you are running an earlier version of Cisco VXC Manager, upgrade to Cisco VXC Manager 4.9.1 (seeInstallation Guide for Cisco Virtualization Experience Client Manager).

Step 2 Set the Cisco VXCManager to use HTTP for server communications (using a custom installation) during theCisco VXC 6215 upgrade process.

Step 3 Download the Cisco VXC 6215 firmware from the Cisco Software Download page:

1 Go to the following URL:

http://www.cisco.com/cisco/software/navigator.html

2 Choose Products > Voice and Unified Communications > IP Telephony > Virtualized Endpoints.

3 ChooseCisco Virtualization Experience Client 6000 Series >Cisco Virtualization Experience Client6215.

4 Choose the desired release version from the list.

5 Click the Download or Add to cart button and follow the prompts.


Upgrading to Firmware Release 9.0Disabled power management settings with Cisco VXME

http://www.cisco.com/cisco/software/navigator.html

Step 4 On the server where you have Cisco VXC Manager installed, extract the zipped OS image files to a localfolder.

Step 5 Create a folder to contain the upgrade package, for example 6215-9.0-platform-files.Step 6 In the 6215-9.0-platform-files folder, create an RSP file for the upgrade, for example

6215-9.0-datetime-template.rsp, with the following content (to create the RSP file, enter the required contentin a text editor, and then save the file with a .rsp extension):

This RSP script is provided as an example; you may need to reconfigure the parameters dependingon your environment. See the Administration Guide for Cisco Virtualization Experience ClientManager for details about configuring RSP files.

Note

[Version]Number=6215-9.0-datetime-templateDescription=90-upgradeOS=SLXCategory=CiscoUSE_Pxe=NO

[Script]RP "<regroot>"EX "/usr/bin/perl /sbin/dhcp2registry"EX "/usr/sbin/thinclient-config --set-update-mode both"EX "/usr/sbin/thinclient-config --set-force-image-update no"EX "/usr/sbin/thinclient-config --set-preserve-changes yes"EX "sync"EX "sleep 2"RB

where the Number= segment must have the exact same value as the RSP file name.

This example RSP script is applicable only if you are upgrading devices from a previous releaseto Firmware Release 9.0. For information about pushing updates to devices that are already runningFirmware Release 9.0, including the required RSP script, see Cisco VXC 6215 Firmware Release9.0 setup, on page 7.

Caution

Step 7 Create a matching folder to contain the remaining package files, in this example, 6215-9.0-datetime-template.Step 8 In the 6215-9.0-datetime-template folder, add the required package files to create the following folder structure:

C:\6215-9.0-platform-files\6215-9.0-datetime-template.rsp

C:\6215-9.0-platform-files\6215-9.0-datetime-template\latest-image.raw

C:\6215-9.0-platform-files\6215-9.0-datetime-template\latest-image.raw.info

C:\6215-9.0-platform-files\6215-9.0-datetime-template\wlx\wlx.ini

See the end of this procedure for the mandatory INI parameters for upgrades to Firmware Release9.0. Also, if you have existing INI configurations on your clients, you must copy and paste theseparameters into the wlx.ini that you push with the upgrade, otherwise the clients will lose thepre-existing configurations.

Note

Step 9 To install the Cisco VXME add-on, include the addons subfolder under the 6215-9.0-datetime-template folder,and copy the VXME RPM and directory file to this folder:C:\6215-9.0-platform-files\6215-9.0-datetime-template\addons\vxme.rpm

C:\6215-9.0-platform-files\6215-9.0-datetime-template\addons\directory

Step 10 To install the Cisco VXME add-on, you must also include the InstallAddons=vxme parameter in the INI file.Step 11 Register the image package:

a) In the tree pane of the Administrator Console, expand Package Manager.


Upgrading to Firmware Release 9.0Update the Cisco VXC 6215 firmware to Release 9.0

b) In the details pane, right-click Other Packages and choose New > Package.c) Choose Register a Package from a Script file (.RSP) and click Next.d) Click Browse and choose the RSP file that you want to register and click Open.e) Click Next to display the Package Wizard summary.f) Click Next to see the Package Registration Progress screen.g) Click Next to create the package.h) After the package is created and registered, click Finish.

Step 12 To upgrade the Cisco VXC 6215, use Default Device Configuration (Schedule device updates using DefaultDevice Configuration, on page 23).

Mandatory INI parameters

The following shows the mandatory parameters that must be included in the INI file to upgrade from Release8.6 or 8.7 to Release 9.0.IniFileSource=cachePrivilege=HighBootorder=P;HAutopower=yes

Add-on INI parameters

If you are deploying the Cisco VXME add-on, be sure that the following InstallAddons parameter is includedin the INI file:InstallAddons=vxme

If you include additional add-ons with the Cisco VXME add-on in the upgrade package, make sure that theCisco VXME add-on is listed last in the wlx.ini file.


If you are using static configuration of the Cisco VXC Manager IP for device discovery, also include thefollowing in the INI file (using the RapportServer parameter to specify the Cisco VXC Manager IP address):




Upgrading to Firmware Release 9.0Update the Cisco VXC 6215 firmware to Release 9.0

C H A P T E R 4Cisco AnyConnect Secure Mobility Client

To provide secure VPN connections, the Cisco VXC 6215 supports the Cisco AnyConnect Secure Mobilityclient. The Cisco AnyConnect Secure Mobility client provides remote users with secure VPN connectionsto the Cisco 5500 Series Adaptive Security Appliance (ASA). On the Cisco VXC 6215, the Cisco AnyConnectSecureMobility client supports Cisco ASA version 8.0(4) or later and the Adaptive Security DeviceManager(ASDM) 6.4(1) or later.

• Feature support, page 33

• Setup, page 34

Feature supportThe following table shows the AnyConnect features supported on the Cisco VXC 6215.

Table 5: AnyConnect Feature Support

Supported on Cisco VXC 6215Feature

YesDatagramTransport Layer Security (DTLS) with SSLaccess to VPN

NoIPSec/IKEv2 support

YesCompression -Increases the communicationsperformance between the security appliance and theclient

YesFallback from DTLS to TLS if DTLS fails

NoCertificate-only authentication

NoMachine certificate authentication for standalonemode

NoRSA SecurID integration

NoSmartcard support


Supported on Cisco VXC 6215Feature

NoDownload certificate from ASA via Get Certificate

NoSimple Certificate Enrollment Protocol (SCEP) toprovision and renew a certificate used for clientauthentication

Yes, LegacyGUI interface

YesMinimize on connect

NoIPv6 VPN access-Allows access to IPv6 resourcesover a public IPv4 connection

NoLocal LAN access

NoLocal printer access via client firewall rules

NoTrusted network detection (TND)

NoCaptive portal (hotspot) detection

NoStart Before Logon (SBL)

YesAutoconnect on start

YesResume session after loss of connectivity

N/A (update using Cisco VXC Manager only)Auto update AnyConnect

YesAuto update AnyConnect profile

N/A (integrated with Cisco VXC troubleshootingtool)

Diagnostic AnyConnect Reporting Tool (DART)

YesFederal Information Processing Standard (FIPS)security

NoBrowser-based (clientless) VPN access

NoEndpoint assessment (Posture)

NoEndpoint remediation

NoWeb security-Enforces acceptable use policies toprotect endpoints from websites found to be unsafe

NoNetwork Access Manager (NAM) - L2

SetupTo enable Cisco AnyConnect connections, you must setup Cisco AnyConnect profiles on the Cisco ASA andspecify the required VPN connection parameters on the Cisco VXC 6215 using Custom connection optionsin the INI file. After you setup the required profiles and push the INI parameters to the client, users can theninitiate secure connections.


Cisco AnyConnect Secure Mobility ClientSetup

Before you provide the devices to your remote employees, you must first push the required configuration tothe devices on your local network first. After you have upgraded the devices with the required parameterslocally, you can then provide the preconfigured devices to remote users to operate behind the Cisco AnyConnectVPN.

Profile setup on Cisco ASAOn the Cisco ASA, AnyConnect profiles provide basic information about connection setup, and users cannotmanage or modify them. The profile is an XML file that lets you identify the secure gateway (Cisco ASA)hosts that you want to make accessible. In addition, the profile specifies additional connection attributes andconstraints for a user. Usually, a user has a single profile file. This profile contains all the hosts needed by auser, and additional settings as needed.

By creating and assigning different profiles to group policies configured on the Cisco ASA, you can differentiateaccess to Cisco ASA features. The Cisco ASA automatically pushes the profile assigned to the user uponconnection setup.

You can configure a profile using the AnyConnect profile editor, a GUI-based configuration tool launchedfrom the Adaptive Security Device Manager (ASDM). The AnyConnect software package, version 3.0 andlater, includes the editor, which activates when you load the AnyConnect package on the Cisco ASA as anSSL VPN client image.

For detailed configuration information, see Cisco AnyConnect Secure Mobility Client Administrator Guide,Release 3.0.

Cisco AnyConnect setup on Cisco VXC 6215 using INI parameters

Custom connection configuration

To setup a Cisco AnyConnect connection, you must configure the Custom Connect parameter in your INIfile. The Custom Connect parameter includes a Command option which you can configure to enable CiscoAnyConnect at startup and to include a Cisco AnyConnect icon on the desktop.CONNECT=Custom \Description="ASA Connection" \AutoConnect=Yes \Reconnect=Yes \ReconnectSeconds=100 \Command=/opt/cisco/anyconnect/bin/vpnui

Also, populate the /etc/anyconnect/.anyconnect_global file on the Cisco VXC 6215 with the ASA addresswhile the thin client is still connected to the corporate network.

In the INI file, also include the INIFileSource=cache parameter in the INI file to ensure that devices usethe local cached version of the INI file if they cannot access the INI files from Cisco VXCManager. Thisis particularly important for devices running the Cisco AnyConnect VPN, so that they have a configurationto reference at bootup before connecting to the network over VPN.

Note


Cisco AnyConnect Secure Mobility ClientProfile setup on Cisco ASA

Table 6: Custom Connect Options

DescriptionParameter

Default is no.

Yes/no option to start a connection automatically at sign-on.

AutoConnect={no, yes}

Mandatory Option

Specifies a command or application to be executed from theclient. For Cisco AnyConnect:Command=/opt/cisco/anyconnect/bin/vpnui

Command=<command or application tobe executed from the client>

Mandatory Option

Connection description. Provides a connection name for theDesktop icon and the Connection Manager.

The text must be enclosed in quotation marks if itcontains spaces or punctuation characters. Thesecharacters are not allowed: & ‘ “ $ ? ! | ; ( ) [ ] { } \

Caution

Description=<string description>

Default is no.

Yes/no option to automatically reconnect to an application serverafter a disconnection.

Reconnect={no, yes}

Default is 30.

Specifies the amount of time in seconds (default is 30) to waitbefore automatic reconnection to an application server after adisconnection. Requires Reconnect=yes or 1.

ReconnectSeconds=<value in seconds>

Upgrades over VPN

If you upgrade devices over VPN, be aware of the following considerations:

• Be aware of the configured Cisco VXC Manager address discovery mechanism (if DHCP, be sureAnyConnect is propagating these tags across the VPN).

• An image upgrade over VPN can take few hours (depending on the speed of the link). If the user is notconnected to the VPN for enough time, you will lnot be able to start the upgrade process, and the downloadwill start from scratch every time.


Cisco AnyConnect Secure Mobility ClientCisco AnyConnect setup on Cisco VXC 6215 using INI parameters

C H A P T E R 5USB redirection

This chapter provides guidelines for setting up USB redirection on the Cisco VXC 6215 devices.

• Recognizing USB cameras using HDX RealTime Webcam with Citrix, page 37

• USB camera redirection not supported with Vmware View, page 37

• USB redirection not supported for Logitech UC Keyboard with Cisco VXME, page 38

Recognizing USB cameras using HDX RealTime Webcam withCitrix

To allow applications to use USB cameras within the XenDesktop session, the Cisco VXC 6215 supports theuse of HDX RealTime Webcam video compression. HDX RealTime Webcam is supported with the CiscoVXC 6215 base firmware and with the Cisco VXME add-on.

With HDX RealTime Webcam, the Cisco VXC 6215 captures the video data, compresses it, and then sendsthe video data to the XenDesktop session.

By default, the Cisco VXC 6215 is configured to support HDX RealTime Webcam. To use HDX RealtimeWebcam with XenDesktop 5.0 and above, you must configure the XenDesktop policies to enable HDXRealTime. (See XenDesktop documentation for details.)

Note • On the base firmware without the VXME, you can alternatively enable HDX Plug-and-Play forconnectivity of USB devices, but it does not support webcams.

• HDXPlug-n-Play for cameras is not supported on the Cisco VXC 6215 with the Cisco VXME add-on(Citrix recommends using HDX Webcam for camera interactions).

USB camera redirection not supported with Vmware ViewUSB camera redirection is not supported with VMware View.


USB redirection not supported for Logitech UC Keyboard withCisco VXME

In all cases where it is available, Cisco strongly recommends that you enable Citrix HDX rather than use USBredirection. If you do enable USB redirection when running Cisco VXME, you must deny the Logitech UCKeyboard K725-C from USB redirection, otherwise the keyboard may not function properly.

To deny the Logitech UC Keyboard K725-C from USB redirection, include the following line in the INI file:ICADenyUSB=vid=046d pid=b320, vid=046d pid=b321


USB redirectionUSB redirection not supported for Logitech UC Keyboard with Cisco VXME

C H A P T E R 6Desktop basics

This chapter provides information to help you get started using your thin client. It describes basic thin clientfunctions and provides instructions for using features available on the desktop.

Cisco thin clients are designed to be centrally managed and configured using Cisco VXC Manager andINI files. Use Cisco VXC Manager to automatically push updates and any desired configuration to allsupported thin clients in your environment. For more information, see Cisco VXC 6215 Firmware Release9.0 setup, on page 7.

Tip

• Logging in, page 39

• Using your desktop, page 40

• Desktop keyboard shortcuts, page 41

• Connecting to a monitor, page 42

• Shutting down, restarting, and suspending, page 42

• Installation update warning, page 43

• Viewing system information, page 43

Logging inThe options and menus that are available depend on access levels and on the add-ons that are enabled on thethin client. By default, the Cisco VXC 6215 automatically logs users into the local desktop after they powerup the thin client.

After the thin client boots up, there is a short delay before it initiates the autologin process. Afterapproximately 10 to 15 seconds, the thin client automatically logs the user into the thin client usingthinuser/thinuser as the default username and password.

Note


After the thin client is powered on, the users can use the hosted desktop connection or client icon to log intothe hosted desktop. To connect to the hosted desktop, double-click the icon and enter the required logincredentials.

Depending on the connection settings you specify, you can provide a hosted desktop client icon (for examplefor VMware View connections) or a Firefox icon (for example, for XenDesktop connections) on the desktopthat users can click to launch their hosted desktop connection. Alternatively, users can launch their hosteddesktop connection by selecting the desired connection in the ConnectionManager (see ConnectionManager,on page 46).

Using your desktopThe desktop provides various applications and tools for use.

Figure 8: Desktop

Use the following guidelines:

• Computer button—Displays the Computer menu containing frequently used programs and commonsystem areas.

◦Connection Manager—Opens the Connection Manager. Use the Connection Manager to viewconnections on the thin client.

◦More Applications—Opens the Application Browser. Use the Application Browser to use andmanage additional features on the thin client (see Accessing additional features with the ApplicationBrowser, on page 45).

◦Logout—Opens the Log Out dialog box (click Log Out to end your session but continue to runthe thin client).

◦Shutdown—Opens the Shutdown dialog box (where you can shut down your thin client, restartyour thin client, or put your thin client in Standby mode. See Shutting down, restarting, andsuspending, on page 42).


Desktop basicsUsing your desktop

If you open the Shutdown dialog box and do not choose a shutdown option, the systemautomatically shuts down after 60 seconds.

Note

Desktop keyboard shortcutsDepending on the type of application window you are using (full screen, standard, or seamless), you can useshortcut keys to manage windows.

You can disable some of these shortcuts by including the INI parameters listed below in your INI file. Bydefault, every shortcut listed is enabled. (Possible values for each parameter are yes or no.)

Table 7: Desktop Keyboard Shortcuts

INI parameter to disable shortcutActionPress

Cisco.DisableKeyBinding.Close=yesClose windowAlt+F4

Cisco.DisableKeyBinding.Close=yesClose browser windowCtrl+F4

Not applicableMaximize windowAlt+F10

Cisco.DisableKeyBinding.Minimize=YesMinimize windowAlt+F9

Cisco.DisableKeyBinding.ShowDesktop=yesMinimize or maximize all windowsAlt+Ctrl+DownArrow

Cisco.DisableKeyBinding.MouseButtonModifier=yesMouse modifier (used by default as amouse modifier)

Alt

Not applicableMove focus to next windowAlt+Esc

Not applicableMove focus to previous windowAlt+Shift+Esc

Not applicableMove window with arrow keysAlt+F7 and press an arrowkey

Not applicableResize the windowAlt+F8 and press an arrowkey

Not applicableRestore maximized window to previoussize

Alt+F5

Not applicableSwitch keyboard focus back to thinclient (used by Citrix Linux receiver tobring keyboard focus back to thin clientlocally)

Ctrl+F2

Cisco.DisableKeyBinding.SwitchWindows=yesSwitch windows using a dialog boxAlt+DownArrow

Not applicableSwitch panel focusAlt+Ctrl+Shift+DownArrow

Cisco.DisableKeyBinding.RunCommand1=yesShow Logout optionAlt+Ctrl+Delete

Cisco.DisableKeyBinding.PanelMainMenu=yesShow Computer Menu windowAlt+F1


Desktop basicsDesktop keyboard shortcuts

INI parameter to disable shortcutActionPress

Cisco.DisableKeyBinding.PanelMainMenu=yesShow Windows start menuCtrl+Esc

Cisco.DisableKeyBinding.PanelMainMenuList=yesShow main panel list when keyboardfocus is shifted to the thin client

Windows Key

Cisco.DisableKeyBinding.WindowMenu=yesShow window menuAlt+Space (you can alsoright-click the window titlebar or border, or click thewindow icon)

The shortcut keys Alt+DownArrow (allows you to switch windows using a dialog box) andAlt+Ctrl+DownArrow (minimizes or maximizes all windows) are useful for navigating multiple remotesessions without having to log out.

Tip

Connecting to a monitorMonitor connections can be made using the DVI (digital) monitor port and the proper monitor cables/splitters.For VGA (analog) monitor connections, you must use the included DVI-to-VGA adapter. For information onconfiguring display settings, see Display Preferences, on page 52.

If you connect one monitor to the DVI port and a second monitor to the Display Port, the Display Portmonitor is always the primary monitor.

However, if you use a DVI to DVI/VGA splitter to connect a DVI monitor and a VGA monitor to theDVI port, the VGA monitor is the primary monitor.

Tip

Shutting down, restarting, and suspendingWhen you are finished using your thin client, you can click Computer > Shutdown and choose:

• Shutdown—Shuts down and turns off your thin client.

• Restart—Shuts down and restarts your thin client.

• Suspend—Places the thin client in Standby mode to preserve power. To exit Standby mode, click themouse.


Desktop basicsConnecting to a monitor

If the ReadyMode feature is enabled and you shut down the thin client, the session ends, the power buttonLED is put in a state of OFF, and the thin client is placed in Standby mode to preserve power. When youpress the power button, the thin client exits Standby mode and immediately prompts the user with thelogin dialog box. For more information on ReadyMode, see Cisco Virtualization Experience Client 6215INI Files Reference Guide.

Tip

Installation update warningWhen the administrator pushes a new update for the thin client, the thin client must reboot for the update tocomplete. If the thin client is running at the time the update is deployed, a window appears asking the userwhether they want to upgrade the image immediately, or wait for 5 minutes.

Figure 9: Installation Update Warning

Viewing system informationClickMore Applications in the Computer menu (see Using your desktop, on page 40) to open the ApplicationBrowser. Click the System Information icon to open the System Information dialog box. Use this dialog boxto view Identity, Network, Packages, System Log, and Copyright information:

• Identity tab—Displays identity information such as Website, Current User, Terminal Name, ProductName, Platform, Build, SLETC, OS Version, Uptime, Processor, Processor Speed, Total Memory, FreeMemory, Flash Size, Serial Number, and BIOS version.

• Network tab—Displays network information such as Network Device, MAC Address, Network Speed,MTU, IP Address, IPv6 Address, Netmask, Gateway, Domain, Primary DNS, Secondary DNS, DHCPServer, Lease, and Elapsed.

• Packages tab—Displays the Package information, including package names, versions, and sizes that areinstalled on the thin client.

• System Log tab—Displays the System Log information, including various messages generated duringthe operation of the thin client.


Desktop basicsInstallation update warning

• Copyright tab—Displays the software copyright and patent notices.

Figure 10: System Information


Desktop basicsViewing system information

C H A P T E R 7Accessing additional features with theApplication Browser

This chapter provides detailed information about using the Application Browser to access the applications,audio and video, and system features that are installed on the thin client.

Although manual configuration of some options is possible on the Cisco VXC 6215, Cisco highlyrecommends that you use Cisco VXCManager to automatically push updates and any desired configurationto all thin clients in your environment. For more information, see Cisco VXC 6215 Firmware Release 9.0setup, on page 7.

Tip

ClickMore Applications in the Computer menu (see Using your desktop, on page 40) to open theApplication Browser.

Figure 11: Application Browser

This chapter includes information on the following:

• Cisco AnyConnect Secure Mobility Client, page 46

• Connection Manager, page 46


• Diagnostics, page 47

• Diagnostics Log Viewer, page 48

• VMware View client, page 49

• Configure Cisco VXC Manager Agent, page 49

• Volume Control, page 51

• Firefox Web Browser, page 52

• Cheese, page 52

• Display Preferences, page 52

• System Information, page 53

• Take Screenshot, page 53

• VNC Server, page 54

Cisco AnyConnect Secure Mobility ClientTo provide secure VPN connections, the Cisco VXC 6215 supports the Cisco AnyConnect Secure Mobilityclient. The Cisco AnyConnect Secure Mobility client provides remote users with secure VPN connections tothe Cisco 5500 Series Adaptive Security Appliance (ASA).

For more information, see Cisco AnyConnect Secure Mobility Client, on page 33

Connect to a VPNUse the following procedure to connect to a VPN using the Cisco AnyConnect client.

Procedure

Step 1 If CiscoAnyConnect is not already started, click theAnyConnect icon from the desktop or from the ApplicationBrowser.

Step 2 In the Connect To field, choose the desired VPN to connect to.Step 3 Click Connect.Step 4 Enter your user name and password, and then click Connect.

Connection ManagerClick the Connection Manager icon in the Application Browser to open the Connection Manager. Use theConnection Manager to view and connect to configured hosted desktop connections from your Desktop.


Accessing additional features with the Application BrowserCisco AnyConnect Secure Mobility Client

DiagnosticsClick Diagnostics in the Application Browser to open the Diagnostics dialog box. Use this dialog box tochoose and use one of the following diagnostic tools:

• Ping—Enter or choose a destination from the Destination list and click Ping.

• Trace Route—Enter or choose a destination from the Destination list and click Trace Route (diagnosticinformation appears on the Trace Route tab).

• Temporary Settings—View the temporary settings of the thin client.

• Permanent Settings—View the permanent settings of the thin client.

• wlx.ini/wnos.ini—View the wlx.ini or wnos.ini file as copied to the thin client.

The Cisco VXC 6215 supports wlx.ini files, but does not support wnos.ini files. For more information,see the INI Files Reference Guide for Cisco Virtualization Experience Client 6215.

Note

• user.ini—View the user.ini file as copied to the thin client.

The Cisco VXC 6215 does not support the user.ini file.Note

Figure 12: Diagnostics Dialog Box


Accessing additional features with the Application BrowserDiagnostics

The title of the Diagnostics dialog box contains "(as superuser)" even when you are logged into the clientusing thinuser credentials.

Note

Diagnostics Log ViewerClick Diagnostics Log Viewer in the Application Browser to open the Diagnostics Log Viewer dialog box.The Diagnostics Log Viewer allows you to display and export log files to a USB key or to a remote server.

Figure 13: Diagnostics Log Viewer

The title of the Diagnostics Log Viewer dialog box contains "(as superuser)" even when you are loggedinto the client using thinuser credentials.

Note

To highlight a log file, click the name of the log file in the Log Name list. The Diagnostics Log Viewer thendisplays messages related to the log file.

To include debug messages in the displayed list, check theMore Logs check box, click OK, and then restartthe device for the changes to take effect. When you highlight the log file after the reset, the Diagnostics LogViewer displays the debug messages.

You can export the log files to a connected USB Key or to a Remote Server, as follows:

• USB Key: Attach a USB key to the client, open the Diagnostics Log Viewer, and check the check boxesfor the logs you want in the Log Name list. In the Export To field, click USB Key, and then click Nextto use the Export Logs dialog box.

• Remote Server: Check the check boxes for the logs you want in the Log Name list. In the Export Tofield, click Remote Server and then click Next to use the Export Logs dialog box.


Accessing additional features with the Application BrowserDiagnostics Log Viewer

Note that you can export the files to a default server (server from the default registry) by clicking Use serverfrom default registry, or to any server by clicking Use the following server and specifying the server pathin the URL field.

Figure 14: Export Logs to Remote Server Dialog Box

Permanent and temporary registry logs are exported by default.Note

VMware View clientClick the VMware View client icon in the Application Browser to open the VMware View client. This iconprovides an alternative to the desktop icon and Connection Manager to launch the VMware View client.

RDP is not supported if a user launches the VMware View client using this icon.Note

Configure Cisco VXC Manager AgentClick Cisco VXC-M in the Application Browser to open the Cisco VXC-M Agent Configuration dialog box.You can use this dialog box to specify which method the client uses to discover Cisco VXC Manager. Bydefault, all discovery methods listed are enabled. You can also use this dialog box to manually specify theCisco VXC Manager server IP address.

In addition, you can specify the number of Cisco VXC Manager check-ins that the device can miss beforethe device reenables the specified discovery methods. (The default is 15 check-ins; 0 specifies to not reenablediscovery if VXC-M checkins fail.)


Accessing additional features with the Application BrowserVMware View client

After the device is discovered, the discovery preferences specified on Cisco VXC Manager (underConfiguration Manager > Preferences > Discovery) take precedence over the settings specified on theclient (either through the GUI or using the MgmtDiscoveryMethod INI parameter).

After you configure the Cisco VXC Manager Agent properties, Cisco recommends that you reboot thethin client.

Tip

Figure 15: VXC Manager Agent Configuration Dialog Box

To configure the Cisco VXC Manager server IP address, perform the following procedure:


Accessing additional features with the Application BrowserConfigure Cisco VXC Manager Agent

Procedure

Step 1 Enter the Cisco VXC Manager Server IP address.Step 2 Enter the Non-secure Port (HTTP) for client-to-server communication (default is 80).Step 3 Enter the Secure Port (HTTPS) for client-to-server communication (default is 443).Step 4 Select the desired Discovery Settings. For more information about Cisco VXC Manager, see Administration

Guide for Cisco VXC Manager.Step 5 Click OK.

After you reboot the thin client, the thin client performs a checkin with the Cisco VXC Manager.

Volume ControlClick Volume Control in the Application Browser to open the Volume Control dialog box. Use this dialogbox to set volume preferences for Playback (system sounds), Recording (application recording sounds), OutputDevices (left and right sounds), Input Devices (left and right sounds), and Configuration (profile). You canuse the Show list on the Playback, Recording, Output Devices, and Input Devices tabs to choose which itemsyou want shown.

Figure 16: Volume Control Dialog Box


Accessing additional features with the Application BrowserVolume Control

For these settings to take effect, sound must be supported and enabled on the server used for ICAconnections, RDP connections, orMPlayer. Sound requires significant bandwidth that may not be availableon some WAN and dial-up connections.

Tip

Firefox Web BrowserClick the Firefox icon in the Application Browser to open a Mozilla Firefox web browser session.

CheeseClick the Cheese icon in the Application Browser to launch the Cheese webcam application. Use Cheese tocapture photos and video using the webcam and apply effects to the captured images and video.

Display PreferencesClick Display in the Application Browser to open the Display Preferences dialog box. Use this dialog box toset the monitor display settings (Primary Display Output, Resolution, Refresh Rate, and Rotation). For mostmonitors, the thin client automatically obtains the correct resolution from the monitor.

When multiple monitors are identified, the screens are extended by default.

To set up mirrored monitors, check theMirror Screens check box.

Note


Accessing additional features with the Application BrowserFirefox Web Browser

If you manually set the monitor settings using the Display Preferences dialog box, the settings are lost at thenext reboot. To retain the monitor settings after a reboot, set the display settings using the INI file.

Figure 17: Display Preferences Dialog Box

System InformationClick System Information in the Application Browser to open the System Information dialog box. SeeViewing system information, on page 43 for details.

Take ScreenshotClick Take Screenshot in the Application Browser to open the Take Screenshot dialog box. Use this dialogbox to set screenshot preferences and effects (for example, entire desktop with pointer, current window with


Accessing additional features with the Application BrowserSystem Information

a border, or a selected area). After setting your preferences, click Take Screenshot to take the screenshot andopen the Save Screenshot dialog box, which allows you to name and save the file.

Figure 18: Take Screenshot Dialog Box

VNC ServerClick VNC Server in the Application Browser to open the VNC Server Preferences dialog box. See Shadowor monitor a thin client, on page 55 for details.


Accessing additional features with the Application BrowserVNC Server

A P P E N D I X AShadow or monitor a thin client

TightVNC Server is installed locally on the thin client. It allows administrators to shadow/operate/monitora thin client from a remote machine on which TightVNC Viewer is installed (TightVNC Viewer is availablefrom the TightVNC website and must be installed on the remote/shadowing machine before use; it is alsoincluded as a component of Cisco VXC Manager software).

You may also be able to shadow thin clients using other third-party VNC viewers.Note

TightVNC (Server and Viewer) allows a remote administrator to configure or reset a thin client from a remotelocation rather than making a personal appearance at the thin client site (VNC is intended primarily forsupport and troubleshooting purposes). TightVNC Server starts automatically as a service at thin clientstartup if the administrator has configured it using the INI file.

The administrator must configure the client using INI parameters to enable VNC access. You must use thesame INI file configuration to enable VNCwhether you are using Cisco VXCmanager or TightVNCViewerto access the thin client. See INI configuration example for enabling VNC, on page 56 for an exampleconfiguration.

Before an administrator on a remote machine (on which TightVNC Viewer is installed) can access a thinclient (with TightVNC Server) the administrator must know the following:

• The IP address (or valid DNS name) of the thin client that is to be shadowed (see Viewing systeminformation, on page 43).

• The security password of the thin client that is to be shadowed.

This appendix includes the following:

• Shadow a thin client from a remote machine, page 55

• INI configuration example for enabling VNC, page 56

• VNC Server Preferences dialog box, page 57

Shadow a thin client from a remote machineTo shadow a thin client from a remote machine:


Procedure

Step 1 Open the New Tight VNC Connection dialog box (for example, from Microsoft Windows, click Start > AllPrograms > TightVNC > TightVNC Viewer).

Figure 19: New TightVNC Connection Dialog Box

Step 2 Enter the IP address or valid DNS name of the thin client that is to be shadowed (you can also set other optionsusing the command buttons).

Step 3 Click OK to open the VNC Authentication dialog box.

Figure 20: Standard VNC Authentication Dialog Box

Step 4 Enter the password of the thin client that is to be shadowed (this is the Security Password of the thin clientthat is to be shadowed), and clickOK. The thin client that is to be shadowed is displayed for the administratorin a separate window on the remote machine. Use the mouse and keyboard on the remote machine to operatethe thin client just as you would if you were operating it locally.

INI configuration example for enabling VNCYou can use the following example INI file configuration to enable VNC on the thin client:


Shadow or monitor a thin clientINI configuration example for enabling VNC

Example:DisableVnc=noVNCAuthTypes=noneVNCPrompt=noThis example enables VNC connections on the client, with no password authentication required to access theclient, and without prompting the user to accept VNC shadowing before the shadowing starts.

For details about using INI files, see INI Files Reference Guide for Cisco Virtualization Experience Client6215 .

VNC Server Preferences dialog boxUse the VNC Server Preferences dialog box (from the Desktop, click Computer >More Applications >VNCServer ) to manually set Sharing, Security, and Notification VNC Server preferences for use with remoteadministration. For example, you can set the Security password (the password an administrator must use whenshadowing the thin client) in this dialog box.

Figure 21:


Shadow or monitor a thin clientVNC Server Preferences dialog box


Shadow or monitor a thin clientVNC Server Preferences dialog box

A P P E N D I X BCisco VXC Manager and Wyse Device Manager

• Cisco VXC Manager with WDM, page 59

Cisco VXC Manager with WDMThis section describes how to manage a network containing a Cisco VXC Manager server and Cisco VXC6215 devices together with a Wyse Device Manager (WDM) server that controls Wyse devices using DHCPtags. The assumption is that the Cisco VXC Manager server is added to a network that already contains aWDM server.

No changes are needed to the production WDM network configuration.Note

Set up Cisco VXC Manager

Procedure

Step 1 Do not modify the existing WDM system with legacy devices and WDM DHCP tags.Step 2 Set up the Cisco VXC Manager 4.9.1 server as normal.Step 3 Configure a DDC package for upgrade on the Cisco VXC Manager server.Step 4 Boot the Cisco VXC 6215 devices.

The devices check in to the WDM server as they boot up for the first time in the network due to theexisting DHCP tags in the network.

Note


Set devices to use Cisco VXC Manager

Procedure

Step 1 After the device boots up, access Cisco VXC Manager and right-click on the device and choose ExecuteCommand.

Step 2 Enter /etc/init.d/sshd start & to enable SSH.Step 3 Use an SSH client to connect to the device and enter su to acquire root privileges.Step 4 Enter the administrator password.Step 5 Execute the following commands:

regset --persist Rapport Servers “xx.xxx.xxx.xx” (IP address of Cisco VXC Manager 4.9.1)regset --persist Rapport MgmtDiscoveryMethod STATICthinclient-config –set-preserve-changes yes (if the .RSP script does not have thiscommand)

Step 6 The device may reboot to allow checkins to the Cisco VXC Manager 4.9.1 server.Step 7 The moment a device checks in to Cisco VXC Manager, the scheduled DDC with the image upgrade is

initiated. When the reimaged device reboots, it automatically continues to report to the same Cisco VXCManager 4.9.1 server.

After you verify the devices check in to the Cisco VXCManager 4.9.1, delete the device entries fromthe WDM server.

Note


Cisco VXC Manager and Wyse Device ManagerSet devices to use Cisco VXC Manager

A P P E N D I X CBIOS upgrade

• Overview, page 61

• Extract BIOS, page 62

• Install BIOS, page 62

• Limitations, page 63

OverviewSummary

This appendix describes how to distribute a BIOS update for a BIOS password change or a BIOS versionupdate.

Description

The Cisco VXC 6215 provides two BIOS utilities. The first utility (bios_util) is used to extract the existingBIOS from a Cisco VXC 6215 unit. The second utility (rpmbuild) creates a squash rpm from the extractedBIOS so that the BIOS image can be deployed as an add-on.

The following instructions are divided into two sections: one for extraction and another for installation.

The extraction instructions describe how to extract a BIOS image from a device and convert the image intoan rpm addon. Use these instructions to create a BIOS add-on to change the BIOS password.

The installation instructions describe how to distribute and install a BIOS add-on. Use these instructions todistribute either a BIOS password or a new BIOS to one or more Cisco VXC 6215 units.

The instructions must be executed in the order provided to update a group of Cisco VXC 6215 devices.


Extract BIOSProcedure

Step 1 Prior to running the utility to extract the BIOS from a Cisco VXC 6215 unit, make the required changes tothe existing BIOS: access the BIOS (reboot the device and repeatedly press or hold down the Delete key tobring up the BIOS menu), update the BIOS password, and save it.

Step 2 After the device boots up, access Cisco VXC Manager and right-click on the device and choose ExecuteCommand.

Step 3 Enter /etc/init.d/sshd start & to enable SSH.Step 4 Use an SSH client to connect to the device and enter su to acquire root privileges.Step 5 Enter the administrator password.Step 6 Launch the following script to extract the BIOS for the device and create an addon:

/etc/addons.d/BIOS_UTIL/createBiosCmos.sh.Step 7 An add-on with the captured BIOS/CMOS image is created in the following directory:

/usr/src/pacakages/RPPMS/. The RPM file name consists of the platform name and the BIOS version.For example:vxc6215_bioscmos_update-3.0b_cso-1.slet11sp2.rpm

Step 8 Copy this captured BIOSRPM to aUSB storage device and deploy the RPM to other CiscoVXC 6215 devicesfrom Cisco VXC Manager.

Install BIOSIn Cisco VXCManager, use DDC to deploy the updated BIOS RPM to one or more Cisco VXC 6215 devices.

Unlike standard add-ons, the BIOS RPMmust be placed in the root package folder and not in the /addonsfolder.

Note

Use the following steps to deploy the BIOS RPM to your devices. In the sample scripts provided, be sure toupdate the .sh and .rpm file names as required.

Procedure

Step 1 To install the .rpm file, use a text editor to create a .sh script file (in this example,vxc6215_bioscmos_update-a3.0c_cso-1.sh) with the following content:#!/bin/bash/usr/sbin/addon-install /tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sletc11sp2.rpm

Step 2 Also, create the biosupgrade.rsp file with the following content:[Version]Number=biosupgrade


BIOS upgradeExtract BIOS

Description=BIOS upgradeOS=SLXCategory=CiscoUSE_Pxe=NO

[Script]CO "SLX"SF "<regroot>/vxc6215_bioscmos_update-a3.0c_cso-1.sh" \"/tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sh"SF "<regroot>/vxc6215_bioscmos_update-a3.0c_cso-1.sletc11sp2.rpm" \"/tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sletc11sp2.rpm"EX "dos2unix /tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sh"EX "chmod u+x /tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sh"EX "/tmp/vxc6215_bioscmos_update-a3.0c_cso-1.sh"

Step 3 Create a DDC package to push the .rpm file. Place the .rpm file and thevxc6215_bioscmos_update-a3.0c_cso-1.sh script file in the root package folder. For example:C:\6215-configs\biosupgrade.rsp

C:\6215-configs\biosupgrade\vxc6215_bioscmos_update-3.0b_cso-1.slet11sp2.rpm

C:\6215-configs\biosupgrade\vxc6215_bioscmos_update-a3.0c_cso-1.sh

Step 4 Register and push the package to your devices using DDC.Step 5 When the BIOS RPM is deployed, a splash screen appears on the target Cisco VXC 6215 devices indicating

the BIOS upgrade is about to begin and the devices will be automatically rebooted.

Step 6 The new BIOS is flashed during the reboot process.The BIOS is not flashed if the device platformmismatches the platform of the BIOS add-on.Note

LimitationsAs with other add-ons, the updated BIOS add-on is installed on a Cisco VXC 6215 device only if it is the firstBIOS add-on installed on that device, or if the new BIOS add-on version number is different from the lastinstalled BIOS add-on.


BIOS upgradeLimitations


BIOS upgradeLimitations

administration guide for cisco v irtualization experience ......figure 6: dhcp scope options: cisco...

Documents