Share via

Impact of ADMT 3.2

Tao Cuong 41 Reputation points
2020-11-11T03:45:42.327+00:00

Hi everyone, i have some important questions for my customer case. Here is it
In AD i have 1 forest/ 3 child domain. User is in 3 child domain. We use hybrid AD with password hash sync. AD connect is synchronization user in 3 child domain depent OU. Hybrid Exchange but all user have all mailbox in Exchange online. We plan to move all user in 3 child domain to root domain use ADMT 3.2

  • Question 1. I think when i migrate user from child to root. I know when migrate user between domain, there are many attribute is exclude by ADMT 3.2. But i think if i can migrate two important attribute is UPN and SourchAnchor. There is no impact to AD connect, to Azure AD, and to Office 365. Am I right? Can anyone have experience about this? Are there more important attribute?
  • Question 2. One more two important attribute is Mail and ProxyAddresses can be migrate when migrate user. But attribute legacyExchangeDN is exclude by ADMT 3.2. So if legacyExchangeDN is lost, user cannot receive mail, so user AD connect don't see that attribute to synchronization, user in Exchange online cannot receive mail. If i export before migrate and import legacyExchangeDN after migrate. It's OK, but cannot do that with thousand users. My question is are there any attribute have to migrate for NO IMPACT to Hybrid Exchange. And anyone have solution for migrate attribute legacyexchangedn?
Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments
Accepted answer
  1. Anonymous
    2020-11-11T09:29:02.473+00:00

    Hello,

    Thank you so much for posting here.

    We mainly focus on on-premise AD. So sorry that we are not professional with the AAD and Exchange and Office 365. So it is suggested that we could turn to the dedicated forum for the specific issues by choosing the dedicated tags.

    As for the question 1, so sorry that we do now know much about SourceAnchor attribute. According to our research, it seems to be related with Azure AD. So we could turn to AAD forum and only choose Azure Active Directory tag.

    Reference: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-design-concepts#:~:text=documents%20as%20well.-,sourceAnchor,two%20names%20are%20used%20interchangeable.

    As for question 2, as per my test, if only migrating a user from child domain to the root domain, the attributes Mail, proxyAddresses amd LegacyExchangeDN could be migrated.

    39101-1111111.png

    I have researched for the below article, and we could kindly have a check whether it helps.

    https://www.petenetlive.com/KB/Article/0001468

    Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

    Best regards,
    Hannah Xiong

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tao Cuong 41 Reputation points
    2020-11-12T07:22:42.397+00:00

    Hi Xiong. Thank you for your answer. I have already checked it. In my test enviroment. The attribute: Mail, proxyAddresses amd LegacyExchangeDN, UPN, ms-DS-ConsistencyGuid (config as Source Anchor) is migrate with user when migrate between domain in One Forest.
    I think with migrate user between forest. The attribute: legacyExchangeDN is cannot migrate.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.