1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Task Sequences.

2. In the Task Sequences pane, select the task sequence that you want to copy.

3. In the Action menu, or from the Actions pane, select Export.

4. In the Save As dialog box, select the location that the task sequence XML file should be saved and enter a file name for the task sequence file. You must save the task sequence as an .XML file.

5. If necessary, place the task sequence XML file on a network share that can be accessed by the other Configuration Manager 2007 site.

6. Using the Configuration Manager 2007 Administrator Console at the other Configuration Manager 2007 site, navigate to Task Sequences.

7. In the Action menu, or from the Actions pane, select Import.

8. Browse to the location of the task sequence XML file that you exported, select it, and click Open. Note the path to where the task sequence was imported to and click OK to confirm the import.

9. The task sequence should now be visible in the list of task sequences. You can also click Refresh the Actions pane to reload list of available task sequence.

   Note

   When you import a task sequence into another Configuration Manager 2007 site, it is important to remember that Configuration Manager 2007 only imports the task sequence. It does not import any boot image packages, operating system image packages, or software packages, user passwords, or product keys that are referenced by the task sequence. Consequently, the imported task sequence contains null references to those types of packages.

10. Select the imported task sequence and edit the task sequence at the new site.

    • Fix any broken package and program references that are needed by the task sequence. All associated programs must be accessible by the task sequence at the new site.
      
      
    • Reconfigure any task sequence steps that require a user account or password with appropriate credentials so the task sequence can run at the new Configuration Manager 2007 site.
      
      
    • If any task sequence steps require a unique product key, reconfigure the task sequence with the product key information that should be used at the new site.
      
      
    • If a boot image is required to run the task sequence you need to associate the task sequence with a boot image that is available at the new site. To associate a new boot image for the task sequence, by right-clicking the task sequence and choosing Properties. Select the Advanced tab and assign the new boot image.
      
      

11. Review the task sequence for any broken or null package references. You can do any of the following:

    • Configure the broken reference to specify an appropriate package at the new Configuration Manager 2007 site.
      
      
    • Remove the task sequence step that contains the broken reference.
      
      
    • Disable the task sequence step that contains the broken reference.
      
      
    • Create a conditional statement for that task sequence step that skips the reference.
      
      

    Note
    If you run a task sequence that has a task sequence step with a broken reference, by default the task sequence will generate an error for that task sequence step and continue to run.

12. Verify that all associated user accounts needed by the task sequence steps have the necessary permissions at the new site. For example; the task sequence may have a step that must have permissions to create a computer account, or connect to a network folder at the new site.

Other Resources