How to properly set up a Task Sequence to deploy Windows 7 images captured via an SCCM 2007 Capture CD

How to properly set up a Task Sequence to deploy Windows 7 images captured via an SCCM 2007 Capture CD

  • Comments 9
  • Likes

imageWhen 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 SCCM 2007 Capture CD.

The Task Sequence Error dialog may show one of the following errors:

Error 1

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

Error 2

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) reveals one or more of the following errors:

Error 1

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
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager
Failed to run the last action: Partition Disk. Execution of task sequence failed.
Catastrophic failure (Error: 8000FFFF; Source: Windows) TSManager

Error 2

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
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager
Failed to run the last action: Apply Operating System. Execution of task sequence failed.
There is not enough space on the disk. (Error: 80070070; Source: Windows) TSManager

Cause

The issue may occur because of two reasons:

  1. The "Create New Task Sequence Wizard" may create 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" may create 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.
Resolution

Use one of the below methods to resolve the issue.  If the 100MB partition for BitLocker is desired, Method 1 is preferred because it is cleaner and less complex. If no 100MB partition is desired for BitLocker, use Method 3.

Method 1

1. Right click the affected Task Sequence and choose “Edit”.

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

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

4. Under “Formatting options”, select “Quick Format”. Make sure that the option "Make this the boot partition" is set. Click on the “OK” button.

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

6. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”.  Under “Formatting options”, select “Quick Format”.

7. Select the “Apply Operating System” task.

8. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”.

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

10. 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 “1-1”.

11. Move the “Apply Data Image 1” task immediately BEFORE the “Apply Operating System” task, but AFTER the “Partition Disk” task.

In Method 1, we apply the Data Image first via the "Apply Data Image 1" task, although the data image really doesn't contain anything we need. The reason we take this step is so that the "Apply Operating System" task that follows it moves on to the second partition via the option "Next available formatted partition". If we did not include the "Apply Data Image 1" task, the Task Sequence would try to apply the OS image on the first partition instead of the second partition.

Method 2

1. Right click the affected Task Sequence and choose “Edit”.

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

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

4. Under “Formatting options”, select “Quick Format”. In the “Variable: ” field under “Advance options”, type

BOOTPART

Make sure that the option "Make this the boot partition" is set. Click on the “OK” button.

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

6. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”.  Under “Formatting options”, select “Quick Format”. In the “Variable:” field under “Advance options”, type

OSPART

Click on the “OK” button.

7. Select the “Apply Operating System” task.

8. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”.

9. Under the “Select the location where you want to apply this operating system”, select from the “Destination:” drop-down menu “Logical drive letter stored in a variable”. In the “Variable name:” field, type

OSPART

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

11. In the right pane of the Task Sequence, click on the “Options” tab. Select “Disable this step”. As an alternative, you can also completely remove the “Apply Data Image 1” task instead of just simply disabling it.

12. Click on the “OK” button to save the changes to the Task Sequence.

In Method 2, we have specified specifically what partition the OS image should be installed onto and not allowed it "guess" via the option "Next available formatted partition". Via Steps 10 and 11, we also have chosen not to apply the 100MB partition data image because it does not contain anything we need so it is not necessary (the "Setup windows and ConfigMgr" task will take care of setting up the Boot Manager on this partition). These steps are actually necessary because if these steps are not taken, it can cause issues 4 & 5 listed in the More Information section. Assigning the variable “BOOTPART” in Step 4 above is actually also not necessary because the variable is never used, but is included to make a clear distinction between the Boot and Windows partitions.

Method 3

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

1. Right click the affected Task Sequence and choose “Edit”.

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

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

4. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”. Under “Formatting options”, select “Quick Format”. Make sure that the option "Make this the boot partition" is set. Click on the “OK” button.

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

6. Select the “Apply Operating System” task.

7. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”.

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

9. In the right pane of the Task Sequence, click on the “Options” tab. Select “Disable this step”. As an alternative, you can also completely remove the “Apply Data Image 1” task instead of just simply disabling it.

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

Hope this helps,

Frank Rojas | Configuration Manager Support Escalation Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • But, what about if we are doing migration using USMT hardlink, and we are facing this system partition problem.

    what we can we do about it , because as you know, there is no disk partition with hardlink migration.

    thanks

  • I knew I knew your name from somewhere. Looking forward to talking with you tomorrow if you've got the time.

  • Thanks you SO much for this fix. I'm just messing about with SCCM to see if we can migrate to it from another vendor's platform and hit this exact problem. Solution 1 made everything better (I hadn't actually bothered checking the size of partition 1 but it would make sense that defaulting to nearly 70GB when I only have a 60GB vhdx to play with would cause it to crash!).

  • and @Hired Geek- you're spot on. SCCM is fantastic, it's just huge and takes a bit of getting used to. (My biggest bug-bear with it is that the installer doesn't even bother trying to install required Windows features which is slightly annoying, but I've documented this now so should minimize future installs to a few warnings.)

  • This also fixed a TS created using the wizard in 2012R2

  • Thanks, I faced Error 1 and your solution worked for me

  • Thanks a lot, solutions 1 worked perfectly!