Part 9 discusses the role of drivers in the Config Mgr 2012 OSD process.
Config Mgr is hardware agnostic to a degree. We will capture an image from a reference computer in Part 10 and it will not matter which make and model of hardware we use. Drivers are injected into the process as required.
Network Card drivers: The deployment process relies heavily on the use of Windows PE. Config Mgr utilises boot images to allow devices to boot into PE. However in order to allow this for your particular makes and models you must first add your network card drivers to the boot images. The process is shown below.
Driver Packages: We will create a driver package for each of our makes and models. Each package will contain the full driver set for that model. When we create our OSD task sequence in Part 11 we will incorporate the driver packages. We will configure a series of WMI queries so that only the correct driver package is applied during a deployment.
Most hardware vendors create cab files for their models. These cab files contain the full driver set and can be downloaded from their web sites. This makes it easy to add the drivers to your driver package in one operation. Otherwise you have to download and add individual drivers as required.
First prepare your Windows and Config Mgr folder structures
Download the required drivers and save them to the folders above
1. Network Card Drivers
Right Click Drivers and Select Import Driver
Browse to the driver folder
Important Note; Add x64 drivers to x64 boot image only (same for x86)
When drivers are Imported to Config Mgr they can be found in the Drivers folder (you cannot import directly to a sub-folder). Move the drivers manually to the sub-folder for good house-keeping.
2. Driver Packages
Create Driver Package folder
Right Click Driver Packages to create
Now that driver package is created you can now import drivers and add to the package.
Right click to import drivers as before.
Browse to folder where you previously downloaded the cab file (or manually added the required drivers)
Add drivers to package you just created
DO NOT ADD THESE DRIVERS TO THE BOOT IMAGE. They are not required and could eventually corrupt the boot image.
Then distribute the package to the distribution point