10. Connecting to Exchange 2003 Routing Groups
Although Exchange 2010 doesn't use routing groups, you must create
routing group connectors to route messages between Exchange Server 2010
Hub Transport servers and Exchange Server 2003 routing groups. You can manage routing group connectors only by using the Exchange Management Shell.
You can view, create, update, or remove routing group connectors using the Get-RoutingGroupConnector, New-RoutingGroupConnector, Set-RoutingGroupConnector, or Remove-RoutingGroupConnector
cmdlet, respectively. With Get-RoutingGroupConnector, you can return a
list of all available routing group connectors if you don't specify an
identity or server. If you want to see only the routing group
connectors configured on a particular server, use the –Server parameter.
When you are creating or updating a routing group connector using
New-RoutingGroupConnector or Set-RoutingGroupConnector, you specify
source and target servers. The source and target servers must be
Exchange 2010 Hub Transport servers or Exchange Server 2003 bridgehead
servers. By using the –Bidirectional parameter, you can specify whether
the connector is used for one-way or two-way mail flow. If you specify
a two-way connector, a reciprocal connector is created in the target
routing group.
Samples Example 13 through Example 16
provide the syntax and usage for the Get-RoutingGroupConnector,
New-RoutingGroupConnector, Set-RoutingGroupConnector, and
Remove-RoutingGroupConnector cmdlets. With the
Set-RoutingGroupConnector cmdlet, you can use the –MaxMessageSize
parameter to set the maximum size for messages that are relayed between
Exchange 2010 Hub Transport servers and Exchange 2003 bridgehead
servers.
Example 13. Get-RoutingGroupConnector cmdlet syntax and usage
Syntax
Get-RoutingGroupConnector [-Identity RoutingGroup\ConnectorIdentity]
[-DomainController DCName]
Usage
Get-RoutingGroupConnector
Get-RoutingGroupConnector -Identity "Exchange Administrator GroupExchange 2003 Interop"
Example 14. New-RoutingGroupConnector cmdlet syntax and usage
Syntax
New-RoutingGroupConnector -Name Name
-SourceTransportServers SourceServer1, SourceServer2,...
-TargetTransportServers TransportServer1, TransportServer2,...
[-BiDirectional <$true | $false>]
[-Cost ConnectorCost] [-DomainController DCName]
[-PublicFolderReferralsEnabled <$true | $false>]
Usage
New-RoutingGroupConnector -Name "Exchange 2003 Interop"
-SourceTransportServers "Exchange2010Server12.cpandl.com"
-TargetTransportServers "Exchange2003Server08.cpandl.com"
-Cost 100
-BiDirectional $true
Example 15. Set-RoutingGroupConnector cmdlet syntax and usage
Syntax
Set-RoutingGroupConnector -Identity Group\Connector Identity
[-Cost ConnectorCost] [-DomainController DCName]
[-MaxMessageSize <Size | Unlimited>] [-Name Name]
[-PublicFolderReferralsEnabled <$true | $false>]
[-SourceTransportServers SourceServer1, SourceServer2,...]
[-TargetTransportServers TransportServer1, TransportServer2,...]
Usage
Set-RoutingGroupConnector -Identity "Exchange Administrator
Group\Exchange 2003 Interop" -Name "Exchange 2003 Interop"
-SourceTransportServers "Exchange2010Server12.cpandl.com"
-TargetTransportServers "Exchange2003Server08.cpandl.com"
-Cost 100
-BiDirectional $true
Example 16. Remove-RoutingGroupConnector cmdlet syntax and usage
Syntax
Remove-RoutingGroupConnector [-Identity RoutingGroup\ConnectorIdentity]
[-DomainController DCName]
Usage
Remove-RoutingGroupConnector -Identity "Exchange Administrator GroupExchange 2003 Interop"
