Error when use ADMT 3.2

Tao Cuong 41 Reputation points
2021-10-11T06:24:59.78+00:00

Hi guys, hope anyone can support me.

Here is my enviroment:
Root domain: domain.com
Child domain 1: North.domain.com
Child domain 2: Central.domain.com
ADMT server: Member server of root domain.
Client computer: join domain North and use user account abc in North domain (North\abc)

I user ADMT 3.2 for migrate, When i migrate user account abc from North to Central and immediately rollback user account abc from Central to North. I did un check user must change password next logon after rollback.

The problem is when end-user log on again to client computer with North\abc. Window 10 in client did load a temp profile, Window cannot load to old profile of user abc.
Here is registry of client computer. One registry .bak.

139270-image.png

Does anyone have a same situation and know a root problem.

Thank you guys

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,908 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
408 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,381 Reputation points
    2021-10-11T16:48:08.823+00:00

    Hello @Tao Cuong

    This is a expected behavior when migrating users if the same profile SID exists in the domain. In this case this is not a coincidence but because the user is rolled back to it's previous state.

    The solution is to:

    A) delete the C:\users\xxxxxx folder of the user
    B) Delete de SID folder from \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList

    Of course this actions, should be better performed before rolling back the user as a pre-stage roll back, but it works even if the user has been migrated.

    Hope this helps with your query,

    ------------

    --If the reply is helpful, please Upvote and Accept as answer--

  2. Clément BETACORNE 2,031 Reputation points
    2021-10-12T08:05:39.457+00:00

    Hi @Tao Cuong ,

    Normally SID History or SID-to-GUID mapping should allow the user to access the profile but based on your explanation it doesn't seem to be the case, that's why I suggest you the translate local user profile to see if you still have the issue.
    If you don't have the issue you can assume that SID History or SID-to-GUID is not working and investigate more but at least you have a workaround