Applies to: Exchange Server 2013
Topic Last Modified: 2012-10-01
With routing groups and Routing Group connectors you can consolidate communication between servers by designating bridgehead servers that act as communication points between routing groups. For example, your organization may have a remote site connected through a wide-area-network (WAN) link to your main office. In this example, you can use a Routing Group connector to route Exchange traffic between a server at your main office and a server at your remote site.
In some cases, you may want to connect routing groups at more than one point, so that if your primary bridgehead server at a remote site fails, the remote site can continue to receive Exchange Server traffic from another location (perhaps another remote site, in this instance). To do this, you can create a secondary Routing Group connector with a higher Cost parameter value than your primary Routing Group connector.
Routing Group connectors are created and configured using the Exchange Management Shell, by means of the New-RoutingGroupConnector and Set-RoutingGroupConnector cmdlets. New-RoutingGroupConnector describes each parameter for Routing Group connectors in more detail and includes an example that shows how to create one.