This topic has not yet been rated - Rate this topic

New-RoutingGroupConnector

Exchange 2010

Applies to: Exchange Server 2013

Topic Last Modified: 2012-09-18

Use the New-RoutingGroupConnector cmdlet to establish a connection between routing groups.

New-RoutingGroupConnector -Name <String> -SourceTransportServers <MultiValuedProperty> -TargetTransportServers <MultiValuedProperty> [-BiDirectional <$true | $false>] [-Confirm [<SwitchParameter>]] [-Cost <Int32>] [-DomainController <Fqdn>] [-PublicFolderReferralsEnabled <$true | $false>] [-WhatIf [<SwitchParameter>]]

Examples

EXAMPLE 1

This example creates the routing group connector named Interop RGC with the following properties:

The Exchange 2013 server is Hub.contoso.com.
The connecting server is group1.contoso.com.
The routing group connector is a two-way connector between the Exchange 2013 routing group and the routing group associated with the specified server.
The cost is 100.

New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Hub.contoso.com" -TargetTransportServers "group1.contoso.com" -Cost 100 -Bidirectional $true

Detailed Description

The New-RoutingGroupConnector cmdlet creates a new routing group connector. The source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2013 system grants Send to and Receive from permissions on the servers running the Transport service 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.

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 Mail Flow 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. To enter multiple values and overwrite any existing entries, use the following syntax: `<value1>,<value2>...`. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: `"<value1>","<value2>"...`. To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="<value1>","<value2>"...; Remove="<value1>","<value2>"...}`.
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. To enter multiple values and overwrite any existing entries, use the following syntax: `<value1>,<value2>...`. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: `"<value1>","<value2>"...`. To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="<value1>","<value2>"...; Remove="<value1>","<value2>"...}`.
BiDirectional	Optional	System.Boolean	The BiDirectional parameter specifies whether this is a one-way or two-way connector. The default value is `$false`.
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 `$true`.
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.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)