Exchange 2013’s extended support ends in April and Exchange 2016 has been out of mainstream support for a while now. It therefore makes sense to migrate to Exchange 2019 or straight to Microsoft 365. This article provides an overview.
On April 11, 2023, the extended support for Exchange 2013 expire. A migration to Exchange 2019 or Microsoft 365 should therefore have already been complete by now at the latest. From now on, Exchange 2013 will receive neither security nor stability updates. Due to the enormous number of attacks on Exchange servers, email servers should under no circumstances be used productively without ongoing support. Unlike older versions of Windows, there will be no Extended Support Updates program for Exchange.
For Exchange 2016, mainstream support expired on October 1, 2020, and extend support ends on October 14, 2025. In general, Microsoft recommends that products should only be use productively within mainstream support, as this is the only way to ensure that the software is maintain and update for current processors, VM generation versions, drivers, settings, tools, and for collaboration with other products. Outside of mainstream support, a product only receives security updates.
Exchange 2019 is long up to date
Microsoft has announce that it will introduce the successor to Exchange 2019 in the course of 2025. Currently, mainstream support for Exchange 2019 Honduras Phone Number List ends on January 9, 2024, and extended support ends on October 14, 2025. It is currently not possible to say whether these deadlines will be postponed due to the delay of the successor, or whether the successor may come onto the market earlier.
Using Exchange 2019 with Windows Server 2022
In the article ” Running Exchange with different Windows Server versions ” we look at the different Exchange and Windows combinations that are currently available and that enable a supported installation. If you have problems or are migrating, the tips in the article ” 10 tips for troubleshooting Exchange servers ” are also a good starting point. When migrating to Exchange 2019, the versions will inevitably be mixed up. For this reason, in addition to the article linked above, you should also read the page ” Exchange Server supportability matrix“ from Microsoft.
Migration approach: Testing is important
Before the actual migration, admins should take the Cell Phone Number Database time to set up a test environment for the procedures. In addition, a complete backup of the current environment should be made so that the migration can be quickly reverse in an emergency. This applies to the Exchange servers and the domain controllers in the environment.
Before the migration, all servers involve should be update to the latest version. This applies to ongoing operations anyway, but the source servers must be as up-to-date as possible by the time of the migration. For Exchange 2013, Cumulative Update 23 (CU 23)be install.
To migrate from Exchange 2013 to Bulk Database Exchange 2019, MAPIoverHTTP should be activate. The new protocol controls the collaboration between Outlook and the Exchange servers. Activation is describe in the article “Configuring MAPI over HTTP in Exchange Server
Install Exchange 2019 in existing organization
When migrating from Exchange 2013/2016 to Exchange 2019. A new server with Exchange 2019 is first install in the existing organization. In the article link above, we show the necessary preparations for this. When installing Exchange 2019 in an existing environment, the schema is extend. It is a good idea to carry out this step a few days before installing. The server and then prepare the individual domains at the same time:
