When you manually recache drivers into the K2000 KACE server do the drivers get pushed to the image from there or am I missing a step after the recache?

I'm waiting for my manager to renew our KACE license and we just got a new laptop model I need to image. I uploaded the drivers for that specific laptop into our server but yet the image process fails to apply the image. We've had images fail like this in the past and we've just had to add the drivers manually, but I can't remember if I'm missing a step after recaching the drivers. I can see all the new drivers I added in the Drivers tab which confirms they were uploaded to the server successfully but still no luck.

Side note: I'm still able to image previous computer models even with the expired license, I just can't get this new one to work. I'm also not sure if the license issue is what's causing the new drivers to not be pushed out.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 8 months ago
Red Belt

What error message do you see?
It sounds that the KBE you are booting up does not contain the nessesary drivers for the laptop in question.
What version of the SDA do you use?

The first I would do is:
1. clean out all subfolders (the subfolders itself are R/O, so you cannot clean out them directly) under \\sda\drivers
2. download the latest (Dell) driver pack from here: https://support.quest.com/download-install-detail/6125141 (for W10 and W11)
3. put the subfolders from 2. in \\sda\drivers\kbe_windows_x64 (and x86 if you still use 32Bit) (no need to have kbe_windows_x64\kbe_windows_x64)
4. Recache
5. download the latest Media Manager from your appliance
6. build a new KBE
7. Retry.
If fails:
8. download the drivers from the vendor (storage and network, sometimes also video drivers needed), unpack the .exe (use 7zip or similar to unpack the exe) and exctract the driver folder from the deployment package and put it into a subfolder of the kbe_windows_x64 (or x86 depending on the architecture)
repeat 4,6 and 7.
If you are stuck, you can contact support. 

  • Agreed! I had same issue and downloading the latest Dell driver Pack and recreating my KBE fixed it. I will add that injecting the drivers from a local directory instead of the SDA improved our client PCs kace boot environment speeds. I did this by selecting the Driver tab in the SDA media manager, selected the "Inject drivers from a local directory", browsed to the WinPE10 folder and selected the x64 folder. - josed558 8 months ago
Posted by: Hobbsy 8 months ago
Red Belt

Drivers are deployed to the system after the image or scripted installation has completed I believe, so the act of recaching drivers is more about making the SDA catalog the drivers it has so it knows what to use.

Post deployment the SDA makes a wmi call to the device to establish what make and model it is. It then uses that information to lookup the correct drivers to deploy from the driver share. Hence you need to recache so the SDA has access to all drivers.

  • well, the recache just updates the database of the uploaded drivers for building a KBE. Recache does not impact any mid level or post level driver tasks. - Nico_K 8 months 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


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