Forum Discussion
prabks
Jan 12, 2022Copper Contributor
Active Directory Domain Consolidation
Currently I am involved in one of the AD consolidation project (AD Cross forest migration) and I have the current setup like this: 2 Domains abc.local and xyz.local in 2 different forest. I have sin...
prabks
Jan 17, 2022Copper Contributor
No on-premise Exchange on any side, its only Exchange Online (O365)
Jan 17, 2022
Ok, that makes it somewhat less difficult.. Would definitely go for one Azure AD Connect and move the users using migrate tooling.. As long as their source anchor doesn't change, the users should remain linked between AD en Azure AD
- prabksJan 17, 2022Copper ContributorWhat would be the best way to achieve this migration? if you can give me a high level steps that would be of great help .. I am planning to use ADMT for User/Computer migration. Current Source Anchor is ObjectGuid in both Azure AD Connect. Going forward I will have only one AD Connect.
- Jan 17, 2022This is a nice article describing this: https://www.smikar.com/move-users-to-another-domain-and-retain-ad-connect-sync/
- prabksJan 18, 2022Copper ContributorI am planning to enable ConsistencyGuid feature from the existing AD Connect deployment as both Azure AD Connects running on new versions .. with this I will change source anchor from ObjectGuid to mS-DS-ConsistencyGuid and with the help of ADMT I will migrate a user along with mS-DS-ConsistencyGuid attribute and resync the User from the target domain. This should rejoin the objects from on-premises and the cloud. I will carry out this in my test and then do it in the production.