Auto-configuration of legacy endpoints via Microsofts DHCP server.

Document created by gman on Mar 4, 2015Last modified by gman on Mar 4, 2015
Version 2Show Document
  • View in full screen mode

This can be done by using DHCP option 157 using a standard DHCP server on the network.


Here is how to configure Microsoft DHCP server to support the (pre-Icon) LifeSize endpoint auto configuration feature over DHCP in conjunction with a config file stored on a HTTP, TFTP, or FTP server.


1. Open the DHCP administrative tools applet:



2. Make sure the server name is highlighted in the list and choose Action -> Set Predefined Options...:



3. Click the Add... button:



4. Fill out appropriate details, the only mandatory choices here are that it must be “String” Data type, and Code must be “157” but otherwise the Name and Description are for your reference, and click the OK button:



5. Configure the option according to how you want it set up; refer to the DHCP section starting on page 35 of the user / administration guide for all of the options.


  • The one shown above as an example would retrieve a .cfg file with the MAC address of the endpoint as its name with the colons replaced by underscores, from the HTTP server at IP address x.x.x.x (eg: 00_11_22_33_44_55.cfg)
  • There are many other options for naming, server type, and for configuring multiple possible config files to be attempted to be retrieved in order, shown in the guide.


6. Finally click OK, and you’re done.


The config file itself is simply a list of autoshell (CLI) commands, so you can write your own using CLI commands which are appropriate for what you want to do (for which you should refer to the CLI (Command Line Interface) full manual , or, if you prefer, you can use the exported config from a “template” codec that you have exported and edited to remove any commands or settings that you don’t want to be in the config file (for example, names, IPs etc).