Driver Feed for Non-Dell systems
Managing non-Dell systems with the K2000 can be hit or miss. you should be able to feed in drivers for non-dell systems, even without the other manufacturers support.
Kace users could submit model specific driver packages to a temporary Kace FTP site, and Kace or other kace users could test and validate the drivers.
Once validated, the drivers could be included in the driver feed library alongside the existing Dell systems.
I have many great Lenovo notebook Driver Packages (T500, T510, T520, W520 etc...) I would love to share, but could use some working HP Desktop Driver Packages (like the 6200ProMTPC).
Sounds like a win/win.
Researching ways to integrate the ITNinja community, and this may be one of the big draws. We’ll look into it.
Ray M commented
I have this feature currently working. Its working out of the PETEMP share but would love if KACE provided access to some of the shares or helped us do some dev work to get the K2 working best for unique environments.
Wayne Wescott commented
They made it simple enough, it seems, here:
You will of course need to login with your Quest account to access the article. Basically, run the driver_feed_discovery_tool.vbs from your K2000's drivers_postinstall\feed_tools folder and it tells you the path you need to create and add your drivers to. These drivers are then pulled from as if they are part of the driver feed in mid-level tasks of your imaging process.
AdminCorey (Admin, Quest KACE) commented
The article is still relevant and following it will allow the surface 4 drivers to be injected.
Is there an update to Article 111333? We want to include Microsoft Surface 4 to our mix and some of the files indicated in the preceding article do not exist in the K2000 v3.7.120251.
Keith Botelho commented
I also think that is a good idea. I have a HP house and would not mind contributing to the driver share.