We're in the test/pilot phase of a migration with QMMAD. We have groups and pilot/test users migrated from source.net to target.com. Using a test workstation in source.net, we have one of the users log in and create a profile on a workstation with their source.net user. We then use rum to discover and process the workstation. Processing statistics show one profile updated as well as many files and registry entries, some typical warnings on registry processing. Prior to the move, we check permissions on c:\users\<username> and see that it has two sets of permissions, as expected. We also check the ProfileList in the registry and see that there is an entry with the target.com user SID that has profile path set to c:\users\<username>, again, as expected.
The move step proceeds as normal, no warnings or errors, but when the user logs in after reboot, a new profile is created c:\users\<username>.target.com. No prompts to the user about problems loading their profile, and no entries in the system or application logs about problems with the profile. If we then manually change profileimagepath to point to c:\users\<username> the user can log in and get their proper profile.
Where should I be looking to diagnose what is going on with these machines?