Install Microsoft Exchange Server 2019 Step by Step
Microsoft released the first Exchange version 4.0 in the year 1996. In October 2018, Microsoft released its latest Exchange Server 2019. Its minimum Server OS requirement is Windows Server 2019 and can be deployed on Windows Server 2019 Core Edition as well.
Exchange 2019 Standard can only be installed on Windows Server 2019 Standard. Similarly, Exchange 2019 Datacenter can only be installed on Windows Server 2019 Datacenter. Exchange 2010 is not supported, however, Exchange 2013 CU21 and later and Exchange 2016 CU11 and later are supported as co-existence.
Exchange 2019 will not be supported with any Domain Controller running on Windows Server 2012 or older in the organization, however, will support Domain Controller running Win Server 2012R2 or later. If you have any Win Server 2012, you need to first upgrade it to Win Server 2012R2. Domain & Forest Functional Level should also be at least Win Server 2012R2.
On the client side, Exchange Server 2019 will not support any workstation running Windows 8 or older, however, it will support Windows 10. If you have client machines running Windows 7 or Windows 8, you can use OWA access. The browsers supported for OWA are Edge, IE11, chrome, firefox.
Outlook 2019, 2016 and 2013 will be supported with Exchange 2019.
Unified Messaging has been completely removed from it, now the organizations using Skype For Business now have to move to alternative solutions for voicemail like Azure Cloud Voicemail, etc.
Exchange 2019 can support up to 48 processor cores and 256 GB of RAM. All roles (Mailbox, CAS, Hub) are consolidated into one Exchange Server 2019 as seen its predecessor Exchange 2016. You can install Exchange 2019 as an Edge Transport Server as well in DMZ.
b) Visual C++ Redistributable Package for Visual Studio 2012
Note: Do not install Windows Management Framework 5 i.e., Powershell V5, else Exchange Management Shell will not be able to connect.
c) Open Powershell in Admin mode:
Install-WindowsFeature NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, 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-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
d) Open CMD in Admin mode and cd into the Exchange Installation Directory:
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Setup.exe /PrepareAD /OrganizationName: XYZCompany /IAcceptExchangeServerLicenseTerms
Note: Replace XYZCompany by your Organization Name. If you have two words enter them in quotes e.g., “Xyz Company”.
GUI mode of Installation will open – Connect to Internet and check for Updates – Select Mailbox + Management Tools + check Automatically Install Windows Server Roles and Features. It will perform the Prerequisites check and if you get Warning, kindly ignore it unless you get an error message. Click Install.
Note: I highly recommend you to create a new user e.g, [email protected] with Domain Admin, Organization Management & Enterprise Admin Roles. Enable his mailbox on Exchange 2016 Database.
Enable-Mailbox -Identity [email protected] -Database DatabaseOn2019
It will help you open the Exchange Admin Center 2019 directly if you type https://localhost/ecp
A hybrid deployment with Office 365 has been detected. Please ensure that you are running setup with the /TenantOrganizationConfig switch.
Cause: If you have an existing Exchange 2010 Server and have configured Hybrid Setup with Office 365, you may find an error:
1. Connect to Exchange Online Powershell.
2. Run the command
Get-OrganizationConfig | Export-Clixml -Path C:\MyTenantOrganizationConfig.XML
Setup.exe /PrepareAD /TenantOrganizationConfig C:\MyTenantOrganizationConfig.XML /IAcceptExchangeServerLicenseTerms
Restart the machine and you will find your newly Exchange 2019 environment. Open Google Chrome and type:
Login with Administrator credentials. Configure it properly.
If you have Exchange 2010 and wants to decommission it, follow the steps below:
1) Export 3rd party SSL Certificate from Exchange 2010 and import it into Exchange 2019. Assign the services IIS & SMTP to imported certificate.
2) Export all the Receive connectors using the script and run the command in Exchange 2019 Management Shell:
.\Copy-ReceiveConnector.ps1 -SourceServer DC1 -ConnectorName "Specific Receive Connector" -Targ etServer DC5 -MoveToFrontend -ResetBindings -DomainController DC1.exolab.tk
3) Point all Firewalls & Load Balancers to Exchange 2019 Private Ip Address.
4) Try validating with [email protected] user from Office 365 – Outbound to On-Premises Connector in to check mail flow is working. Try sending one test email from 2016Admin user to migrated cloud user and vice versa.
5) Point all Multi-Functional Devices / Applications using SMTP Relay to the Private Ip Address of Exchange 2016 Server.
6) Migrate all three Arbitration/System Mailboxes from Exchange 2010 to Exchange 2019 using Migration Tab in Exchange 2019 Admin Center.
7) Shut down Exchange 2010 server and check mail flow working fine. Leave it shut down for one week to check reporting from any end-user. Once everything seems working for 1-2 weeks, then think of De-commisioning the Exchange 2010 Server.
There are total 13 Steps. I have included the Live Demo of all the above steps. I hope if you are facing any issues, the tutorial will help you:
Thanks a ton for reading my blog, don’t leave without mentioning your comments, errors and I will try to revert with a best possible resolution. Please do Subscribe our Youtube Channel for more upcoming videos like this.
Ajey Kumar Gupta
a) Install Windows 2016 Step by Step
b) How to create Linkedin Learning Premium Account for free?