Microsoft Exchange 2010 to Exchange 2013 Transition (part 1)
Microsoft has made the Exchange 2013 transition from Exchange 2010 a bit easier than it was in the past. This article should help to explain the process. Prerequisites Before you begin with this endeavor: Make sure that your Exchange 2010 infrastructure has been patched to Exchange Service Pack 3, this includes Edge transport servers, Client Access Servers, Hub Transport Servers and Mailbox Servers. This service pack is required for the coexistence period with Exchange 2013 as noted in the Exchange Team’s Blog. Say goodbye to Exchange 2003. You can not have Exchange 2003 in your organization any longer. Check your DNS Server and Event logs for errors. It’s unlikely that you had DNS errors before an upgrade that you didn’t already know about but it’s certainly worth taking a look just to check. A few minutes of discovery is well worth not having hours of troubleshooting afterwards. Plan your Exchange 2013 infrastructure. This article only explains the transition steps, but you should research and understand what your infrastructure should look like before you start a migration. Do you have multiple sites that need High Availability? Do you need multiple Exchange servers in a Database Availability Group? Do you need to separate your Client Access Server from your Mailbox Server for performance or management reasons, or can you put them on the same box? How many different Mailbox databases should you have? These are important design considerations. Licensing There are two flavors of Exchange 2013. Standard allows for up to five mailbox databases, and Enterprise allows for up to 50. ...