Custom driver before generic
Hello there,
I'm trying to get custom drivers to install rather then generic ones. With the driver harvest tool, it seems to only grab drivers that are unique, and not covered by windows generic drivers. This is also a problem with deployment. It looks like the kace system only uses drivers from the library for devices that dont already have drivers, the rest are covered by windows generic drivers.
I would rather have the updated drivers made for the hardware then the generic windows drivers.
I want to know how to get custom drivers to install before the windows generic ones with scripted installs.
I'm trying to get custom drivers to install rather then generic ones. With the driver harvest tool, it seems to only grab drivers that are unique, and not covered by windows generic drivers. This is also a problem with deployment. It looks like the kace system only uses drivers from the library for devices that dont already have drivers, the rest are covered by windows generic drivers.
I would rather have the updated drivers made for the hardware then the generic windows drivers.
I want to know how to get custom drivers to install before the windows generic ones with scripted installs.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
cblake
13 years ago
You could install them as Postinstall tasks to ensure they run after the generic drivers.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
