Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

5208 LiteTouch.wsf Invalid DeploymentType value
%DeploymentType% specified.
5208 LiteTouch.wsf Unable to find the SMS Task Sequencer.
The deployment will not proceed.
5210 LiteTouch.wsf ValidateDeployRootWithRecovery:
Cancel
5211 LiteTouch.wsf ValidateDeployRootWithRecovery:
Cancel
structure. This is harmless, but will result in a
yellow summary screen at the end of the
deployment.
1 7 Normally the DeploymentType task sequence
variable is set automatically. But if for some
reason the variable was set through some other
means (e.g. a command line parameter or
CustomSettings.ini) to an invalid value, MDT will
generate an error before other bad things happen.
4 7 There are a set of executables and DLLs needed to
run the task sequencing engine. These are copied
to the local machine before the task sequence
initially starts, and it’s expected that these files
remain through the process. If something happens
where MDT can determine that there is an inprogress
task sequence (by the presence of an
_SMSTaskSequence folder) but can’t find the task
sequencer files that are supposed to be present,
you’ll see this error. This can happen with rouge
scripts that delete the MININT folder, or images
that accidentally contain a MININT folder (which
can cause the “real” MININT folder to be moved to
WINDOWS.OLD).
7 5 MDT tried to connect to the deployment share
specified by the DeployRoot task sequence
variable, but it wasn’t able to connect. A popup
was displayed to the user asking to retry or cancel,
and the user chose cancel. So this message means
MDT is giving because the user told it to do so.
0 5 It’s presently impossible for this error to occur.
When MDT is unable to connect to a deployment
share, there used to be an option to suspend the
task sequence, letting you manually fix the
problem and then resume the task sequence, but
this thoroughly confused people, so that option
has been disabled. The logic is still in the script
Page | 11