Resolution
Will roaming profiles be translated if the user is logged on?
fact
Domain Migration Administrator 7.1
fix
Roaming profiles cannot be translated while they are in use. The tool must be able to access the NTUser.dat file in the roaming profile in order to update the ACL on it as well as the Registry hive associated with it.
If the user is logged in when attempting to translate security on the roaming user profile, the error message received in the migration.log will be:
E20802: Failed to lookup the encrypted settings for profile (\\servername\C$\Tem\users\username) Error = 2.
If security is successfully translated on the roaming profile, the migration.log will contain:
'Translating user profile for username', followed by many lines of 'Changed, \\path...'
If you have migrated a user with SID History, the migrated users should still have access to their Roaming Profiles. However, the only opportunity to translate security on roaming profiles is during the User Migration.