/build/static/layout/Breadcrumb_cap_w.png

Adding DBAN to K2000 BE

I've found a bunch of old guides on how to add DBAN to the K2 but none of them seem to be even slightly accurate anymore.  Generally I can reverse engineer stuff like that but I'm not having any luck figuring out how to use the KBE manipulator or the Media Manager to upload a custom BE anymore.

Anyone have any advice or know of an updated guide?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Channeler 6 years ago
Red Belt
1
Since version 4.x , the KBE Manipulator lost the ability to upload custom ISOS. (It was removed).

You will not find any new guides for this at the moment, please read, comment and vote here:

https://kace.uservoice.com/forums/82717-sda-k2000/suggestions/18800059-make-the-isos-non-windows-work-again

I believe it will be back at some point in the future, because the status says Started.

Comments:
  • 6.0 will give the ability to boot a specific KBE(s) from ISO, so the feature to upload the ISO in KBEM will return!!! However, we will also have tasks that can be imported that allow you to do a wipe with Custom Deployments. See https://www.itninja.com/blog/view/custom-deployments - cserrins 6 years ago
    • Updated version of KBEM was released to allow upload of custom ISOs again. This does not guarantee that all ISOs will pxe boot successfully though. Also, you must be on 6.0 for it to work. After uploading the ISO, go to the boot environment detail page of that ISO and check the "Boot from memdisk option" This will only work with bios/legacy configured machines. - cserrins 6 years ago
      • dban kbe failed upon network team changing pxe settings. I download and install the new kbem, enter the samba pswd, enter the ip address of the appliance, point to the dban.iso and it uploads successfully. I checked the memdisk box, saved.

        I boot okay to the kbe menu, select the dban kbe, enter the credentials and get the following message: Wimboot...ok
        http://(k2000 ip address)/boot/ipxe/313/uefi/boot/bcd… no such file or directory(http://ipxe.org/2d0c613b

        could not boot:no such file or directory (http://ipxe.ord.2d0c613b)

        Selected boot device failed, press any key to reboot the system. - gjhill 6 years ago
      • @gjhill, With version 6.0+ for this to work, you can only use it for legacy machines and on the boot environment detail page you must check the box to use memdisk. - cserrins 6 years ago

Don't be a Stranger!

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

Sign up! or login

Share

 
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