Return
-
Title
How, Why, and When to run the Driver Feed Discovery Tool on K2000 Version 3.7.1 or later -
Description
From time to time a new model of a machine will become available and the WMI model identifiers do not fit the standard model. When this happens the Driver injection fails to find a matching path in the \\K2000\drivers_postinstall share resulting in no drivers being injected into the image.
As of K2000
3.7.1 the modelcatalog is downloaded every night so new machines can be added without the need to reinstall the copy_drivers script. Once a problem has been reported and fixed. it will be available to all clients the following evening. This new method will cut down dramatically on the impact of a misidentified machine as once it is reported, all users will get the update. -
Resolution
If a syspreped image or Scripted Installation fails to find and inject the drivers installed for Dell model systems installed in the K2000 Driver Feed:- Boot the target machine to the Operating System (not the KBE)
- Run the Driver Feed Discovery Tool (instructions below).
- Compare the path it displays with the installation location of the corresponding driver feed package.
- If the path shown by the Driver Feed Discovery tool and the path in \\K2000\drivers_postinstall do not match, then you will need to open a ticket to support and provide a screen shot of Driver Feed Discovery Tool output or its logs.
How to Run Driver Feed Discovery Tool ( K2000 version 3.7.113224 or better )- Update the Driver Feed Discovery Tool Catalog.
- On the K2000 go to Library > Driver Feed > Driver Feed Settings
- Make sure "Enable Driver Feed" is checked.
- Click "Check for Updates"
- Wait until the "Driver Feed Status" returns to "Completed"
- Boot the target machine to the Operating System (not the KBE)
- Navigate to, or map, the \\k2000\drivers_postinstall share to the target machine as a network drive.
- Copy the feed_tools folder over to the desktop of the local machine.
- Double click on the feed_tools folder you just copied.
- Double click on the Driver_Feed_Discovery_Tool.vbs script
- Capture the results.
NOTE: since the Driver Feed Discovery Tool uses configuration files contained within the feed_tools folder you must copy the entire folder and its contents to the local machine, and run it from the local copy. You will not have execution rights to run it directly from the network drive.