StarWind is a hyperconverged (HCI) vendor with focus on Enterprise ROBO, SMB & Edge

Installing Exchange Server 2016 on Windows Server 2016

  • January 30, 2017
  • 9 min read
IT Production Manager. Nicolas is primarily focused on Microsoft technologies, he is a Microsoft MVP in Cloud and Datacenter Management.
IT Production Manager. Nicolas is primarily focused on Microsoft technologies, he is a Microsoft MVP in Cloud and Datacenter Management.

Exchange server 2016

On October 1st, Microsoft Exchange Team released the new Exchange Server 2016. Microsoft had been testing and improving on millions of mailboxes in their Office365 environment before it released the product on-premises. In this article, I will describe a step-by-step guide for the installation of Microsoft Exchange Server 2016. The installation considers:

  • Single server deployment of Exchange Server 2016 with the Mailbox role on the new Windows Server 2016
  • Windows Server 2016 forest functional level
  • Exchange Server 2016 with the latest Cumulative Update 4

Because Windows PowerShell is a powerful tool that every sysadmin should already know, I will use PowerShell to perform the installation. But If you prefer the graphical interface, you can use that.

Step 1: Requirements

Before installing Exchange Server 2016, you must review the following requirements:

Forest Functional Level for Exchange 2016
  • Windows Server 2008 or higher
Minimum Operation System
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
Minimum Memory Requirement (RAM)
  • Mailbox Server 8GB minimum
  • Edge Transport Server 4GB minimum

To check your Active Directory Forest Functional Level, you can run the “Get-ADForest” cmdlet:

PowerShell script


  1. Note that Microsoft doesn’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.
  2. Client Access Role is removed in Exchange Server 2016, which simplifies the Exchange architecture.

If you need further information about what you need to have in your environment before installing Exchange 2016, please visit the following link:

Step 2: Installing Pre-Requisites

Open Windows PowerShell as Administrator, and run the sconfig utility to install the latest Windows Updates. Exchange Server 2016 requires the update described in Microsoft Knowledge Base article KB3206632. Without this update, Exchange Server 2016 will not work reliably on Windows Server 2016. Choose number 6 to download and install Updates:

Open Windows PowerShell as Administrator

Next, run the following command to install the Remote Tools Administration Pack:

PowerShell script

Now, we will install the required roles. The prerequisites for Exchange Server 2016 varies if you run Windows Server 2012 or 2016. So be careful, and use the following for Windows Server 2016:

Windows indicates that no reboot is required, but I advise you to restart the server.

PowerShell script

.Net Framework 4.5 and higher is required, so to check the .Net version on Windows Server 2016:

If it’s above “394747”, then it means you have the necessary .NET Framework 4.6.2 or later installed.

PowerShell script

To finish with pre-requisites, you must download and install Unified Communications Managed API 4.0 Runtime:

Unified Communications Managed API 4.0 Runtime

Click Next and Finish to install Microsoft UCMA component:

Unified Communications Managed API 4.0 Runtime

Step 3: Preparing Schema and Active Directory

After you’ve prepared a Windows Server with the Exchange Server 2016 pre-requisites, you can proceed with the schema update. To apply only the schema update:

First, mount the Exchange Server 2016 installation media, open a PowerShell console and navigate to the setup files. Then, type the following command:

Windows PowerShell

Extending schema status must be “Completed”. After applying the schema update we can prepare our Active Directory with the PrepareAD parameter:

Windows PowerShell

The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed.

Windows PowerShell

If you have more than one domain, you can replace the PrepareDomain parameter with PrepareAllDomains parameter.

StarWind HyperConverged Appliance is a turnkey, entirely software-defined hyperconverged platform purpose-built for intensive virtualization workloads. Bringing the desired performance and reducing downtime, the solution can be deployed by organizations with limited budgets and IT team resources. Also, it requires only one onsite node to deliver HA for your applications that makes the solution even more cost-efficient.
Find out more about ➡ StarWind HyperConverged Appliance

Step 4: Installing the Mailbox Server Role

The Mailbox server role contains all of the components required to run an Exchange Server 2016 server. If you need an Edge Server, you can still install it in Exchange 2016 but that is not a mandatory role. At this point, it’s up to you. To install the Mailbox Role, there are two ways you can do this:

  • Using the graphical interface. Run the exe, choose Next, Accept the agreement, select the Mailbox Role, specify the path for the Exchange Server installation and choose Install.
  • Or you can try to install Exchange with Windows PowerShell.

Below are the available parameters to customize your installation:

In my opinion, it’s never a good idea to install the Exchange Database and the log folder on the root partition.

The setup process will collect some information needed for installation, check the prerequisites and configure your Exchange Server. Just wait …

Windows PowerShell

When it’s done, open Internet Explorer and go to https://<FQDN of Mailbox Server>/owa to validate your Exchange installation.

Exchange installation validation

You have successfully installed your Exchange Server 2016 on Windows Server 2016. The idea of this article was to illustrate how PowerShell can allow us to simplify and automate our daily tasks.

Thanks for checking out this guide!


Found Nicolas’s article helpful? Looking for a reliable, high-performance, and cost-effective shared storage solution for your production cluster?
Dmytro Malynka
Dmytro Malynka StarWind Virtual SAN Product Manager
We’ve got you covered! StarWind Virtual SAN (VSAN) is specifically designed to provide highly-available shared storage for Hyper-V, vSphere, and KVM clusters. With StarWind VSAN, simplicity is key: utilize the local disks of your hypervisor hosts and create shared HA storage for your VMs. Interested in learning more? Book a short StarWind VSAN demo now and see it in action!