Cisco Cisco Virtualization Experience Client 2111 Administrator's Guide
B-2
Cisco Virtualization Experience Client 2112/2212 ICA Administration Guide for WTOS 7.0_214
OL-215152-01
Appendix B Remote System Administration
Managing Icons and Logos
After obtaining software updates from Cisco, you must replace the existing software images in the wnos
subdirectory on the FTP server to allow the zero clients to automatically detect and self-install the new
software (upon zero client system start). The FTP server address and exact path to these files are
specified in DHCP Options 161 and 162 (if DHCP is not used, the path is specified in the Network Setup
dialog box on the zero client).
subdirectory on the FTP server to allow the zero clients to automatically detect and self-install the new
software (upon zero client system start). The FTP server address and exact path to these files are
specified in DHCP Options 161 and 162 (if DHCP is not used, the path is specified in the Network Setup
dialog box on the zero client).
Each time a zero client boots, it checks the software images on the FTP server, and if configured,
automatically performs an update if a newer version is detected. Whether or not an update is performed
depends on the AutoLoad parameter setting in the wnos.ini file as described in the Cisco Virtual
Experience Client 2112/2212 WTOS INI Files Reference Guide.
automatically performs an update if a newer version is detected. Whether or not an update is performed
depends on the AutoLoad parameter setting in the wnos.ini file as described in the Cisco Virtual
Experience Client 2112/2212 WTOS INI Files Reference Guide.
Be aware that there is a significant distinction between using DHCP and not using DHCP to access the
various necessary files as follows:
various necessary files as follows:
•
If DHCP is used, zero client software automatically inserts the path command /cisco following what
it receives from the DHCP server (unless the path is terminated by a $); this is done only if a value
is received from DHCP. The dollar sign character ($) acts as a flag that notifies WTOS that the
absolute path has been given (that is, where it expects to find WTOS configuration files inside a
“wnos” folder) instead of the relative path (where it expects to find the general “cisco” configuration
folder).
it receives from the DHCP server (unless the path is terminated by a $); this is done only if a value
is received from DHCP. The dollar sign character ($) acts as a flag that notifies WTOS that the
absolute path has been given (that is, where it expects to find WTOS configuration files inside a
“wnos” folder) instead of the relative path (where it expects to find the general “cisco” configuration
folder).
•
If DHCP is not used and the configuration is done manually, the full path up to the wnos component
must be inserted; there is no automatic /cisco insertion and no $ processing.
must be inserted; there is no automatic /cisco insertion and no $ processing.
•
Note that WTOS software does not recognize a $ terminator as a legal meta-character in a locally
entered string.
entered string.
Tip
Citrix ICA Auto-Update does not function for the ICA client installed on the zero client; the ICA
client is fully contained in the zero client system and can only be updated by changing that entire
system. The RDP client is also not replaceable.
client is fully contained in the zero client system and can only be updated by changing that entire
system. The RDP client is also not replaceable.
Caution
Interrupting power during the update process can corrupt the FLASH on the zero client. Zero clients with
corrupted FLASH must be shipped to Cisco for service.
corrupted FLASH must be shipped to Cisco for service.
Managing Icons and Logos
Icons and logos specified in the INI files must be placed in the file server /wnos/bitmap subdirectory.
Icons are specified in the Icon clause of the connection statement and logos are specified in the
FormURL statement. Supported image file types include .ico (icon), .bmp (bitmap), .jpg (JPEG), and
.gif(GIF). Color depth for logos can be up to 256 colors. Color depth for icons can be 16 colors. It is
recommended that .jpg format not be used for desktop icons.
Icons are specified in the Icon clause of the connection statement and logos are specified in the
FormURL statement. Supported image file types include .ico (icon), .bmp (bitmap), .jpg (JPEG), and
.gif(GIF). Color depth for logos can be up to 256 colors. Color depth for icons can be 16 colors. It is
recommended that .jpg format not be used for desktop icons.
Use the following guidelines:
•
Typical desktop icons are 64 x 48 pixels.
•
Typical sign-on logos are 100 x 61 pixels, with transparent background.
•
Maximum size for sign-on logos is 352 x 80 pixels (if smaller than this, it will be positioned in the
upper-left corner).
upper-left corner).