Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-03-19
You can use the Exchange Management Shell to configure routing group connectors between the default routing group in Microsoft Exchange Server 2010 and Exchange Server 2003 routing groups.
The first routing group connector between Exchange 2010 and Exchange 2003 is created and configured during installation of the first Hub Transport server role in an existing Exchange organization. Perform this procedure if you have planned your routing topology and decided to create additional connectors between Exchange versions.
|You can't use Exchange System Manager in Exchange 2003 to manage the Exchange 2010 routing group or any routing group connectors that include an Exchange 2010 Hub Transport server as either a source server or target server.|
To learn more about routing group connectors between Exchange 2010 and Exchange 2003, see Upgrade from Exchange 2003 Transport.
Suppress minor link state updates on all Exchange 2003 servers. For more information about how to suppress link state updates, see the "Link State Updates in a Coexistence Environment" section in Upgrade from Exchange 2003 Transport.
Use the Shell to create a routing group connector
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Routing group connectors" entry in the Transport Permissions topic.
|You must use the Shell to create and manage routing group connectors. They aren't shown in the EMC.|
This example creates reciprocal routing group connectors between the Exchange 2010 routing group and the routing group associated with the specified Exchange 2003 server, assigns a cost of 10 to that connector, and enables public folder referrals.
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2010Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true