|
Option
|
Description
|
Notes
|
| 1 |
Subnet Mask |
Required. However, it is not required
unless the thin client must interact with servers on a different subnet.
MS DHCP requires a subnet mask and is always send one.
|
| 2 |
Time Offset |
Optional. |
| 3 |
Router |
Optional, but recommended. It is
not required unless the thin client must interact with servers on
a different subnet.
|
| 6 |
Domain Name Server(DNS) |
Optional, but recommended. |
| 15 |
Domain Name |
Optional, but recommended. See Option 6. |
| 28 |
Broadcast Address |
Optional. |
| 44 |
WINS servers IP Address |
Optional. |
| 51 |
Lease Time |
Optional, but recommended. |
| 52 |
Option Overload |
Optional. |
| 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 requires the slash to be specified in order
to complete proper access.
|
| 181 |
PNAgent/ PNLite server list |
Optional string. The thin client
uses the server to authenticate the Windows credentials of the user
and to obtain a list of ICA published applications valid for the validated
credentials. The user supplies those credentials when logging in to
the thin client.
|
| 182 |
NT domain list for PNAgent/ PNLite
|
Optional string. The thin client
creates a pull-down list of domains from the information supplied
in option 182. This list is presented at thin client login in the
order specified in the DHCP option (for example, the first domain
specified becomes the default). The selected domain is the one which
must authenticate the user ID and password. Only the selected domain
is used in the authentication process. If the domain list is incomplete
and the user credentials must be verified against a domain not in
the list, assuming that the server in option 181 is capable of authenticating
against a domain not in the list, the user has the option of not using
any of the domains specified in option 182 and typing a different
domain name at the time of login.
|
| 184 |
File server Username |
Optional string. Username to use
when authenticating to the server specified in Option 161.
|
| 185 |
File server Password |
Optional string. Password to use
when authenticating to the server specified in Option 161.
|
| 186 |
WDM server list |
Optional binary IP addresses of
WDM. This option can specify up to two WDM servers. If two are specified,
at boot time the thin client attempts to check-in to the first server.
If it cannot contact the first server, it tries to check-in to the
second server.
|
| 187 |
WDM server port |
Optional number. Byte, word, or two-bytes array.
-
NOTE: The value of this option
tag, when not embedded in Vendor Class Specific Information option,
is interpreted in reverse order when it is sent as 2-bytes example,
the value of 0x0050 was interpreted as 0x5000. This option tag was
used by old ThinOS releases. New ThinOS releases still accept this
option tag for backward compatibility.
|
| 188 |
Virtual Desktop Broker server |
Optional string. |
| 190 |
WDM secure port |
Optional number, word or two-bytes
array. Specifies to use HTTPS to communicate with WDM instead of HTTP.
|
| 192 |
WDM server port |
Optional number, word or two-bytes array.
-
NOTE: The
value of this option tag represents the same information as option
tag 187. The difference is that ThinOS interprets the value of this
option tag in correct order (for example, the value of 0x0050 is interpreted
as0x0050). If the DHCP server provides both option tag 192 and 187,
option tag 192 takes precedence.
|
| 194 |
WDM FQDN |
Optional Fully Qualified Domain Name for the WDM. |
| 199 |
Cloud Client Manager Group Key
|
Optional string. Can provide a
CCM Group Registration Key for the cloud Client Manager agent. When
cloud Client Manager is disabled and the Group Key of Cloud Client
Manager is null, this option takes effect. Cloud Client Manager uses
the optional string as the Group Registration Key. If the Cloud Client
Manager server or MQTT server is null, the Cloud Client Manager agent
sets the values to the default server values.
|
