Microsoft explicitly recommends Windows Server Core as the primary operating system platform for Exchange Server 2019 (CU14/CU15) and Exchange Server Subscription Edition (SE). Running Exchange on Server Core eliminates the Desktop Experience GUI shell, reducing the OS memory footprint, shrinking the monthly Patch Tuesday attack surface, and cutting reboot requirements across Database Availability Group (DAG) members.
Because Windows Server Core has no graphical Setup Wizard, every stage of the deployment—from configuring static IP addresses and joining Active Directory to installing .NET Framework 4.8, Visual C++ Redistributables, IIS URL Rewrite, UCMA 4.0, and executing Setup.exe—must be performed from the command line or PowerShell.
In this enterprise deployment runbook, we walk through the complete start-to-finish installation of Exchange Server 2019 and Exchange Server SE on Windows Server Core.
Upgrading from Exchange 2019 to Exchange Server SE? If you already have Exchange Server 2019 CU14 or CU15 deployed, see our companion guide: Exchange Server SE vs. Exchange 2019: In-Place Upgrade Runbook.
OS & Active Directory Support Matrix (Exchange 2019 vs. Exchange SE)
Before mounting the Exchange ISO on Windows Server Core, confirm that your underlying Windows Server OS and Active Directory Forest Functional Level match the supported matrix:
| Requirement | Exchange Server 2019 (Initial / CU1–CU11) | Exchange Server 2019 (CU12–CU15) | Exchange Server Subscription Edition (SE) |
|---|---|---|---|
| Supported Windows Server Core OS | Windows Server 2016 Core (Preview only) / Windows Server 2019 Core | Windows Server 2019 Core / Windows Server 2022 Core | Windows Server 2019 / 2022 / 2025 Core |
| .NET Framework Requirement | .NET Framework 4.7.2 – 4.8 | .NET Framework 4.8 / 4.8.1 | .NET Framework 4.8 / 4.8.1 (Built-in on 2022/2025) |
| AD Forest Functional Level | Windows Server 2012 R2 or higher | Windows Server 2012 R2 or higher | Windows Server 2012 R2 or higher |
| IIS URL Rewrite Module | Not required prior to CU11 | Required (v2.1+) for Mitigations Service | Required (v2.1+) |
Step 1: Configure Windows Server Core Networking & Domain Membership
When you log in to a fresh installation of Windows Server Core, you can either use the built-in text menu (sconfig.cmd) or run PowerShell directly to set a static IP address, point DNS to your internal Active Directory Domain Controller, and join the domain:
# Launch PowerShell from the Server Core CMD prompt
powershell.exe
# 1. Configure Static IPv4 Address and DNS Server
$Adapter = Get-NetAdapter | Where-Object { $_.Status -eq "Up" } | Select-Object -First 1
New-NetIPAddress -InterfaceIndex $Adapter.ifIndex -IPAddress "10.10.10.25" -PrefixLength 24 -DefaultGateway "10.10.10.1"
Set-DnsClientServerAddress -InterfaceIndex $Adapter.ifIndex -ServerAddresses ("10.10.10.10", "10.10.10.11")
# 2. Set High Performance Power Plan (Recommended for Exchange Mailbox Servers)
powercfg.exe -setactive c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
# 3. Rename the Server and Join the Active Directory Domain
Rename-Computer -NewName "EXCH-CORE-01" -Force
Add-Computer -DomainName "lab365.local" -Credential (Get-Credential) -Restart
Building a Standalone Isolated Test Lab? Only if you are building a single-VM lab and have no existing Domain Controller, you can promote a lab DC usingInstall-WindowsFeature AD-Domain-ServicesandInstall-ADDSForest -DomainName "Samayra.com" -DomainNetbiosName "SAMAYRA" -InstallDns:$true. In production, never install Exchange on a Domain Controller.
Step 2: Install Windows Server Core Features & Prerequisite Runtimes
Before installing the Unified Communications Managed API (UCMA 4.0) or running Exchange Setup, install the required Windows Server Core features—especially Server-Media-Foundation and RSAT-ADDS—and silently install the required redistributables.
# 1. Install Required Windows Server Core Features for Exchange 2019 / Exchange SE
Install-WindowsFeature Server-Media-Foundation, NET-Framework-45-Features, RPC-over-HTTP-proxy, `
RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-PowerShell, WAS-Process-Model, `
Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, `
Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, `
Web-Metabase, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, `
Web-Static-Content, Web-Windows-Auth, Web-WMI, RSAT-ADDS
# Reboot if required by Windows Features
Restart-Computer -Force
Next, copy the prerequisite installers to C:\Prereqs on your Server Core host and install them silently:
- Visual C++ Redistributable 2012 & 2013 (
vcredist_x64.exe) - IIS URL Rewrite Module 2.1 (
rewrite_amd64_en-US.msi) — Mandatory for Exchange 2019 CU11+ and Exchange Server SE - .NET Framework 4.8 (only needed on Windows Server 2019 Core; already included in Windows Server 2022/2025 Core)
- UCMA 4.0 Runtime (located inside the
\UCMARedistfolder on the Exchange ISO)
# 2. Silently Install Visual C++ Redistributables and IIS URL Rewrite 2.1
Start-Process -FilePath "C:\Prereqs\vcredist_x64_2012.exe" -ArgumentList "/install /quiet /norestart" -Wait
Start-Process -FilePath "C:\Prereqs\vcredist_x64_2013.exe" -ArgumentList "/install /quiet /norestart" -Wait
Start-Process -FilePath "msiexec.exe" -ArgumentList "/i C:\Prereqs\rewrite_amd64_en-US.msi /qn /norestart" -Wait
# 3. Mount the Exchange Server 2019 CU15 / Exchange SE ISO Image
$IsoPath = "C:\ISOs\ExchangeServerSE-x64.iso"
$MountResult = Mount-DiskImage -ImagePath $IsoPath -PassThru
$DriveLetter = ($MountResult | Get-Volume).DriveLetter
Write-Host "[+] Exchange ISO mounted on drive $($DriveLetter):\" -ForegroundColor Cyan
# 4. Install Unified Communications Managed API (UCMA) 4.0 from the Mounted ISO
Start-Process -FilePath "$($DriveLetter):\UCMARedist\Setup.exe" -ArgumentList "/quiet /norestart" -Wait
Write-Host "[✔] UCMA 4.0 installed successfully." -ForegroundColor Green
Step 3: Prepare Active Directory Schema & Organization
Using an account that belongs to Schema Admins and Enterprise Admins, run the unattended Active Directory preparation commands from the mounted Exchange ISO drive (E:\ or D:\):
# 1. Extend the Active Directory Schema
& "$($DriveLetter):\Setup.exe" /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
# 2. Prepare Active Directory & Exchange Organization
& "$($DriveLetter):\Setup.exe" /PrepareAD /OrganizationName:"LAB365" /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
# 3. Prepare All Active Directory Domains
& "$($DriveLetter):\Setup.exe" /PrepareAllDomains /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
Note on Licensing Switch: Starting with the September 2021 Cumulative Updates (and in Exchange Server SE), the legacy/IAcceptExchangeServerLicenseTermsswitch was replaced by/IAcceptExchangeServerLicenseTerms_DiagnosticDataON(or_DiagnosticDataOFF). To verify your schema version (rangeUpper = 17003for Exchange 2019 CU14/CU15 and Exchange SE RTM), see How to Verify Active Directory Schema Version via PowerShell.
Step 4: Run Unattended Exchange Server Setup (Setup.exe /m:Install)
Once Active Directory replication has completed across your Domain Controllers, execute the unattended Exchange Mailbox role installation:
# Install the Exchange Mailbox Role Unattended on Windows Server Core
& "$($DriveLetter):\Setup.exe" /Mode:Install /Roles:Mailbox /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /InstallWindowsComponents
The command-line setup progresses through 14 installation steps directly inside the console window:
- Organization Preparation
- Copy Exchange Files
- Language Files
- Restoring Services
- Language Configuration
- Exchange Management Tools
- Mailbox Role: Transport service
- Mailbox Role: Client Access service
- Mailbox Role: Unified Messaging service
- Mailbox Role: Mailbox service
- Mailbox Role: Front End Transport service
- Mailbox Role: Client Access Front End service
- Finalizing Setup (100%)
Step 5: Post-Installation Reboot & Launching EMS (LaunchEMS)
When Setup.exe reports The Exchange Server setup operation completed successfully, reboot the server immediately:
Restart-Computer -Force
After logging back in to Windows Server Core, open the Exchange Management Shell directly from the Command Prompt by typing:
LaunchEMS
Once the Exchange Management Shell loads, verify server health, build number, and services:
# Verify Exchange Server Edition and Build Version
Get-ExchangeServer -Identity $env:COMPUTERNAME | Format-List Name, Edition, AdminDisplayVersion, ServerRole
# Verify All Required Exchange Windows Services Are Running
Test-ServiceHealth -Server $env:COMPUTERNAME
Summary Checklist for Windows Server Core Exchange Admins
- Manage Remotely with EAC & PowerShell: Because Windows Server Core does not include a web browser (or you should avoid browsing on it), access the Exchange Admin Center (
https://exch-core-01/ecp) from a hardened management workstation. - Enter Your Product Key: A newly installed Exchange server runs in Trial Edition for 180 days. Activate it via
Set-ExchangeServer -Identity EXCH-CORE-01 -ProductKey XXXXX-...and restart theMSExchangeISservice. See our Exchange Server Product Key Activation Runbook for full details.