By now you should have a working Exchange 2010 Client Access server. However, an Exchange 2010 environment needs at least two more server roles installed: the Hub Transport Server Role and the Mailbox Server Role. It doesn’t matter if you are going to deploy these roles on the same server as the Client Access Server Role or if you choose a different server; the procedure is nearly the same. Because installing the three roles on the same server might lead to performance issues, however, Microsoft recommends to not combine the Mailbox Server Role with any other role on the same server. In small environments, performance shouldn’t drop when you run all of them on the same server, even if the server is virtualized.

Let’s start with the Hub Transport Server Role. The installation process will differ slightly if you install this role together with the Client Access Server Role or on a standalone system. If you do the latter, you should install the prerequisites before you launch the setup wizard. The fastest way to achieve this is by typing these PowerShell commands:

Import-Module ServerManager

   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 –Restart

Now you can launch the setup wizard. First, you have to choose the language; choose the same option you chose when installing the Client Access Server Role. Proceed to the next step and install the Exchange server. If you started the installation routine on an Exchange server where other roles are installed, the routine will tell you that Exchange is going into maintenance mode. On a bare system, you have to click through a few dialogs until you reach the Server Role Selection page. Here, choose the Hub Transport and click Next. The next steps are the same as when you installed the Client Access server, except that the Client Access-specific dialogs do not show up and one Hub Transport-specific dialog is displayed. This dialog, called Mail Flow Settings, is where you will choose the legacy server to which the Exchange 2010 server will connect.

After the installation finishes, open the Exchange Management Console and navigate to Server Configuration -> Hub Transport. Under Receive Connectors, you will find a default receive rule that is automatically generated during the installation to ensure that e-mails can be exchanged between the legacy server and the Exchange 2010 Hub Transport server. Although everything should already be configured, you should manually check these settings.

By default, no send connector exists. To create one, navigate to Organization Configuration -> Hub Transport, right-click in the result pane to open the context menu, and choose New Send Connector. This opens the New Send Connector wizard, where you should choose a meaningful name for the connector and select Internet as the intended use for this connector. You’ll define the address space in the next window. Usually you want to route your external mail traffic to one relay, so you should type a * here. Don’t change the Type and Cost settings. The next step, called Network Settings, is where you will choose the server to which outgoing messages are sent. The default setting (using DNS to route outgoing mail traffic) is the right one unless your company has a mail relay that works as a smart host. In the last dialog, you can add other Hub Transport servers to this send connector, but you shouldn’t have one at the moment. Finalize the wizard by clicking the Next and New buttons. Now your Exchange 2010 environment is ready to deliver mail to your legacy Exchange server and to every other mail server on the Internet.

Subscribe to 4sysops newsletter!

Before you start installing the Mailbox Server Role, you should delete the Exchange 2003 SMTP connector. I recommend verifying that the message flow of the Exchange 2010 server works as intended before you delete the SMTP connector. In my next post, I will talk about the deployment of the Mailbox Server Role, which is the only required role that is still needed for a working Exchange 2010 environment.

1 Comment
  1. upendra 9 years ago

    Hi , it is helpful to configuring in hub transport rule.

Leave a reply

Please enclose code in pre tags

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

*

© 4sysops 2006 - 2022

CONTACT US

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

Sending

Log in with your credentials

or    

Forgot your details?

Create Account