Preparing System Center Configuration Manager for Deployment

Using Configuration Manager Console, the Image Engineering feature team can supply images, drivers, driver packages, applications, operating systems, and other packages for deployment. When the team adds these items to System Center Configuration Manager, the team is essentially storing in System Center Configuration Manager the files that System Center Configuration Manager will eventually distribute to the production environment. When the items are in place, the team associates these stored items with task sequences in the configuration process.

The following sections of this document provide guidance on ways the Image Engineering feature team can use Configuration Manager Console to import and prepare the images and packages that System Center Configuration Manager will use during deployment.

On This Page

Import Microsoft Deployment Task Sequences
Create a New Driver Package
Add Language Packs
Add Updates
Create an Operating System Image Capture Image
Install an Existing Image Package Using the Import Microsoft Deployment Task Sequence Wizard and the Client Task Sequence
Use the Import Microsoft Deployment Task Sequence Wizard and the Client Replace Task Sequence
Use the Import Microsoft Deployment Task Sequence Wizard and the Server Task Sequence

Import Microsoft Deployment Task Sequences

Although team members can manually create new task sequences in System Center Configuration Manager, Microsoft Deployment includes task sequence template files that can be imported into System Center Configuration Manager. These task sequence templates dramatically reduce the effort required to create task sequences in System Center Configuration Manager to use in Microsoft Deployment. To import the Microsoft Deployment task sequence templates, use the System Center Configuration Manager Import Microsoft Deployment Task Sequence Wizard.

Create New Task Sequences Using the Import Wizard

To create task sequences, the Import Microsoft Deployment Task Sequence Wizard moves the necessary files to System Center Configuration Manager. Configuration Manager Console contains the Import Microsoft Deployment Task Sequence Wizard, which allows team members to create the task sequences required for successful deployment of ZTI images. This functionality is new in Microsoft Deployment and requires the installation of Microsoft Deployment to operate correctly in Configuration Manager Console. This integrated functionality does not exist between System Center Configuration Manager and Microsoft Deployment by default and requires the team to run the Configure ConfigMgr Integration Wizard.

Note   Run the Configure ConfigMgr Integration Wizard for the Import Microsoft Deployment Task Sequence Wizard to be installed in System Center Configuration Manager. Use the section, “Enable Configuration Manager Console Integration,” in the Microsoft Deployment document, Preparing for Microsoft System Center Configuration Manager 2007 , to complete this process.

Table 3 lists the task sequences templates that are included in Microsoft Deployment, the file name for each template, and a description of the template. The template files are located in the install_folder\SCCM folder (where install_folder is the folder in which Microsoft Deployment was installed).

Table 3. Task Sequence Templates Included in Microsoft Deployment

The Import Microsoft Deployment Task Sequence Wizard guides team members through the process of creating these packages and images (or specifying existing packages and images). The task sequence templates contain placeholders for each of the packages and images listed in Table 3. The Import Microsoft Deployment Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates. After completing the wizard, the new imported task sequence references the appropriate packages and images.

Note   Always use the Import Microsoft Deployment Task Sequence Wizard to import the task sequence templates. Although team members can manually import the task sequence templates, this process is not recommended.

Using the Import Microsoft Deployment Task Sequence Wizard, choose the template type to create, and then customize it for the needs of the environment. Table 4 describes the different sections of the Import Microsoft Deployment Task Sequence Wizard.

Table 4. Import Microsoft Deployment Task Sequence Wizard Sections and Descriptions

To import task sequences into Configuration Manager Console

1. In Configuration Manager Console, expand Computer Management, right-click Task Sequences, and then click Import Microsoft Deployment Task Sequence.

2. On the Choose Template page, click Client Task Sequence, and then click Next.

3. On the General page, in the Task Sequence Name box, type the name of the task sequence to create. In the Comments box, type a comment (optional) that describes the sequence, and then click Next.

4. On the Details page, select either the Join a workgroup or Join a domain option, and then type the name of the workgroup or domain name in its associated box.

5. Type the credentials for joining the domain in the Account text box by clicking Set.

6. In the Windows Settings section, type the registered user name in the User name box, type the registered organization in the Organization name box, and type the product key into the Product key box.

7. In the Capture Operating System Image Settings section, type the location for captures in the Capture Destination box, type the authorized account for capture placement in the Capture account box, and then click Next.

8. On the Boot Image page, click Create a New Boot Image Package. Type the Universal Naming Convention (UNC) path to the package, and then click Next.

9. On the General Settings page, type the relevant information in the following boxes, and then click Next:

   • Name: The name of the boot image.

   • Version: The package version.

   • Comments: Optional comments.

10. On the Image Options page, type the relevant information or click the relevant options, and then click Next:

    • Platform section: Click the relevant operating system.

    • Optional Components section: Click ADO, if required.

    • Optional Fonts section: Click additional fonts, if required.

    • Additional Files section: Click Browse to add a custom a background bitmap image file, and then click Browse to add an extra additional directory, if required.

    Note   The background bitmap file must be specified using a UNC path.

11. On the Microsoft Deployment Package page, click Create a New Microsoft Deployment Files Package; in the UNC path box, type the UNC path (for example, \\DeploymentServer\packages$\Deployment4files) for the deployment files package the wizard will create, and then click Next.

12. On the Microsoft Deployment Details page, type the relevant information in the following boxes, and then click Next:

    • Name: The name of the Microsoft Deployment files.

    • Version: Optional section containing the version of the Microsoft Deployment files.

    • Language: The language of the Microsoft Deployment files.

    • Comments: Optional comments.

13. On the OS Image page, click Create a new OS install package; in the OS installation folder location box, type or browse to the relevant location; in the Package source folder to be created box, type or browse to the relevant UNC location; and then click Next.

    Note   The OS installation folder contents are copied from the specified UNC location to the package source folder, which are then used to create the package.

14. On the Install Source page, type the relevant information in the following boxes, and then click Next:

    • Name: The name of the operating system image.

    • Version: The operating system package version.

    • Comments: Optional comments.

15. On the Client Package page, click Create a new ConfigMgr client package, and then click Next.

16. On the USMT Package page, click Create a new USMT package, type the relevant information in the following boxes, and then click Next:

    • Path to the USMT executables and related files: The path to the location on the network where USMT files are stored.

    • Package source folder to be created: The name of the package source folder to create.

    CAUTION   A network location for USMT cannot be specified in the CustomSettings.ini file for a task sequence. The Request state store task automatically determines the location. For this to work, define a state migration point. See the Configuration Manager Documentation Library at http://technet.microsoft.com/en-us/library/bb680651.aspx for additional guidance on this process.

    Note   The default location of USMT files is C:\Program Files\USMT301. If the team is planning to use USMT with System Center Configuration Manager, run the USMT 3.0.1 .msi file on the System Center Configuration Manager server and specify this location as the source location. For additional information about configuring System Center Configuration Manager to use USMT, refer to the Configuration Manager Documentation Library at http://technet.microsoft.com/en-us/library/bb680651.aspx.

17. On the Specify USMT package properties page, type the relevant information in the following boxes, and then click Next:

    • Name: The name of the USMT package.

    • Version: The version of the USMT package.

    • Language: The USMT package language.

    • Manufacturer: The manufacturer of the USMT package.

    • Comments: Optional comments.

    CAUTION   For more information on using roaming profiles, see the Managing Roaming User Data Deployment Guide at http://technet2.microsoft.com/WindowsVista/en/library/fb3681b2-da39-4944-93ad-dd3b6e8ca4dc1033.mspx?mfr=true. USMT will back up and restore locally cached user profiles, but not network copies.

18. On the Settings Package page, click Create a new settings package, type the UNC path for the location where the wizard will create the package, and then click Next.

19. On the Settings Details page, type the relevant information in the following boxes, and then click Next:

    • Name: The name of the settings package.

    • Version: The version of the settings package.

    • Language: The settings package language.

    • Manufacturer: The manufacturer of the settings package.

    • Comments: Optional comments.

20. On the Sysprep Package page, click Create a new Sysprep package; in the Path to Sysprep executables and related files box, type the UNC path for the location where the wizard will create the Sysprep package; in the Package source folder to be created box, type or browse to the location where the wizard will create the package source folder; and then click Next.

    Note   This selection is optional and irrelevant for Windows Vista and Windows Server 2008 if team members are not capturing a custom image.

21. On the Sysprep Details page, type the relevant information in the following boxes, and then click Next:

    • Name: The name of the Sysprep package.

    • Version: The version of the Sysprep package.

    • Language: The Sysprep package language.

    • Manufacturer: The manufacturer of the Sysprep package.

    • Comments: Optional comments.

The Summary page displays a status bar that shows the progress of the tasks defined in the wizard. The wizard closes when it completes the tasks.

Top of Page

Create a New Driver Package

Complete the following steps to create a new driver package in System Center Configuration Manager. System Center Configuration Manager creates a package file in the UNC share path defined in the Import Microsoft Deployment Task Sequence Wizard.

1. In Configuration Manager Console, expand Computer Management, expand Operating System Deployment, and then click Driver Packages to start the New Driver Package Wizard.

2. Type the relevant information in the following boxes, and then click OK:

   • Name: The name of the new driver package.

   • Comments: Optional comments.

   • Driver Package Source: The path to the new driver package.

Import Drivers to System Center Configuration Manager

To import drivers into System Center Configuration Manager, complete the following steps:

1. In Configuration Manager Console, expand Computer Management, and then expand Operating System Deployment. Right-click Drivers, and then click Import to start the Import New Driver Wizard.

2. On the Locate Driver page, click one of the following options. Type or browse to the UNC path of the source folder that holds the drivers to import; and then click Next:

   • Import all drivers in the following network path (UNC)

   • Import a specific driver by specifying the network path (UNC) to its .inf or txtsetup.oem file

3. On the Driver Details page, the driver name is shown in the Name box. Click Enable this driver and allow computer to install it, and then click Next.

4. On the Applicability page, click one of the following options, and then click Next:

   • This driver can be run on any platform

   • This driver can run only on the specified platforms , and then select your OS option(s)

5. On the Add Driver to Package page, click one of the following options, and then click Next:

   • Select All

   • Clear All

   • New Package

   • Update distribution points when finished

   Note   A package must be created to add a package. If no package is listed, add the drivers to one or more packages later.

6. Click the package to which to add the drivers or create a new package.

   Note   Click Update distribution points when finished to force the wizard to perform the update.

7. On the Add Driver to Boot Image page, add updated mass storage drivers, network drivers, or critical drivers for the system boot, as appropriate. Click the boot image (x86 or x64), and then click Next.

   Note   Boot images must be refreshed on distribution points before the new drivers are available for use.

8. The Summary page shows the details of the selections made while completing the wizard. To change an option or setting, click Previous, make the necessary changes to selections, and then click Next.

   The Progress page displays a status bar that indicates the wizard is processing. Then, the Confirmation page shows the success or failure of the wizard’s ability to complete the tasks defined for the driver creation.

9. Click Close to return to Configuration Manager Console.

Top of Page

Add Language Packs

Add language packs to packages in System Center Configuration Manager either offline or online. Before team members can begin adding language packs, they must first create a package that contains the language pack.

To create a package containing a language pack

1. Create a folder that will contain the package source for the language files.

   Note   Create this folder where previously created packages are stored or where space is available to accommodate them.

2. Add the language pack folders downloaded from Microsoft into the folder created in step 1.

   Note   Language packs are available to download from Microsoft’s volume license Web site already in CAB format.

3. In Configuration Manager Console, expand Computer Management, expand Software Distribution, and then expand Packages. Right-click Packages, and then click New Package.

4. Name the package Vista Language Packs, and then click Next.

5. Click This package contains source files, and then click Set to set the source directory.

6. Type the path to the source directory, and then click OK.

7. Click Enable binary differential replication, and then click OK.

8. On the Data Access page, click Next.

9. On the Distribution Settings page, click Next.

10. On the Reporting page, click Next.

11. On the Security page, click Next.

12. On the Summary page, click Next, then click Close.

To add language packs offline to Windows Vista and Windows Server 2008

1. In Configuration Manager Console, expand Computer Management, and then expand Task Sequence. Right-click task_sequence (where task_sequence is the name of the task sequence to edit), and then click Edit.

2. In the Task Sequence Editor dialog box, go to the Postinstall phase.

3. Under the Postinstall phase, go to the Setup Windows and ConfigMgr task.

4. Click the task immediately above this task, so that the new added task will be positioned just above the Setup Windows and ConfigMgr task.

5. Click Add, click MDT, and then click Install Language Packs Offline.

6. Complete the appropriate Name and Description fields, and then click Browse to select an appropriate language pack package to install.

7. Click OK to save the settings, and then close the Task Sequence Editor.

   Note   When used with Microsoft Deployment, the term offline means that the computer is booted into Windows Preinstallation Environment (Windows PE), and thus the image can be modified offline—not the currently booted operating system.

To add language packs online to Windows Vista and Windows Server 2008

1. In Configuration Manager Console, expand Computer Management, and then expand Task Sequence. Right-click task_sequence (where task_sequence is the name of the task sequence to edit), and then click Edit.

2. In the Task Sequence Editor dialog box, click Add, click General, and then click Install Language Packs Online.

3. In the Task Sequence Editor dialog box, go to the State Restore phase.

4. Click the Restart Computer task.

5. Click Add, click MDT, and then click Install Language Packs Online.

6. Complete the appropriate Name and Description fields, and then click Browse to select an appropriate language pack package to install.

7. Click OK to save the settings, and then close the Task Sequence Editor.

   Note   When used with Microsoft Deployment, the term online means that the computer is booted into an operating system but run as an Administrator user so that final configurations can be made to the running operating system.

Top of Page

Add Updates

Use System Center Configuration Manager to add updates during the task sequence. Team members have the option to add updates online or offline. Manage software updates in System Center Configuration Manager using a server configured as a software update point. For detailed information on software updates using System Center Configuration Manager, see Tasks for Software Updates at http://technet.microsoft.com/en-us/library/bb693776.aspx.

Use deployment packages to deploy software updates; specifically, team members can use deployment packages. For more information about configuration and deployment of software update packages, see Download Updates Wizard at http://technet.microsoft.com/en-us/library/bb632835.aspx.

To install operating system updates online, the updates need to be added to a Deployment Management item. Create a Deployment Management item using the Deploy Package Wizard. For more information on Deploy Packages and Deployment Management, see the Configuration Manager Library at http://technet.microsoft.com/en-us/library/bb693754.aspx.

To add offline updates to Windows Vista

1. In Configuration Manager Console, expand Computer Management, and then expand Task Sequence. Right-click task_sequence (where task_sequence is the name of the task sequence to edit), and then click Edit.

2. Beneath the Postinstall phase, locate the Setup Windows and ConfigMgr task.

3. Click the task immediately above this task, so that the new added task will be positioned just above the Setup Windows and ConfigMgr task.

4. In the Task Sequence Editor dialog box, click Add, click MDT, and then click Install Updates Offline.

5. Complete the appropriate Name and Description fields, and then click Browse to select an appropriate updates package to install.

6. Click OK to save the settings, and then close the Task Sequence Editor.

To add online updates to Windows XP , Windows Server 2003 , Windows Server 2008 , and Windows Vista

1. In Configuration Manager Console, expand Computer Management, and then expand Task Sequence. Right-click task_sequence (where task_sequence is the name of the task sequence to edit), and then click Edit.

2. In the Task Sequence Editor dialog box, go to the State Restore phase.

3. Click the Restart Computer task.

4. Click Add, click MDT, and then click Install Updates Online.

5. Complete the appropriate Name and Description fields, and then click Browse to select an appropriate updates package to install.

6. Click OK to save the settings, and then close the Task Sequence Editor.

Note   Team members must set the Software Update Point role and Windows Server Update Services (WSUS) for this purpose. Use the Install Software Updates task to accomplish this task.

Top of Page

Create an Operating System Image Capture Image

When a reference computer has been built that must be captured to be deployed using System Center Configuration Manager, first capture that image and add it to Configuration Manager Console as an operating system image package. The Image Capture image is created using an operating system deployment media task sequence. For additional guidance on this process, see “Sample Build and Capture Operating System Image Task Sequence” in the Configuration Manager Documentation Library.

Top of Page

Install an Existing Image Package Using the Import Microsoft Deployment Task Sequence Wizard and the Client Task Sequence

To install an existing image package using the Microsoft Deployment client task sequence, complete the following steps:

1. In Configuration Manager Console, expand Computer Management, and then expand Operating System Deployment.

2. Right-click Task Sequences, and then point to Import Microsoft Deployment Task Sequence. Click Client Task Sequence, and then click Next.

3. On the General page, type the relevant information in the following boxes, and then click Next:

   • Task Sequence Name: A name for the task sequence.

   • Comments: Optional comments.

4. On the Details page, in the Join workgroup or domain section, choose the appropriate settings to either add the computer to a workgroup if building a reference image, or to a domain, if required.

5. If adding the computer to a domain, click Set to configure appropriate credentials to add the computer to the designated domain.

6. In the Windows Settings section, type:

   • User Name: The owner of this copy of Windows.

   • Organization name: The organization name.

   • Product key: Product key, usually a 25-character alphanumeric value.

7. In the Capture Operating System Image settings field, type a UNC path to a location and file name, as listed below, and click Next to advance to the Boot Image page.

   • Capture destination: \\servername\sharename\%computername%.wim.

   • Capture account: Click Set to type appropriate credentials with Write access to the capture destination share location.

8. On the Boot Image page, click Browse to locate an existing boot image package in the Select a Package dialog box, and then click Next.

9. On the MDT Package page, click one of the following options:

   • Specify a new Microsoft Deployment Files package: Click Browse to select an existing MDT tools package.

   • Create a new Microsoft Deployment Files package: Browse to the location of the appropriate deployment point created in Deployment Workbench.

10. On the OS Image page, browse to select an existing image package for deployment, and then click Next.

    Note   This page also allows team members to create a new operating system package by browsing to a .wim file that will create a new System Center Configuration Manager package.

11. On the Client Package page, click Browse to select an existing ConfigMgr client package to install, and then click Next.

12. On the USMT Package page, as listed below, specify the USMT package, and then click Next.

    • Specify an existing USMT Package: Click Browse to select a USMT package.

13. On the Settings Package page, browse to select a settings package.

14. On the Select a Sysprep Package page, if deploying Windows, click No Sysprep Package is required, because Sysprep in already in the operating system image.

15. If deploying Windows XP with SP2, select one of the following selections, and then click Finish :

    • Select an existing Sysprep package: Browse to select an existing Sysprep package.

    • Create a new Sysprep package: Browse to the location of the existing Sysprep files, such as C:\Sysprep, and type the package path to store the created package.

16. The Summary page shows the details of the selections made while completing the wizard. Click Close to return to Configuration Manager Console.

Top of Page

Use the Import Microsoft Deployment Task Sequence Wizard and the Client Replace Task Sequence

Microsoft Deployment provides a Client Replace task sequence. This task sequence is primarily used to capture the user state data from an existing computer so that it can be restored on a user’s new destination computer. To create a Client Replace task sequence, team members import the Microsoft Deployment Client Replace task sequence for use in Replace Computer scenarios. The team must associate a computer with System Center Configuration Manager before running the client task sequence. Without the computer association, it is not possible to restore the captured user state on the new computer. It is also not possible to add a computer association with System Center Configuration Manager after the user state has already been captured from the old computer.

To create a Client Replace task sequence

1. In Configuration Manager Console, expand Computer Management, and then expand Operating System Deployment.

2. Right-click Task Sequences, point to Import Microsoft Deployment Task Sequence, and then click Client Replace Task Sequence. Click Next.

3. On the General page, type the relevant information in the following boxes, and then click Next:

   • Task Sequence Name: An appropriate name for the task sequence.

   • Comments: Optional comments.

4. Click Next to advance to the Boot Image page.

5. On the Boot Image page, click Browse to locate an existing boot image package in the Select a Package dialog box.

6. Click Next.

7. On the MDT Package page, click one of the following options:

   • Specify a new Microsoft Deployment files package: Click Browse to select an existing MDT tools package.

   • Create a new Microsoft Deployment files package: Browse to the location of the appropriate deployment point created in Deployment Workbench.

8. Click Next.

9. On the USMT Package page, browse to select a USMT package. Click Next.

10. On the Settings Package page, click Browse to select a settings package, and then click Next.

    The wizard finishes and returns to Configuration Manager Console.

Top of Page

Use the Import Microsoft Deployment Task Sequence Wizard and the Server Task Sequence

Microsoft Deployment provides a task sequence that can be used for server deployment. This task sequence is used to completely automate the build, capture, and deployment of Windows Server 2003 or Windows Server 2008. To create a server task sequence, Image Engineering feature team members import the Microsoft Deployment server task sequence into Configuration Manager Console.

To create a server task sequence

1. In Configuration Manager Console, expand Computer Management, and then expand Operating System Deployment.

2. Right-click Task Sequences, point to Import Microsoft Deployment Task Sequence, click Server Task Sequence, and then click Next.

3. On the General page, type the relevant information in the following boxes, and then click Next:

   • Task Sequence Name: An appropriate name for the task sequence.

   • Comments: Optional comments.

4. On the Details page, in the Join workgroup or domain section choose the appropriate settings to either add the computer to a workgroup if building a reference image, or to a domain if required.

5. If adding the computer to a domain, click the Set button to configure appropriate credentials to add the computer to the designated domain.

6. In the Windows Settings section of the dialog box, type the relevant information in the following boxes:

   • User Name: The owner of this copy of Windows.

   • Organization name: The organization name.

   • Product key: Product key, usually a 25 character alphanumeric value.

7. In the Capture Operating System Image settings field, enter an UNC path to a location and filename, such as:

   • Capture destination: \\servername\sharename\%computername%.wim.

   • Capture account:  Click the Set button to enter appropriate credentials with Write access to the capture destination share location.

8. Click Next to advance to the Boot Image page of the wizard.

9. On the Boot Image page, click the Browse button to locate an existing Boot Image package in the Select a Package dialog box.

   Note   Alternatively, use the Create a new boot image package field by typing a UNC path to store the newly created image package; and then click Next to continue.

10. On the MDT Package page, click one of the following to:

    • Specify a new Microsoft Deployment Files package: Click Browse to select an existing MDT tools package.

    • Create a new Microsoft Deployment Files package: Browse to the location of the appropriate deployment point created with Deployment Workbench.

11. Click Next.

12. On the OS Image page, click one of the following options:

    • Specify an existing OS image: Browse to select an existing server image package.

    • Create a new OS Image: Browse to the location of an existing server WIM image, and then define the location to store the resulting server image package.

    • Specify an existing OS Install Package: Browse to select an existing server OS install package.

    • Create a new OS Install Package: Select this option to install and capture a new Windows Server 2003 OS install package from the “flat” operating system source files.

13. Click Next.

14. On the Client Package page, click one of the following:

    • Specify an existing ConfigMgr Client package: Browse to select an appropriate System Center Configuration Manager client installation package.

    • Create a new ConfigMgr Client package: If this option is selected, the wizard creates a new System Center Configuration Manager client package.

      Note   This page is for the installation of the ConfigMgr Client and is not specific to the client operating system installation.

15. Click Next.

16. On the Settings Package page, click Browse to select a settings package.

17. On the Select a Sysprep Package page, if deploying Windows Server 2008, click No Sysprep Package is required, because Sysprep in already part of the operating system image.

18. If deploying a version of Windows Server 2003, click one of the following options:

    • Select an existing Sysprep Package: Browse to select an existing Sysprep package.

    • Create a new Sysprep package: Browse to the location of the existing Sysprep files, such as C:\Sysprep, and type the package path to store the created package.

19. Click Next.

    The wizard finishes and returns to Configuration Manager Console.

Top of Page

Download

Get the Microsoft Deployment Solution Accelerator

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions

Top of Page