Coexistence and migration of EX2010 and EX2013 01-Design and description

1.1Coexistence Condition Description

- versions of Exchange 2013 that were released years ago do not support coexistence, and only the Exchange version CU1 that is released on April 2, 2013 supports coexistence, and Exchange 2010 must be supported for SP3 and 2013 for coexistence and migration. EXCHANGE2003 does not support coexistence and migration with 2013. The following is a detailed coexistence note:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/80/6C/wKiom1dBLNnhW6z6AACH1vRmgPo476.png "title=" 02.png "alt=" Wkiom1dblnnhw6z6aach1vrmgpo476.png "/>

1.2test Environment Description

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/80/6A/wKioL1dBLlOif7UwAAH4W49mIt8809.png "title=" 03.png "alt=" Wkiol1dblloif7uwaah4w49mit8809.png "/>

1 ) Internal domain: beijing.local

2 ) Public domain name: daodefangxiang.com

3 ) Active Directory: one for Windows 2008 Active Directory

4 ) Exchange 2010:exchange 2010 Server One

5 ) Exchange 2013:exchange2013 CAS server one, Exchange mailbox server one

6 ) test client: One for internal test client, one for public network test client

1.3Test Target

1 ) to enable Exchange 2010 and Exchange 2013 coexistence.

2 ) for Exchange 2010 and Exchange 2013 data migration.

3 mail clients are unaffected by coexistence and data migration, ensuring that mail is accessible to both internal and external mail clients.

1.4test Plan design and description 1.4.1 Coexistence Scenario Design:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/80/6C/wKiom1dBMDHzrkIvAADkSyePiMg927.png "title=" 04.png "alt=" Wkiom1dbmdhzrkivaadksyepimg927.png "/>

1.4.2 Migration Design steps:

You see this picture must be very familiar with it, in fact, this is my Exchange 2010 upgrade plan to change, just a little bit different, first of all, the upgrade step.

Step One: Exchange 2010 is upgraded to Exchange SP3.

Step Two: Exchange 2013 uses the CU1 version to deploy the Exchange 2013 servers sequentially. Install the mailbox server first, and then install the CAS server.

Step three: Move the Internet host name to Exchange CAS,MX records to Exchange CAS.

Step four: Move the mailbox to Exchange 2013.

Note: During the Exchange 2013 upgrade planning process, Exchange2010 does not need to specify a legacy host name on the public network.

1.4.3 Coexistence, migration instructions

Exchange there is a need to coexist between 2 versions before migrating to 2013. Exchange coexistence refers to the fact that multiple versions of Exchange servers are joined to the same Exchange organization, and that the servers can be accessed and co-existed before the migration of the message data is realized. The purpose of exchange coexistence is not only to restrict the migration of messaging data, but also to enable the coexistence of mail clients between different versions of Exchange, for example: Customers have about 2T of mail data, and customers are ready to upgrade their mail systems to exchange 2013, but we can not be in the week of Six, a short 2 days to migrate all the mail data, if the migration can not be completed, the mail client is bound to be affected, so we have to implement the mail client coexistence before migration.

What we need to know before migrating:

1 , public network A records point to Exchange Cas: Span style= "line-height:150%;font-family: ' The song Body '; >exchange

2 , MX record points to Exchange Cas: as a stateless proxy for all inbound and outbound external SMTP traffic for the organization. The front end transport service does not check the message content, but it can filter messages based on connection, domain, sender, and recipient. The front end transport service communicates only with the transport service on the mailbox server. That is, Exchange CAs can do inbound and outbound proxies for Exchange Mailbox, Exchange hub messages, and this time you should know why you should point your MX records to Exchange Cas.

3 , Exchange2013 OWA client can be automatically redirected to Exchange on OWA: Exchange Cas The main feature is redirection, since it can be redirected to Exchange 2013Mailbox, and of course can be redirected to Exchange on CAs, Microsoft is not so weak.

4 , Exchange2013 CAS supports exchange Outlook anywhere client redirection: Exchange Cas with respect to the old version of anywhere, note that redirection is not a prior takeover, and all the anywhere features of Exchange 2010 are also turned on.

5 , the Outlookanywhere client automatically updates the client configuration after data migration: Migrating user mailboxes The configuration of the Hu anywhere client does not need to be changed manually, it will automatically notconsistent the user configuration to the new server, using the technology you can certainly guess, is automatic discovery, in-house anywhere through the SCP discovery, Public network anywhere is discovered through Autodiscover.

Note, RPC is no longer a supported direct access protocol. This means that all Outlook connections must use Outlook Anywhere.  

This article is from the "Juck Zhang" blog, please be sure to keep this source http://daodefangxiang.blog.51cto.com/8658374/1775835

Coexistence and migration of EX2010 and EX2013 01-Design and description