Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-05-05
Use the New-RoutingGroupConnector cmdlet to establish a connection between a Microsoft Exchange Server 2010 routing group and an Exchange Server 2003 routing group when the organization is running more than one version of Exchange.
Syntax
New-RoutingGroupConnector -Name <String>
-SourceTransportServers <MultiValuedProperty>
-TargetTransportServers <MultiValuedProperty> [-BiDirectional
<$true | $false>] [-Confirm [<SwitchParameter>]] [-Cost
<Int32>] [-DomainController <Fqdn>]
[-PublicFolderReferralsEnabled <$true | $false>] [-WhatIf
[<SwitchParameter>]]
|
Detailed Description
The New-RoutingGroupConnector cmdlet creates a new routing group connector between the Exchange 2010 routing group and Exchange Server 2003 routing groups. A routing group connector is used to send and receive messages between computers that have the Exchange 2010 Hub Transport server role installed and Exchange 2003 bridgehead servers. The Exchange 2003 source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2010 system grants Send to and Receive from permissions on the Hub Transport servers to the members of this group.
To create the routing group connector, you must specify the source servers from the originating routing group and the target servers in the destination routing group. The routing group connector is created in the routing group of which the source server is a member. 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. The source and target servers must be Exchange 2010 Hub Transport servers or Exchange 2003 bridgehead servers.
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Routing group connectors" entry in the Transport Permissions topic.
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Name |
Required |
System.String |
The Name parameter specifies the name to assign to the routing group connector. |
|
SourceTransportServers |
Required |
Microsoft.Exchange.Data.MultiValuedProperty |
The SourceTransportServers parameter specifies the host name or fully qualified domain name (FQDN) of the transport servers used to send messages to the target transport servers. You can specify more than one server by separating each entry with a comma. |
|
TargetTransportServers |
Required |
Microsoft.Exchange.Data.MultiValuedProperty |
The TargetTransportServers parameter specifies the host name or FQDN of the transport servers that receive messages from the source transport servers. You can specify more than one server by separating each entry with a comma. |
|
BiDirectional |
Optional |
System.Boolean |
The BiDirectional parameter specifies whether this is a
one-way or two-way connector. The default value is
|
|
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch. |
|
Cost |
Optional |
System.Int32 |
The Cost parameter specifies a cost to the connector. Transport servers use the connector cost to determine the least cost routing path from a source server to the destination server for message delivery. The default value is 1. |
|
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory. |
|
PublicFolderReferralsEnabled |
Optional |
System.Boolean |
The PublicFolderReferralsEnabled parameter specifies
whether users can use this routing group connector to access a
public folder replica located in the routing group of the target
servers when an instance of that public folder isn't available in
the same routing group as the user's mailbox. The default value is
|
|
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch. |
Input Types
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.
Return Types
To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.
Examples
EXAMPLE 1
This example creates the routing group connector Interop RGC with the following properties:
- The Exchange 2010 server is Hub2010.contoso.com.
- The Exchange 2003 bridgehead server is
Bridghead2003.contoso.com.
- The routing group connector is a two-way connector between the
Exchange 2010 routing group and the routing group associated with
the specified Exchange 2003 server.
- The cost is 100.
 Copy Code |
|
|---|---|
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Hub2010.contoso.com" -TargetTransportServers "Bridgehead2003.contoso.com" -Cost 100 -Bidirectional $true |
|