Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
6191 LTISysprep.wsf FAILURE: Test for CloneTag in registry to<br />
verify Sysprep completed.<br />
6192 LTISysprep.wsf FAILURE: Test for<br />
SystemSetupInProgress in registry to<br />
verify Sysprep completed.<br />
10401 UDIWizard.wsf FAILURE: Download configuration file<br />
<br />
10402 UDIWizard.wsf FAILURE: Find configuration file<br />
<br />
<strong>Windows</strong> XP and <strong>Windows</strong> Server 2003 don’t write<br />
a log during the sysprep process, figuring out the<br />
cause is a trial-and-error process. Typically this is<br />
caused by invalid [SysprepMassStorage] entries in<br />
the sysprep.inf.<br />
6 4 The LTISysprep script ran sysprep.exe to prepare<br />
the OS (<strong>Windows</strong> XP or <strong>Windows</strong> Server 2003) for<br />
capture, but even though it returned a zero return<br />
code the process did not appear to work. As<br />
<strong>Windows</strong> XP and <strong>Windows</strong> Server 2003 don’t write<br />
a log during the sysprep process, figuring out the<br />
cause is a trial-and-error process. Typically this is<br />
caused by invalid [SysprepMassStorage] entries in<br />
the sysprep.inf. Do not ignore this error and think<br />
that it is OK because sysprep.exe reported a return<br />
code of zero; the operating system image is<br />
corrupt and needs to be recreated.<br />
2 4 See above. Generally if this test fails, so does the<br />
previous one, so this error is not typically seen.<br />
3 5 The UDIWizard script enables the specification of a<br />
URL for the wizard configuration XML file. In this<br />
case, an attempt was made to download that<br />
configuration file, but that download failed.<br />
Without this file, the wizard cannot be displayed.<br />
Make sure the URL specified on the UDIWizard<br />
command line was correct.<br />
3 5 The UDIWizard tried to find the wizard<br />
configuration file either at the path specified on<br />
the command line or in a “well-known location” in<br />
the MDT toolkit files package, but it was unable to<br />
find the file. Without this file, the wizard cannot<br />
be displayed. Make sure the URL specified on the<br />
UDIWizard command line was correct or that the<br />
file is present in the MDT toolkit files package.<br />
Page | 26