This is the second part of a two part series on Microsoft Exchange 2010.

In the first article we examined the changes and

enhancements in Exchange 2010. This time we'll walk through the steps required to install a fully functional Exchange 2010 server on
Windows Server 2008 R2.

System Requirements
First, you need to make sure that your Active Directory (AD) environment and your Exchange server meet the minimum requirements:

AD forest functional level is Windows Server 2003 (or higher)

AD Schema Master is running Windows Server 2003 w/SP1 or later
Full installation of Windows Server 2008 w/SP2 or later OR Windows Server 2008 R2 for the Exchange server itself
Exchange server is joined to the domain (except for the Edge Transport server role)

Prerequisites
In this example we are going to install Exchange 2010 on a Windows Server 2008 R2 operating system. Before installing Exchange we
need to install some Windows components. It's important that you don't miss anything here because the Exchange 2010 installer does
not provide very good feedback if Server 2008 R2 is missing required components.
1.
2.
1.
2.
3.

Install the 2007 Office System Converter: Microsoft Filter Pack

Add the appropriate Windows components/features
Open PowerShell via the icon on the task bar or Start >> All Programs >> Accessories >> Windows PowerShell
>> Windows PowerShell. Be sure that PowerShell opened with an account that has rights to install Windows
components/features.
Run the following command: Import-Module ServerManager
For a typical install with the Client Access, Hub Transport, and Mailbox roles run the following command: Add-

WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,WebMetabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,WebDigest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart. For a full matrix of the

3.
1.
2.

required Windows components with regards to the Exchange server roles see: http://technet.microsoft.com/enus/library/bb691354.aspx#WS08R2
If your Exchange server will have the Client Access Server role set the Net.Tcp Port Sharing Service to start automatically
Open PowerShell via the icon on the task bar or Start >> All Programs >> Accessories >> Windows PowerShell
>> Windows PowerShell. Be sure that PowerShell opened with an account that has rights to modify service startup settings.
Run the following command: Set-Service NetTcpPortSharing -StartupType Automatic

Exchange 2010 Installation

Now we're ready to run the Exchange 2010 installer. We'll go through a typical installation that includes the Client Access, Hub
Transport, and Mailbox roles. This is what you will want to install if you are only going to be running one Exchange server. If you scale

out your Exchange architecture with multiple servers then you will want to familiarize yourself with the Exchange server roles for a
proper deployment.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

Logon to the desktop of your soon to be Exchange server with a Domain Admin account.
Run setup from the Exchange 2010 media.
Click on "Step 3: Choose Exchange language option" and choose one of the options (Install only languages from the DVD
will be fine in most cases).
Click on "Step 4: Install Microsoft Exchange."
Click Next at the Introduction page.
Accept the license terms and click Next.
Make a selection on the Error Reporting page and click Next.
Stick with the default "Typical Exchange Server Installation" and click Next.
Choose a name for your Exchange Organization and click Next.
Make a selection on the Client Settings page and click Next.
If you want your Exchange server to be available externally then choose a domain name such as mail.myorganization.com,
click Next.
Make a selection on the Customer Experience Improvement Program page and click Next.
If all the prerequisites are there then you can click Install.
Grab a cup of coffee or take a walk while the installation process does its thing.
When the installation has finished go back to the Exchange installation page click on "Step 5: Get critical updates for
Microsoft Exchange."
Install Microsoft Update (if necessary) so that Windows update will check for non-OS updates, and verify that there are no
Exchange updates.

EDIT: This is one of my most popular posts, if you find it useful please comment or share
the post. Thanks.
Now Microsoft Exchange 2010 SP3 has been released it provides support for Windows Server
2012 as the host operating system. In this blog well run through the installation process.
The demo environment I am using includes a Server 2012 DC and a Server 2012 member
server.
As this is a virgin demo environment as part of the installation the Exchange 2010 setup will
upgrade the AD Schema, if this is an additional server in a migration scenario then the following
wont be necessary. To upgrade the Schema you have two options.
Option 1: Run the Exchange 2010 SP3 setup command with
the PrepareAD and OrganizationNameswitches on the domain controller.
setup /preparead /organizationName:oxfordsbsguy
Then on the member server follow the instructions below to install Exchange 2010 SP3.

Option 2: Install the Remote Server Administration Tools (RSAT) onto the member server you
are installing Exchange onto so that the ldifde.exe is in the correct location that the Exchange
setup expects it to be.

With that done, on to the install.

1. On a Server 2012 member server, run PowerShell as Administrator.

2. Run the following command to install the prerequisite Rolls

required for a typical Exchange 2010 installation. (Source: Exchange 2010 Prerequisites)

3. Wait for the rolls to be completed. On my test server this took about 4 minutes. The server will
restart automatically.

4. Download Microsoft Exchange 2010 SP3, Microsoft Office 2010 Filter Pack, and Microsoft
Office 2010 Filter Pack SP1

5. Install the Microsoft Office 2010 Filter Pack.

6. Install the Microsoft Office 2010 Filter Pack SP1.

7. Run and extract Exchange 2010 SP3.

8. Browse to the location you extracted the files to and run Setup.exe, then click on Step 4:
Install Microsoft Exchange.

9. Read the introduction and click Next.

10. Accept the license agreement, and click Next.

11. Enable Exchange Error Reporting, and click Next.

12. Select the Installation Type. In our example we will use the Typical
Option, deselectAutomatically install Windows Server roles and features required for
Exchange, click Next.

13. Enter the Organization Name, Ive changed mine from the default First Organization in the
picture below to OxfordSBSGuy.

14. Select the appropriate client settings, click Next.

15. Enter an external domain name to use with Exchange, click Next.

16. Opt in/out of the Customer Experience Improvement Program, click Next.

17. Resolve any errors, you should have none! Note Organization Prerequisites, this refers to the
Schema upgrade highlighted at the start of this article. Click Next.

18. Watch the progress bars (or go and make a cuppa) as Exchange is installed. You can see it if
fairly quick at just under 20 minutes. Click Finish to complete the installation.

19. Run WSUS or Windows update to install any patches that have been release since SP3.
20. Reboot the server to complete the installation.
21. Once restarted log in to the Exchange Management Console and start configuring!

Related Posts:
1. How to install Exchange 2013 (SP1) on Windows Server 2012 R2
2. Exchange PowerShell: How to find users hidden from the Global Address List
3. Exchange Server and Update Rollups Build Numbers
4. How to check which version of Microsoft Exchange you are using?
5.