Software Question

Trouble adding a driver to K2000 KBE

09/02/2015 3785 views
I'm trying to image a (new model to my organization) Dell Optiplex 3030 AIO with a pre-existing x86 k-image. 

I followed these instructions to determine that the x86 KBE was missing a network driver for the 3030 AIO. I was able to fully mount the x86 KBE after mounting the driver locally, and proceeded to image, so I know it's the correct driver.  

But I'm missing some really crucial, obvious step about *where* to insert this driver correctly to make it available for the K2000 for loading the x86 KBE. 

Here's the network driver (from driver CAB from Dell Enterprise) that works, sitting on my desktop...:

Here's our K2000 drivers share:

If I try to mimic what is already in place, I guess I'm supposed to put the folder "7TRHR_A00-00" into...what? "dell-winpe3-a15.2" inside a "network" folder like below?

And then I recache all drivers...yet I continue to be unable to mount the x86 KBE on this Optiplex 3030 AIO. 

I know I'm missing something obvious. Please help! Thanks in advance.
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

You need to rebuild your KBE after recaching, recaching alone won't do it.  At least that was my experience.
Answered 09/02/2015 by: nheyne
Red Belt

  • Aha! I don't know how we've managed to go this long without having to rebuild any KBEs (my predecessor built current ones)!

    Do you have any feedback on my driver placement within \\K2000\drivers? Does it matter?

    Thank you!
    • I think you're good, it's recursive so as long as it's in the kbe folder, you should be fine.
      • Awesome. I appreciate it! Now time to learn how to build a KBE...
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