Urgent: Litetouch deployment failed, Return Code = -2147467259 During PC Refresh

[Christopher9737]

I am in need of some major assistance. Unfortunately, I volunteered for the task of migrating our Windows XP machines to Windows 7. I've done about 30 machines already using MDT 2012 Update 1 with no issues, but tonight I received two "litetouch deployment failed, Return Code = -2147467259. Here is a picture of the full error :. I have three questions regarding this error. 1: Why did it happen in the first place? As i stated, I've successfully migrated around 30 machines with no such error. 2: Is there a way to continue the deployment? 3: If I have to do a fresh install, is there a way to recover the user's data. The task sequence for user state capture ran successfully using hardlink migration and is there a way to recover the user state after a fresh install. Any prompt advice will be greatly appreciated as I am at the site and want to have this resolved before the morning.

[free780]

Hit f8. See what state the PC is in. Is the image applied?

[Christopher9737]

Hi Free780,

 

Thank you for your reply. The image was not applied and the PC was stuck in a state of limbo. I was, however, able to restart the deployment from the command prompt using the net use command and starting the litetouch.vbs script again. It seems as though it is picking up right where it left off and is trying to apply the image again, but I won't know until the deployment is finished.

[free780]

The trouble is with that error is it can be quite a few things.

[Christopher9737]

Unfortunately, that is the case, but I did find one post that makes sense. OS Deployments to Multiple Clients from Server 2012 are either Slow or Fail | WindowsDeployments.net. Couldn't try the solution, though, because I had machines that are still in the deployment process.

[Gatt]

Looking at the error code 000015f8 - this may be a corrupt WIM file:

 

Deployment Research > Research - Going Production – Deploy Windows 8 using MDT 2012 Update 1

 

(Search the page for the second post by a guy called "fraigoza" who's posted the same error text)

[Christopher9737]

Thank you for your reply Gatt. The .wim file is not corrupt because it has successfully been deployed to more than 30 machines already. Even tonight, when the two failed, there were 7 others that were still going and a couple of machines that finished already.