Systems Deployment Question

KBEM in K2000 v4

04/04/2017 1681 views
We upgraded a few weeks ago to version 4 of the K2000. It took us a while to get up and running but now both UEFI and Legacy booting work great. We have been imaging W10 and W7 perfectly as before. The only issue now is with custom KBEs like AVG Boot, DBAN, and Hiren's. None of them work. I tried downloading the latest version of KBEM and re-uploading all the KBEs but no success. I get an immediate error on boot saying : 

"wimboot... ok"
"http://XX.XXX.XXX.XXX/bott/ipxe/112/uefi/BOOT/BCD... no such file or directory (http://ipxe.org/2d0c613b)"
"Could not boot : no such file or directory (http://ipxe.org/2d0c613b)"
"Selected boot device failed. Press any key to reboot the system"

I'm at a lost now. Any help to get this up and running would be great.
1 Comment   [ + ] Show comment


  • hi lan.pham,

    i have the same problem as you. Now in K2000 version 4.1, every KBEs are loaded with Wimboot instead of memdisk.
    here my post :http://www.itninja.com/question/ipxe-menu-kace-2000-v4-1-x-why-to-generalize-the-way-to-load-all-the-isos-with-wimboot-in-bios-mode

    I open a uservoice entry to fix this problem : https://kace.uservoice.com/forums/82717-k2000/suggestions/18800059-kace-2000-v4-1-make-the-isos-non-windows-work-ag

All Answers

Version 4, should still work fine with custom uploaded images that use legacy pxe boot.  Version 4.1 changed how some of the pxe booting worked because of numerous issues with legacy booting.  This changed has made custom KBEs that are not windows fail.  There is a uservoice entry to fix this if you want to vote on it.
Answered 04/04/2017 by: cserrins
Red Belt

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