We're a dept. on a campus with a central dhcp server, and I want to ask the admins about setting up dhcp for pxe boot for k2000 imaging. Right now, I have a few KBE boot disks with static addresses, but that's pretty limiting. I've never configured a dhcp server, so I want to make sure I know what to request before I bother them.

We already have our own subnet for our department, and a dhcp scope set up with 50 addresses for windows laptops to use from that subnet. All LAN, no WAN. Can we pull from the existing scope for pxe, or do we need a different one that is only for the pxe boots?

If I give them the info for Options 66 and 67 per the K2000 3.4 Admin guide, should that be enough info for them, or do I need to provide something else?


0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


Be careful creating and implementing 66 and 67 at dhcp server level, implement at the subnet level.  If you have older xerox printers they read the pxelinux.0 file and print it at bootup.

Answered 07/16/2012 by: SMal.tmcc
Red Belt

  • We split the bad xerox'x off to a different vlan so now we have PXE on all subnets. Word of wise put a PXE password on the boot.
Please log in to comment



Thanks for the responses. I'm still waiting for the dhcp admins to get back to me. In the meantime, any thoughts on pulling IPs from the same scope we already have for our laptops? Or were you saying before that it should be OK as long as we put a password on the pxe boot? Thanks.

Answered 07/17/2012 by: tpr
Fifth Degree Brown Belt

Please log in to comment

We set the machines to boot HDD 1st and PXE 2nd in bios.  When you hit f12 and choose pxeboot it goes to the Kace PXE boot menu.  We place a password on this so no one but IT can choose anything but boot from hdd from it just in case. (boot manager password).  When we create a boot action in the k2000 for the machines to image with, we also do a k1000 push to use the cctk and change the boot order to pxe first and the machines take off and image when they reboot, I switch the boot order back in a post task.

The password in another way.  Years ago.... when I worked with Zen a friend of mine who used to work for GM rebooted a bunch of windows servers after patching them, they never realized the servers boot order had pxe first.  Someone entered the options 66 and 67 in as dhcp server level options instead of subnet options, the servers checked in with the zen server and started imaging xp to them.

Answered 07/17/2012 by: SMal.tmcc
Red Belt

Please log in to comment

option 066 (use name) IE ikbox.tmcc.edu

option 067 according to page 37 of http://www.kace.com/support/~/media/Files/Support/Resources/Documentation/K2000-Admin-Guide-v34.ashx should be kbox2000.0 (sorry!)

 option 244  (create and name it "kace option 244") put in IP of ikbox. 

Answered 07/16/2012 by: SMal.tmcc
Red Belt

  • Option 67 should be k2000.0
    I prefer using the IP address of the K2 or RSA for option 66.
    For other dhcp servers, option 66 is next-server and 67 is bootfilename.

    Lead L3 Enterprise Solutions Engineer, K2000
    If my response was helpful, please rate it!
  • That is interesting Cory, I have had pxelinux.0 for my option 67 without problem. I looked in the manual and it shows one different from the one you and I mentioned.

    This is from page 37 of the 3.4 guide.

    Setting up an external DHCP server
    If your network already has a DHCP server that assigns IP addresses, configure BootP (Boot Parameters)
    Server and Client settings to allow Windows clients to locate the appliance and download the bootstrap file.
    To configure network boot parameters on a Windows DHCP 2003 Server:
    1. On the DHCP Server, open the DHCP Manager by clicking Start > Programs > Control Panel >
    Administrator Tools > DHCP.
    2. Configure client redirects as follows:
    • For WAN set up Windows client redirects on each scope, click the name of the scope, click Scope
    Options, then right-click and choose Configure Options.
    • For LAN (without scopes) set up redirect for all Windows clients, click Server Options, then right-click
    and choose Configure Options.
    The Configuration window appears.
    3. Click the General tab.
    4. Click the Option 066 check box, and enter the FQDN or IP address of the local appliance (either the
    K2000 appliance or RSA instance).
    5. Click the Option 067 check box, and enter kbox2000.0 for the bootstrap file name.
    6. Click OK to apply the changes and then close the DHCP Manager.
    The DHCP server automatically redirects PXE compliant Windows clients to the appliance the next time they
    start up while connected to the network, the clients download the bootstrap file, and use the environment set
    up by the K2000 administrator to boot.
Please log in to comment

I forgot to mention that I don't know if they're running MS or Linux DHCP servers. SMal, the 244 option is only necessary if they're using Linux, correct?


Answered 07/16/2012 by: tpr
Fifth Degree Brown Belt

  • Yes, we had some Novell Linux servers around, that was why we had it, all MS now. I also noticed it gave the client an IP vs DNS name if the client had problems getting DNS info.
  • OK, thanks. I just sent a preliminary message to the dhcp admins.
Please log in to comment
Answer this question or Comment on this question for clarity