GETTING STARTED WITH EXCHANGE

SERVER 2013
Exchange Server 2013 is available as a trial download so that you can
install and try it yourself.

Download Exchange Server 2013 from Microsoft

Installing Exchange Server 2013 Pre-Requisites on Windows

Server 2008 R2

Installing Exchange Server 2013 Pre-Requisites on Windows

Server 2012

How to Install Exchange Server 2013

Installing an Exchange Server 2013 Edge Transport Server

Installing Exchange Server

2013 Pre-Requisites on
Windows Server 2012 or
Windows Server 2012 R2
Exchange Server 2013 can be installed on Windows Server 2012 and
Windows Server 2012 R2, either Standard or Datacenter edition.

Windows Server 2012 will support any of the Exchange 2013 server
roles. Unlike Windows Server 2008 R2, if you want to run Exchange
Server 2013 Mailbox servers as members of a Database Availability
Group you can still do so with the Standard edition of Windows Server
2012. Enterprise edition is not required for DAG members.
Note: Exchange Server 2013 Service Pack 1 added support for
installing on Windows Server 2012 R2. For the purposes of this article
any mention of Windows Server 2012 includes R2, and assumes that
you will be installing Exchange Server 2013 SP1 or later.

As there are only two mandatory Exchange Server 2013 server

roles there are only two combinations of pre-requisites required:

Mailbox servers, or combination Mailbox and Client Access

servers

Client Access servers

Both of these server role installation scenarios are covered in this

article.

For the third server role, Edge Transport, the pre-requisites are quite
minimal. Find out more about installing Exchange 2013 Edge Transport
here.

INSTALLING PRE-REQUISITES FOR AN

EXCHANGE SERVER 2013 MAILBOX,
OR MAILBOX AND CLIENT ACCESS
SERVER
For a Windows Server 2012 server that will host either the Exchange
2013 Mailbox server role, or both the Mailbox and Client Access server
roles, the following PowerShell commands is used to install the
required server roles and features.

Note: the Add-WindowsFeature command is quite lengthy and you will

need to scroll across to be able to copy/paste all of it.

PS C:\> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,

NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-
Clustering-CmdInterface, 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, RSAT-ADDS

Success Restart Needed Exit Code Feature Result

------- -------------- --------- --------------

True Yes SuccessRest... {Application Server, HTTP

Activation, .NET...

WARNING: You must restart this server to finish the installation process.

A restart is required after the roles and features have finished

installing. To restart automatically, append -Restart to the command
above.

Next, install the Unified Communications Managed API 4.0 Runtime.

Some documentation also references installing Microsoft Office 2010

Filter Pack 64 bit and Microsoft Office 2010 Filter Pack SP1 64 bit.
Neither of those components are mandatory, however if you do not
install them youll see a warning during setup (that you can ignore). For
more information refer to this article.

INSTALLING PRE-REQUISITES FOR AN

EXCHANGE SERVER 2013 CLIENT
ACCESS SERVER
For a Windows Server 2012 server that will host only the Exchange
2013 Client Access server role, the following PowerShell command is
used to install the required roles and features.

Note: the Add-WindowsFeature command is quite lengthy and you will

need to scroll across to be able to copy/paste all of it.

PS C:\> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,

NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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

Success Restart Needed Exit Code Feature Result

------- -------------- --------- --------------

True Yes SuccessRest... {Application Server, HTTP

Activation, .NET...

WARNING: You must restart this server to finish the installation process.

A restart is required after the roles and features have finished

installing.

Next, install the following software. This is the same requirement as the
Mailbox server role just without the Office Filter Pack.

Unified Communications Managed API 4.0 Runtime

The server is now ready for the installation of Exchange Server 2013.

How to Install Exchange

Server 2013
Deployment of an Exchange Server 2013 server goes through three
main stages.

1. Preparing Active Directory (if you are installing Exchange Server

2013 for the first time)

2. Installing the Exchange Server 2013 pre-requisites on the server

3. Running Exchange Server 2013 setup

PREPARING ACTIVE DIRECTORY FOR

EXCHANGE SERVER 2013
When you are installing Exchange Server 2013 for the first time the
Active Directory needs to be prepared.

There are a series of requirements for Active Directory preparation to

be successful:

Schema master running Windows Server 2003 with SP2, or a

later version of Windows Server

At least one Global catalog server per site that Exchange will be
installed in that is running Windows Server 2003 SP2 or later

At least one Domain controller per site that Exchange will be

installed in that is running Windows Server 2003 SP2 or later

Forest functional mode of Windows Server 2003 or higher

An account with Schema Admins, Domain Admins, and

Enterprise Admins permissions to run Exchange setup

Although Active Directory preparation can occur as part of the

installation of the first Exchange Server 2013 server, you can also run
the Active Directory preparation as a separate task beforehand on a
64-bit server running Windows Server 2008 or higher.

Because the Active Directory preparation requires the RSAT-ADDS

tools I am running it on the domain controller in my test lab.

Alternatively, you can install the tools on a member server to run

Exchange 2013 Active Directory preparation.

For Windows Server 2008 R2 (SP1 or later), in PowerShell run:

Import-Module ServerManager

Add-WindowsFeature RSAT-ADDS

For Windows Server 2012, in PowerShell run:

Install-WindowsFeature RSAT-ADDS

If you are installing Exchange Server in the AD forest for the first time
run the following Exchange 2013 setup command to prepare Active
Directory:

setup /PrepareAD /OrganizationName:"your organization name"

/IAcceptExchangeServerLicenseTerms

Note: if your organization name contains spaces then it must be

enclosed in quotes as shown above.

If an Exchange organization already exists you can omit the

/OrganizationName parameter.

setup /PrepareAD /IAcceptExchangeServerLicenseTerms

For other Active Directory preparation scenarios, such as multiple

forests or multiple domains, refer to this article on TechNet.

INSTALLING EXCHANGE SERVER 2013

USING THE SETUP WIZARD
After installing the pre-requisites a restart of the server may be
required. If you proceed without restarting then setup may be unable to
proceed when it detects the pending restart.

From the location where you have stored your Exchange 2013 files run
Setup.exe.

The first dialog gives you the opportunity to check for updates to the
setup files before you proceed.
Check for updates to Exchange 2013 setup files

After the setup files have updated click Next to continue.

Click Next to continue past the Introduction message.

Exchange 2013 setup introduction

Accept the license agreement and click Next to continue.

Exchange 2013 license agreement

Choose whether or not to enable Error Reporting and click Next to

continue.

Configure Exchange 2013 error reporting

After a check that all the pre-requisites are installed the setup wizard
will move on to the next step automatically (if the check was
successful).

Now we can choose the server roles to install. If this is the first server
youre installing Microsoft recommends you install the Mailbox server
role first (this can be either a Mailbox-only server or a combined
Mailbox/Client Access server).

Choose the Exchange 2013 server roles to install

Verify that you have enough disk space for the installation, or choose a
path that does have enough disk space, and click Nextto continue.

Choose the location to install Exchange 2013

If there is no existing Exchange organization in Active Directory, and

you havent already prepared Active Directory for Exchange, you will
be prompted to enter an Exchange organization name.
When installing the Mailbox server role you are given the option to
disable malware protection. If you disable it now you can enable it
again later.

Configure anti-malware protection for the Mailbox server

Some readiness checks are performed. If this is the not the first server
youre installing and there is no Send Connector defined for outbound
email then you may see a warning, but you can still proceed with the
server installation.

Setup cant detect a Send connector with an address space of *. Mail

flow to the Internet may not work properly.

Exchange 2013 setup pre-requisite warning

When you are ready to proceed you can click Install to begin.
Begin the installation of Exchange 2013

The install is a fairly lengthy process, so you may want to go and do

something else while you wait. When setup has finished click Finish.

Exchange 2013 setup is finished