Systems Deployment Question

Why does the Kace image deployment not work on the M6600 dell laptops?

05/30/2012 3713 views

When you try to network boot to the dell KACE deployment setup, the M6600 never is able to get an IP configuration in order for the KACE to work.

The internet is working fine, the cable works, several different M6600 laptops have been used. The drivers have been uploaded and cache'd into the KACE system.

As far as i can tell it is a hardware compatability error rather than a software error. I am looking for a way around this problem, so I can capture and deploy M6600 images.

0 Comments   [ + ] Show comments


All Answers


Is the KBE booting, just giving an error that it cannot connect to the k2000 once it boots?

If the KBE isn't even booting then my first guess would be something in the BIOS settings.

If it is booting and you uploaded the drivers to the KBE folders (kbe_windows_x86 and/or kbe_windows_x64), after re-caching the drivers you have to create a new KBE using the media manager.  The KBE is a customized Windows PE boot image and the tools to create or update them are only available in Windows.  The K2000 server is not running a Windows OS.

Answered 06/01/2012 by: ncsutmf
Second Degree Green Belt

  • Something I forgot to mention, after the new KBE is created, you either have to specifically boot to it, or make it the default. We typically test a new KBE for a while before setting it as default and after a period of time delete any older ones. When deleting you have to delete the KBE under Deployments first and then the KBE under Library, Source Media to free up the disk space used by it. You cannot delete a KBE if it is set as the default.
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