Scenario:New User Account, Newcomputeraccount, Set user profile to be roaming to DFS location eg: \\contosso.net\data\profiles\user1Log in as user in old domain. Logout & ensure profile properly saved up to DFS location.Migrate user using ADMT wizardERR3:7438 No NTUser.DAT file foruser1 was found in \\contosso.net\data\profiles\user1User account confirmed migrated.User unable to login with roaming profile but gets a temporary local profile.Looking at application logs it shows an ownership issue to be the cause of the problem.If I change the ownership on the profile to the new domain account the user can continue to access the old roaming profile.I have run the security translation wizard and whilst this will allow access to the profile it turns it into a local profile which negates the benefit of a roaming profile.Is it an issue with ADMT being unable to deal with DFS paths? Is there another solution apart from manually changing ownership on the roaming profile?

I'm having sort of the same issue. I've translated roaming profiles and so the users from my new domain (and users from the old domain)have access to the profiles. I've run a script to override ownership of the folders (subinacl /subdirectories profiles/* /setowner=administrators)because I found that if the folders were owned by the old domain user and the new domain user logs in they get an error and vice-versa but if the owner is administrators either one of the accounts can login problem free. Where I'm finding the problem is once a user logs into a PC then logs out it replaces the ownership with itself for the ntuser.dat file. When the other user logs in and because the ownership of the file has changed when that user logs out it doesn't save any settings back to the profile and there areno errors reported. Unlike you were describing Roy, it logs in with a roaming profile not local.I'm thinking I have to change my migration strategy and after my cut-over date I will be required to disable all old domain accounts forcing users to immediately login with their new credentials then re-run my take ownership script. Its going to be a lot messier than I had originally planned.. or change the profile path to a new profile directory.

Microsoft confirmed that DFS is not supported with ADMT so in the end I set a gpo not to check for ownership of roaming profiles which got round the isue.