Wednesday, May 23, 2012 6:17 PM
When I run scanstate /all on one of my Windows XP machines it captures the data for all but one of the profiles on the system. I have checked the profile list in the registry and everything is there for this profile. It is a domain account that is comprised of all numbers, which is the only difference between it and the 3 other domain accounts on the system that do get migrated. It also the account of the primary user of this computer so it has the most data. Is there something else that could be causing scanstate to skip this profile?
Thursday, May 24, 2012 11:27 AM
Try using this script to validate the profiles on the machine - http://blogs.technet.com/b/deploymentguys/archive/2010/03/28/usmt-failures-due-to-bad-profile-list-entries.aspx
Also, if you bump the logging to verbose level - 13 - USMTCapture.log might help!!
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"
Wednesday, May 30, 2012 6:09 PM
I moved on from the origninal system and tried another. I am having the same issue with this one. It catches all the profiles except the one where the user name is all numbers. I ran the MDTValidateUserProfileFolders.wsf script and it recognizes the profile and doesn't report errors. But I get a "Cannot get user SID" error in the scanstate.log file. When I look at the registry ProfileList I don't see any problems with this profile. This is starting to look like it is related to the profile name not containing any letters.
Wednesday, May 30, 2012 10:06 PMI was not able to replicate this issue on a brand new profile, all numeric user name, created on a virtual XP machine so I am back to looking at the Profile List in the registry to see if I can locate the issue.