ConfigMgr 2007: How to properly set up a Task Sequence to deploy Windows 7 images captured via an Configuration Manager 2007 Capture CD

Article ID: 2009592
Expand all | Collapse all

Symptoms

When a Task Sequence is created via the "Create New Task Sequence Wizard", the Task Sequence may fail if the Windows OS being deployed is Windows 7 and the reference Windows 7 WIM image being deployed was manually created and then captured using the Configuration Manager 2007 Capture CD.  The Task Sequence Error dialog may show one of the following errors:

Task Sequence: <Task_Sequence_Name> has failed with the error code (0x8000FFFF). For more information, please contact your system administrator or helpdesk operator.

or

Task Sequence: <Task_Sequence_Name> has failed with the error code (0x80070070). For more information, please contact your system administrator or helpdesk operator.

Examining the SMSTS.log(s) may also reveal one or more of the following errors:

Partition 1 larger than remaining disk space. Requested partition size: <X>, remaining size: <Value_smaller_than_X> OSDDiskPart
LoadPartitionConfiguration( i, oDisk, cbDiskSize, cbContainerPartitionSize, pCurPartition), HRESULT=8000ffff (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,751) OSDDiskPart
LoadDiskConfiguration(oDisk), HRESULT=8000ffff (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,1412) OSDDiskPart
Invalid configuration specified.  Please ensure that the task sequence is properly configured. OSDDiskPart
OSDDiskPart.exe failed: 0x8000ffff OSDDiskPart
Process completed with exit code 2147549183 TSManager
!--------------------------------------------------------------------------------------------! TSManager
Failed to run the action: Partition Disk.
Catastrophic failure (Error: 8000FFFF; Source: Windows) TSManager

or

Successfully wiped C:\ ApplyOperatingSystem
Applying image to C:\ ApplyOperatingSystem
Applying image 2 to volume C: ApplyOperatingSystem
WIM error:C:\Windows\winsxs\x86_microsoft-windows-mulanttsvoiceenudsk_31bf3856ad364e35_6.1.7600.16385_none_0f51daf70520cd99\M1033DSK.CSD.
There is not enough space on the disk. (Error: 80070070; Source: Windows) ApplyOperatingSystem
WIMApplyImage( hVolumeImage, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY), HRESULT=80070070 (e:\nts_sms_fre\sms\framework\tscore\wimfile.cpp,512) ApplyOperatingSystem
Unable to apply (0x80070070) ApplyOperatingSystem
this->imageFile.ApplyVolumeImage(imageIndex, this->targetVolume), HRESULT=80070070 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,707) ApplyOperatingSystem
ApplyImage(), HRESULT=80070070 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1416) ApplyOperatingSystem
Apply(), HRESULT=80070070 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1456) ApplyOperatingSystem
Installation of image 2 in package SP20001C failed to complete..
There is not enough space on the disk. (Error: 80070070; Source: Windows) ApplyOperatingSystem

Failed to run the action: Apply Operating System.
There is not enough space on the disk. (Error: 80070070; Source: Windows) TSManager

Cause

The issue can occur because of two reasons:

1. The "Create New Task Sequence Wizard" creates the Task Sequence with the "Apply Operating System" task and "Apply Data Image 1" task in the incorrect order.

2. The "Create New Task Sequence Wizard" creates a partition the size of the hard drive where the Task Sequence was created, which usually will not match up with the size of the hard drive where the Task Sequence is deployed to.

The Data Image being applied in these scenarios is normally a 100MB boot partition that contains the boot manager and boot files. Normally the boot manager and boot files are installed on the same partition as the Windows OS. However the reason this separate partition is created is to account for a possible future installation and use of BitLocker. If BitLocker is being used, the boot manager and boot files need to reside on a partition that is not encrypted. Putting the boot manager and boot files on a separate partition allows the partition containing the Windows OS to be encrypted, but leaves the partition containing the boot manager and boot files to be unencrypted.

The separate 100MB partition is not a requirement. Only one partition can still be created and the boot manager and boot files can still be installed on the same partition as the Windows OS. However creating the 100MB partition at Windows installation time makes the process of installing and enabling BitLocker in the future less complex.

Please see the More Information section for a detailed explanation.

Resolution

Use one of the below methods to resolve the issue.

  • If the 100MB partition is desired, Method 1 is preferred because it is less complex.
  • If no 100MB partition is desired, use Method 3.

Note that in Methods 1 & 2 below, the size of the boot partition is purposely changed from 100MB to 300MB. This is to account for future reimage scenarios when WinPE may need to be staged on the local hard drive and/or to allow enough room for WinRE* to be stored on the partition. A 100MB partition is not large enough to stage WinPE onto and/or to install WinRE onto. Increasing this partition size from 100MB to 300MB will ensure WinPE can be properly staged on this partition and/or install WinRE onto without running out of space. Despite this change, the below instructions still refers to this partition as the "100MB partition".

In all methods, the Boot Manager is installed by the "Setup windows and ConfigMgr" task based on which partition is marked with the "Make this the boot partition" option.

Note: WinRe, or the Windows Recovery environment, is a bootable Windows OS based on Windows PE (WinPE) that allows recovery of a Windows Operating System. Normally WinRE is installed on the same partition as the Windows OS. However, under certain circumstances, when BitLocker is installed and enabled on a PC, WinRE is moved to the unencrypted boot partition. This allows WinRE to still be booted to for recovery purposes.


Method 1:

1. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Operating System Images" node, right click on the Windows 7 image being deployed and choose "Properties".

2. Click on the "Images" tab.

3. Under the option "Select image you want to view:", switch between the different images (i.e., "1-1" or "2-2") that are contained in the WIM file. Determine which image, i.e. 1-1 or 2-2, contains the Windows installation. The image that contains the Windows installation will have information next to the fields "OS version", "Architecture", "HAL Type", and "Description". The non-Windows data image will not have anything next to these fields.

4. Click on the "OK button.

5. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node, right click the affected Task Sequence and choose “Edit”.

6. In the left pane of the Task Sequence select "Partition Disk".

7. Double click on the first item under "Volume" to bring up the "Partition Properties".

8. In the "Partition Properties" window:

  • Under "Partition options", change the value next to "Use specific size" from 100 MB to 300 MB.
  • Under "Partition options", make sure that the option "Make this the boot partition" is set.
  • Under “Formatting options”, make sure the “Quick Format” option is selected.
  • Click on the "OK" button.

9. Double click on the second item under "Volume:" to bring up the "Partition Properties" window.

10. In the "Partition Properties" window:

  • Under "Partition options", select "Use a percentage of remaining free space" and set the field "Size(%)" to "100".
  • Under "Formatting options", make sure the "Quick Format" option is selected.
  • Click on the "OK" button.

11. Select the "Apply Operating System" task.

12. Under the "Apply operating system from a captured image" option, make sure that the "Image:" drop down menu is set to the Windows installation image as determined in Step 3 (i.e., "1-1" or "2-2").

13. Select the "Apply Data Image 1" task.

14. Under the "Select the image from this package that you want to apply. This image can not contain any operating system." option, make sure the "Image:" drop down menu is set  to the non-Windows data image as determined in Step 3 (i.e., 1-1 or 2-2).

15. Move the "Apply Data Image 1" task immediately BEFORE the "Apply Operating System" task, but AFTER the "Partition Disk" task.

16. Click on the "OK" button to save the changes to the Task Sequence.

In Method 1, the 100 MB boot partition that was captured using the Capture Media is applied first via the "Apply Data Image 1" task. This allows the "Apply Operating System" task that follows it to move on to the second partition and apply the Windows OS image to the second larger partition via the option "Next available formatted partition". If we did not include the "Apply Data Image 1" task or the "Apply Data Image 1" task is after the "Apply Operating System" task, the Task Sequence would try to apply the Windows OS image on the first smaller partition instead of the second larger partition. This would cause the "There is not enough space on the disk" since the size of the WIM image is larger than the partition size.


Method 2:

1. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Operating System Images" node, right click on the Windows 7 image being deployed and choose "Properties".

2. Click on the "Images" tab.

3. Under the option "Select image you want to view:", switch between the different images (i.e., "1-1" or "2-2") that are contained in the WIM file. Determine which image, i.e. 1-1 or 2-2, contains the Windows installation. The image that contains the Windows installation will have information next to the fields "OS version", "Architecture", "HAL Type", and "Description". The non-Windows data image will not have anything next to these fields.

4. Click on the "OK button.

5. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node, right click the affected Task Sequence and choose "Edit".

6. In the left pane of the Task Sequence select "Partition Disk".

7. Double click on the first item under "Volume" to bring up the "Partition Properties".

8. In the "Partition Properties" window:

  • Under "Partition options", change the value next to "Use specific size" from 100 MB to 300 MB.
  • Under "Partition options", make sure that the option "Make this the boot partition" is set.
  • Under "Formatting options”, make sure the "Quick Format" option is selected.
  • Under "Advance options" in the field "Variable: " type:

    BOOTPART

  • Click on the "OK" button.

9. Double click on the second item under “Volume:" to bring up the "Partition Properties".

10. In the "Partition Properties" window:

  • Under “Partition options”,select "Use a percentage of remaining free space". Set the "Size(%)" field to "100".
  • Under "Formatting options", make sure the "Quick Format" option is selected.
  • Under "Advance options" in the field "Variable:" type:

    OSPART

  • Click on the "OK" button.

11. Select the "Apply Operating System" task. In the "Apply Operating System" task:

  • Under the "Apply operating system from a captured image" option, make sure that the "Image:" drop down menu is set to the Windows installation image as determined in Step 3 (i.e., "1-1" or "2-2").
  • Under the “Select the location where you want to apply this operating system.” option, select from the "Destination:" drop-down menu and choose "Logical drive letter stored in a variable".
  • Under the "Select the location where you want to apply this operating system." option, in the "Variable name:" field, type:

    OSPART

12a. Select the "Apply Data Image 1" task. In the "Apply Data Image 1" task:

  • Under the "Select the image from this package that you want to apply. This image can not contain any operating system." option, make sure the "Image:" drop down menu is set to the non-Windows data image as determined in Step 3 (1-1 or 2-2).
  • Under the “Select the location where you want to apply the image.” option, select from the "Destination:" drop-down menu and choose "Logical drive letter stored in a variable".
  • Under the "Select the location where you want to apply the image." option, in the "Variable name:" field, type:

    BOOTPART

12b. As an alternative, the "Apply Data Image 1" task is actually not needed and can either be removed or disabled. To disable the task, select the "Apply Data Image 1" task, click on the "Options" tab, and then select the option "Disable this step". To delete the task, select the "Apply Data Image 1" task, right click on it, and then select "Delete".

13. Click on the "OK" button to save the changes to the Task Sequence.

In Method 2, we can install the images "out of order" by specifically specifying what partition each image should be installed onto. Additionally, using this method, we do not actually have to install the Data Image that contains the 100MB boot partition. This Data Image only contains the Boot Manager and boot files, and since the Boot Manager and boot files are removed and then reinstalled by the "Setup windows and ConfigMgr" task, the Data Image does not need to be applied.


Method 3:

Method 3 should only be used to create only one partition that fills the entire hard drive in cases where the 100MB partition is not desired for either immediate or future use of BitLocker:

1. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Operating System Images" node, right click on the Windows 7 image being deployed and choose "Properties".

2. Click on the "Images" tab.

3. Under the option "Select image you want to view:", switch between the different images (i.e., "1-1" or "2-2") that are contained in the WIM file. Determine which image, i.e. 1-1 or 2-2, contains the Windows installation. The image that contains the Windows installation will have information next to the fields "OS version", "Architecture", "HAL Type", and "Description". The non-Windows data image will not have anything next to these fields.

4. Click on the "OK button.

5. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node, right click the affected Task Sequence and choose “Edit”.

6. In the left pane of the Task Sequence select “Partition Disk”.

7. Double click on the first item under “Volume” to bring up the “Partition Properties”.

8. In the "Partition Properties" window:

  • Under "Partition options", select "Use a percentage of remaining free space" and set the field "Size(%)" to "100".
  • Under "Formatting options", make sure the "Quick Format" option is selected.
  • Click on the "OK" button.

9. Single click on the second item under “Volume:” to highlight it, and then click on the red “X” button to delete it.

10. Select the “Apply Operating System” task.

11. Under the "Apply operating system from a captured image" option, make sure that the "Image:" drop down menu is set to the Windows installation image as determined in Step 3 (i.e., "1-1" or "2-2").

12. Select the “Apply Data Image 1” task.

13. The "Apply Data Image 1" task is not needed and can either be removed or disabled. To disable the task, select the "Apply Data Image 1" task, click on the "Options" tab, and then select the option "Disable this step". To delete the task, select the "Apply Data Image 1" task, right click on it, and then select "Delete". Make sure to take either one of these two actions.

14. Click on the "OK" button to save the changes to the Task Sequence.

Method 3 is actually the exact way that Task Sequences are created by the "New Task Sequence Wizard" when deploying non-Windows 7 OSes.

 

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2009592 - Last Review: August 4, 2010 - Revision: 16.0
Keywords: 
KB2009592

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com