Driver Feed Workaround and drivers
The driverfeed has been updated in 3.4 and now includes this workaround automatically when deploying scripted installs, so you can remove any previous tasks you had assigned. However, the process is not automatic for images, so you can still use the tasks provided here.
If you are deploying Windows XP, you might still want to use the driverfeed workaround with scripted installs as well. The latest version of the tasks now looks at the drivers that are copied over to the workstation and identifies all the directories that have an .inf. These directory paths are then inserted into your XP answer file (scripted install or image). If you have an image, they are also injected into the XP registry “DevicePath” entry. This means that many drivers are installed during the PnP process and ready for you before post installs start running. The drivers that are not picked up should be during the postinstall task to run dpinst. It is possible that some drivers will need a reboot, and even with this method, some drivers will not install at all.
The drivers_postinstall path has also been changed in 3.4, please refer to the KB Article 1142:
K2000 3.4 Drivers Postinstallation Structure
Refer to KB 1128 if using non-dell systems and would like to setup the correct path:
K2000 Setting up Driver Feed with non-Dell Systems in 3.4
In 3.4, the drivers_postinstall share has a directory named feed_tools that contains a vbscript named Get_Manufacturer_Model_OS.vbs. You can run this script on the machine in question to get the Manufacturer, Model, and OS of that machine. You can also choose to run the new version of model_report.exe to get the 3.3 or 3.4 path needed for your machine.
Note: Many have asked about the combo drivers and how to use them in 3.4. Here are the paths used in 3.4 for these drivers, however, you will HAVE to use the driverfeed workaround tasks even in scripted installs for the combo drivers to work.
Download driverfeed tasks - http://downloads.kace.com/support/downloads/k2000/tasks/driver_feed_tasks-3.4.zip
After downloading the file, unzip the contents and you will be presented with:
README – general information
model_report.zip – x86 and x64 version of the script to run on the machine, either in Windows or KBE.
driver_feed_mid_task.zip – This file gets uploaded as an application midlevel task, with the command line: “call driver_feed_mid_task.bat”
install_drivers.exe – Gets uploaded as an application postinstall task to be used with XP images.
so that the conversation will remain readable.