Administrator Guide

Table 26. DHCP options (continued)
Option Description Notes
53 DHCP Message Type Recommended.
54 DHCP Server IP Address Recommended.
55 Parameter Request List Sent by thin client.
57
Maximum DHCP
Message Size
Optional (always sent by thin client).
58 T1 (renew) Time Optional, but recommended.
59 T2 (rebind) Time Optional, but recommended.
61 Client identifier Always sent.
161 File server (ftp/http/https)
Optional string. Can be either the name
or the IP address of the file server.
If a name is given, the name must be
resolvable by the DNS servers specified
in Option 6. If the option provided by the
server is blank or the server provides no
value for the field, the machine on which
the DHCP server resides is assumed to
also be the file server.
162
Root path to the file server (ftp/http/
https)
Optional string. If the option provided
by the server is blank and the server
provides no value for the field, a null
string is used.
\wyse\wnos is automatically appended
to the search path. For example,
if you enter pub\serversoftware,
the path searchedare
pub\serversoftware\wyse\wnos.
NOTE: You can have the
\wyse automatic component of
the search path omitted by
appending a dollar sign ($) to the
entered path. For example, if you
enter pub\serversoftware$,
the path searched will be
pub\serversoftware\wnos.
NOTE: The usage or omission of
a leading slash (\) on the path
is critical on some servers. Some
servers limit access to the root
path of the user specified at login.
For those servers, the usage of
the leading slash is optional. Some
*NIX servers can be configured to
allow the file user access to the
entire file system. For those servers,
specifying a leading slash specifies
that access is to start at the root
file system. Proper matching of the
file specification to the file server
in use is critical to ensuring proper
operation. A secured Windows server
Automating updates and settings using central configuration 159