Hello Abdulaziz ALHAKMANI,
Thank you for posting in Microsoft Community forum.
Migrating user roaming profiles to new domain controllers can be a multi-step process, but it can be done efficiently by following these steps carefully:
1.Preparation:
Make sure you have a full backup of all user data before starting the migration.
Plan the migration during off-peak hours to minimize the impact on users.
2.Set Up the New Domain Controllers:
Install and configure the new Windows Server domain controllers in the same domain.
Waite for the AD replication to complete in the new Active Directory (AD) domain controller as existing old ones in the domain.
3.Copying Roaming Profiles:
Use a tool like Robocopy to copy the user profile data. Robocopy can preserve permissions and attributes which is crucial for roaming profiles.
robocopy \OldServer\Profiles \NewServer\Profiles /MIR /COPYALL /SECFIX /R:3 /W:5 /LOG:ProfileMigration.log
/MIR
mirrors the directories,
/COPYALL
copies all file attributes,
/SECFIX
fixes security on all files,
/R:3
and /W:5
control retry behavior,
and /LOG
logs the process.
4.Update Profile Path in Active Directory:
Select more users and right click them\Properties\Profile tab\change the profile path from old path to new path.
5.Verify Permissions and Access:
Ensure that file and folder permissions on the new server are correctly configured so users can access their profiles without issues.
Test with a few user accounts to ensure that profiles load correctly from the new server.
6.Update Group Policies:
If you are using Group Policies to manage roaming profile paths, ensure that any relevant GPOs are updated to point to the new profile paths.
7.Inform Users:
Notify users about the migration and any actions they might need to take (e.g., logging out at a specific time).
8.Final Testing:
After the migration, monitor the system closely for any issues with profiles loading or data access. Make necessary adjustments as required.
By following these steps, you should be able to migrate user roaming profiles with minimal disruption and without losing data.
Note: Please had better test it in lab first, if there is no any issue, you can do the migration in production environment.
I hope the information above is helpful.
If you have any question or concern, please feel free to let us know.
Best Regards,
Daisy Zhou