Identify the Packages and Images That the MDT Task Sequence Templates in Configuration Manager 2012 Require

Table 122 lists the packages and images that the task sequence templates in MDT require. These packages and images must exist (or be created) for the task sequences to run correctly in Configuration Manager 2012.

Table 122. Packages and Images Required by the Task Sequence Templates Included in MDT for Configuration Manager 2012

This package or image	Contains the
Boot image package	Boot image used to initiate the ZTI deployment process and in the middle of the process when performing the Refresh Computer deployment scenario.
Microsoft Deployment Files package	Script and tools necessary for the MDT task sequence templates for Configuration Manager 2012.
OS image package	Image of the target operating system to be deployed to the target computer.
OS install package	All the files required to install the operating system (using WINNT32 for Windows XP and Windows Server 2003 or Setup.exe for Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 operating systems).
Client package	Configuration Manager 2012 client installation files.
USMT package	USMT files used to capture and restore user state.
Custom Settings package	Contains unattended files and customsettings.ini.
Sysprep files package	Contains the specific Sysprep files defined for a package, which is only required when capturing an image of a computer running Windows XP or Windows Server 2003.

Note You can use the generic boot images (WIM files) that the Deployment Workbench generates in ZTI deployments. However, you cannot use the LTI LiteTouch boot images (WIM files) that the Deployment Workbench generates in ZTI deployments using Configuration Manager 2012.

The Create MDT Task Sequence Wizard can automatically create these packages and images or can use existing packages and images. The task sequence templates contain placeholders for each package and image listed in Table 122. The Create MDT Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates. After completing the wizard, the new created task sequence references the appropriate packages and images.

In addition to the packages and images that the task sequence templates require, consider creating and including the following elements in the task sequences to provide similar functionality in the Deployment Workbench:

· Software distribution packages. This package includes any software that will be installed as part of the operating system deployment (similar to the Applications node in the Deployment Workbench). These packages are created as packages and programs in Configuration Manager 2012. For more information on how to create these packages, see the following sections in the Configuration Manager 2012 Documentation Library, which is included with Configuration Manager 2012:

· “Content Management in Configuration Manager”

· “Application Management in Configuration Manager”

· Windows package file (software update) packages. These packages include any Windows package files that contain software updates (such as language packs, security updates, and service packs) that will be installed as part of the operating system deployment (similar to the OS Packages node in the Deployment Workbench). You can use these software update packages:

· Without modification by using the Software Updates feature in Configuration Manager 2012. For more information on using these packages in the Software Updates feature, see the section, “Software Updates in Configuration Manager,” in the Configuration Manager 2012 Documentation Library, which is included with Configuration Manager 2012.

· As installed directly by ZTI using the Install Updates Offline task sequence step type. For more information about configuring a task sequence step based on this type, see Configuring ZTI Task Sequence Steps in Configuration Manager 2012.

· Custom software distribution packages in Configuration Manager 2012. For more information on how to create these packages, see the section, “Technical Reference for Content Management in Configuration Manager,” in the Configuration Manager 2012 Documentation Library, which is included with Configuration Manager 2012.

· Device driver package. Configuration Manager 2012 uses driver packages to control the distribution of drivers to distribution points. You can specify device driver categories in an Auto Apply Drivers task sequence step type to limit which drivers are installed, or you can install all device drivers using an Apply driver package task sequence step type. For more information about how to include device drivers in the operating system image, see the section, “How to Install Device Drivers to Computers by Using Task Sequences,” in the Configuration Manager 2012 Documentation Library, which is included with Configuration Manager 2012.