Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

More documents

Recommendations

Info

User State Migration Tool Logs The User State Migration Tool (USMT) creates one log file for each execution of the Scanstate.exe and Loadstate.exe tools. The default name for the log file will be Scanstate.log and Loadstate.log, but a different file name can be specified on the command line. The Microsoft Deployment Toolkit specifies a different name, while ConfigMgr uses the default names. Log file Description Where to find it USMTEstimate.log Log created by the MDT ZTIUserState.wsf script when In the same location as the BDD.LOG file. running Scanstate.exe to determine whether there is enough disk space to save the user state locally. This is only applicable to USMT 3.0, since USMT 4.0 and 5.0 use hardlinks when keeping user state locally meaning there is always sufficient disk space. USMTCapture.log Log created by the MDT ZTIUserState.wsf script when In the same location as the BDD.LOG file. running Scanstate.exe to capture user state from the current computer. USMTRestore.log Log created by the MDT ZTIUserState.wsf script when In the same location as the BDD.LOG file. running Loadstate.exe to restore user state to the current computer. Scanstate.log Log created by the ConfigMgr “Capture User State” step In the same location as the SMSTS.LOG file. when it runs Scanstate.exe to capture user state from the current computer. Loadstate.log Log created by the ConfigMgr “Restore User State” step when it runs Loadstate.exe to restore user state to the current computer. In the same location as the SMSTS.LOG file. Configuration Manager Logs In addition to the task sequencer logs described above, there are additional log files on the ConfigMgr server that are useful for troubleshooting specific issues. See http://technet.microsoft.com/en-us/library/bb932135.aspx for a complete list of log files used by ConfigMgr. Log file Description Where to find it DriverCatalog.log Contains information that may be useful when getting C:\Program Files\Microsoft Configuration Manager\Logs errors while importing drivers Page | 7
TaskSequenceProvider.log Useful when getting errors while saving or importing a C:\Program Files\Microsoft Configuration Manager\Logs task sequence SMSPXE.LOG Used when troubleshooting PXE boot issues C:\Program Files\SMS_CCM\Logs SMSPROV.LOG May have more error details while saving or importing a task sequence C:\Program Files\Microsoft Configuration Manager\Logs Page | 8
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: Smsts.log Main log file written by
Page 11 and 12: 5204 LiteTouch.wsf The logged-on us
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

Create successful ePaper yourself

Delete template?

Save as template?