Testing out the driver feed with a e6410.

Steps taken:
Enabled the driver feed, downloaded the selected driver packs for the 780, t5500 and e6410 (our usual dell models).
Confirmed they are in the drivers_postinstall folder.
Re-cached driver share
Scripted install with only the basic sysprep file. Only with Create single partition, format C and install windows 7 mbr. no post installation tasks

The system boots up, but no drivers were installed from what I can tell in device manager.

Any ideas?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Talking with support and it seems there may still be a few issues with the driver feed. patch should be out in the near future. Back to my manual post install tasks. :)
Answered 04/08/2011 by: ngbrown24
Blue Belt

Please log in to comment
I have this exact same issue. I talked with support and they said that I needed to rebuild the KBE after changing drivers, which I tried and it didn't work at all.

I do exactly the same with you. When you say 'basic sysprep file' you mean a basic answer file right?
Answered 05/03/2011 by: dogfish182
Orange Belt

Please log in to comment
You might try this patch:

KBOX 2000 Driver Feed patch is available - Knowledge Base - Dell KACE™
Answered 05/13/2011 by: brucegoose03
Third Degree Black Belt

Please log in to comment
Thanks for the post. I just applied this patch and have a question. In the notes for the patch, it says:

We have a patch that which moves the non Plug and Play (PnP) driver causing the issue from the driver share to a new share called drivers_postinstall. In this location, the files can be used to create a unattended driver installs

Can someone clarify if this means we should be using the files in these locations to create post-installation tasks? If so, does anyone have any tips on how to do this with the driver files on the "drivers_postinstall" share on the KBOX 2000?
Answered 05/17/2011 by: asanchez
Orange Senior Belt

Please log in to comment
We are having similar issues and I'm looking at applying this patch, are their any known issues caused by this patch?
Answered 05/18/2011 by: jrscribner
Purple Belt

Please log in to comment
I started migrating our pc images into the K2000, after struggling with manually uploading drivers, i started messing around with the Driver Feed section and it seems to work abt the same as manually uploading.

I am working on windows xp images and they seeems to work alright my biggest problem is that Video Driver will never install properly for the optiplex 980. I will try E6410 and E5500 to see if the problem exist on those models...

I used the basic sysprep file from kace kb section and works fine.. again all this is in Windows XP
Answered 05/19/2011 by: blizzster
Senior Yellow Belt

Please log in to comment
As far as I can tell the driver feed does nothing. You get an installed network card on windows 7 and then nothing else. The drivers simply never install. Being that the driver feed never contains the exes/msis whatever, you can't use the files on the post_install dir to build post install tasks. the only good it does is makes things convenient if you want to manually install the drivers from device manager. Which is terrible.

Really disappointed in the driver feed so far, I feel like I must be missing something, but it seems essentially worthless?
Answered 05/24/2011 by: dogfish182
Orange Belt

Please log in to comment
Guys, the driver feed works great. I have used it with only a minor issue until the patch was added. Now the patch is giving me some grief but I'm figuring that out. Here are some things that will help:

Blizzster; You need to run your video drivers as a post install task. The main reason for this is because the driver feed on it's own does not install drivers that require a setup.exe to run. To fix your issue, do the following:
1: Download the file for the video driver from support.dell.com
2: Extract the file on your local PC but don't install it. You can do this on your desktop without having to do this on the client PC
3: Look for the readme.txt file. This will usually include the switches for the setup.exe so you can run the install as a silent install. usually setup.exe -s on most Intel drivers
4: Open the file where you extracted the files. Select all of the files within that folder, right click and make them a zip file.
5: Upload that zip file to the post install application task
6: Add the setup executable name and the appropriate switches to the command line section of the post install task
7: Save it

Dogfish: If you are using images instead of scripted installs, the driver feed will not be used. During scripted installs, the driver feed is added or injected as an additional path for PnP or Plug and Play to search for drivers. In an image, you must add the drivers you need for your image to your sysprep folder and point the sysprep file to the correct path of the drivers on your system.

If the driver feed is not installing drivers, did you make sure to recache your drivers after you downloaded them from the driver feed page? That was something I forgot when I first got my Kbox.
Answered 06/09/2011 by: cball79
Yellow Belt

Please log in to comment
Well, with the patch on the driver feed \\KACE\drivers only really has the network/wireless drives for a feed. You have to build a little post install, or a run once script to call the \\KACE\drivers_postinstall into the image. I'm hoping they get the driver feed fixed and it'll do all the major drivers. Still, I like rebooting my windows 7 images and doing a driver pack at the end. Working on perfecting windows xp (damn you legacy users) and hoping to do something similar. If you can pull it off, fully scripted (modular) images is the only way to go!
Answered 06/15/2011 by: ngbrown24
Blue Belt

Please log in to comment