Overview of Migration from MS Exchange 2007\2010 to MS Exchange 2013


Differences in Migration from Exchange Server 2007/Exchange 2010 to Exchange Server 2013

Transitioning from Exchange Server 2007 to Exchange Server 2013 is very similar in principle to an Exchange Server 2010 to Exchange Server 2013 migration, though there are a few key differences. These differences are as follows:

• Exchange Server 2013 Outlook Web App (OWA) servers can proxy a mailbox on an Exchange Server 2010 OWA server but cannot do so for a 2007 mailbox. 2007 mailboxes need to be presented with a referral to the 2007 OWA server, requiring a second logon.

• Exchange Server 2013 servers show up as servers within the Exchange Management Console in Exchange Server 2010 but do not in Exchange Server 2007. They can still be used as mailbox migration targets from the 2013 side, however.

It is noted throughout the chapter where the transition process differs. If it is not noted, it can be assumed that the same process is utilized as is with a 2010 migration.

High-Level Steps to Transition

Ultimately, a transition to Exchange Server 2013 from Exchange Server 2007/2010 is not a terribly complex endeavor. In principle, the migration paths are similar as well, though a few key differences do exist between the two.

Simply put, it requires the following fundamental steps:

1. Upgrade all Exchange servers to Exchange Server 2007 Service Pack 3 RU8 or Exchange Server 2010 Service Pack 3 so they can understand Exchange Server 2013 functionality.

2. Prepare a Windows Server (2008 R2 Service Pack 1 [SP1] or 2012) server for the first Exchange Server 2013 server.

3. Install any necessary prerequisites (WWW for Client Access server [CAS] role, .NET Framework 4.5, Windows Management Framework 3.0, Unified Communications Managed API 4.0, and Windows Identity Foundation 64-bit). Also install the Active Directory Domain Services (AD DS) tools to be able to upgrade the server.

4. Run setup on the Exchange Server 2013 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step, or separate at the command line.)

5. Install the Exchange Server 2013 role servers and configure per 2013 design. Validate functionality.

6. Create new certificates for Exchange Server 2013 using the End to End Certificate Wizard in the Exchange Administration Center (EAC). Be sure to include a legacy namespace for old OWA clients that haven’t been migrated yet to Exchange Server 2013.

7. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers and validate using the Remote Connectivity Analyzer.

8. Transfer inbound and outbound mail traffic to the 2013 SMTP Connectors.

9. Configure Databases (database availability group [DAG] if needed).

10. Create public folder mailboxes on Exchange Server 2013 servers to replace the existing public folder hierarchy (if required).

11. Move mailboxes to Exchange Server 2013 using the Move Mailbox Wizard or PowerShell.

12. Transfer all public folder replicas to Exchange Server 2013 public folder store(s) and cutover public folders when replication is complete.

13. Delete public and private Information Stores from Exchange Server 2007/2010 server(s).

14. Uninstall all Exchange Server 2007/2010 servers.

Please note: Microsoft has not provided migration facility from MS Exchange 2003 to MS Exchange 2013

Advertisements
This entry was posted in Exchange 2007, Exchange 2010, Exchange 2013 and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s