Step by Step guide on how to install Exchange Server 2010

Step by Step guide on how to install Exchange Server 2010- Part 1: Install


It has been a long time since; I wrote an article or a tutorial for any

Microsoft products. I noticed that exchange 2010 is out so why not give

a try and check out the new features included.

I will be using a complete copy of exchange 2010 from MSDN Library

for my tutorial. Please get your own copy or download an evaluation

copy from Microsoft at:

ok, so pull up your chair, get your cup of coffee and let`s have fun 🙂

The Lab

Below is the Exchange Server 2010 Lab setup; all the servers are

virtualized using VMWARE.

1. A windows 2008 R2 Domain controller with all FSMO Roles

installed, including certificate server (DC01), this will be my

domain controller and will not host any exchange services. It is

not recommended to install exchange on a domain controller per

Microsoft specifications.

2. Windows Domain :

3. A windows 2008 R2 server with exchange recommended

requirements (Exch01)

4. This server will hold all roles.

All Exchange and windows 2008 requirements can be found at:

This is a simple virtualized Lab, on an actual production environment

you may have different roles installed and you may need a separate

server for each role depending on designed infrastructure.


Before installing an Exchange Server 2010, there are prerequisites to be

installed in all the servers.

1. Net Framework3.5

2. Power shell 2.0 CTP 3

3. Windows Remote Management

4. IIS server with required features

The first three components must be installed regardless of which role

you will install. These requirements can be added easily using server

manager on windows 2008.

In addition, before you begin your Exchange 2010 install, be aware of

the following:

• For e-mail messages to flow correctly, you must install both the

Mailbox server role and the Hub Transport server role in the same

Active Directory site.

• You can install the Mailbox server role, the Hub Transport server

role, the Client Access server role, and the Unified Messaging

server role on the same computer or on separate computers.

Step by Step:

ok let` s take care of requirements first :

1. Prepare the forest and organizat ion in Act ive Directory

First we need to prepare our Schema. Since this is a new setup and not

an upgrade or migration, I will perform the preparation on the domain

controller in My Case: DC01

As we are preparing active directory schema we need Schema admin

rights. The account running the preparation must be a member of

schema admins group on active directory.

Open a command prompt on the domain controller with elevated

privilege (Run as command).

Run Setup from the directory where your Exchange 2010 installation

files are located. Here is the cmdlets

Setup / PrepareSchema or Setup / ps

And here is the screenshot showing that preparation was complete on

my domain controller.

We can install Exchange 2010 directly from the command line, we really

don`t need to use GUI Interface for install. But for now let`s install

requirements using command line then finish with the fancy setup

interface for the sake of simplicity.

Now on the server that will host exchange server, in my case


We need a number of pre-requisites for Windows 2008 SP2 before we

can successfully start the setup.

To install the following components:

• .Net Framework 3.5 SP1, from here, you can also run from

command line

◦ servercmd –I NET-FRAMEWORK

• WinRM & Powershell v2, from here

• Office 2007 Syetem Convertor – Microsoft Filter Pack, from here

If you are installing CAS role, run sc config NetTcpPortSharing

start=autoto change the startup type of NetTcpPortSharing service. You

can do the same graphically from the services snap-in as well.

Exchange 2010 Install Media comes with xml files which have all prerequisite

information for different 2010 server roles. Navigate to the

Scripts folder within the 2010 installation media using an elevated

command prompt and you will see a list of xml files provided by the

Exchange team to install the necessary pre-requisites.

For example, I am doing a typical installation (Mailbox, CAS and HUB on

the same box), so I need to use the Exchange-Typical.xml file . Run

the following command,

ServerManagerCmd –ip “x:\scripts\Exchange-Typical.xml” –Restart

(where “X” as the drive with the 2010 media) or navigate to the Scripts

folder and run

ServerManagerCmd –ip Exchange-Typical.xml –Restart

For CAS role alone, run sc config NetTcpPortSharing start=auto and

SevrerManagerCmd –ip Exchange-CAS.xml –Restart

For HUB role alone, run ServerManagerCmd –ip Exchange-Hub.xml –


For Mailbox role alone, run ServermanagerCmd –ip Exchange-MBX.xml


For UM role alone, run ServerManagerCmd –ip Exchange-UM.xml –


For Edge role alone, run ServerManagerCmd ip Exchange-Edge.xml –


I f you get to this part then you are done with prerequisites, let` s

start our install.

Run setup.exe from you installation folder or CD, an install menu will


As you can see .Net framework 3.5 and windows power shell are already

installed, so the option is grayed out. If they are not installed you can

still install them here.

Choose your Exchange 2010 language bundle; in my case I selected all

languages from DVD.

Now select Step 4: I nstall Microsoft Exchange

Click next and accept the Terms in the license agreement, well you

know what happens if you don`tJ.

Click next and choose to either participate in Error reporting or no.

Click Next and Select Typical Exchange Server I nstallation.

Ok let me explain: some exchange roles cannot co-exist on the same

server, for example Edge Transport and unified Messaging Role. If you

need these roles you have to select “Custom Exchange Server

Installation”. Notice that if you choose “Edge Transport” or “Unified

Messaging Role” you will not be able to install other roles on same

server and vice versa.

In my case I will not be installing unified messaging or edge transport.

These roles require more customization and can be added anytime after

first install, I will be skipping them for now.

Click next and Rename “First Organization” to your organization name. I

will rename this to “New York” as I like to name my organization unit

according to location.

Now Click next, and choose if you need to enable Public Folders or no.

In earlier versions of Exchange, we used to have those nice public


On exchange 2007 and 2010 we can install exchange without public

folder database. For more info about public folders and reason why it

was omitted on latest versions of exchange, check:

ht tp:/ / technet .microsoft .com/ en-us/ library/ bb397221.aspx

For my case I won`t be using Public Folders so I selected No confirming

that I do not have any outlook 2003 clients. Notice, I can still add public

folders after install.

Now Click next and enter your Public Client Access server address, this

is the address that all external users will use to access Outlook web

access, active sync etc.

I have split DNS in my infrastructure, so I will be using


Confirm your FQDM and hit next

Choose if you would like to join Customer I mprovement Program, I

selected No for that option

Now Click Next to start the Install

Exchange setup will run readiness check and verify that it is ready for


If all is ok you will get a confirmation like the one below, if you are

missing something exchange setup will let you know.

The yellow warning in my case is indicating that setup will run

setup / preparead for me.

You can run this before running exchange setup; I prefer running it with

the GUI interface.

If exchange readiness check is ok, Install Button will be enabled.

If you are missing something exchange setup will not continue and will

prompt to you to install missing requirements with a retry button


If you get a screen like the one above you are good to go. Hit Install

and go enjoy your coffee as this may take few minutes.

And here you go install is complete.

This was a simple step by step install for a single server running all roles

except unified messaging and Edge Transport role. Exchange setup is

still a complicated task. If you are installing in a production

environment, this may involve designing and planning your exchange

infrastructure before implementing any roles. In some cases you may

have a migration from earlier versions of exchange; you may have to do

a migration from other mail servers. All these cases involve more

design, planning and time. This is beyond the topic of this tutorial, I will

try and cover configuration of exchange in future Tutorials.

I hope you found this article informative for you and thank you for


This entry was posted in Guides. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *

You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


Powered by WP Robot

Show Buttons
Hide Buttons