Shulou(Shulou.com)06/02 Report--

The focus of this blog is:

Secure migration mailbox

Safely uninstall exchange 2010 after migration

For information about how to build a coexistence environment for this case and all the tools you need, you can visit the previous blog: building a coexistence environment based on exchange 2010 migrating exchange 2016

1. Case analysis 1. Case overview

In this case, the intranet uses Windows active Directory to manage network resources, and all Windows servers are Windows server 2008 R2. One of the servers runs exchange server 2010 mail system, which is responsible for enterprise mail communication. With the continuous expansion of business, the scale of the enterprise is getting larger and larger, and the diversity of user needs makes the function and performance of the existing mail system more and more stretched. After comprehensive consideration, the enterprise decided to purchase a new server and upgrade the mail system. To this end, the upgrade plan is studied as follows:

1) the operating system of the new server is Windows server 2016, and the mail system is exchange server 2016. 2) make an overall backup of the exchange 2010 server. 3) since it is not possible to upgrade locally from exchange 2010, the two versions coexist first. 4) in the coexistence environment, migrate user mailboxes and related functions to exchange 2016, and maintain stability for a period of time. 5) after the stabilization period, uninstall the exchange 2010 server. 2. Case pre-knowledge points 1) coexistence environment

Because the architecture of exchange 2016 is different from that of exchange 2010, local upgrade from exchange 2010 is not supported, which means that a coexistence environment must be deployed first. The purpose of deploying a coexistence environment is to migrate exchange 2010 mailboxes and other related features to exchange 2016. Before deploying a coexistence environment, make sure that the forest functional level is at least Windows server 2008 and exchange 2010 installs at least the UR11 patch for SP3.

2) migrate mailboxes

In the coexistence environment, both mail servers have their own mailbox databases, so the mailboxes in the exchange 2010 mailbox database need to be migrated to the mailbox database in exchange 2016. And after the migration is completed, all mailbox management operations will be carried out on the mailbox data of exchange 2016, and after a period of stability, the mailbox database of exchange 2010 will be deleted.

3) Uninstall exchange 2010

In addition to the mailbox database, exchange 2010 also provides other services for users, which cannot be uninstalled directly, otherwise the whole mail system will be abnormal. Therefore, the relevant services should be removed before uninstalling exchange 2010. For example, address list services provided to clients through IIS virtual directories, OWA, autodiscovery, offline address books, and so on. When these services are deployed correctly in a coexistence environment, exchange 2016 can provide them properly.

Case implementation 1, deployment of coexistence environment 1) active directory requirements

Ensure that DC/DNS is working properly and that the forest function level is raised to at least Windows server 2008, and in this case to Windows server 2008 R2. For more information on how to build a coexistence environment, you can refer to the blog article to build a coexistence environment based on exchange 2010, Migration exchange 2016.

2) confirm that exchange 2010 is working properly

Install exchange 2010 SP3, create a test mailbox, and send and receive test emails to make sure it is normal.

Make an overall backup of the exchange 2010 SP3 server. The method of operation is slight. 2. Start the migration from exchange 2010 to exchange 2016

Test exchange 2010 intranet coexistence environment

Tom received an email reply to bob

Test the coexistence environment of exchange 2010 public network

Marry receives the email and replies to bob

Test the coexistence environment of exchange 2016 public network

Marry received the email and replied to tom. The coexistence environment is fine, and then the migration begins.

Migrate offline address book

Migrate accept Connector

Migrate the send connector, delete the DC2 server, and add DC01

Configure server DNS query

Migrate virtual directory

Migration completed, click the close button

Migrate user mailboxes

Select the migrated user

Create a migration name

Keep the default, just create a new one.

Wait for synchronization to complete

Migration completed

Send test email, whether you can send and receive email normally after the migration is completed.

Uninstall the exchange 2010 mailbox database

Delete mailbox database directory

Delete IIS virtual directory

After the deletion is completed

Uninstall exchange 2010

When the uninstall is complete, the computer exits the benet.com domain and shuts down.

Domain controller removes DC2

Modify internal and external DNS

Modify public network DNS

Add Host

New alias

New MX record

After configuration, clear the DNS cache and restart

Log in to OWA and send email to test whether the sending and receiving of internal and external network is normal.

Modify client login

The client tests whether the internal and external networks communicate properly.

At this point, the migration from exchange 2010 to exchange 2016 has been completed, and you can send and receive email normally.

-this is the end of this article. Thank you for reading-

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.