Thought Leadership on Managed IT Services presented by SecurElement Infrastructure Solutions.
Microsoft Exchange was introduced into the marketplace more than nine years ago and included some pretty advanced features: high-availability architecture, which included local continuous replication (a second copy of data stored on the same server as production), cluster continuous replication (a clustered fail-over solution using a non-shared server) and standby continuous replication (replicates data from a standalone server or clustered server to standby recovery server).
Additionally, Exchange Server 2007 “also marked the start of the transition to building Exchange Server on the .Net Framework.” (Exchange Team, 2016) Microsoft has continued to expand and build using the .Net Framework for additional versions of Exchange, including Exchange 2013, Exchange 2016 and Office 365. As announced by Microsoft, April 11, 2016 marks the one-year countdown to Exchange Server 2007 End of Support. Now is the time to plan a migration if you are still running Exchange 2007.
The Microsoft Exchange Team offers up some great information for customers still running Exchange 2007 and considering a move: “Customers running Exchange 2007 have the option to upgrade via mailbox move to Exchange 2010, Exchange 2013 or migrate directly to Office 365. Customers wanting to migrate to the latest version of Exchange Server, Exchange Server 2016, will need to first decrement Exchange Server 2007. Customers wanting to maximize their on-premises server investment should strongly consider migrating to Exchange Server 2016 as Exchange Server 2013 is already three years into its own 10-year lifecycle.” (Exchange Team, 2016)
A great resource when considering an Exchange upgrade is the Microsoft Exchange Server Deployment Assistant, which is a web-based tool that assesses your current environment through simple questions and produces a checklist to deploy the Exchange environment that’s right for your organization. The tool outlines deployment and migration scenarios for Exchange 2010, Exchange 2013, Exchange 2013, Exchange Online and Office 365.
The Microsoft Exchange Team also provides some great articles around upgrading from Exchange 2007 to Exchange 2013, as well as planning and deploying Exchange 2016.
As with any migration or deployment, speak with your trusted IT advisor/Microsoft partner, who can help design a migration plan that’s right for your organization.
Exchange Team. (2016, April 11). Microsoft Exchange Team Blog. Retrieved from Microsoft TechNet: https://blogs.technet.microsoft.com/exchange/2 016/04/11/exchange-server-2007-t-1-year-andcounting/