Instalacion Exchange Server 2016


Exchange Server 2016 can be installed on Windows Server 2012 and Windows Server 2012 R2. For both versions of Windows Server either the Standard or Datacenter edition can be used to run Exchange Server 2016. Exchange itself does not rely on any specific features of either the Standard or Datacenter editions.

Note that a full server installation with GUI is required for Exchange Server 2016, it can’t be installed on a Core mode installation of Windows Server.

There are three possible installations of Exchange Server 2016 that you can perform:

  • Mailbox server role (this is the only mandatory server role)
  • Edge Transport server role (this is optional, and can’t co-exist with the Mailbox server role on the same Windows Server)
  • Management Tools (for admin workstations or servers)

The requirements for each installation type are different, so let’s look at each of them in turn.

Installing pre-requisites for an exchange server 2016 mailbox server

For an Exchange Server 2016 Mailbox server installation open an elevated (run as administrator) PowerShell console and run the following command to install the operating system roles and features.

A restart is required after the roles and features have finished installing. If you’d prefer that the server restarts itself automatically simply append -Restart to the command.

After the restart download and install (in order):

The server is now ready to install Exchange Server 2016.

Installing pre-requisites for an exchange server 2016 edge transport server

For an Exchange Server 2016 Edge Transport server the pre-requisites installation is a little simpler than for a Mailbox server. Open an elevated PowerShell console and run the following command.

When that has completed download and install (in order):

The server is now ready to install the Exchange Server 2016 Edge Transport role.

Installing pre-requisites for the exchange server 2016 management tools

Exchange Server 2016 uses a web-based administrative interface called the Exchange Admin Center, similar to Exchange Server 2013. There is nothing required to be installed on a workstation or server other than a web browser to access the Exchange Admin Center.

However if you want the Exchange Management Shell to be installed on a management workstation or server (Windows Server 2012 R2 or Windows 8.1) then the only pre-requisite is to install .NET Framework 4.5.2. After the .NET Framework is installed you can install the Exchange Server 2016 management tools.

Installing Exchange Server 2016

After you’ve prepared a Windows Server with the Exchange Server 2016 pre-requisites you can proceed with the installation of Exchange Server itself.

In this tutorial we’ll cover:

  • Preparing Active Directory for Exchange Server 2016 installation
  • Installing the Exchange Server 2016 Mailbox server role on a new server

Before you start there are a few things to be aware of:

  • Installing Exchange Server 2016 requires an Active Directory schema update. We’ll look at that in more detail shortly.
  • Aside from the schema update installing Exchange Server 2016 makes other irreversible changes to your Active Directory forest. If you’ve never backed up your Active Directory, or you’ve never heard of a forest recovery, here’s some reading for you.
  • If you’re installing Exchange into the forest for the first time you will be choosing an organization name. The Exchange organization can’t be renamed at a later date, so choose a name you’re happy with keeping forever.

Preparing active directory

A new installation of Exchange Server 2016 involves applying an Active Directory schema update, as do most Exchange Server cumulative updates, as well as preparing the Active Directory domains where Exchange Server 2016 and any mail-enabled objects will be located. In an Active Directory forest with a single domain this can all be performed as one task.

The Active Directory schema update will automatically apply when you run Exchange Server 2016 setup on the first server in your environment. A Windows Server 2012 R2 server with the Exchange Server 2016 Mailbox server role pre-requisites installed doesn’t quite meet the requirements (you’ll need to add the RSAT-ADDS feature as shown below). A domain controller will have RSAT-ADDS installed already, but may also need the .NET Framework version shown below to be installed first.

Whether you’re running the schema update from an Exchange server or a separate server (some organizations do it as a separate task due to change control reasons, or because of different teams having different administrative responsibilities in the environment) then the following requirements apply:

  • The forest functional level must be at least Windows Server 2008
  • The account used to run the schema update and Active Directory preparation must be a member of Enterprise Admins and Schema Admins. These are high privilege groups I recommend you plan to remove your account from the groups when you’re done with this task. Note, if you’ve just added yourself to these groups you’ll need to log out and back in to the server for the new group membership to take effect.
  • The server you’re running the schema update from must be located in the same Active Directory site as the Schema Master. You can identify your Schema Master by running my Get-ADInfo.ps1 script, or by using the Get-ADForest PowerShell cmdlet.
    • (Get-ADForest).SchemaMaster

Now we’re ready to run the Active Directory schema update and and preparation.

If you’ve already got Exchange Server running in your environment you can check the current Exchange schema version before applying the update, so that you can see what the before and after version numbers are.

In PowerShell run the following one-liner created by Exchange Server MVP Michael B Smith:

  • C:\> “Exchange Schema Version = ” + ([ADSI](“LDAP://CN=ms-Exch-Schema-Version-Pt,” + ([ADSI]”LDAP://RootDSE”).schemaNamingContext)).rangeUpper

    Exchange Schema Version = 15317

Note, in my example above there is no existing Exchange server installed, hence no Exchange schema version to report.

Extract the Exchange Server 2016 setup files into a folder, open a command prompt window, and then navigate to the location where the Exchange setup files were extracted.

To apply only the schema update run the following command:

  • setup /PrepareSchema /IAcceptExchangeServerLicenseTerms

After applying the schema update we can check the version number again.

  • C:\> “Exchange Schema Version = ” + ([ADSI](“LDAP://CN=ms-Exch-Schema-Version-Pt,” + ([ADSI]”LDAP://RootDSE”).schemaNamingContext)).rangeUpper

    Exchange Schema Version = 15317

02.-To prepare Active Directory run one of the following commands. Note this will also apply the schema update if you did not perform that step already.

If you do not already have an Exchange organization you’ll need to provide a name for the organization now, for example:

  • setup /PrepareAD /OrganizationName:”Exchange Lab” /IAcceptExchangeServerLicenseTerms

If you’re installing Exchange Server 2016 into an existing Exchange organization you do not need to specify the organization name, for example:

  • setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Remember, you can’t change the Exchange organization name later, so choose a name you’ll be happy to live with forever. Also, after installing Exchange Server 2016 as a new organization you will not be able to install any earlier versions of Exchange into the same organization.

If you have additional domains in your forest that you need to prepare (any domain that will host an Exchange server or mail-enabled objects) follow the guidance on TechNet here.

Installing the exchange server 2016 mailbox server role

The mailbox server role contains all of the components required to run an exchange server 2016 server. There is also an edge transport role, but that is not a mandatory role and is not covered in this tutorial.

After installing the exchange server 2016 pre-requisites on a server you can install the exchange server 2016 mailbox server role by running the following command from an elevated command prompt.

  • setup /mode:install /role:mailbox /iacceptexchangeserverlicenseterms


Installing Exchange Server 2016 into an Existing Organization

Exchange Server 2016 can be installed into an existing Exchange organization as long as it meets the system requirements. This includes:

You can have a combination of Exchange 2010 and 2013 servers in the organization as long as they each meet those minimum versions.

If you have Edge Transport servers or legacy server objects that were not properly removed from Active Directory you may encounter a setup error when you first try to install Exchange Server 2016. You can find more details about this, and the solutions, at the following article:

In your Active Directory environment the following requirements exist:

  • All domain controllers must be running at least Windows Server 2008
  • The forest functional level must be at least Windows Server 2008 (steps here)

The system requirements for Exchange Server 2016 may change over time so always be sure to check TechNet for the latest information.

When you have your environment ready you can:

When you’re running Exchange setup note that:

  • You do not need to provide an organization name when you’re installing into an existing organization
  • There is Active Directory preparation performed automatically by setup when you install the first Exchange 2016 server. If you’d prefer to handle those steps separately you can do so (the steps are broken out separately in this article)

After Exchange Server 2016 has been installed you should, at minimum, configure the Autodiscover namespace to avoid certificate warnings appearing for Outlook clients in your environment. You can then proceed with the rest of your Exchange Server 2016 configuration, such as:

In an upcoming article I’ll explore further how you can start to add the Exchange 2016 server into your production environment

Be the first to comment

Leave a Reply