Exchange 2003 to Exchange 2010 migration – Deploy Exchange 2010 Client Access role

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,
        Web-Windows-Auth,Web-Metabase,Web-Net-Ext,
        Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,
        Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,
        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, mail.contoso.com) 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.

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.