This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 46%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIH%3C/text%3E%3C/svg%3E)
One of our customers is looking the solution of Exchange 2016 server migration from one data center to other data center. The scenario is customer has one Exchange 2016 Edge server and three Mailbox DAG servers.
I have following queries and know the impact while migrating and shifting the mailboxes from one data center to other center
@Innocent Heartvoice
I am writing here to confirm with you any update about this thread now.
If the suggestion below helps, please feel free to accept it as an answer to help more people.
The coexistence will be established between two separate data centers to migrate users mailboxes
I want to double confirm with you that those two data centers are separated or coexist in one organization?
If they coexist in one organization:
About MX record:
You could point MX record to any of them (New or old data center), you could also confirm with your DNS supplier, whether they could provide DNS points to two datacenters.
About Edge server:
You could create a new Edge server in the new datacenter, then follow this article to create Edge Subscriptions with Exchange server in new data center.
About migration:
You could migrate them from old data center database to new data center database directly.
If they are two separated organizations, you will need to migrate data with export/import PST. After migration, switch MX record from old one to new one.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
This is the single organization but both data centers are separated and want to coexistence.
The second part is that the Edge server has a definition update for the SPAM filter or the agent has to manually update it to protect the environment.
I guess we have different definitions of coexistence:
The situation I described belongs to the same AD environment/forest, different AD sites. Exchange servers coexist in the same AD forest.
I guess you want to say old data center and new data center exist at the same time:
If those two data centers are separated in different AD sites, you will need to migrate data with export/import PST. You can also do a cross forest migration to migrate mailboxes from old forest to new forest.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If you want to change them to in the same AD forest, you need to remove the new data center, then recreate it as the second site for old domain/forest. Then create Exchange in it, in this way. Exchange server will coexist in the same AD forest.
Sorry, my mistake that couldn't explain properly.
Yes, it's a same AD environment/forest, different AD sites which needs the coexistence between both sites.
What about the second part that Edge server has definition update for SPAM filtering or how it works to control spam?
Do you mean that there exists some customized filtering configuration on the old Edge server, you want to do the same configuration on this new Edge server? Please point out if my understanding is wrong.
If so, you could follow this article to use Get-XXXXX (Such as Get-IPBlockListConfig) command to check configuration on your old server, then use Set-XXXX (Such as Set-IPBlockListConfig) command to create the same configuration on your new Edge server.
If you mean that there exists additional third-party spam filtering works with your Edge server, you could create Edge Subscriptions to make sure mail flow between Edge server and Exchange server first. Then create connector manually for mail flow between your Edge server and third-party spam filtering.