Documente Academic
Documente Profesional
Documente Cultură
in 1 Series
A Technote by
Systems Engineering
March 2006
Wyse Product Support
Summary
This technote describes how DHCP Vendor ID is used and implemented in Blazer or 1
Series Winterms. It assumes that the reader is familiar with basic DHCP and Blazer
specific server configuration parameters.
Audience
Affected Products
Definition
It should be noted that theoretically Vendor Class Identifier (DHCP option 60) should
work together with Vendor Specific Information (DHCP option 43) to provide a complete
solution for customers who want to provide different set of network configurations to
individual Vendor Class product. Once configured, DHCP client sends a Vendor Class
Identifier in option 60 of its discovery/request/inform packets to identify itself to the
DHCP server. Using the Vendor Class Identifier information, DHCP server responds with
specific set of DHCP option values in option 43 of its offer and ack packets. DHCP
option values embedded in option 43 follows the same “Code-Length-Data” format that
is used in standard DHCP options field. But we will not implement option 43, the vendor
specific tag at this time in 1000 series terminals.
Requirements
Based on DHCP Vendor ID sent by client, different configurations can be sent from
DHCP server to the client. This enables the customers to customize the environment the
terminals operate. An example is setting different FTP server rootpath (thus different
wnos.ini) for different group of clients. Similar requirement will arise if two different sets
of terminals should use two different Rapport servers.
Here are the steps to enable the DHCP Vendor ID for the 1 Series.
First, follow Microsoft’s procedures on configuring the DHCP Vendor ID server side.
Vendor-defined classes are used for managing DHCP options assigned to clients identified by vendor
type.
User-defined classes are used for managing DHCP options assigned to clients identified by a
common need for a similar DHCP options configuration.
After defining an option class, individual scopes must be configured with any class-related options to
be provided to clients.
Next, make sure to specify the FTP directory for option tag 162 you wish to use. By
default we use “ftproot\wyse\wnos\wnos.ini”. I changed the 162 value to WyseDHCP1
and the new structure for the wnos.ini is now “ftproot\WyseDHCP1\wyse\wnos\wnos.ini”
Lastly amend the wnos.ini file w/ the appropriate command and DHCP Vendor ID.
DHCPVendorID=xxxxxx
DHCPVendorID=WyseDHCP1
If you have an technical enquiry please use the online knowledge portal at
http://www.wyse.com/serviceandsupport/support/askwyse.asp or contact the
numbers mentioned below.
© 2006 Wyse Technology Inc. All rights reserved. This material is copyrighted. You may not
reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or
computer language, in any form or by any means, electronic, mechanical, magnetic, optical,
chemical, manual or otherwise, any part of this publication without express written permission.
Wyse, WY, and WyseWorks are registered trademarks, and the Wyse logo, Winterm logo, Wyse,
and Winterm are trademarks of Wyse Technology Inc. ICA is a registered trademark and MetaFrame
is a trademark of Citrix Systems Inc. Rapport is a registered trademark of Rapport Technologies,
Inc., a division of Wyse Technology Inc. Microsoft, Windows, and Windows NT are registered
trademarks of Microsoft Corporation. Other product names mentioned herein are for identification
purposes only and may be trademarks and/or registered trademarks of their respective companies.
09/04 880924-45 Rev. A