All Chapters about SCCM
13. Failed to run Task Sequence, 0x8007000D, 0x80070490, 0x80004005, solve from the client computer
13-1 Error Code
Sometimes we are stuck at the client end when running SCCM to deploy computers, especially on the used computers. The error message is "Failed to run Task Sequence" with some different code in different situation such as- 0x8007000D
- 0x80070490
- 0x80004005
Those 3 error messages tell the boot image from SCCM server is not able to locate to the boot disk of the client computer, the reason may be partition table is wrong, the disk volume is not able to find or disk is not partitioned in the proper format.
13-2 Solving problem from Server-side
You can use a task sequence variable "_OSDDetectedWinDrive" to scans the computer's hard drives for a previous operating system installation when Windows PE starts. The hard drive location for where the operating system is installed is stored in this variable. You can configure your task sequence to retrieve this value from the environment and use it to specify the same hard drive location to use for the new operating system. (Reference MS Task sequence variables)13-3 Solving problem from client-side
As you are in a large company, sometimes you are just a deployment guy, not the SCCM administrator. So you have to work it out from client-side.When the "Failed to run task sequence" windows appear, press "F8". it will pop up a command prompt. Then type those commands below
diskpart
list disk
select disk 0
clean
convert gpt
create partition efi size =300
assign letter=k
format quick fs=fat32
create partition msr size=128
create partition primary
assign letter=c
format quick fs=ntfs
exit
exit
Then click the "Previous" button on the "Failed to run task sequence" window and do the rest steps you used to do. It will work. The command above must run with the right order otherwise it will fail. DiskPart commands help you to manage your PC's drives. If you like to understand what the code mean, you can refer to DiskPart commands.
