another quick post, if you are trying to troubleshoot USMT and want finer details about what is migrated (or not) then you should of course enable Verbose logging using /v:13
in addition, you can enable a Diagnostic mode by setting a variable called MIG_ENABLE_DIAG to be equal to a filename both on your Scanstate source and Loadstate Destination. To set MIG_ENABLE_DIAG as a system variable do as follows,
- open a command prompt, and type set MIG_ENABLE_DIAG=<filename path>, eg:
- perform your scanstate or loadstate commands
- review the newly created log in C:\Windows\TEMP
the resulting log file contains details about mappings, patterns, group names, and a whole lot more and is granular in detail, so if you want to find out why your custom USMT xml files are not doing what you told them to then enable this option and review the new log.
Note: make sure there is no space in between MIG_ENABLE_DIAG and the = sign.
Additonal note: you MUST set the verbosity level to /v:13 as otherwise it will
not use the variable above and it will also not even mention the MIG_ENABLE_DIAG variable in
scanstate.log, and as a result, no mig_diag.log will appear in your target folder.
If you want to verify that you've set your environment variable correctly, open a command promtp and type Set, in the list that appears check for the variable it should look like this MIG_ENABLE_DIAG=C:\Windows\TEMP\MIG_DIAG.LOG
Related reading: USMT Log files, Technet - http://technet.microsoft.com/en-us/library/dd560780%28WS.10%29.aspx