Exchange 2016 system requirements
Applies to: Exchange Server 2016
Topic Last Modified: 2017-05-16
Summary: What you need to have in your environment before installing Exchange 2016.
 Tip: |
|---|
| Coming from the Exchange Deployment Assistant? Click Exchange 2013 system requirements. |
Before you install Exchange 2016, we recommend that you review this topic to ensure that your network, hardware, software, clients, and other elements meet the requirements for Exchange 2016. In addition, make sure you understand the coexistence scenarios that are supported for Exchange 2016 and earlier versions of Exchange.
The following table lists the scenarios in which coexistence between Exchange 2016 and earlier versions of Exchange is supported.
Coexistence of Exchange 2016 with earlier versions of Exchange Server
| Exchange version | Exchange organization coexistence |
|---|---|
| Exchange 2007 and earlier versions | Not supported |
| Exchange 2010 | Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers. |
| Exchange 2013 | Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers. |
| Mixed Exchange 2010 and Exchange 2013 organization | Supported with the following minimum versions of Exchange:
|
Exchange 2016 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365. For more information about specific hybrid deployments, see Hybrid deployment prerequisites.
The following table lists the requirements for the network and the directory servers in your Exchange 2016 organization.
Network and directory server requirements for Exchange 2016
| Component | Requirement |
|---|---|
| Domain controllers | All domain controllers in the forest need to be running one of the following:
|
| Active Directory forest | The Active Directory forest functionality level needs to be at Windows Server 2008 or higher. |
| DNS namespace support | Exchange 2016 supports the following domain name system (DNS) namespaces:
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. |
| IPv6 support | In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the 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. |
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2016.
 Note: |
|---|
| In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese (ja-jp), your servers may not receive some attributes that are stored on an object during inbound replication. For more information, see Microsoft Knowledge Base article 949189, A Windows Server 2008 domain controller that is configured with the Japanese language locale may not apply updates to attributes on an object during inbound replication. |
For security and performance reasons, we recommend that you install Exchange 2016 only on member servers and not on Active Directory 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 recommendedAfter Exchange 2016 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
For information about deploying Exchange in a virtualized environment, see Exchange 2016 virtualization.
Hardware requirements for Exchange 2016
| Component | Requirement | Notes |
|---|---|---|
| Processor |
| For more information, see Sizing Exchange 2016 Deployments. See the "Operating system" section later in this topic for supported operating systems. |
| Memory | Varies depending on Exchange roles that are installed:
| For more information, see Sizing Exchange 2016 Deployments. |
| Paging file size | The page file size minimum and maximum must be set to physical RAM plus 10MB, to a maximum size of 32,778MB (32GB) if you're using more than 32GB of RAM. | None |
| Disk space |
| For more information, see Sizing Exchange 2016 Deployments. |
| Drive | DVD-ROM drive, local or network accessible | None |
| Screen resolution | 1024 x 768 pixels or higher | None |
| File format | Disk partitions formatted as NTFS file systems, which applies to the following partitions:
Disk partitions containing only the following types of files can optionally be formatted as ReFS:
| None |
The following table lists the supported operating systems for Exchange 2016.
| 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 to install the Desktop Experience on Windows Server prior to starting Exchange 2016 Setup:
|
Supported operating systems for Exchange 2016
| Component | Requirement |
|---|---|
| Mailbox and Edge Transport server roles |
|
| Management tools | One of the following:
|
*Requires Exchange Server 2016 Cumulative Update 3 or later.
Supported Windows Management Framework versions for Exchange 2016
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.
Installing other software on an Exchange 2016 server
We don't support the installation of Office client or Office server software, such as SharePoint Server; Skype for Business Server; Office Online Server; or Project Server, on Exchange 2016 servers. Other software that you want to install on Exchange 2016 servers needs to be designed to run on the same computer as Exchange.
We strongly recommend that you use the latest version of .NET Framework that's supported by the release of Exchange you're installing.
| Important: |
|---|
| Releases of .NET Framework that aren't listed in the table below are not supported on any release of Exchange 2016. This includes minor and patch-level releases of .NET Framework. |
| Exchange version | .NET Framework 4.7.1 | .NET Framework 4.6.2 | .NET Framework 4.6.1 | .NET Framework 4.5.2 |
|---|---|---|---|---|
| Exchange 2016 CU8 | X | X |
|
|
| Exchange 2016 CU5 - CU7 | X |
|
| |
| Exchange 2016 CU4 | X | X3 | X3 | |
| Exchange 2016 CU3 | X | X | X | |
| Exchange 2016 CU2 |
| X1,2 | X | |
| Exchange 2016 RTM or CU1 |
|
| X |
1 .NET Framework 4.6.1 requires post-release fixes if you want to install it on a server running Exchange 2016 CU2. For more information. see Exchange 2016 prerequisites.
2 If you're upgrading to Exchange 2016 CU4 from Exchange 2016 RTM, CU1, or CU2, we strongly recommend that you install Exchange 2016 CU4 before .NET Framework 4.6.2 or .NET Framework 4.6.1 and its related post-release fixes.
3Starting with Exchange 2016 CU5, .NET Framework 4.6.1 and 4.5.2 will no longer be supported with Exchange 2016. While those versions of .NET Framework are supported by Exchange 2016 CU4, we strongly recommend that you upgrade servers running Exchange 2016 to .NET Framework 4.6.2.
-
Outlook 2016
-
Outlook 2013
-
Outlook 2010 SP2 and updates KB2956191 and KB2965295
-
Outlook for Mac for Office 365
-
Outlook for Mac 2011