Cisco Cisco Virtualization Experience Client 2212 Administrator's Guide
A-6
Cisco Virtualization Experience Client 2112/2212 ICA Administration Guide for WTOS 7.0_214
OL-215152-01
Appendix A Central Configuration: Automating Updates and Configuration
Configuring Network Services
Configuring Network Services
Before you use the information in this section to configure your network services, be sure you have read
, and remember the following
important issues:
•
Restrictions to Network Services can Exist—Zero client network services reside on the enterprise
intranet. When setting up zero client network services, remember that if zero clients are to access
the enterprise intranet through Dial-up, PPPoE, or PPTP VPN, restrictions imposed by these access
paths must be considered.
intranet. When setting up zero client network services, remember that if zero clients are to access
the enterprise intranet through Dial-up, PPPoE, or PPTP VPN, restrictions imposed by these access
paths must be considered.
•
Know How Your Environment Works—Either the FTP server or the Virtual Desktop server
(depending on your environment) holds the INI files, while the FTP server (if available) holds the
current and upgrade versions of the zero client software.
(depending on your environment) holds the INI files, while the FTP server (if available) holds the
current and upgrade versions of the zero client software.
The zero client software is acquired from either local flash memory or the FTP server. During the
boot process, the local image is transferred to RAM and executed far enough for the zero client to
check the image and the INI files on the file servers. Under direction of the INI files and the version
of the remote image, the image in RAM can be replaced with the remote image; and separately, the
remote image can update the local flash-memory.
boot process, the local image is transferred to RAM and executed far enough for the zero client to
check the image and the INI files on the file servers. Under direction of the INI files and the version
of the remote image, the image in RAM can be replaced with the remote image; and separately, the
remote image can update the local flash-memory.
•
Functionality Depends on You—The WTOS INI files contain the parameters and associated values
necessary for the various functionality you want. The INI files (wnos.ini file and {username}.ini
file) are constructed and maintained by you and are stored on the file server for use with zero clients
running WTOS.
necessary for the various functionality you want. The INI files (wnos.ini file and {username}.ini
file) are constructed and maintained by you and are stored on the file server for use with zero clients
running WTOS.
Tip
The INI files contain connection definitions and zero client settings. These text-based files must be
created and maintained by using an ASCII text editor. If the INI files are omitted or they cannot be
accessed because a file server is not used, the zero client user must enter connection definitions
locally (or for FTP servers, use what is published by PNAgent/PNLite servers residing on the
network).
created and maintained by using an ASCII text editor. If the INI files are omitted or they cannot be
accessed because a file server is not used, the zero client user must enter connection definitions
locally (or for FTP servers, use what is published by PNAgent/PNLite servers residing on the
network).
You can also define connections in the INI files which are to be stored in local NV-RAM and used in
cases where the file server fails.
cases where the file server fails.
A wnos.ini file contains the “global” parameters you want that will affect all zero clients accessing the
file server. A {username}.ini file contains the user-specific or “user profile” parameters you want that
will comprise the connection profile for an individual user. The zero client accesses the wnos.ini file
upon zero client initialization and accesses any individual {username}.ini file when the user logs on (if
user login is required, the {username}.ini file must exist before that user can log in). For information on
constructing these INI files, refer to Cisco Virtual Experience Client 2112/2212 WTOS INI Files
Reference Guide.
file server. A {username}.ini file contains the user-specific or “user profile” parameters you want that
will comprise the connection profile for an individual user. The zero client accesses the wnos.ini file
upon zero client initialization and accesses any individual {username}.ini file when the user logs on (if
user login is required, the {username}.ini file must exist before that user can log in). For information on
constructing these INI files, refer to Cisco Virtual Experience Client 2112/2212 WTOS INI Files
Reference Guide.
To configure network services, use the information in the following sections:
•
•
•
•
•
•
•