I am currently supporting a Intra-Forest Migration (migration between domains of the same Forest) and experiencing a problem with Windows 10 Computers.

Scenario: Migrating shared computers from the source domain to the target domain prior to some of the functional users of that machine have had their source account migrated. All source accounts have a target account created, SIDHistory applied and security identifiers merged, and are mapped in the Quest Migration Manager database. Migrated machines are resource updated with the Quest RUM tool and no issues are identified.

Expected Behvaior: When a source user, who has used the machine in the past and has a local profile on the machine, logs into the workstation they get their previously established profile to load. When that user is migrated and begins to use target credentials, they continue to get their profile.

Results:
Windows 7 - Works perfectly
Windows 10 - Source user gets a new profile <username>.domainname. If we edit the registry to point the newly created profile to point to the profile directory of the correct profile, it works for 1 logon, after a logoff and a logon event the new, profile loads. If we log on with the Target credentials the correct profile to loads

Can anyone help me understand why the source and target credentials are not getting the same profile to load in this scenario?