{"id":3744,"date":"2022-11-16T03:00:13","date_gmt":"2022-11-16T03:00:13","guid":{"rendered":"https:\/\/www.sebae.net\/blog\/servicing-exchange-server\/"},"modified":"2022-11-16T03:00:13","modified_gmt":"2022-11-16T03:00:13","slug":"servicing-exchange-server","status":"publish","type":"post","link":"https:\/\/www.sebae.net\/blog\/servicing-exchange-server\/","title":{"rendered":"Servicing Exchange Server"},"content":{"rendered":"
\n

Earlier this year, we announced<\/a> changes to our servicing model for Exchange Server that moved to a servicing cadence of two Cumulative Updates (CUs) per year, releasing in H1 and H2 of each calendar year, with general target release dates of March and September.<\/p>\n

Today we\u2019re announcing that the next CU for Exchange Server will be the H1 2023 CU (aka Exchange Server 2019 CU13<\/em><\/strong>). Because there are only 2 weeks remaining in November, and because based on customer feedback we don\u2019t release CUs in December, there won\u2019t be an H2 2022 CU.<\/p>\n

The H1 2023 CU will be only for Exchange Server 2019<\/em><\/strong> because it is the only version of Exchange Server in Mainstream<\/a> support. Exchange Server 2016<\/a> and Exchange Server 2013<\/a> are in Extended<\/a> support, and there will be no more CUs for those versions.<\/p>\n

There are significant differences between Mainstream and Extended support:<\/p>\n\n\n\n\n
\n

Mainstream support<\/strong><\/p>\n<\/td>\n

\n

Extended support<\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

\u00b7 Customers receive Security Updates (SUs) and time zone updates.<\/p>\n

\u00b7 Customers can file bugs and request features and receive bug fixes and enhancements.<\/p>\n

\u00b7 To get support (and SUs), customers must run the current CU (N<\/em>) or the one immediately previous (N-1<\/em>) \u2013 today, that\u2019s either Exchange Server 2019 CU11<\/em> or Exchange Server 2019 CU12<\/em>.[1]<\/span><\/a><\/p>\n<\/td>\n

\n

\u00b7 Customers receive only SUs and time zone updates.<\/p>\n

\u00b7 To get support (and SUs), customers must run the current CU \u2013 either Exchange Server 2016 CU23<\/em> or Exchange Server 2013 CU23<\/em>.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Updating an Exchange server is straightforward. You can start by using the\u00a0Exchange Server Health Checker<\/a> script\u00a0to inventory your servers and see if any of your Exchange Servers need updates (CUs or SUs), and if any additional actions need to be taken by an admin.<\/p>\n

Once you know what updates are needed, you can use the Exchange updates step-by-step guide<\/a> (aka the Exchange Update Wizard)\u00a0to choose your currently running CU and your target CU and get directions for updating your environment.<\/p>\n

If you encounter errors during update installation, the\u00a0SetupAssist<\/a> script can help troubleshoot them.\u00a0 And if something does not work properly after updates, have a look at the Update Troubleshooting Guide<\/a>, which covers the most common issues and how to resolve them.<\/p>\n

Be sure to always read our blog post announcements, noting any known issues or required manual actions. For CUs, always follow our guidance and best practices<\/a>, and for SUs, use the Security Update Guide<\/a> to find the relevant information.<\/p>\n

Exchange Server 2013 End of Support<\/font><\/p>\n

As a reminder, Exchange Server 2013 reaches the end of support on April 11, 2023, which is less than 150 days from today!<\/p>\n

Exchange Server 2013 will continue to run after this date, of course; however, because it will no longer be supported after that date and because it won\u2019t receive any further updates, we strongly recommend that you migrate from Exchange Server 2013 as soon as possible.\u00a0If you haven’t already begun your migration from Exchange Server 2013 to Exchange Online or Exchange Server 2019, now’s the time to start planning.<\/p>\n

Your best option is to:<\/p>\n