none
interforest exchange migration RRS feed

  • Question

  • Hi Folks , we found ourselves in a strange configuration !

    we have an exchange server 2007 environment ; about 100 users , sensitive environment .  company cannot tolerate
    blank GAL for some users or free+Busy not being available ..

    domain is SLD based ! ( not my fault !)  , so instead of company.local or company.com ; it's only company . that requires
    a active directory migration. (let's say from company to company.com)

    Management is also asking for an office 365 migration , so that email will be moved to cloud eventually .

    what 's the best approach in here ?

    I thought about a hybrid deployment ; but I don't know where to locate the new exchange server for 365 hybrid ; new forest ? old forest ? how does that work ?



    Monday, June 2, 2014 3:07 PM

All replies

  • ExDeploy is your friend

    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AgAEAAAAQAAAAAEAAQAAAAA~


    Where Technology Meets Talent

    • Proposed as answer by Prem P Rana Tuesday, June 3, 2014 4:34 AM
    Tuesday, June 3, 2014 3:39 AM
  • Mailbox moves and mailbox migrations in Exchange 2016 and Exchange 2019 from one forest to another require that you prepare the destination forest, which is made easier by Exchange tools and cmdlets. Exchange 2016 supports mailbox moves and migrations using the Exchange Management Shell, specifically the New-MoveRequest and New-MigrationBatch cmdlets. You can also move the mailbox in the Exchange admin center (EAC).

    To move an Exchange mailbox from a source forest to the target Exchange 2016 or Exchange 2019 target forest, the target forest needs to contain a valid mail user (also known as a mail-enabled user) with a specified set of Active Directory attributes.

    In Exchange 2016, you can move an Exchange 2010, Exchange 2013, or Exchange 2016 mailbox from a source Exchange forest to a target Exchange 2016 forest. If there's at least one Exchange 2016 Mailbox server in the target forest, the forest is considered an Exchange 2016 forest.

    In Exchange 2019, you can move an Exchange 2013, Exchange 2016, or Exchange 2019 mailbox from a source Exchange forest to a target Exchange 2019 forest. If there's at least one Exchange 2019 Mailbox server in the target forest, the forest is considered an Exchange 2019 forest.

    To prepare for the mailbox move, you need to create mail users (also known as mail-enabled users) with the required Active Directory attributes in the target forest. There are two recommended approaches for creating mail users with the necessary attributes:

    If you deployed Identity Lifecycle Manager (ILM) for cross-forest global address list (GAL) synchronization, we recommend that you use Microsoft Identity Manager 2016 Service Pack 1. We've created sample code that you can use to learn how to customize ILM to synchronize the source mailbox user and target mail user.

    For more information, including how to download the sample code, see Prepare mailboxes for cross-forest moves using sample code.

    If you created the target mail user using an Active Directory tool other than ILM or Microsoft Identity Integration Server (MIIS), use the Update-Recipient cmdlet with the Identity parameter to generate the LegacyExchangeDN attribute for the target mail user. We've created a sample PowerShell script that reads from and writes to Active Directory and calls the Update-Recipient cmdlet.

    For more information about using the sample script, see Prepare mailboxes for cross-forest moves using the Exchange Management Shell.

    After creating the target mail user, you can then run the New-MoveRequest or the New-MigrationBatch cmdlets to move the mailbox to the target Exchange 2016 or Exchange 2019 forest.

    For more information about remote move requests, see the following topics:

    New-MigrationBatch

    New-MoveRequest

    For more information about remote mailbox moves and remote legacy moves, see Move Mailboxes to Exchange 2016.

    The remainder of this topic describes the mail user Active Directory attributes that are required for a mailbox move. These attributes are configured for you when you use either the code or the script to prepare for the mailbox move. However, you can manually copy these attributes using an Active Directory editor. I hope this information helps you in Exchange 2010 to office 365 migration.
    Friday, May 1, 2020 11:42 AM