Task Sequence error 0x8007002 SCCM 2012

[Config_Mgr_noob]

Hi,

 

I'm receiving an error message 0x8007002 during OSD Applying image phase and cannot seem to get the drivers installed as well. The image gets applied but without the necessary drivers. Also, I have imported our answer file from MDT into sccm to be used; however, sccm does not apply these settings. I have attach a screenshot of the smsts.log file from the client pc I imaged. Also, while updating my x64 boot image to the distribution point i receive the below error message not sure if this could be the root of my previous stated problem but worth mentioning here:

 

Error: The wizard detected the following problems when updating the boot image.

• Failed to inject a ConfigMgr driver into the mounted WIM file

The SMS Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

• Description = "Failed to insert OSD binaries into the WIM file";

• ErrorCode = 2152205056;

• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";

• Line = 4716;

• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

• Operation = "ExecMethod";

• ParameterInfo = "SMS_BootImagePackage.PackageID=\"FTL00005\"";

• ProviderName = "WinMgmt";

• StatusCode = 2147749889;

};

[Edenost]

I have recieved this error recently my self, but I cannot 100% recall what I did to fix it.

 

I know I have had a couple of issues since updated to R2, so it could be any of the following:

 

Make sure you can connect to the image server from WinPE. Check IP Config and ping.

Make sure permissions are correct and the file location of the image is correct as well. 80070002 is saying it cannot find the files

Make sure there is space on the drives of SCCM (I have had trouble where I'm running low on space and it just causes random problems for me).

Reboot SCCM server (updates/fresh start??).

How many deployements are available to the machine in question? There can be "too many". I know if it is that, generally it's a different error, but I have found with my WSUS/SUP being automated it can sometimes kick out too many deployments to the machines and they can't handle the imaging. I work through old ones on a weekly basis now and delete them my self to keep on top of it so I have less than 30. If I get lazy and reach 100, it seems to kick out then.

 

Good luck, at the moment that's all I can remember off the top of my head!!

[Edenost]

There is this post which I have found.

It talks about virtual machines, but it could also be relevant to a physical machine in a sence of the BIOS. Maybe change the HDD settings in the BIOS?

 

http://social.technet.microsoft.com/Forums/systemcenter/en-US/29c3813a-04ce-447a-bc59-446bca066191/sccm-osd-0x80070002-parition-disk?forum=configmgrosd