|
Configuring Thin Clients - DHCP Boot Options |
|
|
|
|
Written by Tom Hirt
|
|
Saturday, 04 April 2009 14:37 |
|
Page 3 of 5
DHCP Boot Options
We’ll begin our configuration with the DHCP boot options. I have included a table below with the most commonly used options:
| Option |
Description |
| 003 |
Default Route |
| 006 |
DNS Server(s) |
| 015 |
DNS Domain Name |
| 161 |
FTP server list. This can be either the name or IP address of the ftp server(s) seperated by commas or semicolon |
| 162 |
Root path to the FTP files. /wyse/wnos is automatically appended to this value. So if /config were entered, the affective path would become /configs/wyse/wnos. You can have 'wyse' omitted from the path by apending a dollar sign ($) to the path. i.e. /configs$ would imply a path of /configs/wnos |
| 184 |
FTP Username |
| 185 |
FTP Password |
| 186 |
WYSE Device Manager |
| 188 |
View Connection Broker. This can also be specified within your wnos.ini. |
For our example, we’ll use Microsoft’s DHCP snap-in to configure a new DHCP scope and options for our thin clients. Let’s begin by opening the snap-in as a domain administrator from a DHCP server configuring DHCP with custom options 161, 162, 184, 185, 186 and 188:
- Click ‘Start’ then ‘Run’. In the ‘Run’ window, type ‘dhcpmgmt.msc’ and click OK

- Right click on the hostname of your DHCP server and select the ‘Set Predefined Options’ from the menu

- Click the ‘Add’ button on the Predefined Options and Values window

- You be presented with the following window:

- I’ve provided the following example for option ID 161:

Repeat steps 3 through 5 to create DHCP options - 161, 162, 184, 185, 186 and 188 on your DHCP server:
- In the ‘Name’ field, provide a brief description of the new Option value.
- Change the ‘Data type’ to ‘String’
- Enter the DHCP Option in the ‘Code’ field (i.e. 161)
- Provide a brief description in the ‘Description’ field so you know what this value represents when looking at this later
|
|
Last Updated on Tuesday, 02 June 2009 11:09 |