Cisco Cisco Virtualization Experience Client 2111 Guida Dell'Amministratore
B-1
Cisco Virtualization Experience Client 2112/2212 ICA Administration Guide for WTOS 7.0_214
OL-215152-01
A P P E N D I X
B
Remote System Administration
This appendix provides remote system administration information to help you perform the routine tasks
needed to maintain your WTOS environment.
needed to maintain your WTOS environment.
It includes:
•
•
•
•
Using Cisco VXC Manager Software For Remote Administration
Cisco VXC Manager servers provide network management services to the zero client (complete
user-desktop control, with features such as remote shadow, reboot, shutdown, boot, rename, automatic
device check-in support, Wake-On-LAN, change device properties, and so on).
user-desktop control, with features such as remote shadow, reboot, shutdown, boot, rename, automatic
device check-in support, Wake-On-LAN, change device properties, and so on).
Updating Software
The software version is embedded in both the RAM and flash memory images. This version information
is used to compare the images on the FTP server to the currently-loaded flash image on the zero client.
A major revision number supersedes a minor revision number when making the comparison. In turn the
minor version number takes precedence over the build number. The image names and date-time stamps
determine whether or not the update is newer than the version currently installed on the zero client.
is used to compare the images on the FTP server to the currently-loaded flash image on the zero client.
A major revision number supersedes a minor revision number when making the comparison. In turn the
minor version number takes precedence over the build number. The image names and date-time stamps
determine whether or not the update is newer than the version currently installed on the zero client.
Tip
The code identifier is split into four parts, the major release identifier, the minor release identifier,
the build number identifier, and the sub-build number identifier (if the sub-build number is 0, it will
not be displayed). Each part is compared to the current code internal identifier in the same format. If
the file identifier is greater, the update is performed. If the file identifier is less, the update is
abandoned. If the file identifier is equal, the next term is examined until the build identifiers are found
to be equal and the update is abandoned. This comparison process using the build number can be
important in cases where you are using a beta release, or in cases where you need to reinstall a release
with the same major and minor numbers but with an updated build.
the build number identifier, and the sub-build number identifier (if the sub-build number is 0, it will
not be displayed). Each part is compared to the current code internal identifier in the same format. If
the file identifier is greater, the update is performed. If the file identifier is less, the update is
abandoned. If the file identifier is equal, the next term is examined until the build identifiers are found
to be equal and the update is abandoned. This comparison process using the build number can be
important in cases where you are using a beta release, or in cases where you need to reinstall a release
with the same major and minor numbers but with an updated build.