[step by step]Exchange 2016 Installation Requirement
Microsoft Has released Exchange 2016 recently and we all are eager to see what’s new on Exchange 2016. But, before installing the Exchange 2016 there are few requirements that we need to know about it. Like Operating system, co-existence of system, supported client, .net framework etc. Here I will be elaborating what are the required system for the exchange system.
1. Supported Co-existence scenario.
Unlikely Exchange 2013, Exchange 2016 do have a different architecture. For Exchange 2016 we do have different Architecture, hence we need to know what are the co-existence Exchange server that can be parallel run with Exchange 2016. Below is the table that can help.
| 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:
|
Source: TechNet.
2. Supported Hybrid Deployment Scenario
There is different hybrid scenario that can be mixed up with Exchange 2016 which are listed below.
On-premises Exchange organization
| On-premises environment | Exchange 2016-based hybrid deployment | Exchange 2013-based hybrid deployment | Exchange 2010-based hybrid deployment |
| Exchange 2016 | Supported | Not supported | Not supported |
| Exchange 2013 | Supported | Supported | Not supported |
| Exchange 2010 | Supported | Supported | Supported |
| Exchange 2007 | Not supported | Supported | Supported |
On-premises server roles The server roles you need to install in your on-premises organization depend on the version of Exchange you have installed.
- Exchange 2010 At least one server with the Mailbox, Hub Transport, and Client Access server roles installed. While it’s possible to install the Mailbox, Hub Transport, and Client Access roles on separate servers, we strongly recommend that you install all of the roles on each server to provide additional reliability and improved performance.
- Exchange 2013 At least one server with the Mailbox and Client Access server roles installed. While it’s possible to install the Mailbox and Client Access roles on separate servers, we strongly recommend that you install both roles on each server to provide additional reliability and improved performance.
- Exchange 2016 and newer At least one server that has the Mailbox server role installed.
3. Network and Directory Servers
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:
· Windows Server 2012 R2 Standard or Datacenter · Windows Server 2012 Standard or Datacenter · Windows Server 2008 R2 Standard or Enterprise · Windows Server 2008 R2 Datacenter RTM or later · Windows Server 2008 Standard, Enterprise, or Datacenter |
| 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:
· Contiguous · Non-contiguous · Single label domains · Disjoint |
| 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. |
4. Directory Server Architecture
As or the previous Version of the Exchange server, it was able to get install on the Directory Server too i.e. on Domain Controller. But in case of the Exchange 2016, it is recommended to install on the member servers only not on Active Directory server. However due to security reasons, it is not possible to run DCPromo o a computer running Exchange 2016. Also after Exchange 2016 is installed, changing its role from a member server to a directory server, or vice-versa isn’t supported.
5. Hardware
Although the Hardware required for Exchange 2016 can be calculated using the Exchange Calculator. Which is available on this link. We can recommend the hardware as below.
Hardware requirements for Exchange 2016
| Component | Requirement |
| Processor | · x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T)
· AMD processor that supports the AMD64 platform · Intel Itanium IA64 processors not supported |
| Memory | Varies depending on Exchange roles that are installed:
· Mailbox 8GB minimum · Edge Transport 4GB minimum |
| Paging file size | The page file size minimum and maximum must be set to physical RAM plus 10 MB, to a maximum size of 32778MB if you’re using more than 32GB of RAM. |
| Disk space | · At least 30 GB on the drive on which you install Exchange
· An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install · 200 MB of available disk space on the system drive · A hard disk that stores the message queue database on with at least 500 MB of free space. |
| Drive | DVD-ROM drive, local or network accessible |
| Screen resolution | 1024 x 768 pixels or higher |
| File format | Disk partitions formatted as NTFS file systems, which applies to the following partitions:
· System partition · Partitions that store Exchange binary files or files generated by Exchange diagnostic logging Disk partitions containing the following types of files can be formatted as ReFS: · Partitions containing transaction log files · Partitions containing database files · Partitions containing content indexing files |
6. Operating System Requirement.
Following are the Operating system on which exchange server 2016 can be installed. Also Exchange server 2016 cannot be installed on those servers which are installed on Core Mode. If it is need to install than Core mode should be converted to a full installation of Windows Server by running the command
‘Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart ‘
| Component | Requirement |
| Mailbox and Edge Transport server roles |
|
| Management tools | One of the following:
|
7. .Net Framework
To get install Exchange 2016 MS recommends latest version of .NET Framework that’s supported by the release of Exchange 2016.
| Exchange version | .NET Framework 4.5.2 |
| Exchange 2016 | X |
8. Supported Clients
Exchange 2016 and Exchange Online support the following versions of Outlook:
- Outlook 2016
- Outlook 2013
- Outlook 2010 with KB2965295
- Outlook for Mac for Office 365
- Outlook for Mac 2011
Azure AD My Sign-Ins Activity Report
![[Solved]Error: Sorry, there was a problem and we can’t open this document with Office Online on Exchange Outlook Web Apps](/wp-content/themes/ribbon-lite/images/nothumb-related.png)
[Solved]Error: Sorry, there was a problem and we can’t open this document with Office Online on Exchange Outlook Web Apps
COMMAND FOR WINDOWS
About Author
pdhewjau
Prashant is a Principal Cybersecurity Specialist at Thakral One Nepal. His prior position as a Modern Work Security Specialist at Microsoft saw him providing invaluable guidance to major clients in Bangladesh, Brunei, Cambodia, and Myanmar, assisting them with their foundational security needs. Awarded the esteemed Microsoft Most Valuable Professional (MVP) accolade in 2017, Prashant is recognized globally among Microsoft peers. Since 2010, he has imparted his expertise as a Microsoft Certified Trainer (MCT), conducting specialized training across Nepal.