• State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 29119 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cross-forest migration in Exchange Hybrid with Azure AD connect enabled

Bobby Dore
over 6 years ago

Thanks in advance for the help.

I have two on premises Active Directory forests, ForestA and ForestB. Azure AD Connect is installed on a server in ForestB and has connectors synchronizing both ForestA and ForestB to Office 365. I also have an Exchange hybrid server in ForestA that is being used to manage mailboxes in Office 365 and one in ForestB. Each user in ForestA has a mailbox in O365 and is matched using ms-ds-consistencyGUID (there are no on-premises mailboxes).

I need to migrate all AD user accounts from ForestA to ForestB. When I do this, I need to be sure that the mailbox is not deleted and the migrated user account in ForestB is matched to the O365 mailbox via directory synchronization.

How do I do this? Please note that I need to migrate 5000+ accounts so it will need to be done in batches and I can't disable dirsync at any point. I will use Quest Migration Manager for AD.

Parents
  • 0 over 6 years ago
    Thanks, Jeff. We've purchased the licenses and will be using Quest Migration Manager for AD and not ADMT. I appreciate your help, I've done a number of migrations between on-premises AD forests and am looking for any changes I need to make forests using Azure AD Connect (dirsync).

    Per your mention of this:

    "•Now move the source object from their current OU to OU=Excluded Object,DC=Source
    •AND move the Target object from OU=Excluded Object,DC=Target to Any other OU"

    Will Quest Migration Manager for AD do this for me or should I script it myself?


    Also, for this:

    "Quest Migration Manager for AD has a directory sync function that would allow you to cut all of the the MS Dir Sync functions to the target, has a directory sync function that would allow you to cut all of the the MS Dir Sync functions to the target"

    Are you saying I should create a directory synchronization job to sync objects from ForestA to ForestB and have dirsync operate only against ForestB? I plan to set up a directory sync job anyway as part of the migration so I can use that if so.
Reply
  • 0 over 6 years ago
    Thanks, Jeff. We've purchased the licenses and will be using Quest Migration Manager for AD and not ADMT. I appreciate your help, I've done a number of migrations between on-premises AD forests and am looking for any changes I need to make forests using Azure AD Connect (dirsync).

    Per your mention of this:

    "•Now move the source object from their current OU to OU=Excluded Object,DC=Source
    •AND move the Target object from OU=Excluded Object,DC=Target to Any other OU"

    Will Quest Migration Manager for AD do this for me or should I script it myself?


    Also, for this:

    "Quest Migration Manager for AD has a directory sync function that would allow you to cut all of the the MS Dir Sync functions to the target, has a directory sync function that would allow you to cut all of the the MS Dir Sync functions to the target"

    Are you saying I should create a directory synchronization job to sync objects from ForestA to ForestB and have dirsync operate only against ForestB? I plan to set up a directory sync job anyway as part of the migration so I can use that if so.
Children
No Data