Administrator Guide
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 identier Always sent.
161 File server (ftp/http/https)
Optional string. Can be either the name or
the IP address of the le server. If a name is
given, the name must be resolvable by the
DNS servers specied in Option 6. If the
option provided by the server is blank or the
server provides no value for the eld, the
machine on which the DHCP server resides
is assumed to also be the le server.
162
Root path to the le server (ftp/http/https) Optional string. If the option provided by the
server is blank and the server provides no
value for the eld, 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
specied at login. For those servers,
the usage of the leading slash is
optional. Some *NIX servers can be
congured to allow the le user
access to the entire le system. For
those servers, specifying a leading
slash species that access is to start
at the root le system. Proper
matching of the le specication to
the le server in use is critical to
ensuring proper operation. A secured
Windows server requires the slash to
be specied in order to complete
proper access.
181 PNAgent/ PNLite server list
Optional string. The thin client uses the
server to authenticate the Windows
138 Central Conguration: Automating Updates and Congurations