New-RoutingGroupConnector
Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
Use the New-RoutingGroupConnector cmdlet to establish a connection between a Microsoft Exchange Server 2007 routing group and an Exchange Server 2003 or Exchange 2000 Server 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>] [-TemplateInstance <PSObject>] [-WhatIf [<SwitchParameter>]]
Detailed Description
The New-RoutingGroupConnector cmdlet creates a new routing group connector between the Exchange 2007 routing group and Exchange Server 2003 or Exchange 2000 Server routing groups when the Exchange organization is running more than one version of Exchange. A routing group connector is used to send and receive messages between Exchange 2007 Hub Transport servers and Exchange Server 2003 or Exchange 2000 Server bridgehead servers. The Exchange Server 2003 and Exchange 2000 Server source servers that are specified in this cmdlet are automatically added to the ExchangeLegacyInterop Universal Security Group. By default, the Exchange 2007 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 2007 Hub Transport servers or Exchange Server 2003 or Exchange 2000 Server bridgehead servers.
To run the New-RoutingGroupConnector cmdlet, the account you use must be delegated the following:
- Exchange Organization Administrator role
For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.,
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
Name |
Required |
System.String |
Use the Name parameter to specify the name to assign to the routing group connector. |
SourceTransportServers |
Required |
Microsoft.Exchange.Data.MultiValuedProperty |
Use the SourceTransportServers parameter to specify the host name or fully qualified domain name (FQDN) of the transport servers that will be 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 |
Use the TargetTransportServers parameter to specify the host name or FQDN of the transport servers that will 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 |
Use the BiDirectional parameter to specify whether this will be a one-way or two-way connector. The default value is |
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm parameter causes the command to pause processing and requires the administrator to acknowledge what the command will do before processing continues. The default value is |
Cost |
Optional |
System.Int32 |
Use the Cost parameter to assign 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 |
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
Use the DomainController parameter to specify host name or the fully qualified domain name (FQDN) of the domain controller that this command will bind to and that will write this change to the Active Directory directory service. |
PublicFolderReferralsEnabled |
Optional |
System.Boolean |
Use the PublicFolderReferralsEnabled parameter to specify whether users can use this routing group connector to access a public folder replica that is located in the routing group of the target servers when an instance of that public folder is not available in the same routing group as the user's mailbox. The default value is |
TemplateInstance |
Optional |
System.Management.Automation.PSObject |
When an existing object is supplied to the TemplateInstance parameter, the command uses the configuration of that object to create an identical copy of the object. |
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf parameter instructs the command to simulate the actions that it would take on the object. By using the WhatIf parameter, the administrator can view what changes would occur without having to apply any of those changes. The default value is |
Input Types
Return Types
Errors
| Error | Description |
|---|---|
|
|
Exceptions
| Exceptions | Description |
|---|---|
|
|
Example
The following example shows how to use the New-RoutingGroupConnector cmdlet to create a two-way routing group connector between the Exchange 2007 routing group and the routing group that is associated with the specified Exchange Server 2003 server, and assign a cost of 100 to the connector.
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2007Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 100 -Bidirectional $true