/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Driver feed for non listed Dell systems

10/29/2012 7657 views

Hello,

We are deploying Windows 7 via scripted installs via the K2000.  We have Optiplex 745's and Optiplex GX520's in our environment, as well as newer machines.

Optiplex 745's and GX520's do not have a driver feed within KACE for some reason.  I did some looking around and found some articles concerning this :

http://www.itninja.com/question/driver-feed-workaround-and-drivers

http://www.kace.com/support/resources/kb/article/Driver-Feed-Builder

http://www.kace.com/support/resources/kb/article/K2000%20-Setting-up-Driver-Feed-with-non-Dell-Systems-in-3-4

I called support about this, and they recommended I just download the combo drivers here: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx and upload them via the driverfeed_builder.  This seemed like it would work just fine, and I know the combo drivers will work as I used them in my last scripted install build via Altiris.

The driverfeed_builder.exe asks for IP's, credentials, etc, then at the end it has a section where you can browse for .exe's.  This is a problem, because the combo driver folders don't all have .exe's in them.  Also, some folders have multiple .exe's in them.  If I was to skip a folder because it has no .exe, I would lose that driver.  

How do I upload combo drivers to the K2000?

Answer Summary:
I simply logged on to the Samba share, created a folder path in \dell\Operating_system(arch)\combo\Desktop,, then dumped my combo drivers in to it. I then created an application mid level task as listed in the read me: driver_feed_mid_task.zip – This file gets uploaded as an application midlevel task. The runtime environment is K2000 boot environment (Windows), with the command line: “call driver_feed_mid_task.bat†I then created another scripted install build, and put this in it. I left this out of my standard build. If the drivers are in the driver feed, we run the standard build. If the drivers are missing, we run this combo driver build. You don't need to use the driverfeed builder.
0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

3

I just got this working.  I simply logged on to the Samba share, created a folder path in \dell\Operating_system(arch)\combo\Desktop,, then dumped my combo drivers in to it.  I then created an application mid level task as listed in the read me: driver_feed_mid_task.zip – This file gets uploaded as an application midlevel task.  The runtime environment is K2000 boot environment (Windows), with the command line: “call driver_feed_mid_task.bat”

I then created another scripted install build, and put this in it.  I left this out of my standard build.  If the drivers are in the driver feed, we run the standard build.  If the drivers are missing, we run this combo driver build.

 You don't need to use the driverfeed builder.

Answered 10/29/2012 by: edwimb
Third Degree Blue Belt

  • Could you post your .bat file, or at least the structure that you used?
  • jknox, it's the bat file and structure used here, as I linked above http://www.itninja.com/question/driver-feed-workaround-and-drivers

All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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