Exchange 2016 Install (Part 2)

Step by step GUI install:

As always, we can run the install via the unattended setup using the command line or by starting Setup.exe and using the GUI. Below I chose to run the install using GUI, but I will do a quick post on the unattended install in a future post. In this case, this is a new Exchange install. No Exchange server currently exists in the environment and because of this, I won’t be discussing any topics related to a coexistence situation. The process we’ll follow will be to extend the AD schema, prepare the AD environment for Exchange, and finally run the install.

The whole process is pretty straight forward (assuming we have the prerequisites installed correctly). Performing the schema update and preparing AD are just a simple commands that needs to be run before the install. And the Exchange 2016 install itself is a next, next, finish type install with some settings that we will need verify.

To run the Schema upgrade, run the following command:

[PS] C:\Users\mkrause\Downloads\EX2016> .\setup.exe /prepareSchema /IAcceptExchangeServerLicenseTerms

After you have updated the schema, you will not be able to install any version of Exchange prior to 2016 and this can’t be undone so be sure this is what you want to do.

If you haven’t installed the active directory management tools on the exchange server, you will need to prepare the AD from a server that has the tools installed, like a DC, by running the following command:

[PS] C:\Users\mkrause\Downloads\EX2016> .\setup.exe /PrepareAD /OrginizationName:"EX16Lab" /IAcceptExchangeServerLicenseTerms

Preparing the AD in a separate command isn’t necessary in a GUI install as the Exchange installer will perform this task and ask you to name the organization as long as the server has the AD management tools installed. I typically run the prepareAD command from the DCs at the same time I run the prepareSchema command because I prefer to run the unattended installer most of the time.

Finally, to start the setup process, browse to the Setup.exe file and start the install. The first page we are presented with is a general Introduction. There really isn’t anything important here other than some links to Microsoft documentation that can help you plan your Exchange deployment.

Next, we need to accept the license agreement to continue with the install.


Now we have the choice of using the recommended settings or manually configuring our settings. In almost every install I do I prefer to chose to manually configure the install settings and we have selected this option here.


In this install we will not be deploying an Edge Transport server so all we need is the Mailbox Role. You will notice that when we select the Mailbox role, the other options are grayed out. This is because you can’t have the Mailbox and Edge Transport roles on the same server. We have already installed the prerequisites so we shouldn’t need to check the automatically install Windows Server roles/features check box.


Now we need to chose the install location. Typically, I will install exchange on it’s own drive. But since this is just a lab environment, we left this as the default location on the C: drive.


I suggest that you leave the default here and allow Exchange to install malware protection. If you have a separate device that will protect your environment you can choose to remove this from the install. We will chose ‘No’ to leave it in place a continue.


Now that we have all the required info for the install, the setup will run a readiness check. Assuming that we have all the prerequisites from earlier correctly installed we should be able to continue on with the install. If any prerequisites were missed, the install will notify us here.


Now we wait for the install process to finish.


We need to restart the server after the install completes. We should now be able to open a web browser and navigate to the Exchange Admin Center. The URL for this is: https://servername/ECP. Since this is the first time we’ll log in and we haven’t configured the server to use a certificate, we can expect to get a certificate error.

Now we are ready to start configuring our new Exchange 2016 environment. The Exchange Release Notes are helpful to look up any info you might have additional questions on.

Exchange 2016 Install (Part 1)

The prerequisites:

Microsoft Exchange 2016 has recently been released to the public and I’ve finally made some time to play around with it in my test environment. To start, I thought I’d throw together a few post on the general install steps starting with the prerequisites. Exchange 2016 can only be installed on Server 2012 or Server 2012 R2 and can’t be run on the core version of the OS. The full OS install is required.

There are 2 separate roles in Exchange 2016.

  1. Mailbox Role
  2. Edge Transport Role

The Mailbox Role is the only required role needed to get an Exchange 2016 server functioning. The Edge Transport Role is an optional role that can be installed, but it can not be run on the same server as the mailbox role. It will require a separate server if used.

To install Exchange 2016 the AD schema will need to be updated. The server that will be used to preform the Schema update has two requirements. You will need to install .NET Framework 4.5.2 and the remote tools administration pack.

To install the admin pack, use the following PowerShell command:
[PS] C:Windows\system32> Install-WindowsFeature RSAT-ADDS

To install the Server 2012 prereq’s, open PowerShell as an administrator and run the following command(s).

For the Mailbox Role:
[PS] C:Windows\system32> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, 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
For the Edge Transport Role:
[PS] C:Windows\system32> Install-WindowsFeature ADLDS

Finally, you will need to download and install the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit.

Once all of the prerequisites have been successfully installed a reboot is required to proceed with the install of Exchange 2016.

Exchange 2010 Server OS Prerequisites.

When installing Exchange on a server for the first time, there are OS prerequisites that you need to install before you can move forward with the Exchange setup. Of course you can install them one at a time through the server manager or you can use PowerShell and run one command to solve all your problems and save a little time. I’m going to assume that you are installing all the standard Exchange roles on one Windows 2012 server. Microsoft recommends keeping all the roles together and not splitting them out to separate servers.

To start, we need to import the server manager module in PowerShell so it will understand the command we need to run.
[PS] C:\Windows\system32> Import-Module ServerManager
Now we’re ready to actually install the needed windows features.
[PS] C:\Windows\system32> Add-WindowsFeature NET-Framework-Features,NET-HTTP-Activation,RPC-over-HTTP-proxy,RSAT-Clustering,Web-Mgmt-Console,WAS-Process-Model,Web-Asp-Net,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-Net-Ext,Web-Request-Monitor,Web-Server,Web-Static-Content,Web-Windows-Auth,Web-WMI -Restart

The above command installs all the needed OS prerequisites to run Exchange CAS, Hub Transport, and Mailbox roles on one Server running Windows 2012. You can get a detailed list of Exchange 2010 prerequisites broken out by OS version here.

This is just a little tip to try and help you save some time while setting up your Exchange 2010 environment.