MDT uses wizards to create and manage configuration files. For more information about the standard MDT configuration files, CustomSettings.ini and BootStrap.ini, see Customizing MDT Configuration Files. However, you can customize configuration files to meet the needs of your organization.

Before configuring the deployment process, select the properties to reference from the predefined or user-defined properties. The properties selected must include all the configuration settings to be supplied during the deployment process.

For ZTI deployments using Configuration Manager 2012 or Configuration Manager 2007 R3, provide all configuration settings required to deploy the target operating system. For LTI deployments, provide a subset of the configuration settings that are provided automatically; the remainder of the settings can be provided manually during the deployment process.

The MDT process occurs in the phases defined in the TS.xml file. The Task Sequencer parses the TS.xml file to identify the appropriate sequence for performing the deployment process. The phases defined in the TS.xml file include:

·     Validate Phase. Performs validation checks to make sure that the operating system installation can proceed; specifically blocks installation on server operating systems.

·     State Capture Phase. Gathers information from the configuration file, databases, and the local machine to determine how the image installation process should proceed, including whether there is enough space to do a local USMT state backup. The scripts also invoke the USMT Scanstate.exe command as appropriate.

·     Preinstall Phase. Confirms that the necessary information has been gathered in the State Capture Phase for the Refresh Computer scenario. In the New Computer and Replace Computer scenarios, the script gathers the necessary information in this phase, because these scenarios do not perform the State Capture Phase. Also, a backup of the computer can be optionally performed for the Refresh Computer scenario.

·     Install Phase. Installs the target operating system on the target computers.

·     Post Install Phase. Updates the Sysprep.inf file, Sysprep.xml file, or Unattend.txt file with information gathered in the previous custom actions based on the operating system being deployed.

·     State Restore Phase. Invokes the USMT Loadstate.exe command to restore the user state that was previously backed up.

The TS.xml file identifies the appropriate steps in each phase based on each type of deployment scenario (Refresh Computer, Replace Computer, and New Computer). Select the properties required during each phase of the deployment process.

For more information on each of the properties used in each phase, see the section, Properties, in the MDT document Toolkit Reference.

Related Topics

Configuring MDT Deployments