SCCM 2012 - OSD Build Failure

Team, I'm not good with pin pointing where exactly based on the smsts.log a build has failed, and subsequently resolving,
Please see attached log files, can you advise what you think the build failure is please?
_____________________________________________________________________________________________________________________________________________
smsts-20160627-144838.logsmsts-20160901-123817.logsmsts.log
Craig PaulsenSystems EngineerAsked:
Who is Participating?
 
Mike TConnect With a Mentor Leading EngineerCommented:
Hi,
You have 3 errors that I can see.

1) Step - Failed to run the action: (COE) Setup Windows RE.
The system cannot find the path specified. (Error: 00000003)
- means you have a file missing or mis-named.

2) Step - Failed to run the action: HP Elite x2 1012 G1. - The hash value is not correct. (Error: 80091007]
Means the driver package for your hardware is not identical to the original, hence the hash does not match. To fix you need to update the that package on the DP.
(Package ID is ps1004f3).

3) You also have an error at the end - Gather Logs and StateStore on Failure has failed and the execution has been aborted.
Operation aborted (Error: 80004004]
Could not find CCM install folder. Don't use ccmerrors.dll.

This suggests the CCM client has not installed correctly but I've never seen that error.

Update the DP with the driver package and track down the file from the first broken step:
 'cmd.exe /c xcopy /y /e "C:\Windows\System32\Recovery\winre.wim" "%REDisk%\RecoveryImage\" & C:\Windows\System32\icacls.exe %REDisk%\RecoveryImage /inheritance:r /T & C:\Windows\System32\icacls.exe %REDisk%\RecoveryImage /grant:r SYSTEM:(F) /T & C:\Windows\System32\icacls.exe %REDisk%\RecoveryImage /grant:r *S-1-5-32-544:(F) /T & C:\Windows\System32\reagentc.exe /setosimage /path %REDisk%\RecoveryImage /target C:\Windows /index 1 /bootkey 8500']LOG]!>

I can't see anywhere where you set a value for REDISK, so that would explain why you get file not found - it is not going find the path as %REDISK% is null.
Add a Set Task Variable step before hand and that should fix it.
Then the last error will probably resolve.

Mike
0
 
Craig PaulsenSystems EngineerAuthor Commented:
Anybody??
0
 
Craig PaulsenSystems EngineerAuthor Commented:
Thank you Mike T, ended up redistributing the driver stack to the DP/Build server, kicked off the build again and it worked
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.