Task Sequence Tasks Explained


This document explains the tasks that you will find in standard task sequence.

Initialization > Gather local only – gathers deployment configuration settings from local sources that apply to the target computer [ZTIGather.wsf]

Validation > Validate – verifies that the target computer meets the specified deployment requirement conditions. Such as ensuring minimum memory, minimum processor speed, specifying image size will fit, and ensuring current operating system to be refreshed

Validation > Check BIOS – checks the basic input/output system (BIOS) of the target computer to ensure that it is compatible with the operating system you are deploying. [ZTIBIOSCheck.wsf]

Validation > Next Phase –updates the Phase property to the next phase in the deployment process. It determines the sequence in which each task must be completed. [ZTINextPhase.wsf]

State Capture > Generate Application Migration File – generates the ZTIAppXmlGen.xml file, which contains a list of file associations and applications that are installed on the target computer.

State Capture > Capture User State – captures the user state for user profiles that exist on the target computer. [ZTIUserState.wsf]

State Capture > Capture Groups – step captures group membership of local groups that exist on the target computer.

State Capture > Capture Network Settings – gathers the network adapter settings from the target computer [ZTIICConfig.wsf]

State Capture > Refresh Only > Disable BDE Protectors – If BitLocker is installed on the target computer, this task sequence step disables the BitLocker protectors.

State Capture > Refresh Only > Apply Windows PE – prepares the target computer to start in Windows Preinstallation Environment (Windows PE).

Preinstall > New Computer Only > Copy scripts – copies the deployment scripts used during the deployment processes to a local hard disk on the target computer. [LTICopyScripts.wsf]

Preinstall > Refresh Only > Backup – backs up the target computer before starting the operating system deployment. [ZTIBackup.wsf]

Preinstall > Configure – configures the Unattend.xml, Sysprep.inf, or Unattend.txt files with the required property values that are applicable to the operating system you are deploying to the target computer. [ZTIConfigure.wsf]

Preinstall > Inject Drivers – injects drivers that have been configured for deployment to the target computer.

Preinstall > Apply Patches – installs updates to the image on the target computer after the operating system has been deployed but before the target computer has been restarted. [ZTIPatches.wsf]

State Restore > Apply Network Settings – configures the network adapter on the target computer.

  • Give the network connection the name
  • Obtains an IP address automatically
  • Obtains a DNS

State Restore > Post-Apply Cleanup – cleans up unnecessary files after the installation of an image on the target computer. [LTIApply.wsf]

State Restore > Recover From Domain – will verify the target computer has joined a domain. [ZTIDomainJoin.wsf]

State Restore > Tattoo – step tattoos the target computer with identification and version information

State Restore > Enable BitLocker – configures BitLocker Drive Encryption on the target computer.

State Restore > Prepare to Capture Image > Copy Sysprep files – copies the Sysprep files to the target computer.

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

MDT – Joining a Computer to a Domain Using PowerShell

Using PowerShell scripts within a task sequence provides more flexibility than using the CustomSettings.ini file to join a computer to a domain. The parameters of the CustomSettings.ini file are common to any deployment you perform. That’s why creating a custom PowerShell script to join your domain will be customize to …

How MDT uses XML to install Applications

Have you ever thought about what actually happens when you import applications into your MDT environment? How does the task sequence know what application to install? How does it know what command-line arguments to specify during the application install process? Technically, as a user, all that is required of us …

MDT – Working towards Zero Touch Installation

The aim of this is to create a deployment that once started will finish without any further intervention. Step 1 – Create the Perfect task Sequence Before we start the process, we assume that you have tested your deployment process and you are able to deploy operating system as required. …