Exchange 2007 Migration 2010

Last Update:2015-12-07 Source: Internet

Author: User

Tags change domain name one mail

Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

Exchange 2007 Migration 2010

Theoretical part:

Why migrate 2007

After 2010, 2010 of the need for I/O was significantly reduced by 百分之50到70, and 2010 could also use inexpensive disks such as stat SCSI.

2007 Support for the database is limited, up to 50 can be created, some large enterprises are not enough, and 2007 use of storage groups to organize the database, not conducive to management

2007 of the High availability implementation is not particularly good, 2010 of the DAG does not support 2007, so for all these reasons we need to migrate 2007 to 2010

Migration is actually an upgrade, but instead of a direct upgrade, you create a good one mail server on another server

PS: two mail servers joined to a domain to form a messaging system that's what we call the coexistence environment.

2010 of the database number of the best and 2007 of the same number of databases or a total of more than the organization will be completely disorganized, storage must be more than 2007 of the storage

The order of migration is divided into

Migrate the offline Address book.

Change the Send connector.

Migrate user mailboxes.

Offline Address Book: Offline Address Books in exchange (Offline address book/oab) is a useful feature that allows users to query a large amount of useful information on their offline contacts. Also, because it is "offline", when the client is not connected to the Exchange server, it is still possible to be aware that the offline address Book is only available to Outlook clients using Exchange-mode connections (Mapi/outlook Anywhere). And with cache mode enabled, any other type of client will not use the Offline Address book feature.

The purpose of changing the Send connector is to transfer the Hub Transport server to 2010 to send and receive Internet Mail

User mailboxes are needless to say, migrating those data

Finally, uninstall 2007 related operations

Experimental section:

Lab case: Exchange 2007 Migration 2010

650) this.width=650; "Style=" background-image:none; border-bottom:0px; border-left:0px; margin:0px; padding-left:0px; padding-right:0px; border-top:0px; border-right:0px; padding-top:0px "title=" clip_image004 "border=" 0 "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/M00/77/34/ Wkiol1zlp5lsdmkkaaac5vr9-tk701.gif "" "height=" "/> hy company through the Windows AD Domain management company network resources, the domain name is benet.com. and deployed an Exchange Server 2007 Enterprise Edition Server to enable mail communication within the enterprise. A "Typical installation" that is deployed with a "Mailbox server", "Client Access server" and "Hub Transport server" (today's experiment because there is no home build, the domain name that is prepared in the company environment some change domain name is benet.com)

650) this.width=650; "Style=" background-image:none; border-bottom:0px; border-left:0px; margin:0px; padding-left:0px; padding-right:0px; border-top:0px; border-right:0px; padding-top:0px "title=" clip_image004[4] "border=" 0 "alt=" clip_image004[4] "src=" http://s3.51cto.com/wyfs02/M02/77 /35/wkiom1zlpyegq4xkaaac5vr9-tk680.gif "" height= "/>" The company has now purchased a new server and wants to migrate Exchange Server 2007 to this new server. and upgrade to Exchange Server 2010. To ensure smooth migration, the original offline address book, user mailbox and other information cannot be lost

First, we must make sure that 2007 and Exchange-related services must be in the boot state

Figure 1

2007 of Service Status

Figure 2

2010 of services

First we now create three users on 2007, for testing, the user's name Zhang San, John Doe, Harry

Figure 3

The user has already created

Use Zhang San to send a message to Harry Harry be able to receive

This test does not demonstrate

It's done.

Now all of our operations are done on 2010.

Now we're moving on to a formal migration

The first step is to migrate the offline address Book

Offline Address Book not migrated before migration is on 2007

Right-click Migration for offline Address Book

Figure 5

Now migrate the offline Communications department to 2010

Figure 6

The offline Address Book after migration is already on the 2010

The Offline Address Book migration is complete

Start migrating Send Connectors

Figure 7

Locate the Hub Transport for your organization configuration, locate the Send connector, right-click Properties to find the original server

Now we can see that it exists at 2007, and now we move him to 2010.

Delete the old, as shown in the mountain map

Then click Add

Figure 8

Adding 2010 of servers

Figure 9

The original server after the migration becomes 2010.

Next we migrate mailboxes

PS: In general, the Receive connector is 2010 by default, so we do not change here, but if you want to send and receive Internet mail, you need to enable the default server name anonymous

Figure 10

Locate the user you want to migrate CTRL + LEFT mouse button selected, the right side will appear a new local migration tab

PS: If more than one user is recommended to migrate 50-100 users at a time

Figure 11

Select the target database to move to, 2010 of the database will have the database immediately after the ID

Figure 12

Select Skip mailbox here and click Next

Then click on new to do it.

Figure 13

The migration is complete, we can take a look at the local migration

Figure 14

It's all done.

It should be slow in the actual production environment.

Actually, now we're done with the migration.

PS: In the actual production environment, we need to create the same number of databases as 2007 on 2010, and the best names are the same

And the storage needs to be larger than 2007.

Now we will uninstall 2007

Server configuration found in 2007 of EMC-Mailbox

Figure 15

Locate the default database (delete all mailboxes otherwise you cannot uninstall) uninstall off

Figure 16

cannot be removed until uninstallation is complete (note that deletion cannot be completed if a mailbox exists in the database)

Uninstall now delete public folder database

PS: Public folder databases are not routinely deleted we need a tool

Insert the 2003 installation disc

Figure 17

Find this tool, double-click Run

Figure 18

There is no problem here, run the program directly, because here is the 2008R2 tool is 2003, so there may be some problems, but do today's experiment is not a problem

Figure 19

Figure 20

I agree, the next step

Figure 21

Whatever you want, next.

Figure 22

The default installation is available

You can do it.

Figure 23

Console commands for input

Figure 24

Connect to Configuration

Figure 25

Find this path, delete cn=public folder datadase this directory

Figure 26

We can see that the public folder database is no longer present.

Now we start uninstalling Exchange Server 2007

Find Control Panel-Uninstall the program-right-click to uninstall it

Figure 27

Remove all the hooks.

Figure 28

Check the uninstall prerequisites, in fact, check the database has a mailbox, if it is unloaded

Figure 29

There's no problem.

650) this.width=650; "Style=" background-image:none; border-bottom:0px; border-left:0px; padding-left:0px; padding-right:0px; border-top:0px; border-right:0px; padding-top:0px "title=" clip_image064 "border=" 0 "alt=" clip_image064 "src=" http://s3.51cto.com/wyfs02/M00/77/34/ Wkiol1zlp9nb-mb_aaazloukrsi359.jpg "" 244 "height=" 212 "/>

Figure 30

Started uninstalling.

Now we wait for the road 2010 to test the mailbox can also send

It's still there, it works.

Today's experiment is here if there is any place to see you can contact me QQ will have professional staff for you to answer

Exchange 2007 Migration 2010

This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or complaint, to info-contact@alibabacloud.com. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

Get Started for Free

Sales Support

1 on 1 presale consultation

Chat Contact Sales
After-Sales Support

24/7 Technical Support 6 Free Tickets per Quarter Faster Response

Open a Ticket
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.

Learn More