Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 8.6
Cisco VXC Manager Configuration Quick Reference
Downloads: This chapterpdf (PDF - 470.0KB) The complete bookPDF (PDF - 1.01MB) | Feedback

Cisco VXC Manager Configuration Quick Reference

Table Of Contents

Cisco VXC Manager Configuration Quick Reference

Client Discovery Using Cisco VXC Manager

Configuring the DHCP Server for Device Discovery

Create a wlx.ini File for Client Configuration

INI File Examples

Firefox Browser Configuration Example

XenDesktop INI Configuration Example

VMware View INI Configuration Example

RDP INI Configuration Example

Create a Cisco VXC Manager Package for the wlx.ini File

Schedule Device Updates Using Default Device Configuration

Configuring Default Device Configuration Preferences

Procedure for First-Time Default Device Configuration

Procedure for Existing Default Device Configuration

Schedule Device Updates Using the Drag-and-Drop Method

Optional Voice and Video Firmware Add-On

Register a Package to Enable a Cisco Add-On

Update the Cisco VXC 6215 Base VDI Firmware

Configure Multimedia Redirection with a Proxy Server

Additional INI file examples

Enable VNC using an INI file

Time settings

Display and Keyboard settings


Cisco VXC Manager Configuration Quick Reference


This chapter provides a quick reference for the Cisco VXC Manager procedures required to upgrade client configurations, upgrade firmware, and enable add-ons on the Cisco VXC 6215. For detailed information about using Cisco VXC Manager, see Administration Guide for Cisco Virtualization Experience Client Manager.


Note Before you can preform the procedures in this document, you must perform the following prerequisites:

Set up your virtualization server (see your virtualization server documentation).

Install and set up the Cisco VXC Manager (see Installation Guide for Cisco Virtualization Experience Client Manager).

Connect at least one Cisco VXC 6215 to your network and power it on.


This document contains the following topics:

Client Discovery Using Cisco VXC Manager

Create a wlx.ini File for Client Configuration

Create a Cisco VXC Manager Package for the wlx.ini File

Schedule Device Updates Using Default Device Configuration

Schedule Device Updates Using the Drag-and-Drop Method

Optional Voice and Video Firmware Add-On

Register a Package to Enable a Cisco Add-On

Update the Cisco VXC 6215 Base VDI Firmware

Configure Multimedia Redirection with a Proxy Server

Client Discovery Using Cisco VXC Manager

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

Cisco VXC Manager can discover the Cisco VXC 6215 devices in your network using either dynamic discovery or a manual process. After Cisco VXC Manager identifies the devices in the network, it stores information about them in the Cisco VXC Manager Database. You can then use Cisco VXC Manager to manage the devices.

For the Cisco VXC 6215, the recommended discovery method uses a DHCP server. In this case, you must configure DHCP Option Tags (186 and 190, or 186 and 192) on your DHCP server to specify the IP address and port of the Cisco VXC Manager Web Server. The Cisco VXC Manager Agent (HAgent) on the Cisco VXC 6215 uses this information to communicate with the Cisco VXC Manager Web Server, performing check-ins at boot up and at regular intervals. 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 Configuring the DHCP Server for Device Discovery.


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

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

Configuring the DHCP Server for Device Discovery

To allow Cisco VXC Manager to discover the Cisco VXC 6215 devices, configure the following option tag values on your DHCP server:

Option tag 186—IP address of your Cisco VXC Manager server (for example, 192.168.1.10). The value should be in 4-byte IP address format.

Option tag 190—Secure port number to which Cisco VXC Manager server listens (for example, port 443). 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= 0x00 0x50).


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


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

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 2-1 DHCP Window

Figure 2-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

Code—186

Data Type—IP Address

Description (optional)—Enter desired information, or nothing

Figure 2-3 Option Type: Server IP

Step 4 Click OK.

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

Name—Cisco VXC Manager Server Secure Port

Code—190

Data Type—Word

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

Name—Cisco VXC Manager Server Port

Code—192

Data Type—Byte or Word

Figure 2-4 Option Type: Cisco VXC Manager Server Port

Step 7 Click OK.

Figure 2-5 DHCP Scope Options: Cisco VXC Manager Server

Step 8 From the DHCP management wizard, choose Scope Options (from the target DHCP Server Scope, as shown in Figure 2-5), right-click, and choose Configure Options.

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

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

In the list of Available Options, check option number 192, and enter the port number at which your Cisco VXC Manager server listens (Port 80 is shown in Figure 2-6).

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

Step 9 Click OK.

Figure 2-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.


Create a wlx.ini File for Client Configuration

Cisco VXC 6215 Initialization (INI) files are plain-text files that you construct to specify the configuration parameters you want to apply to your thin clients. The most commonly used INI file, wlx.ini, contains the global parameters you want to apply to all thin clients in your environment. (Cisco VXC Manager also allows you to specify a subset of thin clients to which a particular wlx.ini configuration applies.)

The Cisco VXC 6215 supports a number of INI configuration parameters. See INI File Examples for some useful examples, including configurations required to create XenDesktop, VMware View, and RDP connections. For a complete list of supported INI parameters, see Cisco Virtualization Experience Client 6215 INI Files Reference Guide.


Caution By default, an administrator username and password admin/admin is specified on the thin client. Cisco VXC 6215 does not support operation of the client using the administrator username and password in the current release (the only supported mode of operation is using the thinuser credentials). However, Cisco recommends that you change the administrator password using the ChangeAdminPassword INI parameter to prevent unauthorized access to the client.

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 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.


INI File Examples

Firefox Browser Configuration Example

The following is a simple INI file that you can use to test the Cisco VXC Manager client update process. After the package process is successful using this file, the client will load the INI file, and launch the Firefox browser with cisco.com as the home page.

Example:

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

XenDesktop INI Configuration Example

To create XenDesktop server connections, use the Mozilla Firefox Connect options to specify the URL of the XenDesktop 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


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

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

VMware View INI Configuration Example

The 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 \
LocalCopy=yes


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

RDP INI Configuration Example

The 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 \
Drives=J=disk \
Drives=k=floppy \
Sound=off \
LocalCopy=Yes


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

Create a Cisco VXC Manager Package for the wlx.ini File

To push a wlx.ini file to your clients, you must first create a Cisco VXC Manager package, which you can then schedule for distribution to your devices.


Caution Do not modify INI files directly on the Cisco VXC 6215 as doing so can cause configuration issues and operational errors. Only use Cisco VXC Manager to push the INI files to the clients.

Required Folder Structure with Cisco VXC Manager

With Cisco VXC Manager, you must create and register specific packages to push upgrades and configurations to your clients.

Cisco VXC Manager packages are structured relative to the location of an RSP file. To register the package with Cisco VXC Manager, the package must contain a unique RSP file and, at the same folder level, a folder with the same name as the RSP filename. This folder serves as the root folder for the remaining configuration files in the package.

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

~/<packagename>.rsp
~/<packagename>/wlx
~/<packagename>/wlx/bitmap
~/<packagename>/wlx/certs
~/<packagename>/addons

You can create this structure in any location on your Cisco VXC Manager server, as long as the placement of the folders relative to the RSP file remains the same.


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


After you register the package, Cisco VXC Manager stores the package files in the software repository under c:\inetpub\ftproot\Rapport\<packagename>.


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

Use the following procedure to create a Cisco VXC Manager package containing the wlx.ini file for Cisco VXC 6215 client configuration (see Create a wlx.ini File for Client Configuration for information on creating the wlx.ini file).

Procedure


Step 1 Create a folder to contain the client configurations, for example 6215Configs.

Step 2 In the 6215Configs folder, create an RSP file, for example SLE1.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 .rsp extension):

[Version]
Number=SLE1
OS=SLX
Category=Other Packages
USE_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 "sync"
EX "sleep 2"
RB
RB


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


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

Step 3 Also in the 6215Configs folder, create a subfolder using the same name as the RSP file name, for example SLE1.

Step 4 In the SLE1 folder, create a subfolder named wlx.

Step 5 In the wlx folder, copy the wlx.ini that contains the required configuration.
For example:

Location and name of the .rsp file:

C:\VXC-M\6215Configs\SLE1.rsp

Location and name of the wlx directory:

C:\VXC-M\6215Configs\SLE1\wlx

Location and name of wlx.ini file in the wlx directory:

C:\VXC-M\6215Configs\SLE1\wlx\wlx.ini

Step 6 In the tree pane of the Administrator Console, expand Package Manager.

Step 7 In the details pane, right-click Other Packages and choose New > Package.

Step 8 Choose Register a Package from a Script file (.RSP) and click Next.

Step 9 Click Browse to choose the file path of the .rsp package file you want to register (For example: C:\VXC-M\6215Configs\SLE1.rsp) and click Open.

Step 10 Click Next to display the Package Wizard summary.

Step 11 Click Next to see the Package Registration Progress screen.

Step 12 Click Next to create the package.

Step 13 After the package is created and registered, click Finish.

Step 14 To upgrade the Cisco VXC 6215, you can use the Default Device Configuration (DDC) method (see Schedule Device Updates Using Default Device Configuration) or the Drag-and-Drop method (see Schedule Device Updates Using the Drag-and-Drop Method).


Schedule Device Updates Using Default Device Configuration

To update a group of Cisco VXC 6215 devices, you can assign a Default Device Configuration (DDC). A DDC allows you to set default configurations for a group of devices and ensures that the devices conform to your configurations. That is, if there is any deviation from your default configurations, Cisco VXC Manager reverts the devices to your specified configurations automatically (Cisco VXC Manager automatically sends the Cisco VXC Manager packages in the DDC to the devices according to your schedule and without your intervention).

See the following sections to configure a DDC:

Configuring Default Device Configuration Preferences

Procedure for First-Time Default Device Configuration

Procedure for Existing Default Device Configuration

Configuring Default Device Configuration Preferences

Before 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, double-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, click Merlin.

Step 8 Click OK.


Procedure for First-Time Default Device Configuration

Perform this procedure each time you create a new image package that you want to specify as the default image for client upgrades.

Procedure


Step 1 Determine whether a Default Device Configuration already exists:

a. In the tree pane of the Administrator Console, expand Configuration Manager and click Default Device Configuration.

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

Step 2 In the tree pane of the Administrator Console, expand Configuration Manager, right-click Default Device Configuration, and choose New > Default Device Configuration to open the Default Device Configuration Wizard.

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 to the Selected column. (The packages listed in this tab match the packages that you have registered in the Cisco VXC Manager.)

Step 7 Click Next and choose Whenever a device checks in.

Step 8 Click Next and click Finish.

Step 9 Right-click the Cisco VXC 6215 you want to upgrade, and choose Reboot.

When the selected devices reboot, they upgrade to any new OS image version available from Cisco VXC Manager.

Step 10 In the tree pane of the Administrator Console, click Device Manager.

Step 11 Click the top Refresh icon to see the changed software revision.


To verify that Cisco VXC Manager has succesfully 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 (+) to maximise the properties for the device, then click the Deployed Package tab to show all packages that are on the device. You can also click the Log History tab to view the status of the most recent package pushed to the device.

Procedure for Existing Default Device Configuration

Perform this procedure when you want to specify an existing image package as the default image for client upgrades.

Procedure


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

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 Cisco VXC 6215 clients, the clients are updated to the selected package configuration automatically: either at their regularly scheduled checkin time or according to the update time set in the Device Manager DDC preferences in Configuration Manager. You can also right-click the Cisco VXC 6215 you want to upgrade, and choose Reboot to perform a manual upgrade.


Schedule Device Updates Using the Drag-and-Drop Method

As an alternative to Default Device Configuration, you can use the drag-and-drop method to schedule a registered Cisco VXC Manager package to be distributed as an update to your clients.

Procedure


Step 1 In the tree pane of the Administrator Console, expand Package Manager and click the folder that contains the package you have registered so that it appears in the details pane.

Step 2 Expand Device Manager to display the folder (or View) containing the devices that you want to update.

Step 3 Click and drag the package from the details pane and drop it onto the folder containing the target devices.

Step 4 In the Package Distribution Wizard that appears, choose the devices you want to receive the Cisco VXC Manager package and click the arrow to move them to the Selected Devices list (use Ctrl-click or Shift-click to choose multiple devices), and then click Next.

Step 5 Depending on whether or not any of the devices you selected are serviced by a Remote Repository (for example, the Cisco VXC Manager package with the update is contained in a Remote Repository), complete one of the following:

If no, the wizard prompts you to choose when the update should occur. Choose the time and date for the update, click Next, and then continue with Step 6.

If yes, and you have set up your preferences to synchronize Remote Repositories, the wizard prompts you for the synchronization information. Enter the information, click Next, and then continue with step 6.

Step 6 When prompted to create the updates click Next.

Step 7 After the wizard notifies you that the updates have been created, click Finish.

To push the updated package to the clients, right-click the Cisco VXC 6215 devices you want to upgrade, and choose Reboot.


To verify that Cisco VXC Manager has succesfully 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 (+) to maximise the properties for the device, and then click the Deployed Package tab to show all packages that are on the device. You can also click the Log History tab to view the status of the most recent package pushed to the device.

Optional Voice and Video Firmware Add-On

To support Unified Communications on the Cisco VXC 6215, you must purchase and install the Voice and Video Firmware add-on. The optional Voice and Video Firmware add-on provides Unified Communications functionality for Cisco UC Integration for Microsoft Lync and Cisco Unified Personal Communicator.

With the Voice and Video Firmware add-on, users in a virtual environment can use Cisco UC Integration for Microsoft Lync or Cisco Unified Personal Communicator from their thin clients. The Voice and Video Firmware runs on the thin client, and Cisco UC Integration for Microsoft Lync or Cisco Unified Personal Communicator runs on the Windows hosted virtual desktop.

For detailed deployment information about the optional Voice and Video Firmware add-on, see the Deployment Guide for Voice and Video Firmware for Cisco Virtualization Experience Client 6215.

To enable the Voice and Video Firmware add-on on the Cisco VXC 6215, see Register a Package to Enable a Cisco Add-On.

Register a Package to Enable a Cisco Add-On

Use the following procedure to enable a Cisco add-on.

Procedure


Step 1 Download the add-on files from the Cisco Software Download page:

a. Go to the following URL:

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

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

c. Choose Cisco Virtualization Experience Client 6000 Series > Cisco Virtualization Experience Client 6215.

d. Choose the desired add-on from the list.

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

Step 2 On the server on which you have Cisco VXC Manager installed, extract the add-on files to a local folder.


Note Assuming an add-on named ciscoaddontest1, the extracted add-on folder structure appears as follows:
~/ciscoaddontest1/wlx/wlx.ini
~/ciscoaddontest1/ADDONS/<rpmfilename>.rpm
~/ciscoaddontest1/ADDONS/directory
~/ciscoaddontest1.rsp


Step 3 In the extracted wlx.ini file, do not modify the existing parameters, but add any additional INI configurations you require.


Note If you have existing INI configurations on your clients, you must copy and paste these parameters into the wlx.ini that you push with the add-on; otherwise, the clients will lose the pre-existing configurations.


Step 4 In the tree pane of the Administrator Console, right-click Package Manager and choose New > Package to open the Package wizard.

Step 5 Click the Register a Package from a Script File (.RSP) option and click Next.

Step 6 Enter the file path to the Cisco VXC Manager script file (RSP) file contained in the extracted add-on files (you can use Browse to find and choose a file), and then click Next to open the Software Package Information dialog box.
The wizard obtains and displays the name, description, and category of the Cisco VXC Manager package.

Step 7 To have the Cisco VXC Manager active for distribution, check the Active check box.

Step 8 Click Next.
The wizard notifies you that it is ready to create and register the new Cisco VXC Manager package.

Step 9 Click Next to create and register the Cisco VXC Manager package.

Step 10 After the Cisco VXC Manager package is created and registered, click Finish.
The Cisco VXC Manager package is copied to the Master Repository and is displayed under the appropriate category. The Cisco VXC Manager package is now ready for distribution (see Schedule Device Updates Using Default Device Configuration or Schedule Device Updates Using the Drag-and-Drop Method).


Update the Cisco VXC 6215 Base VDI Firmware

To update the Base VDI Firmware image on a Cisco VXC 6215 client, perform the following procedure.


Note If the Cisco VXC 6215 is running the Voice and Video Firmware Add-on, after you upgrade the Base VDI firmware, you must install the compatible release of the Voice and Video Firmware Add-on. See Register a Package to Enable a Cisco Add-On.


Procedure


Step 1 Download the OS image from the Cisco Software Download page:

a. Go to the following URL:

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

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

c. Choose Cisco Virtualization Experience Client 6000 Series > Cisco Virtualization Experience Client 6215.

d. Choose the desired release version from the list.

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

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

Step 3 In the extracted wlx.ini file, do not modify the existing parameters, but add any additional INI configurations you require.


Note If you have existing INI configurations on your clients, you must copy and paste these parameters into the wlx.ini that you push with the add-on; otherwise, the clients will lose the pre-existing configurations.


Step 4 Register the image 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 that is contained in the unzipped image files, 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 5 Configure the DDC preferences (Configuring Default Device Configuration Preferences).

Step 6 To upgrade the Cisco VXC 6215, you can use Default Device Configuration or use the Drag-and-Drop method (see Schedule Device Updates Using Default Device Configuration and Schedule Device Updates Using the Drag-and-Drop Method)


Note If you downgrade a Cisco VXC 6215 thin client from a newer Image DDC (for example, DDC_10) to any older Image DDC (for example, DDC_09), and then try to re-apply the newer image DDC to the client, the operation fails. To successfully re-apply the newer image DDC (DDC_10) to the thin client after a downgrade, you must first rename the newer image DDC using Cisco VXC Manager (for example, to DDC_10a).



Configure Multimedia Redirection with a Proxy Server

When you enable Multimedia redirection to allow the thin client to fetch audio and video media directly, if you have an internal proxy server running on your network, you must configure the thin client with the address of your proxy server to allow the thin client to access the external media.

To configure the proxy server, you must push an RSP file to the clients using Cisco VXC Manager in accordance with the following procedure. Note that you must also specify the internal domain for which no redirection is required.

Procedure


Step 1 Create a folder to contain the client configurations, for example 6215Configs.

Step 2 In the 6215Configs folder, create an RSP file, for example ProxyConfig.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 .rsp extension):

[Version]
Number= ProxyConfig
OS=SLX
Category=Other Packages
USE_Pxe=NO
[Script]
RP "<regroot>"
EX "echo 'export http_proxy=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export HTTP_PROXY=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export https_proxy=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export HTTPS_PROXY=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export ftp_proxy=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export FTP_PROXY=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export all_proxy=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export all_proxy=http://<proxy-server.com:443>' >> /etc/bash.bashrc.local"
EX "echo 'export no_proxy=<.local-domain.com>' >> /etc/bash.bashrc.local"
EX "echo 'export NO_PROXY=<.local-domain.com>' >> /etc/bash.bashrc.local"
RB
RB

Where:

You must replace <proxy-server.com:443> with the address and port of the proxy server for the specified protocols.

You must replace <.local-domain.com> with your local domain name to be added to the proxy bypass list. For example:

EX "echo 'export no_proxy=.cisco.com' >> /etc/bash.bashrc.local"

You must ensure the Number= segment has the exact same value as the RSP file name.

Step 3 Also in the 6215Configs folder, create a subfolder using the same name as the RSP file name, for example ProxyConfig.

Step 4 In the ProxyConfig folder, create a subfolder named wlx.

Step 5 In the wlx folder, copy the wlx.ini file containing your existing INI configuration that you want retained after the configuration update.

For example:

Location and name of the .rsp file:

C:\VXC-M\6215Configs\ ProxyConfig.rsp

Location and name of the wlx directory:

C:\VXC-M\6215Configs\ ProxyConfig\wlx

Location and name of wlx.ini file in the wlx directory:

C:\VXC-M\6215Configs\ ProxyConfig\wlx\wlx.ini

Step 6 In the tree pane of the Administrator Console, expand Package Manager.

Step 7 In the details pane, right-click Other Packages and choose New > Package.

Step 8 Choose Register a Package from a Script file (.RSP) and click Next.

Step 9 Click Browse to choose the file path of the .rsp package file you want to register (For example: C:\VXC-M\6215Configs\ ProxyConfig.rsp) and click Open.

Step 10 Click Next to display the Package Wizard summary.

Step 11 Click Next to see the Package Registration Progress screen.

Step 12 Click Next to create the package.

Step 13 After the package is created and registered, click Finish.

Step 14 To upgrade the Cisco VXC 6215, you can use Default Device Configuration or use the Drag-and-Drop method (see Schedule Device Updates Using Default Device Configuration and Schedule Device Updates Using the Drag-and-Drop Method).


Additional INI file examples

Enable VNC using an INI file

Example:

DisableVnc=no
VNCAuthTypes=none
VNCPrompt=no

Time settings

Example:

Timeserver=yourntpserver.com
Timeformat="24-hour format"
TimeZone="US/Eastern" ManualOverride=1

Display and Keyboard settings

Example:

DisplaySettings=MON1 rotate-normal 1440x900
DesktopTaskBar=left
AutoHide=yes
Keyboard.layouts=us