Today marks the start of the one-year countdown before Exchange Server 2007 reaches the end of extended support. If Exchange 2007 is still part of your messaging infrastructure, it’s not too early to start planning an update.
It’s hard to believe that it’s been 9+ years since we released CCR, LCR and SCR. These technologies of course laid the ground work for the Database availability groups (DAGs) we’ve relied upon since Exchange Server 2010. Exchange Server 2007 also marked the start of the transition to building Exchange Server on the .Net Framework. We have continued that investment and .Net Framework is now the foundation of all critical Exchange processes in Exchange 2013, Exchange 2016 and Office 365.
Exchange PowerShell, also new to Exchange 2007, is even more prevalent in current versions of Exchange and is the de facto management tool for modern Exchange Servers.
As revolutionary as Exchange 2007 was at the time, our latest versions of Exchange Server and Office 365 have even more to offer. 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.
Here are links which you may find helpful to start planning your migration off of Exchange Server 2007 and be on your way to experiencing the latest capabilities of Exchange Server.
The Exchange Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.