KACE Product Support

After spending numerous hours with KACE support on this issue, we determined that the current version of Harvester is "Broken". There is supposed to be a newer tool coming out with the next Kace patch.

nevermind, I deleted the harvested drivers, recached, and now the scripted install goes fine.

I had the same problem. You would think building a machine outside Kbox and capturing the drivers for 7 would be a good idea, but it isn't. I think it corrupts the HD driver.

I had the same experience and deleted the drivers I collected and recached and now the scripted install is working again.
Was anyone ever offered up a solution for this problem?

Same experience here, Thinkpad T500, Windows 7 32-bit. After backing up and then removing all drivers from the kbox, then re-caching, the install worked. Thankfully this was my first test system.

Instead of re-harvesting the drivers, I added a few at a time into the kbox driver folder, recached the drivers, then tested the deployment until it failed. Eventually, I traced my issue to the harvested driver for the Thinkpad PM Device (power management driver). At this time, it is not clear to me if the issue was with the driver itself or how it was harvested by the tool; this is definitely NOT a "boot-critical" driver as it was installed on the original system well after the OS installation.

This driver does want to install a service (per the .inf file) so likely it will have to be setup as a PostInstallation task... I'll find out tomorrow as I continue to learn the K2000.

Edit - [:(] - spoke too soon, looks like there is another harvested driver is causing the same issue - will post tomorrow when i figure out which one as it just might be common between our hardware...

Seems like the new version fixed a few things. I'm running 3.2.29 and the driver harvest works better. It acutally know where to put the drivers. The first driver harvest utility would dump the drivers in a generic location and I had to move them to the correct OS.

The new harvest utility puts the drivers in the OS you capture them from and then you re-cache. Worked well the other day.

Hmm... same kbox release here (fresh installed last Friday), drivers were always placed in the correct OS folder by the harvest utility.

The drivers causing the remaining issue were Ricoh Smart Media/MMC/MemoryStick drivers. After removal from the kbox repository, and recache, the error message no longer appeared during deployment.

For reference, here are the original INF file names for the drivers that caused issue on my system (they were altered to OEMxx.inf after installation on the OS)

ibmpmdrv.inf - Thinkpad PM Device
rixdptsk.inf - Ricoh smart media driver
rimsptsk.inf - Ricoh memory stick driver
rimmptsk.inf - Ricoh MMC driver

NOTE: the Thinkpad PM device driver and part of the Ricoh drivers were added automatically by Windows Update on first reboot - of course, this will depend on your policy for windows update :)

i cant get around this [right][/right]

i have deleted the harvested drivers and inserted drivers i got using drivermagician in the folders windows_7_x64 and windows_7_x86 but i still get the error?

All- Best practice is to lay down your scripted install BEFORE harvesting any drivers. Allow the machine to check in with Microsoft's repository; then download and install any missing drivers and harvest ONLY what you installed. Otherwise we potentially create the conflict that many of you are seeing. This is most prevalent on Win7 but can also affect earlier OS's- we affectionately call it overharvesting :)

bmatore - make sure you're recaching after you delete things.

overhaversting :)

deleted all the drivers and it worked, Thanks cblake.

Awesome- I'm always glad when it's something easy like that.

I have all default drivers working...basically spripted image runs and deploys Win7, but when I log in there are a few drivers missing. Do I update the drivers on the computer, then delete the default ones on the server and then harvest from the image?

There are 4 drivers that are missing:
Biometric Comprocessor
NEtwork controller
PCI Serial Port
PCI Simple Communications Controller

ORIGINAL: tvaquerano

I have all default drivers working...basically spripted image runs and deploys Win7, but when I log in there are a few drivers missing. Do I update the drivers on the computer, then delete the default ones on the server and then harvest from the image?

There are 4 drivers that are missing:
Biometric Comprocessor
NEtwork controller
PCI Serial Port
PCI Simple Communications Controller


You could install them and harvest what you installed (for future machines of similar hardware), or create postinstall tasks to handle them.

I tried installing them and then harvesting them, but that didn't seem to work. I don't want to create postinstall tasks for drivers that windows can and should automatically find. I open a ticket and was told to go to Lenovo's site and download each of the drivers and then extract them into the drivers folder.

Currently trying that.

I have seen a lot of this lately, people not willing to create post-installation tasks to install drivers and don't get it. It's a better method than beating your head against the wall because of driver conflicts due to the driver-share/driver-harvesting/driver-feed. The only drivers I have in our driver share right now are for NICs. It's way to frustrating to hunt down where driver conflicts are coming from when I can spend a few hours building a post-install task, and since so many of the computers use the same drivers I just re-use the modules. It's really a much simpler task in my humble opinion.


ORIGINAL: tvaquerano

I tried installing them and then harvesting them, but that didn't seem to work. I don't want to create postinstall tasks for drivers that windows can and should automatically find. I open a ticket and was told to go to Lenovo's site and download each of the drivers and then extract them into the drivers folder.

Currently trying that.

How is the best way to remove drivers and re-download? Goto the /drives share in windows on the kbox and delete everything? Then redownload just the nic or etc.. from the drivers feed assuming we have all dell PCs?

Trying to follow this thread with same sort of issue;-

Got a Dell Latitude E6500 and am trying to deploy Win7 x64 to it. However, after booting into KBE and doing the pre-installation tasks, it fails in the beginning of the OS installation-> "... could not install one or more boot-critical drivers. ..."

I assume that we're talking the Win7 drivers here??

IF so, I've launched the Driver Feed function, and installed the relevant drivers (Win7 x64) for this modell. Re-cached and sync'd the RSA, but it still fails!

Any ideas??

Same problem here. I'm trying to put Win 7 x64 on a Latitude E6410. I've tried it with & without the driver feed. Is there a log somewhere that could give more information?

I fixed it! I removed every single drive I manually added (through copying files & driver feed). I then recached the drivers, recreated the boot environment executable (don't know if I had to do that, but I did), recreated my bootable USB stick, and success! I guess KACE got it right the first time[:D]

OK, so I've done a bit of trial & error. Have come up with the following solution/workaround:

When the WIn7 install halts (with the above-stated message), do NOT press ok (or what-ever button) to restart the computer. Rather, ALT+TAB back to the DELL KACE 2000 Deployment client, and go in to the Recover option in the main menu, and start Notepad. Now; open the file: X:\Windows\Panther\setupact.log and check what driver was attempted to load last. Simply remove this from your driver share.


Like itguymike, what caused my installation to fail (with only drivers from Driver Feed), was the Ricoh packages for E6500 x64 - named: R215879 and R230630. Once these two were removed (drivers re-cached!) and RSA sync'd, my installation went like a dream [8D].

Just thought I'd share ...

Kace released a patch about 2 weeks ago to resolve this.

Since then driver feed has been working great!

Haven't got to test if it works for the "over harvest" scenario.

[link]http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1103&artlang=en[/link]