Earlier today, I was working on a strange issue: When attempting to image an online 64-bit system from the LiteTouch.vbs script, we were getting a strange error:
FAILURE ( 5610 ): False: Verify File: \\MDT\ProductionShare$\Boot\LiteTouchPE_x64.wim
Notice in the picture, the 0x80004005 error? that’s MDT speak for ‘something really bad happened’
I checked the Official MDT Documentation, and all I got was ‘5610: Verify File’ which was less than helpful.
Next, I checked Neihaus’ guide here: Troubleshooting Windows Deployments and found that 5610 really means, “you haven’t yet updated the deployment share to generate this WIM file (or when that architecture isn’t enabled).”
Turns out the issue was exactly that: a missing 64bit boot wim file, and yes, indeed the architecture needed to be enabled, and the share needed to be updated. Worked like a charm.
Now this confuses a lot of people, back in the day one was pretty much required to use a 32-bit boot image to lay down a 32-bit OS, and the same went for 64bit. If you wanted to deploy 64 bit Vista or 7, you would need to be rocking a 64-bit WinPE bootable media. Eventually support’s gotten better since the MDT 2008 days, and now I can image both 32-bit and 64-bit systems from one 32-bit boot image. However, if you’re using litetouch.vbs switches and shortcuts from live systems, you’ll need to keep the 64bit systems enabaled in your share properties. Just goes to show you, when you do weird things, and get even weirder errors, keep your Troubleshooting Windows Deployments PDF handy.