KACE Product Support Question

Driver Support

06/20/2012 3008 views

I am in a bit of a cloud. I thought that drivers located in your driver share \\x.x.x.x\drivers\windows_xp would be applied when deploying a windows xp (32bit) image to a computer. I uploaded the drivers from the test PC with driver harvester to the driver share and have then recached drivers. I have even built a new boot environment but whenever I do the boot up into windows, the system always prompts for the drivers for the devices (sound/network/video).

Are there additional steps I have to take so that these drivers are installed automatically with deployment??

Answer Summary:
0 Comments   [ + ] Show comments


All Answers


The drivers folder is only for scripted install.  However, you can add the drivers to the drivers_postinstall directory and then use the driverfeed workaround to inject the drivers as a midlevel.  This is much easier than adding drivers for all your models into an image.


See: http://itninja.com/blog/view/driverfeed-workaround-for-k2000-v3-4



Lead L3 Enterprise Solutions Engineer, K2000

If my response was helpful, please rate it!

Answered 07/06/2012 by: cserrins
Red Belt


Is this a scripted install or a caputured image you are deploying?

Answered 06/20/2012 by: SMal.tmcc
Red Belt

  • captured image I am deploying.
  • I believe that directory is for scritped installs, not sure though. try this link

    A trick I found with windows 7 that may work for you is: I cast my syspreped image to a machine and if any drivers are missing I add them to my master and recapture it. I place the driver directories in a folder under windows\inf I called tmccdrivers\model when windows 7 comes out of sysprep it looks at windows inf and all subdirectories for drivers somewhere in the process and adds them. I have one master admin image I can push to the 18 different computer models (pcs and laptops) and never have to add a driver.
  • Thats what I'll probably end up doing is adding drivers and recapturing the image.

Go here. Are you on 3.4?


The path is \\k2\drivers_postinstall.

Answered 06/20/2012 by: dugullett
Red Belt

  • yes i am running 3.4, i'll check it out
    • Make sure to “call driver_feed_mid_task.batâ€. I looked over that and it drove me crazy for about a day.

Don't be a Stranger!

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

Sign up! or login


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