Exchange Server 2013 Requirements
Deandra Uleman
Before you install Exchange Server 2019, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2019. Also, ensure that you understand the coexistence scenarios that are supported for Exchange 2019 and earlier versions of Exchange.
If you deploy Exchange in this configuration, and your network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 Support in Exchange 2013.
To learn more about the issues that you'll encounter when you install Exchange on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange is installed, changing the server role from a member server to a directory server or vice-versa isn't supported.
Exchange 2019 servers support the version of PowerShell that's included in the release of Windows Server where Exchange is installed. Don't install stand-alone downloads of Windows Management Framework (WMF) or PowerShell on Exchange servers.
We don't support installing Office client or Office server software on Exchange servers (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server). Other software that you want to install on an Exchange 2019 server need to be designed to run on the same computer as Exchange Server.
Releases of .NET Framework that aren't listed in the table below aren't supported on any release of Exchange 2019. These releases include minor and patch-level releases of .NET Framework.
If you're integrating Lync presence and instant messaging with Exchange Server, Lync Server 2013 Cumulative Update 10 or later is required. If you're integrating Skype for Business presence and instant messaging with Exchange Server, Skype for Business Server Cumulative Update 7 or later is required.
Before you install Exchange Server 2016, we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange 2016. Also, ensure you understand the coexistence scenarios that are supported for Exchange 2016 and earlier versions of Exchange.
For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces.
For security and performance reasons, we recommend that you install Exchange 2016 only on member servers and not on Active Directory servers. To learn about the issues you can face when installing Exchange 2016 on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController]. After Exchange 2016 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Important: We don't support the installation of Exchange 2016 on a computer that's running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed. To install Exchange 2016, you need to do one of the following steps to install the Desktop Experience on Windows Server prior to starting Exchange 2016 Setup:
Windows Server 2016: Install Windows Server 2016 and choose the Desktop Experience installation option. If a computer is running Windows Server 2016 Core mode and you want to install Exchange 2016 on it, you'll need to reinstall the operating system and choose the Desktop Experience installation option.
Exchange 2016 only supports the version of Windows Management Framework that's built in to the release of Windows that you're installing Exchange on. Don't install versions of Windows Management Framework that are made available as stand-alone downloads on servers running Exchange.
We don't support installing Office clients or other Office server products (for example, SharePoint Server, Skype for Business Server, Office Online Server, or Project Server) on Exchange 2016 servers. Software that you want to install on an Exchange 2016 server need to be designed to run on the same computer as Exchange Server.
Releases of .NET Framework that aren't listed in the table below aren't supported on any release of Exchange 2016. These releases include minor and patch-level releases of .NET Framework.
If you want to use a third-party client that uses our protocols or APIs, we recommend that you thoroughly review and test all considerations (functionality, security, maintenance, management, and so on) before you deploy the client in the enterprise workspace. We also recommend that you ensure that the third-party vendor offers an appropriate Enterprise Support Agreement (ESA).
This topic provides the steps for installing the necessary Windows Server operating system prerequisites for Exchange Server 2016 and Exchange Server 2019 Mailbox servers and Edge Transport servers, and also the Windows prerequisites for installing the Exchange Management Tools on Windows client computers.
After you've prepared your environment for Exchange Server, use the Exchange Deployment Assistant for the next steps in your actual deployment. For information on hybrid deployments, see Exchange Server Hybrid Deployments.
Have you heard about the Exchange Server Deployment Assistant? It's a free online tool that helps you quickly deploy Exchange Server in your organization by asking you a few questions and creating a customized deployment checklist just for you. If you want to learn more about it, go to Microsoft Exchange Server Deployment Assistant.
The system requirements for the Visual C++ Redistributable package do not mention support for Windows Server 2016, Windows Server 2019 or Windows Server 2022, but the redistributable package is safe to install on these versions of Windows.
The Visual C++ redistributable package is required if you're using the Exchange Setup Wizard to prepare Active Directory. If you're using unattended Setup from the command line to prepare Active Directory, this package isn't required. For more information, see Prepare Active Directory and domains.
The requirements to install Exchange 2019 on Windows Server 2019 or Windows Server 2022 computers are described in the following sections. We recommend either of the following methods to install the Windows prerequisites for Exchange 2019:
The system requirements for the Visual C++ redistributable package do not mention support for Windows Server 2016, Windows Server 2019 or Windows Server 2022, but the redistributable package is safe to install on these versions of Windows.
Note that Exchange Setup will re-install MSMQ if you check the Automatically install Windows Server roles and features that are required to install Exchange Server checkbox during the GUI Setup, or if you use the InstallWindowsComponents as part of unattended Setup.
The prerequisites that are needed to install Exchange 2016 on computers running Windows Server 2016 depends on which Exchange role you want to install. Read the section below that matches the role you want to install.
You can only install this update if your Windows Server 2016 version is 14393.576 or earlier (circa December, 2016). You can check your Windows Server version by running the winver command. If your Windows Server 2016 version is greater than 14393.576, you don't need this update or its replacement KB3213522, which was released one week later. Exchange 2016 Setup looks for the installation of this update, won't allow you to continue if this update is missing, and will clearly inform you if you need it.
The prerequisites for Exchange 2016 on Windows Server 2012 or Windows Server 2012 R2 computers depend on the Exchange role that you're installing. Read the following section that matches the role you want to install.
e59dfda104