Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

More documents

Recommendations

Info

Microsoft Deployment Toolkit Return Codes When most of the Microsoft Deployment Toolkit scripts were originally written, they each returned one of two results: Success, with a return code of 0 Failure, with a return code of 1 But that wasn’t particularly useful in identifying why a particular script failed, so in MDT 2010 each of the scripts was reworked to report different return codes (and corresponding error messages) for each different failure that might occur. So now when you see a particular return code, you immediately have more information available telling you about the error that occurred. And if you like digging into the MDT scripts, this return code will also point you to the specific line in the MDT scripts that generated that return code, because the same return code is never used more than once. In theory, the MDT documentation would include a full list of these error codes, along with the error messages that would be reported with each one and some potential troubleshooting suggestions: what might have caused the error, what you might want to consider doing about it, etc. Well, there is a table in the documentation called “Identifying Error Codes”, but it’s not very complete. So the table below can help with that. Note that each version of MDT could change this list, and if any of the scripts are significantly rewritten (e.g. ZTIUserState, which was rewritten in MDT 2012) the numbers being used within the script could be used for different purposes. So the list below is valid for MDT 2012 Update 1, but might not quite sync up with earlier versions. Each of the MDT scripts also has a range of return codes allocated to it, so the error numbers also can tell you from which script the error came. To simplify things, the script name is also included below. Each of the messages is also rated on a scale of 0 to 10 in two different areas: Likelihood. If the error is highly unlikely, it’s not worth worrying about so no troubleshooting suggestion will be provided. If by chance you ever see the error, contact Microsoft Support for assistance. Quality. Some error messages are self-explanatory; others make little sense without further explanation. So each has been rated, with 0 being “absolutely useless” and 10 being “perfectly self-explanatory.” Also, you’ll notice that some items have been highlighted in red. These indicate issues in the MDT scripts: numbers that were reused, numbers that don’t fit into the right number range for each script, spelling and grammar errors, etc. At some point, I might files bugs for these… Return Script Error Message Likely Quality Troubleshooting Suggestions code 5212 LiteTouch.wsf Welcome wizard failed or was cancelled 10 5 This is normal if you cancel the Lite Touch welcome wizard (the initial wizard that shows up Page | 9
5204 LiteTouch.wsf The logged-on user does not have Administrator rights. 5206 LiteTouch.wsf The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed. in Windows PE unless you set SkipWizard=YES). But it also might mean that the wizard crashed. You can’t really tell the difference though. (The wizard sets a variable WizardComplete to “Y” when it succeeds. The error means WizardComplete wasn’t set to “Y”.) You might also see this message show up in the log file for the next task sequence executed on the computer because of a left-over BDD.LOG found on the computer in the C:\MININT folder structure. This is harmless, but will result in a yellow summary screen at the end of the deployment. 5 10 This can happen in two scenarios: You try to run LiteTouch.vbs from Windows XP or Windows Server 2003 when you aren’t logged on as an account with administrator rights. You try to run LiteTouch.wsf from any other OS when you aren’t running elevated (with UAC enabled). The solution in the first case is obvious, but in the second case it’s a little more subtle: Make sure you always run LiteTouch.vbs because it will trigger a UAC prompt to elevate the resulting LiteTouch.wsf process. (That’s one of the main reasons that LiteTouch.vbs exists.) 10 5 This is normal if you cancel the Lite Touch deployment wizard. But it also might mean that the wizard crashed. You can’t really tell the difference though. (The wizard sets a variable WizardComplete to “Y” when it succeeds. The error means WizardComplete wasn’t set to “Y”.) You might also see this message show up in the log file for the next task sequence executed on the computer because of a left-over BDD.LOG found on the computer in the C:\MININT folder Page | 10
Page 1 and 2: SEPTEMBER 11, 2012 Troubleshooting
Page 3 and 4: Document History Date September 6,
Page 5 and 6: Log files Windows logs There are se
Page 7 and 8: Smsts.log Main log file written by
Page 9: TaskSequenceProvider.log Useful whe
Page 13 and 14: 5614 LTIApply.wsf ERROR - Unable to
Page 15 and 16: 7102 ZTIConfigureADDS.wsf ERROR - M
Page 17 and 18: variable (used to control the size
Page 19 and 20: 9701 ZTIUserState.wsf Unable to fin
Page 21 and 22: Version is not supported. You must
Page 23 and 24: deployment share, but it wasn’t t
Page 25 and 26: oot sector on the boot drive. In th
Page 27 and 28: 6191 LTISysprep.wsf FAILURE: Test f
Page 29 and 30: use.”) Then BCDBoot was used to c
Page 31 and 32: emovable disk or network path. In t
Page 33 and 34: 6740 ZTIBDE.wsf FAILURE: Check to s
Page 35 and 36: 7813 ZTIDiskpart.wsf FAILURE: Verif
Page 37 and 38: means that it wasn’t able to find
Page 39 and 40: 10311 ZTIVHDCreate.wsf FAILURE: Ver
Page 41 and 42: User State Migration Tool Return Co
Page 43 and 44: An option argument is missing An op
Page 45 and 46: 12 USMT_ERROR_OPTION_PARAM_T OO_LAR
Page 47 and 48: Another process is preventing migra
Page 49 and 50: valid and that you have write acces

Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?