If you’re finally being pushed off Server 2012, 2016, or 2019 (we’ve covered what happens when Server 2016 hits end of life and what’s actually changing for Server 2019 in detail), here’s the honest answer to “what am I landing on”: Windows Server 2025 LTSC, released November 1, 2024, with mainstream support running to November 13, 2029 and extended support to November 14, 2034. If you also run Exchange on-prem, the mail side of that migration isn’t “Exchange Server 2025.” It’s something Microsoft named differently, and the naming confusion has already cost some admins a wasted afternoon of searching.
What “Windows Server 2025 LTSC” actually means
LTSC stands for Long-Term Servicing Channel: no feature drops, no forced UI changes, just monthly cumulative updates for a fixed lifecycle. That’s the same model Server 2012, 2016, and 2019 shipped under, so if you’ve managed any of those, the patching rhythm won’t surprise you.
The numbers that matter for planning:
- Windows Server 2025: released 2024-11-01, mainstream support to 2029-11-13, extended support to 2034-11-14
- Windows Server 2022: released 2021-08-18, mainstream support to 2026-10-13, extended support to 2031-10-14
- Windows Server 2019: released 2018-11-13, mainstream support already over, extended support to 2029-01-09
- Windows Server 2016: released 2016-08-02, extended support to 2027-01-12
(Dates from Microsoft’s own release health page, which is the only place worth trusting for these; third-party trackers drift.)
Two things worth noticing. First, Server 2022 is not dead: it still has a full decade of combined support ahead of it, so “2025 is newer, therefore go straight there” isn’t automatically correct. We’ve laid out that specific tradeoff in Server 2022 vs 2025 if you’re weighing the two head to head. Second, 2025’s ten-year total lifecycle (five mainstream, five extended) matches the pattern Microsoft has used since 2016, so don’t expect a shorter runway just because it’s the current release.
What’s actually new in the 2025 build: TLS 1.3 support for LDAP (this alone fixes a real compliance gripe from the last few audits we’ve seen), hotpatching that lets you install security updates without a reboot on Azure-connected boxes, and deeper Azure Arc / Azure Stack HCI integration. None of that is a reason to rush a migration on its own. It’s a reason not to be scared of the new release once you’re forced to move.
Exchange SE: the mail server that isn’t called “Exchange Server 2025”
Here’s the part that trips people up. For years, the assumption was that Exchange would follow the same year-based naming as Windows Server: Exchange 2016, Exchange 2019, then presumably “Exchange 2025.” Microsoft didn’t do that. The next on-prem Exchange release is called Exchange Server Subscription Edition, or Exchange SE, and it reached general availability on July 1, 2025.
If you searched for “exchange server 2025 release date” and landed here, this is why you didn’t find a product by that name: it doesn’t exist. Exchange SE is it.
The bigger surprise is how it installs. Exchange SE is not a from-scratch build you stand up on a fresh server. It ships as a cumulative update (CU14 or CU15, depending on your current patch level) on top of an existing Exchange Server 2019 installation, and it can coexist with 2016 or 2019 mailboxes during a phased cutover. If your org is still running Exchange 2016 or 2019, we walked through the underlying end-of-life pressure in Exchange Server 2019 and 2016 end of life; Exchange SE is the destination that piece was building toward.
The other change is the lifecycle model itself. Exchange SE runs under Microsoft’s Modern Lifecycle Policy: no fixed end-of-support date, continuous servicing instead of periodic cumulative-update cycles, and (per Microsoft’s own announcement) no plans for another year-numbered Exchange release after this one. That’s good news for predictability and bad news if you liked having a hard date to plan a migration around. There isn’t one anymore. Support continues as long as you stay on a current, supported configuration.
Stay, jump, or leave on-prem entirely: the actual decision tree
- Still comfortably inside Extended Security Updates or standard support on your current server? Don’t move yet. A migration for its own sake burns budget and introduces risk with no security upside. Finish the current support window first.
- Running Server 2016 (support ends January 12, 2027) or Server 2019 (extended support ends January 9, 2029)? Start planning now. Eighteen months sounds like a lot until you factor in hardware procurement, application compatibility testing, and the inevitable one legacy app that breaks on the new OS.
- Deciding between Server 2022 and Server 2025? If you’re buying new hardware today, go 2025: you get the longer runway and the new security features for the same licensing cost. If you already have 2022 licenses and hardware in flight, finishing that deployment is fine; 2022 isn’t going anywhere until late 2031.
- Considering Azure or a hosted alternative instead of another on-prem box? That’s a legitimate option, and for a single mail server or a handful of file shares it’s often cheaper over five years than a hardware refresh plus CALs. It’s not automatically the right call for line-of-business apps with hard latency or compliance requirements that keep them on-prem. Run the total cost of ownership numbers before committing either way; don’t take “the cloud is obviously better” at face value from a vendor slide.
- Running Exchange on-prem specifically? The CU-based upgrade path to Exchange SE is genuinely less disruptive than past Exchange migrations, since you’re not standing up parallel servers from zero. That said, if you’ve been quietly moving mailboxes to Microsoft 365 anyway, this is a natural decision point to ask whether you need on-prem Exchange at all, versus just keeping it for a hybrid identity or compliance reason.
Licensing gotchas nobody mentions until the invoice arrives
- CAL requirements didn’t go away. Server 2025 still needs Client Access Licenses on top of the server license for most deployments, exactly like 2022 and 2019 did. Budget for both, not just the OS.
- VLSC is gone. If your org bought through the old Volume Licensing Service Center, that’s retired. Downloads and license management for current products now route through the Microsoft 365 admin center, which catches procurement teams off guard when the familiar portal simply isn’t there anymore.
- Exchange SE’s subscription framing isn’t a new recurring fee for on-prem. It describes the servicing model (continuous updates, no year-numbered successor), not a new licensing charge layered on top of your existing Exchange licensing. Don’t let a vendor or reseller imply otherwise without pointing you to the specific SKU.
- Core-based licensing minimums still apply on Server 2025 Standard and Datacenter, same as 2022. If you’re sizing new hardware, check the per-core minimums before you finalize the CPU spec, not after.
Before you start: back up, and actually test the restore
Every migration guide says “back up first.” Say it enough times and it stops meaning anything. So be specific: before you touch a production domain controller, mailbox database, or file server for this migration, do a full backup, then restore it to an isolated environment and confirm the restored system actually boots and the data is intact. A backup job that reports “success” and a backup you’ve verified you can restore from are two different things, and the gap between them is where actual disasters happen during OS upgrades. This matters more here than usual because you’re not just patching in place, you’re moving to a new OS build and, if Exchange is involved, applying a CU that changes the underlying schema.
FAQ
Is Windows Server 2025 LTSC worth moving to now, or should I wait for 2022 to expire?
If you’re not forced by an approaching end-of-support date, waiting is fine. Server 2022 has support into October 2031, so there’s no security reason to rush unless you specifically need a 2025-only feature like LDAP TLS 1.3 or hotpatching.
Does Exchange SE require a clean install, or can I upgrade in place?
It installs as a cumulative update (CU14 or CU15) on top of an existing Exchange Server 2019 deployment. There’s no from-scratch “Exchange SE setup.exe” the way there was for past major versions; you’re patching your way there.
What happened to “Exchange Server 2025” as a name?
It never shipped under that name. Microsoft branded the successor to Exchange 2019 as Exchange Server Subscription Edition (Exchange SE), which reached general availability on July 1, 2025, and moved to a continuous servicing model instead of another year-numbered release.
If you’re mapping out the whole migration, not just this one server, start with whichever end-of-life date is closest on your network and work backward from there. Our Server 2022 vs 2025 comparison covers the OS choice in more depth if you’re still deciding between those two.