Search Engine: Elastic

Article ID: 132949, created on Jul 24, 2018, last review on Aug 8, 2018

Release Notes

Exchange 2016 Coexistence with Exchange 2013 in the Same Active Directory Domain

Now, service providers can deploy Exchange 2016 in the same Active Directory domain where Exchange 2013 is already deployed.

To learn more, refer to the Odin Automation Hosted Exchange Guide >> Deploying Exchange 2016 in AD Domain with Exchange 2013.

Support of Transition from Exchange 2013 to Exchange 2016

Now, service providers can migrate Exchange 2013 subscriptions of their customers to Exchange 2016. Two scenarios of transition from Exchange 2013 to Exchange 2016 are supported:

  • Intra-domain transition. In this scenario, Exchange 2016 is deployed in the same Active Directory domain as Exchange 2013; both Exchange versions function at the same time, and Exchange subscriptions move from Exchange 2013 to Exchange 2016 gradually.
  • Cross-forest transition. In this scenario, Exchange 2013 and Exchange 2016 are deployed in separate Active Directory forests and use their own Active Directory domains; both Exchange versions function at the same time, and Exchange subscriptions move from Exchange 2013 to Exchange 2016 gradually.

During the transition, Exchange objects (mailboxes, distribution lists, contacts, and other items) are moved from Exchange 2013 servers to Exchange 2016 servers. This process is handled by Odin Automation and is performed automatically.

There is a minimal downtime of Exchange services and mailbox access for mailbox users – as little as zero downtime, depending on the current deployment scheme.

The transition may require actions or changes from mailbox users because the access URLs will be changed and will point to Exchange 2016 servers. Most of the mail clients will discover the new URLs via the Autodiscover service, but some clients may require reconfiguration.

Note the following limitations of the transition scenarios:

  • Intra-domain transition
    • Exchange 2013 subscriptions cannot be migrated if their Exchange objects have email addresses based on Exchange shared domains.
    • Exchange 2013 subscriptions cannot be migrated if they have linked mailboxes.
  • Cross-forest transition
    • Migration of public folder is not supported. This means that you can use the scenario only for subscriptions that do not have any public folders in Exchange 2013.
    • Exchange 2013 subscriptions where the Customer Directory Integration (CDI) service is turned on cannot be migrated. To migrate such a subscription, the service must be turned off.
    • Exchange 2013 subscriptions cannot be migrated if their Exchange objects have email addresses based on Exchange shared domains.
    • Exchange 2013 subscriptions cannot be migrated if they have linked mailboxes.

To learn more, refer to the Odin Automation Hosted Exchange Guide >> Exchange 2013 to Exchange 2016 Transition.

Installation

Install the following hotfixes to use this feature:

Email subscription for changes to this article
Save as PDF