The following task sequence steps can be added to a System Center 2012 Configuration Manager task sequence. For information about editing a task sequence, see the How to Modify a Task Sequence section in the How to Manage Task Sequences in Configuration Manager topic.

Apply Data Image Task Sequence Step

Use the Apply Data Image task sequence step to copy the data image to the specified destination partition.

This step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Apply Data Image Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Apply Driver Package

Use the Apply Driver Package task sequence step to download all of the drivers in the driver package and install them on the Windows operating system. This step is necessary to install boot-critical drivers on pre-Vista operating systems.

The Apply Driver Package task sequence step makes all device drivers in a driver package available for use by Windows. This step can be added to a task sequence between the Apply Operating System and the Setup Windows and ConfigMgr steps to make the device drivers in the driver package available to Windows. Typically, the Apply Driver Package step is placed after the Auto Apply Drivers task sequence step. The Apply Driver Package task sequence step is also useful with stand-alone media deployment scenarios.

Ensure that similar device drivers are put into a driver package and distribute them to the appropriate distribution points. After they are distributed Configuration Manager client computers can install them. For example, you can put all the device drivers from a manufacturer into a driver package, and then distribute the package to distribution points where the associated computers can access them. This action can also be used to install boot critical mass storage device drivers for Windows XP x64 SP2, Windows XP SP3, and Windows Server 2003 SP2.

This step is useful for stand-alone media and for administrators who want to install a specific set of drivers, including drivers for devices that would not be detected in a Plug-n-Play scan (for example, network printers).

Note
When deploying pre-Vista operating systems, if the image already has a driver installed for a device on the computer, the Auto Apply Drivers step, the Apply Driver Package step, or any new drivers installed by a task sequence action will not be processed. To ensure the new drivers are installed, in the sysprep.inf file, set the UpdateInstalledDrivers option in the “Unattended” section to ‘Yes.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Apply Driver Package Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Apply Network Settings Step

Use the Apply Network Settings task sequence step to specify the network or workgroup configuration information for the destination computer. The specified values are stored in the appropriate answer file format for use by Windows Setup when the Setup Windows and ConfigMgr task sequence step is run.

This task sequence step runs in either a standard operating system or Windows PE. For more information about the task sequence variables for this action, see Apply Network Settings Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Apply Operating System Image

Use the Apply Operating System Image task sequence step to install an operating system on the destination computer. This task sequence step performs a set of actions depending on whether it is using an operating system image or an operating system installation package to install the operating system.

The Apply Operating System Image step performs the following actions when an operating system image is used.

  1. Deletes all content on the targeted volume except for those files under the folder specified by the _SMSTSUserStatePath task sequence variable.

  2. Extracts the contents of the specified .wim file to the specified destination partition.

  3. Prepares the answer file:

    1. Creates a new default Windows Setup answer file (sysprep.inf or unattend.xml) for the operating system that is being deployed.

    2. Merges any values from the user-supplied answer file.

  4. Copies Windows boot loaders into the active partition.

  5. Sets up the boot.ini or the Boot Configuration Database (BCD) to reference the newly installed operating system.

The Apply Operating System Image step performs the following actions when an operating system installation package is used.

  1. Deletes all content on the targeted volume except for those files under the folder specified by the _SMSTSUserStatePath task sequence variable.

  2. Prepares the answer file:

    1. Creates a fresh answer file with standard values created by Configuration Manager.

    2. Merges any values from the user-supplied answer file.

Note
Actual installation of Windows is started by the Setup Windows and ConfigMgr task sequence step. After the Apply Operating System task sequence action has run, the OSDTargetSystemDrive task sequence variable is set to the drive letter of the partition containing the operating system files.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Apply Operating System Image Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Apply Windows Settings

Use the Apply Windows Settings task sequence step to configure the Windows settings for the destination computer. The specified values are stored in the appropriate answer file format for use by Windows Setup when the Setup Windows and ConfigMgr task sequence step is run.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Apply Windows Settings Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Auto Apply Drivers

Use the Auto Apply Drivers task sequence step to match and install drivers as part of the operating system deployment.

The Auto Apply Drivers task sequence step performs the following actions:

  1. Scans the hardware and finds the Plug-n-Play IDs for all devices present on the system.

  2. Sends the list of devices and their Plug-n-Play IDs to the management point. The management point returns a list of compatible drivers from the driver catalog for each device. The management point considers all drivers regardless of what driver package they might be in. Only those drivers tagged with the specified driver category and those drivers that are not marked as disabled are considered.

  3. For each device, the client picks the best driver that is appropriate for the operating system on which it is being deployed and that is on an accessible distribution point.

  4. The selected driver or drivers are downloaded from a distribution point and staged on the target operating system.

    1. For image-based installations, the drivers are placed into the newly deployed operating system image and Windows is configured with where to find the drivers on any Plug-n-Play scan. On Vista and later, the drivers are placed into the operating system driver store.

    2. For setup-based installations, Windows Setup is configured with where to find the drivers.

  5. When the Setup Windows and ConfigMgr task sequence action runs and Windows initially boots, it will find the drivers staged by this action.

Important
The Auto Apply Drivers task sequence step cannot be used with stand-alone media because Windows Setup will have no connection to the Configuration Manager site.
Note
When deploying pre-Vista operating systems, if the image already has a driver installed for a device on the computer, the Auto Apply Drivers action, the Apply Driver Package action, or any new drivers installed by a task sequence action will not be processed. To ensure the new drivers will be installed, in the sysprep.inf file, set the UpdateInstalledDrivers option in the “Unattended” section to ‘Yes.’ For additional installation about deploying drivers, see Microsoft Support.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Auto Apply Drivers Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Capture Network Settings

Use the Capture Network Settings task sequence step to capture Microsoft network settings from the computer running the task sequence. The settings are saved in task sequence variables that will override the default settings you configure on the Apply Network Settings task sequence step.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For more information about the task sequence variables for this action, see Capture Network Settings Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Capture Operating System Image

Use the Capture Operating System Image task sequence step to capture one or more images from a reference computer and store them in a WIM file on the specified network share. The Add Operating System Image Package Wizard can then be used to import this .WIM file into Configuration Manager so that it can be used for image-based operating system deployments.

Each volume (drive) on the reference computer is captured as a separate image within the .wim file. If the referenced computer has multiple volumes, the resulting WIM file will contain a separate image for each volume. Only volumes that are formatted as NTFS or FAT32 are captured. Volumes with other formats and USB volumes are skipped.

The installed operating system on the reference computer must be a version of Windows that is supported by Configuration Manager and must have been prepared by using the SysPrep tool. The installed operating system volume and the boot volume must be the same volume.

You must also enter a Windows account that has write permissions to the network share that you selected.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Capture Operating System Image Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Capture User State

Use the Capture User State task sequence step to use the User State Migration Tool (USMT) to capture user state and settings from the computer running the task sequence. This task sequence step is used in conjunction with the Restore User State task sequence step. With USMT 3.0.1 and later, this option always encrypts the USMT state store by using an encryption key generated and managed by Configuration Manager.

For more information about managing the user state when deploying operating systems, see How to Manage the User State in Configuration Manager.

You can also use the Capture User State task sequence step with the Request State Store and Release State Store task sequence steps if you want to save the state settings to or restore settings from a state migration point in the Configuration Manager site.

The Capture User State task sequence step provides control over a limited subset of the most commonly used USMT options. Additional command-line options can be specified using the OSDMigrateAdditionalCaptureOptions task sequence variable.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Capture User State Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Capture Windows Settings

Use the Capture Windows Settings task sequence step to capture the Windows settings from the computer running the task sequence. The settings are saved in task sequence variables that will override the default settings you configure on the Apply Windows Settings task sequence step.

This task sequence step runs in either Windows PE or a standard operating system. For more information about the task sequence variables for this action, see Capture Windows Settings Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Connect To Network Folder

Use the Connect to Network Folder task sequence action to create a connection to a shared network folder.

This task sequence step runs in a standard operating system or Windows PE. For more information about the task sequence variables for this action, see Connect to Network Folder Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Convert Disk to Dynamic

Use the Convert Disk to Dynamic task sequence step to convert a physical disk from a basic disk type to a dynamic disk type.

This step runs in either a standard operating system or Windows PE. For more information about the task sequence variables for this action, see Convert Disk to Dynamic Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Disable BitLocker

Use the Disable BitLocker task sequence step to disable the BitLocker encryption on the current operating system drive, or on a specific drive. This action leaves the key protectors visible in clear text on the hard drive, but it does not decrypt the contents of the drive. Consequently this action is completed almost instantly.

Note
BitLocker drive encryption provides low-level encryption of the contents of a disk volume.

If you have multiple drives encrypted, you must disable BitLocker on any data drives before disabling BitLocker on the operating system drive.

This step runs only in a standard operating system. It does not run in Windows PE.

Note
You can use BitLocker only for client computers running Windows Vista SP2 or later and Windows Server 2008 SP2 or later.

Details

Enable BitLocker

Use the Enable BitLocker task sequence step to enable BitLocker encryption on at least two partitions on the hard drive. The first active partition contains the Windows bootstrap code. Another partition contains the operating system. The bootstrap partition must remain unencrypted.

Starting in Configuration Manager SP1, you can use the Pre-provision BitLocker task sequence step to enable BitLocker on a drive while in Windows PE. For more information, see the Pre-provision BitLocker section in this topic.

Note
BitLocker drive encryption provides low-level encryption of the contents of a disk volume.

The Enable BitLocker step runs only in a standard operating system. It does not run in Windows PE. For more information about the task sequence variables for this action, see Enable BitLocker Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Note
BitLocker is used with computers running Windows Vista SP2 or later and Windows Server 2008 SP2 or later.

The Trusted Platform Module (TPM) must be in the following state when you specify TPM Only, TPM and Startup Key on USB or TPM and PIN, before you can run the Enable BitLocker step:

  • Enabled

  • Activated

  • Ownership Allowed

The task sequence step can complete any remaining TPM initialization, because the remaining steps do not require physical presence or reboots. The remaining TPM initialization steps which can be completed transparently by Enable BitLocker (if necessary) include:

  • Create endorsement key pair

  • Create owner authorization value and escrow to Active Directory, which must have been extended to support this value

  • Take ownership

  • Create the storage root key, or reset if already present but incompatible

If you want the Enable BitLocker step to wait until the drive encryption process has been completed before continuing with the next step in the task sequence, select the Wait check box. If you do not select the Wait check box, the drive encryption process will be performed in the background and task sequence execution will proceed immediately to the next step.

BitLocker can be used to encrypt multiple drives on a computer system (both operating system and data drives). To encrypt a data drive, the operating system must already be encrypted and the encryption process must be completed, because the key protectors for the data drives are stored on the operating system drive. As a result, if you encrypt the operating system drive and the data drive in the same process, the wait option must be selected for the step that enables BitLocker for the operating system drive.

If the hard drive is already encrypted but BitLocker is disabled then Enable BitLocker re-enables the key protector or protectors and will be completed almost instantly. Re-encryption of the hard drive is not necessary in this case.

For more information about the task sequence variables for this action, see Enable BitLocker Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Format and Partition Disk

Use the Format and Partition Disk task sequence step to format and partition a specified disk on the destination computer.

Important
Every setting you specify for this task sequence step applies to a single specified disk. If you want to format and partition another disk on the destination computer, you must add an additional Format and Partition Disk task sequence step to the task sequence.

This task sequence step runs only in Windows PE. It does not run in a standard operating system. For more information about the task sequence variables for this action, see Format and Partition Disk Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Install Application

Use the Install Application task sequence step to install applications as part of the task sequence. This step can install a set of applications that are specified by the task sequence step or a set of applications that are specified by a dynamic list of task sequence variables. When this step is run, the application installation begins immediately without waiting for a policy polling interval.

The applications that are installed must meet the following criteria:

  • It must run under the local system account and not the user account.

  • It must not interact with the desktop. The program must run silently or in an unattended mode.

  • It must not initiate a restart on its own. The application must request a restart by using the standard restart code, a 3010 exit code. This ensures that the task sequence step will handle the restart correctly. If the application does return a 3010 exit code, the underlying task sequence engine performs the restart. After the restart, the task sequence automatically continues.

When the Install Application step runs, the application checks the applicability of the requirement rules and detection method on the deployment types of the application. Based on the results of this check, the application installs the applicable deployment type. If a deployment type contains dependencies, the dependent deployment type is evaluated and installed as part of the install application step. Application dependencies are not supported for stand-alone media.

This task sequence step runs only in a standard operating system. It does not run in Windows PE.

Details

Install Deployment Tools

Use the Install Deployment Tools task sequence step to install the Configuration Manager package that contains the Sysprep deployment tools.

Details

Install Package

Use the Install Package task sequence step to install software as part of the task sequence. When this step is run, the installation begins immediately without waiting for a policy polling interval

The software that is installed must meet the following criteria:

  • It must run under the local system account and not the user account.

  • It should not interact with the desktop. The program must run silently or in an unattended mode.

  • It must not initiate a restart on its own. The software must request a restart using the standard restart code, a 3010 exit code. This ensures that the task sequence step will properly handle the restart. If the software does return a 3010 exit code, the underlying task sequence engine will perform the restart. After the restart, the task sequence will automatically continue.

Programs that use the Run another program first option to install a dependent program are not supported when deploying an operating system. If Run another program first is enabled for the software and the dependent program has already been run on the destination computer, the dependent program will be run and the task sequence will continue. However, if the dependent program has not already been run on the destination computer, the task sequence step will fail.

Note
The central administration site does not have the necessary client configuration policies that are required to enable the software distribution agent during the execution of the task sequence. When you create stand-alone media for a task sequence at the central administration site, and the task sequence includes an Install Package step, the following error might appear in the CreateTsMedia.log file: “WMI method SMS_TaskSequencePackage.GetClientConfigPolicies failed (0x80041001)”For stand-alone media that includes an Install Package step, you must create the stand-alone media at a primary site that has the software distribution agent enabled or add a Run Command Line step after the Setup Windows and ConfigMgr step and before the first Install Package step. The Run Command Line step runs a WMIC command to enable the software distribution agent before the first Install package step runs. You can use the following in your Run Command Line task sequence step: Command Line: WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName="Enable SWDist", Enabled="true", LockSettings="TRUE", PolicySource="local", PolicyVersion="1.0", SiteSettingsKey="1" /NOINTERACTIVEFor more information about creating stand-alone media, see How to Create Stand-alone Media section in the How to Deploy Operating Systems by Using Media in Configuration Manager topic.

This task sequence step runs only in a standard operating system. It does not run in Windows PE.

Details

Install Software Updates

Use the Install Software Updates task sequence step to install software updates on the destination computer. The destination computer is not evaluated for applicable software updates until this task sequence step runs. At that time, the destination computer is evaluated for software updates like any other Configuration Manager-managed client. In particular, this step installs only the software updates that are targeted to collections of which the computer is currently a member.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For information about task sequence variables for this task sequence action, see Install Software Updates Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Important
This task sequence step cannot suppress restarts if the software update indicates that a restart is required. If you install software updates on a computer that is in a production environment and you need to suppress a restart, do not use a task sequence to install the software update. Use the software update feature of Configuration Manager to install the software update. For more information about the install software update feature, see Software Updates in Configuration Manager.

Details

Join Domain or Workgroup

Use the Join Domain or Workgroup task sequence step to add the destination computer to a workgroup or domain.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For information about task sequence variables for this task sequence action, see Join Domain or Workgroup Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Prepare ConfigMgr Client for Capture

Use the Prepare ConfigMgr Client for Capture step to take the Configuration Manager client on the reference computer and prepares it for capture as part of the imaging process by performing the following tasks:

  • Removes the client configuration properties section from the smscfg.ini file in the Windows directory. These properties include client-specific information including the Configuration Manager GUID and other client identifiers.

  • Deletes all SMS or Configuration Manager machine certificates.

  • Deletes the Configuration Manager client cache.

  • Clears the assigned site variable for the Configuration Manager client.

  • Deletes all local Configuration Manager policy.

  • Removes the trusted root key for the Configuration Manager client.

This task sequence step runs only in a standard operating system. It does not run in Windows PE.

Details

Prepare Windows for Capture

Use the Prepare Windows for Capture task sequence step to specify the Sysprep options to use when capturing an operating system image on the reference computer. This task sequence action runs Sysprep and then reboots the computer into Windows PE boot image specified for the task sequence. The reference computer must not be joined to a domain for this action to be completed successfully.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For information about task sequence variables for this task sequence action, see Prepare Windows for Capture Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Pre-provision BitLocker

Use the Pre-provision BitLocker task sequence step to enable BitLocker on a drive while in Windows PE. Only the used drive space is encrypted, and therefore, encryption times are much faster. You apply the key management options by using the Enable BitLocker task sequence step after the operating system installs. This step runs only in Windows PE. It does not run in a standard operating system.

Important
To pre-provision BitLocker, you must deploy a minimum operating system of Windows 7 and TPM must be supported and enabled on the computer.

Details

Release State Store

Use the Release State Store task sequence step to notify the state migration point that the capture or restore action is complete. This step is used in conjunction with the Request State Store, Capture User State, and Restore User State task sequence steps to migrate user state data using a state migration point and the User State Migration Tool (USMT).

For more information about managing the user state when deploying operating systems, see How to Manage the User State in Configuration Manager.

If you requested access to a state migration point to capture user state in the Request State Store task sequence step, this step notifies the state migration point that the capture process is complete and that the user state data is available to be restored. The state migration point sets the access control permissions for the captured state so that it can only be accessed (as read-only) by the restoring computer.

If you requested access to a state migration point to restore user state in the Request State Store task sequence step, this task sequence step notifies the state migration point that the restore process is complete. At this point, whatever retention settings you configured for the state migration point are activated.

Important
It is a best practice to set Continue on Error on any task sequence steps between the Request State Store step and Release State Store step so that every Request State Store task sequence action has a matching Release State Store task sequence action.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For information about task sequence variables for this task sequence action, see Release State Store Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Request State Store

Use the Request State Store task sequence step to request access to a state migration point when capturing state from a computer or restoring state to a computer.

For more information about managing the user state when deploying operating systems, see How to Manage the User State in Configuration Manager.

You can use the Request State Store task sequence step in conjunction with the Release State Store, Capture User State, and Restore User State task sequence steps to migrate computer state using a state migration point and the User State Migration Tool (USMT).

Note
If you have just established a new state migration point site role (SMP), it can take up to one hour to be available for user state storage. To expedite the availability of the SMP you can adjust any state migration point property setting to trigger a site control file update.

This task sequence step runs in a standard operating system and in Windows PE for offline USMT. For information about the task sequence variables for this task sequence action, see Request State Store Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Restart Computer

Use the Restart Computer task sequence step to restart the computer running the task sequence. After the restart, the computer will automatically continue with the next step in the task sequence.

This step can be run in either a standard operating system or Windows PE. For more information about the task sequence variables for this task sequence action, see Restart Computer Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Restore User State

Use the Restore User State task sequence step to initiate the User State Migration Tool (USMT) to restore user state and settings to the destination computer. This task sequence step is used in conjunction with the Capture User State task sequence step.

For more information about managing the user state when deploying operating systems, see How to Manage the User State in Configuration Manager.

You can also use the Restore User State task sequence step with the Request State Store and Release State Store task sequence steps if you want to save the state settings to or restore settings from a state migration point in the Configuration Manager site. With USMT 3.0 and above, this option always decrypts the USMT state store by using an encryption key generated and managed by Configuration Manager.

The Restore User State task sequence step provides control over a limited subset of the most commonly used USMT options. Additional command-line options can be specified by using the OSDMigrateAdditionalRestoreOptions task sequence variable.

Important
If you are using the Restore User State task sequence step for a purpose unrelated to an operating system deployment scenario, add the Restart Computer task sequence step immediately following the Restore User State task sequence step.

This task sequence step runs only in a standard operating system. It does not run in Windows PE. For information about the task sequence variables for this task sequence action, see Restore User State Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Run Command Line

Use the Run Command Line task sequence step to run a specified command line.

This step can be run in a standard operating system or Windows PE. For information about task sequence variables for this task sequence action, see Run Command Line Task Sequence Action Variables in the Task Sequence Action Variables in Configuration Manager topic.

Details

Set Task Sequence Variable

Use the Set Task Sequence Variable task sequence step to set the value of a variable that is used with the task sequence.

This step can be run in either a standard operating system or Windows PE. Task sequence variables are read by task sequence actions and specify the behavior of those actions. For more information about specific task sequence variables, see Task Sequence Action Variables in Configuration Manager.

Details

Setup Windows and ConfigMgr

Use the Setup Windows and ConfigMgr task sequence step to perform the transition from Windows PE to the new operating system. This task sequence step is a required part of any operating system deployment. It installs the Configuration Manager client into the new operating system and prepares for the task sequence to continue execution in the new operating system.

This step runs only in Windows°PE. It does not run in a standard operating system. For more information about task sequence variables for this task sequence action, see Setup Windows and ConfigMgr Task Sequence Action Variables.

The Setup Windows and ConfigMgr task sequence action replaces sysprep.inf or unattend.xml directory variables, such as %WINDIR% and %ProgramFiles%, with the Windows°PE installation directory X:\Windows. Task sequence variables specified by using these environment variables will be ignored.

Use this task sequence step to perform the following actions:

  1. Preliminaries: Windows°PE

    1. Performs task sequence variable substitution in the sysprep.inf (operating systems earlier than Windows Vista) or the unattend.xml (Windows Vista SP2, Windows Server 2008 SP2, and later operating systems) file.

    2. Downloads the package that contains the Configuration Manager client and puts it in the deployed image.

  2. Set up Windows

    1. Image-based installation.

      1. Disables the Configuration Manager client in the image (that is, disables Autostart for the Configuration Manager client service).

      2. Updates the registry in the deployed image to ensure that the deployed operating system starts with the same drive letter that it had on the reference computer.

      3. Restarts in the deployed operating system.

      4. Windows mini-setup runs by using the previously specified sysprep.inf or unattend.xml file that has all end-user interaction suppressed. Note: If Apply Network Settings specified to join a domain, then that information is in the sysprep.inf or unattend.xml file, and Windows mini-setup performs the domain join.

    2. Setup.exe-based installation. Runs Setup.exe (Windows Vista SP2 and later operating systems) or WinNT32.exe (operating systems earlier than Windows Vista) which follows the typical Windows setup process:

      1. Copies the operating system install package specified in an earlier Apply Operating System task sequence to the hard disk drive.

      2. Restarts in the newly deployed operating system.

      3. Windows mini-setup runs by using the previously specified sysprep.inf or unattend.xml file that has all user interface settings suppressed. Note: If Apply Network Settings specified to join a domain, then that information is in the sysprep.inf or unattend.xml file, and Windows mini-setup performs the domain join.

  3. Set up the Configuration Manager client

    1. After Windows mini-setup finishes, the task sequence resumes by using an alternative graphical identification and authentication (GINA) library (earlier than Windows Vista) or setupcomplete.cmd (Windows Vista and later).

    2. Enables or disables the local administrator account, based on the option selected in the Apply Windows Settings step.

    3. Installs the Configuration Manager client by using the previously downloaded package (1.b) and installation properties specified in the Task Sequence Editor. The client is installed in "provisioning mode" to prevent it from processing new policy requests until the task sequence is completed.

    4. Waits for the client to be fully operational.

    5. If the computer is operating in an environment with Network Access Protection enabled, the client checks for and installs any required updates so that all required updates are present before the task sequence continues running.

  4. The task sequence continues running with its next step.

Note
The Setup Windows and ConfigMgr task sequence action is responsible for running Group Policy on the newly installed computer. The time at which Group Policy is applied during the task sequence action depends on the operating system being deployed. For example, with Windows XP and Windows Server 2003 Group Policy is applied after the Setup Windows and ConfigMgr task sequence action is completed. On Windows Vista and Windows Server 2008, Group Policy is applied after the task sequence is finished.

Details

See Also