Friday, May 10, 2013

Exchange 2010 - migration from 2007 - Hub Transport - configuration

Here are a number of elements to take into consideration concerning Hub Transport settings.

Send Connector

Although Send-Connector properties exist at the Organizational Level (versus Server Level) and are stored in the configuration partition of Active Directory, it is necessary to modify one Send-Connector setting manually.
I noticed that users whose mailbox was moved to the E2K10 server could not send to external recipients. This was because the E2K10 server must be listed as one of the source servers in the Send-Connector properties. In the EMC, this can be configured under the "Source Server" tab.


In the EMS, this is what displays before the E2K10 server is added to the list of source servers:

Get-SendConnector | fl sourcetransportservers

SourceTransportServers : {ex1}

This is the cmdlet that will add the E2K10 server to the list:

Set-SendConnector -Identity 'MYNET-SendConn-1' -SourceTransportServers 'ex1','EX10C'

Now both servers are in the list:

Get-SendConnector | fl sourcetransportservers

SourceTransportServers : {EX10C, ex1}

Receive Connector

In Exchange 2010, by default, the default Receive-Connector will refuse messages from anonymous senders. Since most or all users outside the Exchange organization qualify as "anonymous", this setting must be modified if we want users to receive mail from external or outside senders.

Let's compare the Receive Connector settings on the E2K7 and the E2K10 servers:

Exchange 2007 server

Get-ReceiveConnector "ex1\Default EX1" | fl *permission*

PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers

Exchange 2010 server

Get-ReceiveConnector "Ex10C\Default EX10C" | fl *permission*

PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers

In the EMC, we would see this:

The E2K10 server lacks the "AnonymousUsers" permission group. We can correct this with the following command:

Set-ReceiveConnector "EX10C\Default EX10C" -PermissionGroups "AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers"

Now the E2K10 server has the correct Receive-Connector permissions:

Get-ReceiveConnector "Ex10C\Default EX10C" | fl *permission*

PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers


  1. This comment has been removed by the author.

  2. Helpful article, I found the good resource from that provides the automate facilitate to intra-forest exchange and cross-forest exchange migration and apply real-time synchronization between two Exchange Servers in order to maintain coexistence and allows migration from any Exchange Server to Office 365.