Win 7 Pixi Build and Capture Failure

[Charlie]

I keep getting the following error message at the Prep and Capture OS portion of the task sequence:

 

"A Failure code od 16389 has returned"

 

The task sequence execution engine failed executing the action (Prepare OS) in the group (Capture the Reference Machine) with the error code 2

Action output: urce.cpp,3031)

TS::Utility::ResolveSource(pszPackageId, rsPackagePath), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\bootimage.cpp,1002)

BootImage::ResolveImageSource( pszPackageId, sImagePackageSourcePath, sImageSourcePath), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\bootimage.cpp,687)

TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,933)

PreStageWINPE(m_bDebug), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,1374)

pCmd->Sysprep(bActivate, bMsd), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\main.cpp,270)

De-Initialization successful

Exiting with error code 2

Failed to find an available source location

Boot Image package not found.

The system cannot find the file specified. (Error: 80070002; Source: Windows)

Failed to pre-stage WINPE image, hr=0x80070002

Unable to sysprep the machine, hr=80070002

Sysprep'ing the machine failed, hr=80070002. The operating system reported error 2: The system cannot find the file specified.

 

Does anyone know how to resolve this issue? Thanks in advance for any assistance with this matter!

 

Cheers,

Charlie

[anyweb]

here's your error

 

Boot Image package not found.

 

so is the boot image assigned to your task sequence distributed to dps ?

[Charlie]

here's your error

 

so is the boot image assigned to your task sequence distributed to dps ?

 

The boot package is assigned to all distribution points. The machine see's when it starts the process because when it boots up via pixi it loads the boot package and performs the the OS install. When it gets to the running Sysprep portion of the build and capture it fails with that message.

[anyweb]

well as you can see from the log, that is exactly what it's complaining about so you need to find out why,

if you repeat the process and at the time of the failure bring up a command prompt, does ipconfig show you an ip address ?

[Charlie]

well as you can see from the log, that is exactly what it's complaining about so you need to find out why,

if you repeat the process and at the time of the failure bring up a command prompt, does ipconfig show you an ip address ?

 

Thanks for the advice. It turns out that the boot image was fine it was actually the sysprep. The sysprep doesn't like the fact that fact that the pc was ever a part of the domain. I removed the join the domain portion and it ran just fine