EXCHANGE2003 Upgrade to 2010 considerations

The latest version of Exchange has evolved to Exchange2013, which adds a lot of practical functionality. Many users of older exchange products are starting to think about product upgrades.

There are two ways to upgrade Exchange: In-place upgrade and migration. In general, in order to improve the availability of the business more is to adopt the migration method. The so-called migration, basically means that the lower version of the mail system and the high version of the coexistence, and then smooth the migration of the mailbox.

EXCHANGE2003 does not support coexistence with exchange2013. So if there is a 03 upgrade to 2013 demand, you have to first transition from exchange2007 or 2010.

650) this.width=650; "title=" clip_image002 "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" clip_image002 "src=" Http://s3.51cto.com/wyfs02/M00/6F/A4/wKiom1Wjl_ Dq88kkaabxkb8wsay560.jpg "" 558 "height=" 183 "/>

The following is a practical case to share the next Exch2003 upgrade to 2010 of the main steps and considerations

Network topology

650) this.width=650; "title=" clip_image004[4] "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" clip_image004[4] "src=" Http://s3.51cto.com/wyfs02/M01/6F/A4/wKiom1Wjl_ Hyzotraacm-romapc232.jpg "" 558 "height=" 219 "/>

Main steps

1. Assume that the existing 03dc+03exchange environment user mail function is normal

2. Upgrade an existing Exchange 2003 server to Exchange 2003 Service Pack 2 (SP2).

3. Deploy the Exchange 2010 server in the following order:

A) Client access

b) Hub Transport

c) Unified Messaging (optional)

d) Email

If it is a all-in-one deployment, choose a typical installation.

4. Configure the Exchange 2003 front-end server and the Exchange 2010 Client Access server.

5. Configure the Exchange 2010 Hub Transport server and the Unified Messaging server.

6. Move mailboxes from Exchange 2003 to Exchange 2010

7. Old and new coexistence period

Precautions

1. Ensure that the current forest has a functional level of at least Win2003 and that the schema master is running 2003SP1 or later

2. Ensure that existing Exchange 2003 servers are upgraded to Exchange 2003 Service Pack 2 (SP2)
Exchange 2003 Service Pack 2 (SP2):
https://www.microsoft.com/en-us/download/details.aspx?id=9664

3. Exchange 2003 mode is native mode and cannot be mixed mode (default)
650) this.width=650; "title=" clip_image006[4] "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" clip_image006[4] "src=" Http://s3.51cto.com/wyfs02/M02/6F/A4/wKiom1Wjl_ Hg5sldaahoi3un93c252.jpg "" 558 "height=" 419 "/>

4. Exchange2010 Pre-Installation Preparation
SETUP/PL//Prepare permissions for legacy EXCHANGE2003 servers
SETUP/PS//Architecture Preparation
setup/p//For forest preparation
Setup/pad//is domain preparation on all domains in the forest, including subdomains within all domain trees

5. If you want to deploy Exchange2010 SP1, it is recommended that you use the integrated SP1 Exchange installation CD. For now, it is recommended to install Exchange2010 SP2 directly (SP3 is primarily for Windows Server 2012)
Exchange2010 SP2:
http://www.microsoft.com/en-us/download/details.aspx?id=28190

6. After you install an Exchange 2010 server, the installation process automatically creates a routing group connector that completes message routing for both 03exch and 10exch.
650) this.width=650; "title=" clip_image008[4] "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" clip_image008[4] "src=" Http://s3.51cto.com/wyfs02/M02/6F/A5/wKiom1Wjl_ Kj1avraafzuh8wca4610.jpg "" 558 "height=" 419 "/>

7. During the coexistence of Exchange2003 and Exchange2010, when users use OWA to access a mailbox, they need to have unified access to the Exchange2010 CAs or CAs Array.
If the mailbox is stored on a Exchange2010 mailbox server, the Exchange2010 CAs or CAS array will jump directly to the user's mailbox;
If the mailbox is accessed on the EXCHANGE2003 server, the CAs or CAS array will first jump the user's access request to EXCHANGE2003 's OWA and access the mailbox through EXCHANGE2003 's OWA.
Exchange2010 generally use the name legacy.ms.local to access Exchange2003, so make sure that the certificate used by Exchange2003 front-end server IIS contains the legacy.ms.local domain name.
Set OWA jump manually
To implement OWA jump, you need to open EMS on EXCHANGE2010 's CAS server and run the following command:

Get-owavirtualdirectory | Set-owavirtualdirectory-exchange2003url Https://legacy.ms.local/exchange
650) this.width=650; "title=" clip_image010[4] "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" clip_image010[4] "src=" http://s3.51cto.com/wyfs02/M00/6F/A2/ Wkiol1wjmcmstyiiaaeq6xdzux0387.jpg "" 558 "height=" 376 "/>

8. In Exchange 2010, all client access requests are connected to the CAS server, authenticated, and then forwarded to the appropriate mailbox server by proxy. In order to improve the security of communications, it is required to access the CAS server in an encrypted manner.
Therefore, when requesting a certificate from a CA, the certificate name should contain the following (assuming intranet domain name ms.local)
08exch.ms.local
Mail.ms.local
Autodiscover.ms.local
Legacy.ms.local
Ms.local
After the EXCH2010CAS server requests, installs the certificate and assigns it to the appropriate service, it can export the certificate with the private key to 03exch.

9. During the coexistence period, Exchange2010 as the backbone of the mail system, incoming and outgoing mail must go through the Exchange2010.
Incoming mail through the Exchange2010 server, the EXCHANGE2010 server to determine whether the mail to Exchange200 or direct mail to the user's mailbox;
Outbound Mail even if submitted to Exchange2003, and finally to go through the Exchange2010 to send to the extranet post office.

10. During coexistence, if a user mailbox needs to be created, it is generally created directly on the Exchange2010.

Migrating mailboxes can use the EMC graphical interface, or you can use the EMS command line. If the type is "Legacy Mailbox" in the EMC mailbox list, it means that these mailboxes are Exchange2003 mailboxes. You can then start the Migration Wizard by creating a new local move request.
650) this.width=650; "title=" clip_image012 "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px;  padding-right:0px "border=" 0 "alt=" clip_image012 "src=" Http://s3.51cto.com/wyfs02/M01/6F/A5/wKiom1Wjl_ Osstobaae7jt1tphi388.jpg "" 558 "height=" 376 "/>
You can also use PowerShell to migrate mailboxes in EMS, such as
New-moverequest-identity ' [email protected] '-targetdatabase ' DB01 '
migrating [email protected] mailboxes to the DB01 mailbox database
For more command parameters please refer to:
Https://technet.microsoft.local/zh-cn/library/dd351123 (v=exchg.150). aspx

11. During coexistence, the associated FQDN name should be able to parse

Mail.ms.local	2010cas/cas Array IP Address
Legacy.ms.local	2003 Front-end server IP address

Exch2010 to implement external communication, configure the Send connector and accept connectors, etc.
The contents of this section can be referenced
http://yiding.blog.51cto.com/499333/1671576

Here are some of the errors I encountered during the migration process, which are posted to you for reference:

Error 1: Access to Exch2010 user mailbox is normal, but access to Exch2003 user mailbox has been unresponsive. No authentication occurs.

The lookup data tip may be a 03exch virtual directory corruption, when you need to rebuild the virtual directory.

Http://www.exchangecn.local/exchange2003/20101218_281.html

After you restart the Microsoft Exchange System Attendant service After the rebuild is complete, you can restart the exchange2003 server if it is not working correctly.

Error 2:exchange OWA Legacy URL redirection HTTP Error

or access to the old user mailbox, redirect address is also right, and so entered the user name and password, is to enter, has been reported HTTP error> after query, the solution is as follows:

http://exchangeserverpro.local/exchange-2010-owa-legacy-url-redirection-http-500-error/

It probably means setting up the 03exch HTTP protocol to enable forms-based authentication. Problem solving.

During coexistence, it is recommended to observe more time. If necessary, we will remove 03exch later. Please look forward to!

EXCHANGE2003 Upgrade to 2010 considerations