KACE Product Support Question

Latitude E7480 and Kace K2100 deployment

06/15/2017 2356 views
Hi Guys,

We're running the Kace K2100 deployment solution (v4.1.182)

Yesterday we received the new Dell Latitude E7480 (with Skylake processor for windows 7 support)

Only when i'm booting the KBE it's unable to create the network shares required. Thus failing the startup of the KBE boot.

I followed this: 
but it seems that the KBE boot still won't get the correct drivers.

Anyone else possibly fixed this issue?
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


Received this from Quest support I wasn't using the ADK for Windows 10.

Issue is resolved 

Thank you for contacting Quest, I have taken ownership ofyour Service Request Number 4063911 - Unable to PXE boot Dell Latitude E7480.


I recommend building a new KBE based on ADK for Windows10 and the latest KBE Driver Pack for WinPE 10. This KBE, while based onWindows 10, will image Windows 7, 8 and 10. We've just found newer model systemsand hardware have fewer issues with this type KBE. This KB article will explainthe process.




Answered 06/15/2017 by: anonymous_135268
White Belt

Community Chosen Answer


Have you added the LATEST drivers to the appropriate kbe_windows_x64 or the kbe_windows_x86

in the share directory on the appliance.

Go to https://support.quest.com/kb/111717 to download the drivers. Use your Support credentials to log in,

then select KBE Driver Pack.

Navigate to the k2000/driver_packs folder to download the appropriate WinPE driver pack.

Manually copy the drivers to one of the following directories:

\\Kace Appliance\drivers\kbe_windows_x86

\\Kace Appliance\drivers\kbe_windows_x64

Re-cache the drivers. See Re-cache drivers.

Answered 06/15/2017 by: akmagnum
Red Belt

  • Yes, I forgot to add that to the question.

    I have downloaded the latest KBE drivers from the dell site (which you linked)

    And afterwards recached the drivers and created a new KBE boot

All Answers

Are you PXE-booting from the internal NIC or are you using a USB-C Dock? We had issues when using a dock for Windows deployment. After booting into the KBE you had to unplug the dock and plug it back in, enter "startnet" in the command line window in order to run the whole process including mounting the shares again.
Answered 06/15/2017 by: CTRL+ALT+DEL
White Belt

  • I was using the Internal NIC. But Quest support helped me on this issue. It's fixed now
  • I noticed this one too back with the USB-A 3.0 dongles... way to go for including drivers on the device themselves (this should have been happening for a long time if you ask me), but it causes problems for things like imaging. If only there was a countdown of some sort, where if you haven't read the files off the USB disk in, say, 60 seconds, it reverts back to the NIC drivers instead of Mass Storage.


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