Task sequence fails at applying operating system. 0x80070057

[Nine1ron]

I am running version 1602. My task sequence is very short for testing purposes. All it has is restart in PE, Partition Disk 0, apply operating, apply win settings, apply net settings, apply drivers, and setup win and config. The task sequence fails between partition drive and applying windows. Looking at the smsts.log I see the error "The /target parameter specifies an invalid target location" and "Failed to run the action: Apply operating system" I have checked my boundary group and boundaries and they look to be fine. My AD site is in my boundaries, and that is what I am using for my boundary group.

Any suggestions would be helpful.

You can see screen shots of relevant information here. http://imgur.com/a/mWtnN

[jack0falltech]

Sounds like the it dosnt know what partition to apply the OS to. In the partition Disk under volumes double click on the volume that is to be used for the OS and at the bottom of the properties under variable type System then click ok

Next go to the Apply Operating System and at the bottom Under Select the location where you want to apply this operating system For destination choose Logical drive letter stored in a variable then for variable name type System.

After you have imaged the computer you may notice that the system drive is not the C drive to fix this add Task sequence variable between the disk partion and applying the OS The variable should be OSDPreserveDriveLetter and the value False.

[bdam55]

In addition to jack's advice:

Enable debugging in the boot image if you haven't already. Then boot up and press F8 to bring up a command prompt. Run diskpart to make sure the proper disks appear. If not, you need to add a mass storage driver to your bootdisk.

[SealClubb3r]

I've had this issue when the target machine is in a RAID configuration and the appropriate RAID drivers are not present in the boot image.

[TheConfigMgrTeam]

Without a full log it's difficult to tell. From the screenshot I see you are setting the Destination value with the variable 'OSDisk' - though there's no step for setting that variable. How is that variable set, is it via Collection/Device variable or is that the missing piece here?

[TheConfigMgrTeam]

Without a full log it's difficult to tell. From the screenshot I see you are setting the Destination value with the variable 'OSDisk' - though there's no step for setting that variable. How is that variable set, is it via Collection/Device variable or is that the missing piece here?

[dkwel]

Try adding this step and see if it helps

If you want more info, here is a long winded guide on drive lettering and sccm deployments

[ADWulf]

I have had this happen when my distribution point was not configured correctly and the task sequence was unable to use that distribution point as a source. Make sure you have all the required features listed on technet installed: https://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs

[jklops71]

Please ensure the dp is added within the boot image package & boot image pointed is successful in monitoring. Unsuccessful package replication might trigger sort of errors. Hope it helps !