Central Configuration: Automating Updates and Configurations
65
Be sure to create/activate the two required MIME Types (
.ini
and
.
) under IIS (on a per
site basis) to enable downloading. Also be sure your Web server can identify the file
types used by Wyse thin clients.
To create/activate
.ini
:
1.
On your IIS server, use the
File Types
menu to add a New Type.
2.
In the
File Type
dialog box, enter the Associated extension
.ini
and Content type
(MIME)
text/plain
.
3.
Click
OK
to apply the settings.
To create/activate
.
:
1.
On your IIS server, use the
File Types
menu to add a New Type.
2.
In the
File Type
dialog box, enter the Associated extension
.
and Content type
(MIME)
text/plain
.
3.
Click
OK
to apply the settings.
For detailed instructions on adding
.ini
and
.
, refer to Knowledge Base Solution #
15508
(go to the Knowledge Base at
http://www.wyse.com/kb
and search for
15508
).
Step 2: Direct the Thin Client to the Server Using DHCP Options
After you set up the folder structure and populate it with the correct files, you must
then direct the thin client to the location of the server using DHCP.
Information about the server and root directory is obtained from the following DHCP
options:
•
161
- The server.
•
162
- Root path to the file server (ftp/http/https).
·
If no root path is defined, /wnos
is assumed.
·
If a root path is defined, the additional path will be appended to the URL supplied
by option 161.
•
184
- (Optional) Server username (to server specified in option 161).
•
185
- (Optional) Server password (to server specified in option 161).
Use the guidelines shown in Table 7 when creating and adding the DHCP options you
need. Ensure that within the DHCP scope the new DHCP option tags you create are
activated (this can be done using the
Scope Options
dialog box on the DHCP server
after you add them, or the
Configure Options
command before you add them).
