Configure Task Sequences to Deploy Device Drivers in Selection Profiles for LTI Deployments

Modify The configuration for your task sequences to reference the selection profiles and deploy the appropriate device drivers to the target computers. Selection profiles are exposed to the LTI deployment process as:

· Selection profiles that can be configured in the Deployment Workbench, the CustomSettings.ini file, or the MDT DB

· Device driver groups that can be configured in the CustomSettings.ini file or the MDT DB

Selection profiles and device driver groups are additive. The LTI deployment process creates the list of device drivers to deploy based on the union of both selection profiles and device driver groups, which can cause unpredictable results, because the default selection profile and default device driver group include all device drivers. For example, if you specify a selection profile that contains only 64-bit device drivers and leave the default device driver group, the result will include all device drivers.

To change this behavior, specify:

· The Nothing device driver group in the CustomSettings.ini file or the MDT DB to allow the selection profile to control the device drivers deployed to the target computer

· The Nothing selection profile in the Inject Driver task sequence step, the CustomSettings.ini file, or the MDT DB to allow the device driver group to control the device drivers deployed to the target computer

· A specific set of device drivers for the selection profile and the device driver group so that a known set of device drivers is deployed

The following are strategies for configuring task sequences to control the deployment of device drivers for LTI deployments:

· For a single selection profile, modify the Inject Driver task sequence step, which is in most of the LTI task sequence templates, to use the selection profile.

· For a limited number of selection profiles, add an Inject Driver task sequence step for each selection profile, and then configure each task sequence step with the corresponding selection profile.

· Configure a single Inject Driver task sequence step in your task sequence, and then override the selection profile specified in the Inject Driver task sequence step using the DriverSelectionProfile task sequence variable in the CustomSettings.ini file or the MDT DB.

Note The selection profile you specify in the DriverSelectionProfile task sequence variable overrides all Inject Driver task sequence steps in a task sequence. If you have multiple all Inject Driver task sequence steps in your task sequence, they all will be overridden.

· Configure a single Inject Driver task sequence step in the task sequence (which already exists in most of the LTI task sequence templates), but specify additional device drivers to be added using the DriverGroup task sequence variable. Because selection profiles and device driver groups are additive, the device drivers specified in the DriverGroup task sequence variable are deployed in addition to the device drivers in the selection profile.

· If you want to use the DriverGroup task sequence variable for backward compatibility with previous versions of MDT, configure the Inject Driver task sequence step to use the Nothing selection profile.

Note You can also use the DriverPaths property to specify the UNC path to the folders containing the device drivers to deploy. However, this method is provided for backward compatibility with previous versions of BDD and MDT. Instead, use selection profiles or the DriverGroup task sequence variable.

Example: Woodgrove Bank Device Driver Task Sequence Configuration for LTI Deployments

Woodgrove Bank has decided that it wants to maintain precise control over the device drivers deployed to target computers. Its IT pros have created a device driver folder structure and selection profile strategy that allows detailed control of device drivers.

The IT pros configured their task sequences using the Inject Driver task sequence step in their task sequences with the most common configuration in their organization, and then used the DriverSelectionProfile task sequence variable in the CustomSettings.ini file and the MDT DB to override the selection profile specified in the Inject Driver task sequence step as necessary.

The IT pros added the following line in their CustomSettings.ini file for the DriverSelectionProfile task sequence variable:

DriverSelectionProfile =%MAKE%-%MODEL%-Win7-%ARCHITECTURE%

Note The operating system is a static value for the DriverSelectionProfile task sequence variable, because the task sequence will deploy only one operating system.