Routing Group connectors are easy to configure and provide the
simplest way to connect two
You can create single or multiple local (source) bridgehead servers, or you can specify that no local bridgehead server exists and every server in the local routing group can make connections through the Routing Group connector. This allows each server in the routing group to act as a bridgehead server. If you want all mail to flow through one computer for the purpose of tracking messages or archiving, a single bridgehead server is appropriate. Multiple bridgehead servers provide load balancing or fault tolerance in the event of a bridgehead server failure.
You can also create multiple remote (destination) bridgehead servers, but you must create at least one remote bridgehead server.
As with SMTP or X.400 connectors, with Routing Group connectors you can specify delivery restrictions and message size limits. Also, the Routing Group connector (like the site connector in earlier versions of Exchange) provides the simplest, easiest way to connect two groups of servers. It has fewer settings and requires only that you specify the routing group to which you want to connect.
In a native-mode Exchange 2000 Server environment, Routing Group connectors are used to connect routing groups. In mixed-mode environments that contain computers running earlier versions of Exchange, routing groups are mapped to the equivalent site connectors.
You can assign each connector a cost to help determine load balancing; for example, suppose you have two bridgehead servers in the local bridgehead server list, one with a cost of 10 and one with a cost of 20. Because the latter server costs twice as much as the other server, it is used less often.
Related TopicsInstall a Routing Group Connector