Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
📧 vmorecloud.com · Enterprise Messaging
Microsoft Exchange Server Subscription Edition (SE) — Download & What’s New
Exchange Server SE is Microsoft’s latest on-premises email platform, released July 2025. Built on Exchange 2019 CU15, it introduces a subscription licensing model, TLS 1.3, certificate management improvements, and a roadmap toward Kerberos-first authentication and REST Admin APIs. This post covers everything enterprise admins need to know — plus direct download links.
⚠️ Important — Exchange 2016 & 2019 are end of life
Exchange Server 2016 and 2019 reached end of support on October 14, 2025. The October 2025 Security Update was the last publicly available patch for those versions. If your organization is still running either version, upgrading to Exchange Server SE is now urgent. Extended Security Updates (ESU) are available only through a paid Microsoft agreement and expire April 2026.
01 Download Exchange Server SE
The files below are hosted directly on vmorecloud.com. These are the official Exchange Server SE installation media obtained from the Microsoft 365 admin center (formerly VLSC). Always verify the SHA-256 hash before installation.
Exchange Server Subscription Edition — Installation Files
All files verified · Hosted on vmorecloud.com · Last updated: May 2026
💡 Verify your download
Always verify the SHA-256 hash before deploying in production. Run the following in PowerShell to get the hash of your downloaded file:
Get-FileHash -Path "C:\Downloads\ExchangeServer-SE-RTM.ISO" -Algorithm SHA256 | Select Hash
02 What’s New in Exchange Server SE
Exchange Server SE introduces a new licensing model and a focused set of security and manageability improvements. Features arrive in two waves: SE RTM (available now) and SE CU1 (2026).
TLS 1.3 Support
SE RTM
TLS 1.3 is now supported on Windows Server 2022 and 2025 (excluding SMTP, coming in a future CU). Eliminates obsolete cryptographic algorithms and encrypts more of the handshake, reducing the attack surface significantly compared to TLS 1.2.
Certificate Management in EAC
SE RTM
Certificate management returns to the Exchange Admin Center. Admins can now create certificate requests, complete requests after receiving certificates, export certificates as PFX files, and import PFX certificates — all without PowerShell.
Subscription Licensing Model
SE RTM
Exchange SE moves to a subscription-based license (like SharePoint SE). Perpetual licenses are gone. Requires active Software Assurance or a subscription CAL. New product keys are required — obtain from the Microsoft 365 admin center. No fixed end-of-support date under Modern Lifecycle Policy.
Kerberos Server-to-Server Auth
SE CU1
CU1 replaces NTLMv2 with Kerberos (Negotiate:Kerberos) as the default authentication protocol for inter-server communication. Setup will enable Kerberos on all Exchange virtual directories during installation. Significantly hardens the authentication surface.
REST-Based Admin API
SE CU1
A new REST Admin API enables remote management and automation without Remote PowerShell (RPS). RPS is deprecated in CU1 and will be removed in a future CU. Aligns on-premises Exchange management with Exchange Online tooling patterns.
Outlook Anywhere Removed
SE CU1
RPC over HTTP (Outlook Anywhere) is removed in CU1. Organizations still relying on Outlook Anywhere must migrate clients to MAPI over HTTP or Exchange ActiveSync before applying CU1. This mirrors Exchange Online, which removed Outlook Anywhere years ago.
Windows Server 2025 Support
SE RTM
Exchange SE fully supports Windows Server 2025 as the host OS. Microsoft recommends deploying on Windows Server 2025 to maximize the support lifecycle and take advantage of the latest Windows security hardening features.
Modern Lifecycle Policy
SE RTM
Exchange SE is governed by the Modern Lifecycle Policy — no fixed end-of-support date as long as you keep current with CUs. Microsoft has also confirmed support for Exchange SE (alongside SharePoint SE) through at least 2035.
03 System Requirements & Prerequisites
Exchange Server SE shares identical hardware and OS requirements with Exchange 2019 CU15. No Active Directory schema changes are required when upgrading from Exchange 2019.
| Component | Minimum | Recommended |
|---|---|---|
| Operating System | Windows Server 2019 | Windows Server 2025 |
| Processor | 64-bit, 4 cores | 8+ cores (Mailbox role) |
| RAM | 128 GB | 256 GB (heavy mailbox load) |
| Disk (OS) | 30 GB | 60 GB SSD |
| Disk (Exchange) | 30 GB | 200 GB+ SSD (binaries + logs) |
| .NET Framework | 4.8 | 4.8.1 |
| AD Forest Functional Level | Windows Server 2012 R2 | Windows Server 2016+ |
| AD Domain Functional Level | Windows Server 2012 R2 | Windows Server 2016+ |
| Visual C++ Redistributable | 2012 / 2013 | 2022 (required for CU1) |
| TLS | TLS 1.2 enabled | TLS 1.3 (WS 2022 / 2025) |
Pre-Installation Checklist
| Task | Done | Notes |
|---|---|---|
| Run Setup /PrepareAD | ✓ | Extends AD schema, requires Schema Admin rights |
| Run Setup /PrepareAllDomains | ✓ | Prepares all domains in the forest |
| Install .NET Framework 4.8+ | ✓ | Reboot required after install |
| Install Visual C++ 2012/2013 | ✓ | Required by Exchange binaries |
| Disable UAC or run as Admin | ✓ | Setup must run with elevated rights |
| Verify TLS configuration | ✓ | All servers must use consistent TLS settings |
| Obtain new SE product key | ✓ | Available in Microsoft 365 admin center |
| Remove Exchange 2013 (if present) | ✓ | SE blocks co-existence with Exchange 2013 |
04 Upgrade Paths to Exchange Server SE
Your upgrade route to Exchange SE depends on your current version. The table below summarizes the supported paths.
Exchange 2019 CU14 or CU15
↓ In-place upgrade
Direct upgrade to SE RTM. Easiest path — install SE RTM as a Cumulative Update on top of CU14/CU15.
Exchange 2019 CU13 or earlier
↓ Two steps
First upgrade to Exchange 2019 CU15, then in-place upgrade to SE RTM.
Exchange 2016 CU23
↓ Classic migration
SE can co-exist with Exchange 2016 in RTM only. Migrate mailboxes to SE, then decommission 2016 before applying CU1.
Exchange 2013 or earlier
↓ Not supported
Exchange 2013 co-existence is blocked. Must be fully decommissioned before SE can be introduced.
🚨 CU2 Warning — Hard Coexistence Block
Starting with Exchange SE CU2, Setup will block installation if any Exchange 2016 or 2019 servers remain in the organization. Plan your decommission timeline accordingly — do not let Exchange 2016/2019 linger after SE CU1 is applied.
05 Key Installation Commands
Prepare Active Directory
PowerShell / CMD (elevated)
# Step 1 — Prepare the AD schema (run from Schema Admin account) .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF # Step 2 — Prepare Active Directory .\Setup.exe /PrepareAD /OrganizationName:"YourOrgName" /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF # Step 3 — Prepare all domains in the forest .\Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF
Install Exchange Server SE (New Server)
PowerShell / CMD (elevated)
# Full Mailbox Role installation (unattended) .\Setup.exe /Mode:Install /Role:Mailbox /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF # With custom install path .\Setup.exe /Mode:Install /Role:Mailbox /TargetDir:"D:\Exchange" /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF
In-Place Upgrade from Exchange 2019 CU14/CU15
PowerShell / CMD (elevated)
# Run SE RTM setup on existing Exchange 2019 CU14/CU15 server .\Setup.exe /Mode:Upgrade /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF # Verify installed build after upgrade Get-ExchangeDiagnosticInfo -Server $env:COMPUTERNAME -Process EdgeTransport -Component VariantConfiguration -Setting Overrides | Select-Object -ExpandProperty Result # Quick build check via EMS Get-ExchangeServer | Select Name, Edition, AdminDisplayVersion
Verify Activation & License
Exchange Management Shell
# Check product key and license status Get-ExchangeDiagnosticInfo -Server $env:COMPUTERNAME -Process EdgeTransport -Component VariantConfiguration # Enter your product key (obtained from M365 admin center) Set-ExchangeServer -Identity $env:COMPUTERNAME -ProductKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX # Restart IIS and Transport after keying net stop MSExchangeTransport && net start MSExchangeTransport iisreset /noforce
06 Frequently Asked Questions
Is Exchange Server SE the same as Exchange Server 2025?
There is no product called “Exchange Server 2025.” Microsoft moved away from year-based versioning. The successor to Exchange 2019 is Exchange Server Subscription Edition (SE), released July 2025. It is code-equivalent to Exchange 2019 CU15 at RTM, but governed by the Modern Lifecycle Policy and requires a subscription license.
Can I do a free in-place upgrade from Exchange 2019?
The upgrade process itself is free, but Exchange SE requires a new subscription license or active Software Assurance. If your existing Exchange 2019 licenses have active SA, you qualify for Exchange SE at no additional cost. Customers without SA must purchase a new subscription. New product keys must be obtained from the Microsoft 365 admin center (formerly VLSC).
Can Exchange SE coexist with Exchange 2016 or 2019?
Yes, with limitations. Exchange SE RTM can coexist with Exchange 2016 CU23 and Exchange 2019 CU14/CU15. However, Exchange SE CU2 will block installation if any Exchange 2016 or 2019 servers remain in the organization. Plan to fully decommission legacy servers before applying CU2.
What happens to Remote PowerShell with Exchange SE?
Remote PowerShell (RPS) is deprecated in CU1 and will be removed in a future CU. This does not mean PowerShell management goes away — the Exchange Management Shell continues to work. What changes is the underlying transport protocol: a new REST-based Admin API replaces the RPS protocol. This aligns on-premises Exchange with Exchange Online management architecture.
Is TLS 1.3 fully supported in Exchange SE RTM?
TLS 1.3 is supported on Windows Server 2022 and Windows Server 2025 in Exchange SE RTM, except for the SMTP protocol. SMTP TLS 1.3 support will be added in a future CU. You cannot disable TLS 1.2 in environments where SMTP is in use until SMTP TLS 1.3 support arrives.
What is the end-of-support date for Exchange Server SE?
There is no fixed end-of-support date. Exchange SE is governed by the Modern Lifecycle Policy — support continues indefinitely as long as you keep your installation current with Cumulative Updates. Microsoft has additionally committed to supporting Exchange SE (alongside SharePoint SE and Skype for Business Server) through at least 2035.
Do I need to upgrade the Active Directory schema?
Only if upgrading from Exchange 2016 or earlier. There are no AD schema changes when upgrading from Exchange 2019 to Exchange SE. The Windows Server 2012 R2 forest functional level continues to be supported. If you’re on Exchange 2016, you must run
Setup /PrepareSchema and Setup /PrepareAD.Can Exchange SE be deployed on Windows Server 2019?
Yes, Exchange SE RTM supports Windows Server 2019, 2022, and 2025. However, Microsoft recommends deploying on Windows Server 2025 to maximize the support lifecycle of both the OS and Exchange SE. Windows Server 2019 reaches end of support in 2029; Windows Server 2025 reaches it around 2034.
