Hi, can anyone suggest an effecient method for handling drivers for WIM images using KACE for hardware that is not DELL? We have 23 different computer models covering desktops and laptops (most are just newer versions of the previous model, e.g. HP dc7800 and dc7900). The drivers we need to ensure work post-build is video, network, and sound but I can't download 207 individual driver packages (that's what it would work out to be covering Win7 x86 and x64 and XP x86). Even if I could spare a week to do that, I then have to put the drivers into KACE taking significant time and then create installation tasks for each individual hardware item. Even if I could be bothered doing all of this, the person who ends up building the PC is going to have to know what hardware is in each PC to deploy the right image tasks.

Surely there's an easier way? When it comes to re-maging 500 PC's at once, how will we ensure we deploy the right one to the right PC? This is a problem which at the moment I can't see a way to overcome :(



Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



Take a look at using the driverfeed workaround in 3.4 for .wim images.



You can setup other manufacturer directories at the root of \\k2\drivers_postinstall.

Use the model_report.exe file included to get the path of where drivers should be installed.

Answered 05/14/2012 by: cserrins
Red Belt

  • This is what we use. We are a Lenovo/HP shop. There is some initial setup, but once it is done it works great.
  • Thanks, the driver feed is working for video card which I'm using as the test but the driver harvest didn't put the drivers in the drivers_post install folder, it put them in the Drivers folder and created a new folder called 'driverharvest'. Then to get it to work I copied them into a new folder I created with the exact model of the PC which was put by model_report.exe. Does what I said just make sense? I'm not sure but KACE is now using the drivers during the WIM build but they're definitely not in the post_install folder.
  • The driver harvest isn't going to get every driver. I manually added all of mine.
  • Cheers, I will have to use the Driver Harvest otherwise I have to download 270 unique driver packages :( I'll mark this as answered. Thanks again.
Please log in to comment