Archive
Task Sequence has failed with error code 0x80070017
I created standalone DVD’s to deploy my Windows 7 Task Sequence and when running the first DVD (of two) I was presented with the below error message.
To begin troubleshooting this I looked at the SMSTS.log file by pressing F8 to bring up the command prompt. (Assuming you enabled command support on the boot images) To examine the log file I copied it to a file share which has Trace32 installed.
You can see the syntax I used from the screenshot, I begin by mapping a drive to my SCCM server since it already has a share, then changing the directory to X:\Windows\Temp where the SMSTS.log file is kept and then use the “Copy” command to copy the file to my SCCM server. Once the file is on my server I can open the file using Trace32.
From the snippet you can just about make out the error “(Cyclic redundancy check) (Error: 80070017: Source: Windows)”
I burned another set of DVD’s and re-ran the deployment but it failed again with the same error code, re-creating the ISO files from the SCCM server had the same effect, I even used different software to burn the ISO files, burned the ISO’s at a slower speed and even tried another manufacturer’s DVD’s but again the results were the same, then I thought maybe my DVD burner on my laptop could be the problem so I used another system to burn the DVD’s and tested them and this time……….Success!!! I was able to deploy the image using the standalone media!!
Out of curiosity I wanted to confirm that it was my laptop’s DVD drive which cost me a few hours in copying and burning DVD’s for testing, so I re-created the media again and this time I selected the option to “Verify data after burning” <- I wish I selected this option the first time, could have saved me a lot of time and Voilà!! I found the culprit.
Task Sequence has failed with error code 0X00002004
I was experimenting with User State Migration Point and an in-place upgrade (In my case just a Windows 7 re-install) and after I had everything setup in my lab I ran the task sequence however I came across the below error message.
The error appears just as the TS requests the user state store. (Both of the test systems do not have KB974571 installed.) I was able to re-create the error on another machine and after looking into this further I found a fix on the Microsoft forum. I applied the fix found here and ran the TS successfully without issue.
Task Sequence has failed with error code 0x80070661
The other day I came across the below error message during OSD deployment in my lab, this threw me for a minute mostly because I’ve used the TS many times in the past without any issue.
I examined the SMSTS.log file and as soon as I saw the error I knew what the problem was, basically in my rush to get a system created to work on, I assigned an x64 application Software install into the TS (App-V client) to an x86 image!! Whoops!!
I ran through the deployment again with the correct version of the App-V client and as expected all was ok.
Task Sequence has failed with error code 0X80070490
A few months back when I first decided to use ConfigMgr OSD to deploy my system image (Of Windows 7) to new machines I came across the below error message
(I did remember to disable the flash on my phone this time, if you’ve seen my posts you’ll know what I mean)
Being new to ConfigMgr at the time I posted a question on the Microsoft System Centre Configuration Manager Forum (Link to original thread below)
The problem was my TS was deploying Image 1-1 which is the 100MB boot partition that Windows 7 creates during installation. This separate parition is not a requirement, one partition can be used for the boot manager\files and Windows OS.
I changed this to Image 2-2 and my TS ran through OK
I’ve found this post which explains it in more detail –
Advertising the Task Sequence
Right click on your TS in my case “Deploy v130 Image” under “Operating System Deployments\ Task Sequences” and click on “Advertise”
Click “Next” Make sure you place a tick in “Make this task sequence available to boot media and PXE”
Click on the yellow star and select “As soon as possible”, change the “Priority” to “High” using the drop down and select “Never rerun advertised program”
Then click “Next”
Match above and click “Next”
Click “Next”
Click “Next”
Click “Next”
Click “Close”
Once this has been done you will need to create a Computer Association in SCCM see – “Creating a Computer Association”
At this point change the Boot sequence on the laptop from the BIOS. For older systems you may need to enable PXE Boot on the Network card via the BIOS.
The restart the laptop and the download and install will begin.
Creating a Task Sequence
(There are many customisations you can make, the below is the basic sequence to deploy an image)
Expand “Operating System Deployment” and right click on “Task Sequence” and select “New\Task Sequence”
Click “Next”
Give a name for the task sequence and comment. The boot image you select will be the same architecture as the reference computer; in this case we know the Dell V130 is an X64 bit computer. Click “Next”
The Image Package is the image you recently captured from a reference computer then uploaded to the distribution point.
Image is 1-1 this is the C:\ on the reference computer if you have more than one partition or external USB drive connected these will appear as 2-2 and 3-3
Enter in the local Admin password to be used on the machine and click “Next”
Note: When I deployed this image it failed this is because the machine was built manually then an image captured from it. When a machine is manually built Windows created a 100MB system reserved partition which holds the Boot Manager and boot files by default. This partition separates the boot manager from the Windows OS files; the purpose of this is for the future use of Bit Locker. If BitLocker is being used, the boot manager and files reside on the partition that isn’t encrypted. The Windows OS partition will be encrypted.
Since IMS Research will not be utilising BitLocker, select 2-2 which contains the Windows OS from the captured .WIM file.
More information is found at – http://blogs.technet.com/b/configurationmgr/archive/2010/04/12/how-to-set-up-a-task-sequence-to-deploy-windows-7-images-captured-via-an-sccm-2007-capture-cd.aspx
Optional but I would like this machine to be joined to the domain so click Browse and select the domain then browse to the OU you would like to place the machine in. In this case I have chosen the X64 bit OU for Windows 7 client in the UK
Enter in the domain admin username and password then click “Next”
We want to install the SCCM client so click Browse and select the package and click “Next”
Un-tick all the options on this screen and click “Next”
We do not want to install Windows Updates – click “Next”
We have no other packages to install – click “Next”, “Next” again
Click “Next”
Click “CLOSE”
You can now see the newly created Task Sequence, right click and select “Edit”. (See below; look at the order of tasks under “Install Operating System”)
Drag – “Apply Network Settings” Under “Setup Operating System”
In the previous configuration it would have tried to join the computer to the domain before installing Network drivers.
Dipan M Patel 