
Central Configuration: Automating Updates and Configurations
59
Tip
The INI files contain connection definitions and thin 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 thin 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.
A wnos.ini file contains the “global” parameters you want that will affect all thin 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 thin client accesses the wnos.ini file upon thin 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 the
Reference Guide: Wyse ThinOS
TM
INI Files
.
To configure network services, use the information in the following sections:
•
"Configuring FTP Servers"
•
"Configuring Virtual Desktop Infrastructure Servers"
•
"Configuring DHCP (DHCP Options)"
•
"Configuring DNS"
•
"Configuring WINS"
•
"Configuring Wyse Device Manager Servers"
•
"Configuring Wireless Access"
Configuring FTP Servers
Before
you use the information in this section to configure your FTP server, be sure you
understand and use the following guidelines:
•
General Guidelines
- When the thin client boots, it accesses the software update
images and INI files from the FTP server. The FTP server and path to the software
update files are available through DHCP vendor options 161 and 162 (see "Configuring
DHCP (DHCP Options)"). If these are not specified, the default FTP server is the
DHCP server from which the thin client receives its IP address and the default directory
(
\wyse\wnos
for Windows FTP servers, or
/wyse/wnos
for Linux FTP servers).
The FTP server and path to the software update files can also be specified locally on
the thin client. DHCP options 184 and 185 can be used to provide the User ID and
Password for non-anonymous access to the FTP server in Wyse ThinOS version 4.3
and later. For Wyse ThinOS versions earlier than 4.3, the file server must have
anonymous login capability and provide at least file read privilege for the anonymous
user (it must also provide file write privilege if users are allowed to change their
passwords).
•
Non-Anonymous Access Guidelines
- You must first create a local account (name
the account so that you remember it is a non-anonymous account) on the FTP server
defined between the DHCP vendor options 161 and 162 (DHCP server). Then, add
DHCP options 184 and 185 to provide the User ID and Password for non-anonymous
access to the FTP server. Ensure that option 184 is the account User ID and that
option 185 is the account Password, and that you keep consistency with FTP server
Содержание V10LE
Страница 4: ...This page intentionally blank...
Страница 14: ...8 Chapter 2 This page intentionally blank...
Страница 54: ...48 Chapter 5 This page intentionally blank...
Страница 80: ...74 Appendix A This page intentionally blank...
Страница 90: ...84 Appendix C This page intentionally blank...