This driver installer will allow you to utilize the driver EXEs from your manufacturer to install drivers during your task sequences in a scripted fashion. It basically sits in the root directory of a package and looks for any script named XYZScript.xyz(configurable), adds it to its list to run and then runs them in order, showing progress when used with progressUI.exe from the Microsoft Deployment Toolkit (MDT) - The filename of scripts searched for is configurable via a config file you include in the root of the source directory of your package. This process gets you away from having to import drivers into SCCM, keeping your driver sets completely separate per model, making it easy to update individual drivers on a per-model basis and also gives you the ability to install any driver apps along with the drivers instead of handling the driver apps you want later on in a separate task sequence step. The utility is customizable via settings file you include in the same path as the exe, allowing you to "brand" the driver installer with your own company name, as well as have it execute scripts based on your organization's own naming standard.

Note: You can utilize the script found here to assist with extracting the driver EXEs you download from your manufacturer (requires 7-zip to be installed on your system). This is known to work well with HP's downloaded driver EXEs, and may work well for others as well. For Lenovo and Dell, you need to run the initially downloaded driver EXE, which will extract itself out to a location such as C:\Drivers (uncheck the box to run the install when this is complete) - you can then use the resulting C:\Drivers\ folder as that drivers source directory in your package. I recommemd doing this in a VM you dont care about incase you forget to uncheck the box to run the driver install after. There may be a better way to automate this, however I have not yet had a chance to look into this.

Update: A collection of scripts has been started below for various driver EXEs that you can use if you see a similar structure. For example, intel chipsets usually have the same installation switches and so can use the same script. Where it has been figured out how to do so, the scripts posted will include installation logging.

Update 2: It has been pointed out that anonymous users are unable to see/access download links on the site. While we look into this, here is a hard link to the FMSCUG Driver Installer ZIP package: Driver Installer ZIP Package, as well as the corresponding documentation: Driver Installer Documenation.