[an error occurred while processing this directive]

The Create MDT Task Sequence Wizard substitutes the packages and images selected for the placeholders in the task sequence templates. After completing the wizard, the new task sequence references the appropriate packages and images.

Note   Always use the Create MDT Task Sequence Wizard to create task sequences based on the MDT task sequence templates. Although you can manually import the task sequence templates, doing so is not recommend.

To create a ZTI task sequence using the Create MDT Task Sequence Wizard

1.   Click Start, and then point to All Programs. Point to Microsoft System Center, point to Configuration Manager 2007, and then click ConfigMgr Console.

2.   In the Configuration Manager console navigation pane, go to Site Database/Computer Management/Task Sequences.

3.   In the Actions pane, click Create MDT Task Sequence.

The Create MDT Task Sequence Wizard starts.

4.   Complete the Create MDT Task Sequence Wizard using the information in Table 133. Accept the default values unless otherwise specified.

Table 133. Information for Completing the Create MDT Task Sequence Wizard

On this wizard page

Do this

Choose Template

1.   In The following SCCM task sequence templates are available, select task_sequence_template (where task_sequence_template is the task sequence template to be selected from Table 118).

2.   Click Next.

Choose Template: General

1.   In Task sequence name, type task_sequence_name (where task_sequence_name is the name of the task sequence displayed in the Configuration Manager console).

2.   In Task sequence comments, type comment (where comment is descriptive text that describes the purpose of the task sequence).

3.   Click Next.

Choose Template: Details

1.   Select Join a workgroup.

The other option is Join a domain. If you select this option, in Workgroup, type workgroup_name (where workgroup_name is the name of the workgroup to join).

2.   Select Join a domain.

The other option is Join a workgroup. If you select this option, perform the following steps:

a.   In Domain, type domain_name (where domain_name is the name of the workgroup to join).

b.   Click Set.

The Windows User Account dialog box appears.

c.   In the Windows User Account dialog box, in User name, type domain_name\user_name (where user_name is the name of the user account used to join the computer to the domain and domain_name is the name of the domain in which the user account resides. This account must be a member of the Domain Admins group in the domain or have sufficient delegated permissions).

d.   In Password and Confirm password, type password (where password is the password for the user account), and then click OK.

3.   In User name, type user_name (where user_name is the name of the registered user that appears in the Windows operating system properties).

4.   In Organization name, type organization_name (where organization_name is the name of the registered organization that appears in the Windows operating system properties).

5.   In Product key, type product_key (where product_key is the product key for operating system).

6.   Click Next.

Choose Template: Capture Settings

1.   Select This task sequence will never be used to capture and image.

The other option is This task sequence may be used to capture and image.

2.   Select This task sequence may be used to capture and image.

The other option is This task sequence will never be used to capture and image. If you select this option, perform the following steps:

a.   In Capture destination, type unc_path (where unc_path is the fully qualified UNC path for the location of the WIM file, including the name of the WIM file).

b.   Click Set.

The Windows User Account dialog box appears.

c.   In the Windows User Account dialog box, in User name, type domain_name\user_name (where user_name is the name of the user account that has Write permission to the folder specified in Capture destination and domain_name is the name of the domain in which the user account resides).

d.   In Password and Confirm password, type password (where password is the password for the user account), and then click OK.

3.   Click Next.

Boot Image

1.   Select Specify an existing boot image.

The other option is Create a new boot image package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In Select a Package dialog box, click package_name (where package_name is the name of the existing boot image), and then click OK.

2.   Select Create a new boot image package.

The other option is Create a new boot image package. If you select this option, in Package source to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

The Configuration Manager 2007 R3 service account must have permission to modify the contents of this UNC path to update the boot images. Ensure that the Configuration Manager 2007 R3 service account has the appropriate permission on this network shared folder.

Tip   You can also click Browse to locate the UNC path.

3.   Click Next.

Boot Image: General Settings

Note   This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the boot image package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the boot image package).

3.   In Comments, type comment_text (where comment_text is descriptive information about the boot image package).

4.   Click Next.

Boot Image: Components

Note   This wizard page appears only if you select Create a new boot image package on the Boot Image wizard page.

1.   In Platform, click platform (where platform is the platform architecture for the boot image—x86 or X64).

2.   Select or clear the ADO check box if you want to add ADO components to the boot image, which is needed to access SQL Server databases such as the MDT DB. By default, this check box is selected. If the check box is:

·     Selected, the ADO components are added to the boot image

·     Cleared, the ADO components are not added to the boot image

Note   Scripting, Hypertext Markup Language Application (HTA), XML, and WMI support are always added to the boot image.

3.   Select or clear the font check box (where font is the name of the font to be added, which can be Chinese [ZH-CN], Chinese [ZH-HK], Chinese [ZH-TW], Japanese [JA-JP], or Korean [KO-KR]) to add support for the optional fonts.

4.   Click Next.

Boot Image: Customization

1.   Select or clear the Add prestart command files to enable the Deployment Wizard for this boot media check box. If this check box is:

·     Selected, the prestart command files are added to the boot image. In Command line, type the prestart command script to run, which defaults to ZTIMediaHook.wsf. In Folder for prestart command files, type unc_path (where unc_path is the fully qualified UNC path to a writable folder).

Note   Alternatively, click Browse to find the folder in which the prestart command files reside.

·     Cleared, the prestart command files are not added to the boot image.

2.   Select or clear the Add extra files to the new boot image check box. If this check box is:

·     Selected, the extra files are added to the boot image. In Path, type path (where path is the fully qualified or relative local or UNC path to a writable folder).

Note   Alternatively, click Browse to find the folder in which the extra files reside.

·     Cleared, the extra files are not added to the boot image.

3.   In Use a custom background bitmap file (UNC Path), type unc_path (where unc_path is the fully qualified UNC path to the bitmap file that you want to use as the background).

Note   Alternatively, click Browse to find the bitmap file.

4.   Select or clear the Enable command support (F8) check box.

5.   Click Next.

MDT Package

1.   Select Specify an existing Microsoft Deployment Toolkit files package.

The other option is Create a new Microsoft Deployment Toolkit files package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

2.   Select Create a new Microsoft Deployment Toolkit files package.

The other option is Specify an existing Microsoft Deployment Toolkit files package. If you select this option, in Package source to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

3.   Click Next.

MDT Package: MDT Details

Note   This wizard page appears only if you select Create a new Microsoft Deployment Toolkit files package on the MDT Package wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the Microsoft Deployment Toolkit files package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the Microsoft Deployment Toolkit files package).

3.   In Language, type language (where language is the language of the Microsoft Deployment Toolkit files package).

4.   In Manufacturer, type manufacturer (where manufacturer is the manufacturer of the Microsoft Deployment Toolkit files package).

5.   In Comments, type comment_text (where comment_text is descriptive information about the Microsoft Deployment Toolkit files package).

6.   Click Next.

OS Image

On this wizard page, you can select (or create) OS image packages or OS install packages. OS image packages are created from WIM files either from distribution media or from custom WIM files you have created. OS install packages contain all the necessary files to install the operating system, such as the contents of a Windows XP CD.

Note   The ZTI task sequence templates always configure the Apply Operating System Image task sequence step to deploy the image index equal to 1. If you want to deploy an image with a different index, change the configuration of the Apply Operating System Image task sequence step.

Also, if you select a SKU that is different from the default SKU, remove the following section from Unattend.xml in the Settings package:

<MetaData>

   <Key>/image/index</Key>

   <Value>1</Value>

</MetaTag>

 

1.   Select Specify an existing OS image.

The other options are Create a new OS image, Specify an existing OS installation package, or Create a new OS install package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

2.   Select Create a new OS image.

The other options are Specify an existing OS image, Specify an existing OS installation package, or Create a new OS install package. If you select this option, perform the following steps:

a.   In OS image file (WIM) location, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the WIM file is located, including the name of the WIM file).

Tip   You can also click Browse to locate the WIM file.

b.   In Package source folder to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

3.   Select Specify an existing OS installation package.

The other options are Specify an existing OS image, Create a new OS image, or Create a new OS install package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

4.   Select Create a new OS install package.

The other options are Specify an existing OS image, Create a new OS image, or Specify an existing OS installation package.

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.

If you select this option, perform the following steps:

a.   In OS installation folder location, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

b.   In Package source folder to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

5.   Click Next.

OS Image: Image Details

Note   This wizard page appears only if you select Create a new OS image on the OS Image wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the package).

3.   In Comments, type comment_text (where comment_text is descriptive information about the package).

4.   Click Next.

OS Image: Install Source

Note   This wizard page appears only if you select Create a new OS install package on the OS Image wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the package).

3.   In Comments, type comment_text (where comment_text is descriptive information about the package).

4.   Click Next.

OS Image: OS Image Index

1.   In The selected operating system image (WIM) file contains multiple images. Specify which image you would like to deploy, select image_index (where image_index is the image index of the image that contains the operating system you want to deploy).

2.   Click Next.

Client Package

1.   Select Specify an existing ConfigMgr client package.

The other option is Create a new ConfigMgr client package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

2.   Select Create a new ConfigMgr client package.

The other option is Specify an existing ConfigMgr client package.

3.   Click Next.

USMT Package

Note   You cannot specify the location for storing the user state migration data in the CustomSettings.ini file for ZTI using Configuration Manager 2007 R3. The Request state store task automatically determines the state migration point to use for storing user state migration data. For more information, see the section, “How to Capture and Restore User State,” in the Configuration Manager 2007 Documentation Library, which is installed with Configuration Manager 2007 R3.

1.   Select Specify an existing USMT package.

The other option is Create a new USMT package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

2.   Select Create a new USMT package.

The other option is Specify an existing USMT package. If you select this option, perform the following steps:

a.   In Path to USMT executables and related, type path (where path is the fully qualified path for the location of the folder in which the USMT source files are located).

Tip   You can also click Browse to locate the path.

b.   In Package source to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

3.   Click Next.

Note   USMT can only back up and restore locally cached user profiles, not network copies. For more information on using roaming profiles, see the Managing Roaming User Data Deployment Guide.

USMT Package: USMT Details

Note   This wizard page appears only if you select Create a new USMT package on the USMT Package wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the package).

3.   In Language, type language (where language is the language of the package).

4.   In Manufacturer, type manufacturer_name (where manufacturer_name is the name of the software manufacturer in the package).

5.   In Comments, type comment_text (where comment_text is descriptive information about the package).

6.   Click Next.

Settings Package

1.   Select Specify an existing settings package.

The other option is Create a new settings package. Select this option for Windows 7 or Windows Vista operating systems. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

2.   Click Create a new settings package.

The other option is Specify an existing settings package.

If you select this option, in Package source to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

3.   Click Next.

Settings Package: Settings Details

Note   This wizard page appears only if you select Create a new settings package on the Settings Package wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the package).

3.   In Language, type language (where language is the language of the package).

4.   In Manufacturer, type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package).

5.   In Comments, type comment_text (where comment_text is descriptive information about the package).

6.   Click Next.

Sysprep Package

1.   Select No Sysprep package is required.

The other options are Specify an existing Sysprep package and Create a new settings package.

2.   Select Specify an existing Sysprep package.

The other options are No Sysprep package is required and Create a new settings package. If you select this option, perform the following steps:

a.   Click Browse.

The Select a Package dialog box appears.

b.   In the Select a Package dialog box, click package_name (where package_name is the name of the existing package), and then click OK.

3.   Select Create a new Sysprep package.

The other option is Specify an existing settings package. If you select this option, perform the following steps:

a.   In Path to Sysprep executables and related, type path (where path is the fully qualified path for the location of the folder in which the Sysprep source files reside).

Tip   You can also click Browse to locate the path.

b.   In Package source to be created, type unc_path (where unc_path is the fully qualified UNC path for the location of the folder in which the package source will be stored).

Tip   You can also click Browse to locate the UNC path.

4.   Click Next.

Sysprep Package: Sysprep Details

Note   This wizard page appears only if you select Create a new Sysprep package on the Sysprep Package wizard page.

1.   In Name, type package_name (where package_name is the name to be given to the package).

2.   In Version, type version_number (where version_number is the version number to be assigned to the package).

3.   In Language, type language (where language is the language of the package).

4.   In Manufacturer, type manufacturer_name (where manufacturer_name is the name of the manufacturer for the software in the package).

5.   In Comments, type comment_text (where comment_text is descriptive information about the package).

6.   Click Next.

Summary

Click Next.

 

The Summary wizard page displays a status bar that shows the progress of the tasks defined in the wizard. The Create MDT Task Sequence Wizard closes when the task sequence is created.

Related Topics

Creating a ZTI Task Sequence Using MDT Task Sequence Templates in Configuration Manager 2007 R3

[an error occurred while processing this directive]