Wyse S10 Administrator's Manual page 67

Central Configuration: Automating Updates and Configurations
To configure an FTP server, complete the following procedures:
1. Create the following directory structure on your FTP server:
<path from anonymous user FTP root>\wyse\wnos\
<path from anonymous user FTP root>\wyse\wnos\bitmap\
<path from anonymous user FTP root>\wyse\wnos\cacerts\
<path from anonymous user FTP root>\wyse\wnos\inc\
<path from anonymous user FTP root>\wyse\wnos\trace\
Tip
There is a difference between a path obtained from the DHCP server and a
path entered in the UI. If the path is obtained from DHCP, /wyse/wnos are
appended. If the path is obtained from the UI, the /wyse portion is not
appended; only /wnos is automatically inserted. As written in this first step,
the configuration procedure will only work in conjunction with a DHCP server.
2. If you need to upgrade the firmware for your thin client, you must have a Software
Maintenance agreement to download the files (for details, go to
products/software/os/index.asp). Copy the RCA_boot and RCA_wnos (if you have an
S10) or V10L_boot and V10L_WNOS (if you have a V10L) and place it in the wnos
subdirectory of your FTP server.
3. Obtain the Sample User INI files (go to http://www.wyse.com/manuals, search for
sample.ini, click the reference guide link, and then click the sample ini link to open and
use the file download dialog box to save the compressed file to a folder you want) and
unpack them into a directory from which they can be examined and modified using an
ASCII text editor. These sample files are annotated to allow you to use them as a
starter set on your FTP server and can be modified to suit your needs. The
compressed file includes:
• wnos.kiosk - Example wnos.ini file for a kiosk configuration
• wnos.login - Example wnos.ini file to enable multiple user accounts
• user.ini - Template for {username}.ini for individual user profiles
4. Determine whether all the thin clients served by this FTP server will be used as kiosks
or will support individual user accounts. You must rename the downloaded files so that
there will be one wnos.ini file available to all users globally; and for a multiple user
account configuration there will be a unique {username}.ini file for each user. In
addition:
• If the kiosk configuration is to be used - Change the name of wnos.kiosk to
wnos.ini. Otherwise, for multiple user accounts, change the name of
wnos.login to wnos.ini.
• If the individual user account configuration is to be used - Make a copy of the
user.ini file for each user name as {username}.ini (where {username} is the
name of the user) and place the files in the subdirectory ini of wnos. The files must
have read permission enabled, and if users are to be allowed to change their
passwords, the files also must have write permission enabled (so that the thin
clients can write the encrypted user passwords to them). For Linux servers, use
the chmod command to set the read/write permissions. For Microsoft servers, use
the Properties dialog box to set read/write permissions.
5. If desired, you can customize the INI files to match the local environment using the
instructions in the Reference Guide: Wyse ThinOS
files to include icons and logos, be sure to place the images in the FTP server/wnos/
bitmap subdirectory.
http://www.wyse.com/
TM
INI Files. If you modify the INI
61