Configuring Ezupdate Via Dhcp; Manually Configuring Ezupdate On The Client - Neoware c50 - Thin Client User Manual

Configuring
ezUpdate via DHCP
Manually
configuring
ezUpdate on the
client
A Dynamic Host Configuration Protocol (DHCP) server may be
configured to provide Neoware thin client appliances with the loca-
tion (URL) of the ezUpdate server and files (the ezUpdate direc-
tory). Although ezUpdate can be configured to use any DHCP tag
number, by default ezUpdate is configured to use DHCP tag 137.
The ezUpdate DHCP tag (by default, tag 137) may be set on your
DHCP server to specify the FTP or NFS location (URL) of configu-
ration and/or software update files. If provided by DHCP, NeoLinux
thin client appliances will use the URL to check for updated config-
uration files or updated software files at every bootup.
The syntax of the URL address provided in the ezUpdate DHCP tag
depends on the type and setup of the ezUpdate server you are using.
For password-protected FTP, the URL should be in the following
format:
ftp://username:password@host/path_to_ezupdate_directory
For anonymous FTP, the URL should be in the following format:
ftp://host/path_to_ezupdate_directory
If you are using anonymous FTP, and your FTP server resides on the
same machine as your DHCP server, the URL should be in the fol-
lowing format:
ftp://@DHCPSERVER/path_to_ezupdate_directory
For an NFS server, the URL should be in the following format:
nfs://host/path_to_ezupdate_directory
On an NFS server, the ezUpdate directory should be shared for all
users, read-only access.
If DHCP is not used to provide the path information to the ezUpdate
directory, that information may be entered in the NeoLinux client
setup interface. Even if DHCP is used, the NeoLinux client ezUp-
date configuration may be set to ignore the DHCP setting.
To manually configure ezUpdate on the NeoLinux thin client appli-
ance:
ezUpdate and NeoLinux 95