Best Practices Question

KACE2000 PXE Boot Not Working

08/11/2014 3533 views


I have my K2100 live on the network and DHCP has been turned off on the K box as we have another server dealing with DHCP requests.  Settings have been put in place to theoretically direct any PXE boot requests to the K box.

Have enabled pxe boot on pc (Dell OptiPlex 990 with BIOS version of A13) but despite this K box does not load to menu to be able to select an image to be deployed.

I know there was an issue with OptiPlex 990 systems not being able to be booted via PXE but thought A13 BIOS and above was fine.

Any other reasons for this not working?

Was unsure about what boot file to specify on DHCP redirect so that may be issue



Answer Summary:
0 Comments   [ + ] Show comments


All Answers

Do you have option 66 and 67 selected in DHCP scope options? Boot Server Host Name should be set to your IP address of your K2000.
Answered 08/11/2014 by: LBarclay
Orange Senior Belt

  • Hi, yep option 66 and 67 are set in scope and boot server host name is set to ip address of kbox.
    • What did you set for the boot file?
  • Boot file I was confused about so set it to the name of boot environment file which is 990Master, have also tried setting to KBE_x86_34 which is maybe where I am going wrong?
    • It needs to be "k2000.0" (no quotes), give that a try and see if that helps.
  • Thank you, will give that a go and report back, much appreciated
  • Thank you that fixed it, God what an idiot, it was even in the manual I must have just glossed over that. Kind regards
    • No problems, easily done!

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ