I am running K2000 v3.7.116629.  I am trying to do a WinXP scripted install on a bunch of older Dell Latitude D-series laptops.  These are all old computers that we want to donate to local school and community organizations.  They've been wiped clean, but I need to get a base OS on them so they're useful (the places we will donate to have no IT staff).

My boot environment still has drivers for these systems, but it looks like the D-series models have been removed from the driver feed so after doing a scripted install they are missing a ton of drivers.  I tried to readd the driver feed for these systems but it does not seem like it exists any longer.

I tried looking to see if the old driver packs were still around somewhere but didn't find them.

Can someone please help me understand what I need to do in order to get the proper drivers loaded back into my K2000 so I can successfully do scripted installs on these computers?
0 Comments   [ + ] Show Comments


Please log in to comment


if you have a copy of the drivers still you could harvest them from an existing laptop, I have had to do this on a couple when the drivers were yet to come online for k2000.

I got the Driver Harvest Tool here on IT Ninja once you have harvested the drivers, you will need to rebuild the driver cache. Hope this helps...

Answered 10/21/2015 by: glen.craig
White Belt

  • Ugh, thanks for your suggestion but I was hoping it would be easier. I don't have a laptop with an OS on it. I wonder whos bright idea it was to discontinue support for laptops that are only 5 years old.
Please log in to comment
KACE supports only systems in their life cycle.
From my point of view it is a bad idea but it is like it is.
You can use the driver.cab from the questioned model from the dell page, extract the drivers and put it into the driver feed.

Driver cabs are found here:

Then go to \\k2000\drivers_postinstall\feed_tools\ and run driver_feed_discovery_tool.vbs on the questioned machine. It shows you where to put the drivers.
If you have a Latitude D630 you need to put them for Win7x64 here:

If you have the driver.cab for other systems you can do it similar.
It is the easier way than using the driver feed builder/driver harvester, but if you don't have such driver.cab this would be the only way.
Answered 10/22/2015 by: Nico_K
Red Belt

  • I see, also the D series (which was replaced 2008 by the first E series) has been removed from the page.
    It looks like that all supported OS for this series are EOL now.
    So you may really need to use
    http://www.itninja.com/blog/view/driver-feed-builder to create the feed
    (it is always the last resort)
Please log in to comment
> donate to local school and community organizations.
Whoa!! HUGE licensing implications here, my friend, as well as issues such as where will the machines look for OS updates - your WSUS server?

Send them out wiped. They may well not have IT staff but anyone can slip in a Windows DVD and click through an OS installation.
Answered 10/22/2015 by: VBScab
Red Belt

  • Huge licensing implications, as far as what? The systems all have OEM Windows licenses, and that's all that's on them. Obviously we would not configure systems we're giving to someone else to look for updates via WSUS, I figured that was self evident.
    • Well... it technically is against Microsoft EULA to deploy an OEM OS as a mass deployment. Other than that... :D
Please log in to comment
Have you *seen* some of the stuff people post here?!? Ha, ha, ha!
Answered 10/23/2015 by: VBScab
Red Belt

Please log in to comment
Once a .cab has been uploaded to the K2000 service page, it hasn't been removed.  If it isn't in the driverfeed now, it never was there.
I kind of remember doing something special with 3.4 with the D-Series and implementing the "combo" pack because these drivers were not available any other way.  Of course, that process doesn't work anymore.
Answered 10/23/2015 by: cserrins
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity