Appendix A Central Configuration Using File Server

How to Set Up Central Configuration Using a File Server

Table A-1

DHCP Option Tags

 

 

 

 

Option

Description

Notes

 

 

 

161

Server (ftp/http/https)

Optional string. If this is an IP address or resolvable hostname, the

 

 

protocol is assumed to be FTP; however, it may be the leading

 

 

portion of a URL that specifies another protocol. If the URL form

 

 

is used, it should not include a trailing slash (for example,

 

 

http://server.example.com or ftp://192.168.0.1).

 

 

 

162

Root path to the server (ftp/http/https)

Optional string. The relative directory starting from the root

 

 

directory must be given. For example, on an FTP server, the full

 

 

directory may be C:/Inetpub/ftproot/wyse, where wyse is the

 

 

directory that contains the firmware. In this example, the correct

 

 

string value for this DHCP option is /wyse.

 

 

On a Linux server, an FTP user-based directory might be

 

 

/home/test/wyse. In this example, if the FTP user is test, then the

 

 

FTP root path is /wyse and not the full path (/home/test/wyse).

 

 

This value should use URL path notation (start with a forward

 

 

slash, /, and use a forward slash as folder separators).

 

 

 

181

PN Server

Optional string. IP address or FQDN of the PNLite server.

 

 

 

182

Admin List

Optional string. DHCP equivalent of the DomainList INI file

 

 

parameter.

 

 

 

184

Server Username

Optional string. Username to use when authenticating to the server

 

 

specified in Option 161.

 

 

 

185

Server Password

Optional string. Password to use when authenticating to the server

 

 

specified in Option 161.

 

 

 

186

Cisco VXC Manager

Optional binary IP address of the Cisco VXC Manager server. This

 

 

option can specify up to one Cisco VXC Manager server.

 

 

 

191

XenDesktop DDC URL

Optional string. You can connect to your XenDesktop URL by

 

 

using DCP Option tag 191 to specify the XenDesktop DDC URL.

 

 

 

194

Cisco VXC Manager FQDN

Optional FQDN of the Cisco VXC Manager server. This option can

 

 

specify up to one Cisco VXC Manager server.

 

 

 

Step 3: Rebooting

To reboot your thin client, click Computer > Shutdown and choose Restart.

Note To reboot the client, use the Restart option to ensure the client performs a full boot sequence. This step is especially important when you are upgrading client firmware or configurations; otherwise, the upgrades may not take effect.

After you reboot (or start the thin client), the thin client searches in the defined root path for the latest available image and updates if necessary. Additionally, it checks the directory file in the add-ons folder to determine whether any updates for installed add-ons are defined. Add-ons that exist in the add-ons folder but are not listed in the directory file are ignored during update check-in.

Administration Guide for Cisco Virtualization Experience Client 6215 Firmware Release 8.6

A-5

Page 55
Image 55
Cisco Systems CVXC6215SK9 manual Rebooting