/build/static/layout/Breadcrumb_cap_w.png

Non Dell drivers not installing during deployment

Hi

We are using the KACE SDA 7.0.357 virtual appliance.

The models we wish to deploy to are HP. The Driver Feed Builder 3.0 utility has been used on the HP models to upload the required drivers. However when we deploy using our system image it deploys fine but doesn't install the drivers. If i download the driver folder from the drivers_postinstall directory to the local machine and manually update the driver pointing at this directory they install fine so the drivers are not the issue.

Within the system image, does the option Use driver feed (only with sysprepped images) need to be checked? My understanding was that this is only required to get Dell drivers from the library.

Thanks in advance

Alistair


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Channeler 4 years ago
Red Belt
2

I needs to be checked, otherwise, the drivers_postinstall folder will be ignored.

When the Imaging job is done, go to the imaged device, via Windows Desktop, get the dism.log from c:\windows\dism.log (Not the one from c\windows\logs\dism\dism.log).

That log generated by Windows will tell you what drivers were injected and from where.

Also, Why are you using a third party tool to obtain HP drivers, when they are posted here:
https://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html

I'd rather get them from there, unless the device you are looking to image is not listed there.

(Driver feed builder works fine, but it's based on Double Drivers... I'd rather get them from the manufacturer, and unpack them into the correct folder, and recache all drivers, don't forget to do that).
(not mandatory for drivers postinstall but I always do it).


Comments:
  • Thank you, that makes sense, I will enable and redeploy.

    The reason we are using the Driver Feed Builder 3.0 utility is because some of the machines don't have some specific Windows 10 drivers. Someone has installed Windows 10 on all the reference machines along with required drivers so its easier to use the tool.

    Thanks for the advice - AllyRussell 4 years ago
 
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