Blog Post

Exchange Team Blog
1 MIN READ

Updates on Servicing Exchange Server 2019

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Dec 09, 2024
In early 2022, we announced 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...
Updated Feb 10, 2025
Version 3.0
announcements
exchange 2019
on premises
Ken Brussel's avatar
Ken Brussel
Brass Contributor
Jan 28, 2025

Hi Nino-

Maybe we'd have a little more appreciation for the delays if there was transparency in what issues Microsoft is seeing with the internal regression testing and the TAP program.  It's hard to call this 24H2 (seeing as how this is now in 25H1) and January has only 3 days remaining... the schedule continues to slip.

Also, I don't think we've seen a document/article showing us what's expected to be coming in this update / ExchangeSE (or what differences would be made between CU14+all the SU's and CU15/SE).

Ken

Nino_Bilic's avatar
Nino_Bilic
Icon for Microsoft rankMicrosoft
Jan 28, 2025

Thanks, Ken... the following are going to be "the same":

Exchange 2019 CU15 + SUs released in the mean time + rebrand / new EULA = Exchange SE RTM

We are making no other changes. No features, nothing. Exchange 2019 CU15 is therefore a "lrager release" for us (as it is the last E2019 CU and is the last chance to release any features before Exchange SE CU1). But otherwisse, there will be no other changes.

You are right on the slipping schedule. Soon now...

  • DavidYorkshire's avatar
    DavidYorkshire
    Steel Contributor
    Jan 28, 2025

    "You are right on the slipping schedule. Soon now..."

    I'm afraid a lot of us have now reached the stage of not believing any expected release timescales, given the number of delays.

    This all comes on top of the fact that there was no Exchange release corresponding to Windows Server 2022, which there normally had been with previous server releases.

    And some of us only actually need it to manage hybrid deployments with EOL mailboxes - MIcrosoft could easily have created a set of lightweight tools to do this, but hasn't and still requires a full Exchange server (I am aware that Powershell is a possibiity, but this is not an efficient method for the sort of one-off quick changes that most admins will make fairly regularly, e.g. adding aliases to mailboxes, hiding mailboxes from the GAL, etc).