After you prepare the active directory and determine the hardware resources, you can start deploying Exchange 2010. The first role you have to deploy is the Client Access role. Before you can run the Exchange server’s setup routine, you must install the following software: .NET Framework 3.5 SP1, PowerShell 2.0, WinRM 2.0, and IIS 7.0.

You also have to install a few server roles and features. You can do this via the Server Manager interface, or you can use this PowerShell command:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,
        NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart

You must also set the .NET TCP Port Sharing Service to automatic. Just copy and paste this command to the PowerShell command line:

Set-Service NetTcpPortSharing -StartupType Automatic

Now that the prerequisites are installed, you are ready to run the Exchange 2010 setup. It is easier to use the GUI for this installation step. When you insert the installation media, the setup wizard should launch automatically; if not, manually launch setup.exe on the installation media.

When the wizard starts, you’ll see five steps listed under the heading Install. The first and second ones are grayed out because, assuming you followed this guide, you have already completed these steps. To complete Step 3, you have to choose the languages you want to install. If you don’t have any exotic language requirements it is sufficient to use only the languages delivered with the DVD.

The installation routine starts when you click on the next step. After the introduction screen, you have to accept the License Agreement. If desired, you can also disable the sending of error reports to Microsoft. On the next page you have the option to make a typical or custom Exchange installation; choose “custom” here.

Now it gets interesting because you can select which Server Roles you want to install. At first you only need the Client Access Role, so check the appropriate box. You’ll see that the Management Tools are selected automatically. The Edge Server Role is grayed out because this role can’t coexist with any other Server Role.

When you click the Next button, you will be asked if the Client Access server is Internet facing. If you want to use Outlook Web Access, Outlook Anywhere, or ActiveSync outside of your company’s network, you will have to make the Client Access server Internet facing. You will also have to provide a namespace (for example, under which your users can access Exchange 2010 from the Internet. If the namespace you plan to use for Exchange 2010 is already taken by your previous Exchange server, you will have to change the namespace of the legacy Exchange server later. Entering your productive namespace will also make some Exchange services, such as ActiveSync, unavailable for your users until you fix some things. I will talk about that in another post, so if you want to use your existing namespace it is a good idea to read the post before you continue.

Subscribe to 4sysops newsletter!

After you enter the domain name, click Next. The installation routine automatically starts the Readiness Checks. As long as you followed this post you should not run into any problems. However, if any errors occur, the setup wizard gives a helpful description of the problem and its solution. After every check completes successfully, proceed to the next page. The setup wizard begins copying the files to the hard disk and configuring the Exchange 2010 environment. After a few minutes, the installation of the Client Access Role is completed.

  1. NAvin 11 years ago

    Thanks Alex, that was really helpful tute.

  2. Dean 11 years ago

    I am afraid that you will confuse some people, Alexander.

    What OS are you installing Exchange 2010 on - Windows Server 2008 or Windows Server 2008 R2?

    You should run the command "Import-Module ServerManager" before you use Add-WindowsFeatue, when you are installing Exchange 2010 on R2. On the Windows 2008 OS you can use the scripts provided by Microsoft for the different scenarios.

    How about Exchange 2010 SP1? It is a standalone installation - you don't have to install Exchange 2010 and then apply SP1, and it brings a huge amount of new features.

    One of the changes which you notice immediately it the installation process itself - it can install automatically the required features, based on the selected type of Exchange 2010SP1 installation (typical or custom).

    Why would you install Exchange 2010 now, and then have to install SP1 which despite of its name is more like a new release?


  3. Author
    Alexander Weiß 11 years ago

    Yes, you have to run the Import-Module ServerManager before you can use the ADD-WindowsFeature cmdlet. Thanks for reporting Dean.

    The reason why I don't write about Exchange 2010 SP1 is that I started to write the Exchange 2010 migration series way before the SP1 was available. I also recommend to install Exchange Server 2010 with SP1, but allmost any topic I cover here is identical for Exchange 2010 or Exchange 2010 SP1.

  4. AD-QE 11 years ago

    Hi Alexander,

    Many thanks for your post - very informative!

    I am hoping for some advice: I have never worked on exchange 2010 before, and have just been given a job at a new company that is migrating from 2003 to 2010 (the last person left without leaving any documentation!). He had already installed their Exchange 2010 server, and I think that all I need to do is make the 2010 server the main mail server, and start moving mail boxes across from the Exchange 2003 server to the Exchange 2010. How do I do this, so that all of the mailboxes that are still on 2003 can receive mails in the meantime? I don't even know what to do to configure the firewalls! can you help me?

    Thank you!

  5. Author
    Alexander Weiß 11 years ago

    If Exchange 2010 is running and every role is installed it should be the main hub already, because the installation routine automatically configures the Exchange 2010 server this way. The only things you have to configure manually are the connectors.
    On the firewall you just have to open the ports to your Exchange 2010 server. If you already have rules for Exchange 2003 just add the Exchange 2010 server to these rules.
    I hope that this short explanation is helpful.

Leave a reply

Please enclose code in pre tags

Your email address will not be published. Required fields are marked *


© 4sysops 2006 - 2022


Please ask IT administration questions in the forums. Any other messages are welcome.


Log in with your credentials


Forgot your details?

Create Account