Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-05-07
Use the Set-RoutingGroupConnector cmdlet to modify the properties of an existing routing group connector between a Microsoft Exchange Server 2010 routing group and an Exchange Server 2003 routing group. You can also use this cmdlet to configure the maximum message size that can pass across a routing group connector.
Syntax
Set-RoutingGroupConnector -Identity
<RoutingGroupConnectorIdParameter> [-Confirm
[<SwitchParameter>]] [-Cost <Int32>] [-DomainController
<Fqdn>] [-MaxMessageSize <Unlimited>] [-Name
<String>] [-PublicFolderReferralsEnabled <$true |
$false>] [-SourceTransportServers <MultiValuedProperty>]
[-TargetTransportServers <MultiValuedProperty>] [-WhatIf
[<SwitchParameter>]]
|
Detailed Description
The Set-RoutingGroupConnector cmdlet modifies the properties of an existing routing group connector. A routing group connector is used to send and receive messages between computers running Exchange 2010 that have the Hub Transport server role installed and Exchange 2003 bridgehead servers when the organization is running more than one version of Exchange.
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 members of this group. The source and target servers must be computers that have the Exchange 2010 Hub Transport server role installed, 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 |
---|---|---|---|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.RoutingGroupConnectorIdParameter |
The Identity parameter specifies the name or GUID of the routing group connector. The name is expressed as [[Administrative Group Name\]Routing Group Name]\Routing Group Connector Name. |
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. |
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. |
MaxMessageSize |
Optional |
Microsoft.Exchange.Data.Unlimited |
The MaxMessageSize parameter specifies the maximum size
of a message that can pass through a routing group connector. The
default value is
Unqualified values are treated as bytes. The valid input range
for this parameter is from |
Name |
Optional |
System.String |
The Name parameter specifies the name of the routing group connector. |
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
|
SourceTransportServers |
Optional |
Microsoft.Exchange.Data.MultiValuedProperty |
The SourceTransportServers parameter specifies the host name or FQDN of the transport servers that are used to send messages to the target transport servers. You can specify more than one server by separating each entry with a comma. For more information about how to add or remove values from multivalued properties, see Modifying Multivalued Properties. |
TargetTransportServers |
Optional |
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. For more information about how to add or remove values from multivalued properties, see Modifying Multivalued Properties. |
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 makes the following configuration changes to the routing group connector Ex2010 to Ex2003 RGC:
- Sets the cost to 70.
- Sets a maximum message size limit of 10 MB.
- Specifies new source and target servers for the connector.
Copy Code | |
---|---|
Set-RoutingGroupConnector -Identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\Ex2010 to Ex2003 RGC" -Cost 70 -MaxMessageSize 10MB -SourceTransportServers 2010Hub1.contoso.com -TargetTransportServers 2003BH1.contoso.com |