If you’ve been using the Microsoft Deployment Toolkit (MDT), aka Deployment4, then you will have probably had the scenario at some point where you PXE boot your client into PE and then the whole process just stops.

The giveaway sign here is that you have the command prompt returned to you.

This can be a bit perplexing, as to what your next move should be in working out what went wrong. During the Beta I was given a helpful hint from the MS guys:

cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true

This provides a bit more output and has been successful in pointing me in the direction of whatever was causing the grief.

The last line is the important one in this example. The path with “broken” in it is showing that I had entered the wrong BuildID in the computers details configuration. That would explain why it couldn’t find the TaskSequence in question! ;)