Export (0) Print
Expand All

Setup Windows and ConfigMgr Task Sequence Step

Updated: September 1, 2010

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

Use the Setup Windows and ConfigMgr task sequence step to perform the transition from the Windows Preinstallation Environment (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 2007 client into the new operating system and prepares for the task sequence to continue execution in the new operating system.

This task sequence step runs only in the Windows Preinstallation Environment (Windows°PE) and does not run in a standard operating system. For 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, Windows Server 2008, and later operating systems) file.

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

  2. Set up Windows

    1. Image-based installation.

      1. Disables the Configuration Manager 2007 client in the image (that is, disables Autostart for the Configuration Manager 2007 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 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 2007 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 2007 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.

noteNote
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 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.

Specify the following settings:

UI Element List

Name
Specifies a short user-defined name that describes the action taken in this step.

Description
Specifies additional information about the action taken in this step.

Package
Specifies the Configuration Manager 2007 client installation package that will be used by this task sequence step. Click Browse and select the client installation package that you want to use to install the Configuration Manager 2007 client.

Installation Properties
Site assignment and the default configuration are automatically specified by the task sequence action. You can use this field to specify any additional installation properties to use when you install the client. To enter multiple installation properties, separate them with a space.

If you are installing the Configuration Manager 2007 client on a computer that is a member of a workgroup, you must specify a Configuration Manager 2007 server locator point. The server locator point locates the assigned software packages and updates that will be installed on the target computer. Use the following to specify the server locator point for a computer that is a member of a workgroup:

Modify the following registry key with the value provided:

Registry Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\SMSSLP

Value:

SMSSLP=<serverlocatorpointname>

For more information about Configuration Manager 2007 client installation properties, see About Configuration Manager Client Installation Properties.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft