Task Sequence Failed with the Error Code 0x80070002

175634

Task Sequence Failed with the Error Code 0x80070002

Error

ERROR: Task Sequence Failed with the Error Code 0x80070002. For more information, contact your system administrator or helpdesk operator.

Task Sequence Failed with the Error Code 0x80070002

 

Troubleshooting

Task Sequence Failed with the Error Code 0x80070002 – we see this error usually during the operating system deployment using SCCM 2012 R2. When you deploy the task sequence to a collection and when you boot the computer from the network, during the step “Applying Operating System” you encounter the Error Code 0x80070002. In this situation what one might think would be to check SMTS.log file. I would recommend that but there is something else that you need to check first. Error code 0x80070002 in SCCM 2012 can be interpreted as a network error wherein during the OSD the necessary files are not accessible by the computer where the operating system is being deployed.

 

Resolution

To fix the issue Error Code 0x80070002, we have to define the network access account. The Network Access account is used only for accessing the content and not for running the task sequence. This account should have the minimum appropriate permissions on operating system deployment content it needs to access. This account is important because the computer receiving the operating system does not have a security context it can use to access content on the network.

To configure the Network Access Account, open the CM2012 R2 console, click on Administration, expand Overview, expand Site Configuration, click Sites, on the top ribbon click Configure Site Components, click Software Distribution.

Task Sequence Failed with the Error Code 0x80070002

Click on the tab Network Access Account, choose Specify the account that accesses network locations (by default the option is set to Use the computer account of Configuration Manager client). Click on the orange icon and add the user account that enough permissions to access the content which is required while deploying Operating System.

Task Sequence Failed with the Error Code 0x80070002

48 COMMENTS

  1. Hi,

    0x80007002 can also be an error when the NIC drivers are not installed from the Task sequence.
    currently, i am facing this issue with lots of physical devices. I don’t wanted to use Auto apply device drivers step on my TS so, i have added separate driver package for all the devices in which i am running the TS. These steps are present with a condition to check for the device & then apply the drivers but the TS fails again & again. I am applying all the drivers before Apply network Settings step.

    Thanks,
    Pranay.

  2. This post helped me a lot, followed your steps and the issue got fixed. Thanks Prajwal. Can you also post the resolutions for other error codes ?

  3. I had the same problem and had a network Access Account already set up. In my case, I had to clear the network access account, restart the SCCM server, and then re-add the access account for my 80070002 errors to go away.

  4. I am also getting same error (ox80070002). But i get this after applying operating system.

    2nd thing i am facing problem when window installer image does not appear when i task sequence.

  5. Thanks a lot, I was getting the same error after I going through the routine password change for ALL employees. Your blog helped us a lot in our deployment.

  6. I’ve checked Our SCCM deployment and I have specified the network Access account already. What riddles me is, that the 80070002 doesn’t show in every OSD. Most of the times we don’t see it if we don’t start a New OSD until after we’ve pressed the “Finish” button. Could it be network problems? We have gigabit from Client machines to the serverrom and SCCM DP and Client machines are in the same subnet so no firewall working Magic here..

  7. I had this error after updating our Network Service Account password in Active Directory. To fix it, I went to AdministrationSecurityAccounts opened the properties of the account, clicked Set, then typed in the new password. After updating the password, OSD wouldn’t fail at “Applying Operating System.”

  8. Prajwal,

    I am late to this and could use some assistance. I am experiencing the same issue as others on this thread. The difference with me though is that I can deploy OSD but if I attach an Answer File to my TS it fails. I thought I have given all proper rights to my share in order to access content. Is there something I can do to fix this?

  9. When i deploy the task sequence to a vm, i do not get the error 0x80070002. I get it when the ts is deployed to a physical machine on the same domain. Any ideas
    ?

  10. I checked the account like you outlined; however, an administrator account already exists there that has access to all network locations! I can’t access the smts.log file because I cannot access the machine that I am deploying to because after I PXE boot and the computer restarts and it boots this shows “an operating system is not installed” what do I do?

  11. Under the category of KISS (Keep It Simple Stupid), “Workstation” class machines from any vendor tend to come from the factory configured to use RAID as the HD Controller Mode Default. If your Boot Image is not created for RAID, and AHCI is the default …. you will ALSO see this error. If it is an option and you do not need RAID Mode, change the HD Controller mode to AHCI. You will see in the SMSTS.log file that there are issues writing to the HD. This BIOS change takes very little time, and eliminates one possible cause very quickly.

    Just something simple to check.

  12. I am getting this error message on a specific machine, we are able to build other machines no problem, we are running SCCM 2007, how could I check these options on a 2007 system?

  13. There could be some other issue if you are sure that network access account is configured correctly.
    1) Review you SMSTs.log
    2) check Allow Client to Connect Anonymously and see if it fixes the issue.
    3) Software Library > Operating Systems > Operating System Images), and select “Manage Access Accounts”, and then add the SCCM Administrator account.

    • I have already configured the network access account but issue not fixed. After enable connect anonymously its working. But why not its working with without anonymously. I am using same steps which is mentioned in your step by step guide.

  14. Many thanks for sharing this nugget of information. I have followed your articles on OS deployment, and found them to be very helpful in getting it up and running in much less time than I first feared.

  15. Hi Prajwal, not sure if you can help but I’m encountering this problem despite having a network account specified. I followed your guides (which are excellent by the way) to get the system up and running, I have a man site server for management and a distribution point on a different VLAN. I’ve captured my image, created the task sequence and PXE boot is working. Both boot images have been deployed to the distribution point and I can get the system to pick up a task sequence. However, after it formats the drive, the PXE multicast session is started then I immediately get this error. My biggest problem is that there are no decent logs. The log on the X drive shows the format worked OK but it’s not got as far as creating the log on the C: drive. I can’t tell if it’s an access thing or if it’s trying to pull down from the wrong location. I initially had the management server as a distribution point and I think the OSD was trying to deploy from there? I’m a little bit stumped at the moment. Packages are set to download and not to run from a share, although I’m going to try that to see if it makes a difference. I have a collection with the machine in it and I assigned it the distribution group associated with the distribution point/boundary groups. Any pointers of where to look or other logs I can check? Getting a bit frustrated.

  16. I get this issue when it’s almost halfway through the applying OS. We have two other DP’s and they work fine. The server and the clients are on the same gig network switch. For some reason it was working a couple of weeks ago then these error starting popping up. The smsts log doesn’t have any error messages.

  17. I suggest you to check the source of the package and ensure to give the UNC path instead of shared folder path. I had this problem and had gave the shared folder path, after correcting it, the error went. I hope it helps

  18. Hello, thank you very much. That was my missing link. I had a migration of SCCM 2012 R2 to new hardware and then upgrade to Current Branch. EVERYTHING worked fine. Deployment, Patch Management, everything. Only the OS Tasksequences failed at the point you described.

    I forgot to set the correct Network Access Account!

    Thank you again.

    Juergen

  19. Hi, Am getting 0x80070490 on UEFI disk partition and this is from dell precision t5810 using Using 1TB HDD

    Invalid disk number specified: 0 OSDDiskPart 3/3/2017 12:22:42 PM 2012 (0x07DC)
    Invalid configuration specified. Please ensure that the task sequence is properly configured. OSDDiskPart 3/3/2017 12:22:42 PM 2012 (0x07DC)
    OSDDiskPart.exe failed: 0x80070490 OSDDiskPart 3/3/2017 12:22:42 PM 2012 (0x07DC)
    Failed to run the action: Partition Disk 0 – UEFI.
    Element not found. (Error: 80070490; Source: Windows) TSManager 3/3/2017 12:22:42 PM 1772 (0x06EC)
    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 3/3/2017 12:22:42 PM 1772 (0x06EC)
    Failed to run the last action: Partition Disk 0 – UEFI. Execution of task sequence failed.
    Element not found. (Error: 80070490; Source: Windows) TSManager 3/3/2017 12:22:42 PM 1772 (0x06EC)

  20. I know this is an older post, but the solution is still relevant. I came across this same error 80070002 while applying the WIM during my Task Sequence, but found the cause was not the Net Access Account as recommended here and wanted to post my findings in case it helps someone else.
    In the Task Sequence I had decided to speed up the imaging process by configuring the “Access content directly from the distribution point” setting in the Options of the “Apply Operating System” task. When doing this the WIM file being deployed must also be configured to support this as the WIM will be applied directly from the DP it must be in the “legacy” (unhashed) Distribution Point form. To configure the WIM file for this set the “Copy the content in this package to a package share on the distribution point” setting in the Data Access tab of the properties of the WIM file. You will then need to redistribute the WIM file.
    Essentially what this does is create two instances of the WIM file, one in it’s legacy form, the other in the SCCM 2012 data library hashed form.
    I had made some changes to my WIM and forgot that I had configured this so I just had to configure the WIM and the 80070002 error while applying the WIM was gone!
    Hope this helps someone else, happy imaging!

LEAVE A REPLY

Please enter your comment!
Please enter your name here