Set-RoutingGroupConnector
Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
Use the Set-RoutingGroupConnector cmdlet to modify the properties of an existing routing group connector between a Microsoft Exchange Server 2007 routing group and an Exchange Server 2003 or Exchange 2000 Server 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>]]
Set-RoutingGroupConnector [-Confirm [<SwitchParameter>]] [-Cost <Int32>] [-DomainController <Fqdn>] [-Instance <RoutingGroupConnector>] [-MaxMessageSize <Unlimited>] [-Name <String>] [-PublicFolderReferralsEnabled <$true | $false>] [-SourceTransportServers <MultiValuedProperty>] [-TargetTransportServers <MultiValuedProperty>] [-WhatIf [<SwitchParameter>]]
Detailed Description
Use the Set-RoutingGroupConnector cmdlet to modify the properties of an existing routing group connector. 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 when the organization is running more than one version of Exchange.
If you use this cmdlet to set a source server or target server, the cmdlet overwrites existing entries. To prevent this, use the procedure that is described in Modifying Multivalued Properties. 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. The source and target servers must be computers that have the Exchange 2007 Hub Transport server role installed, or Exchange Server 2003 or Exchange 2000 Server bridgehead servers.
By default, Exchange 2007 does not impose a maximum message size limit on messages that are relayed across a routing group connector. If you use the Set-RoutingGroupConnector cmdlet to configure a maximum message size on a routing group connector, routing generates a non-delivery report (NDR) for any message that has a size larger than the maximum message size limit that is configured on any routing group connector in the least cost routing path. This configuration is useful for restricting the size of messages that are sent to remote Exchange Server 2003 and Exchange 2000 Server servers that must communicate over low-bandwidth connections.
To run the Set-RoutingGroupConnector cmdlet, the account you use must be delegated the following:
- Exchange Server Administrator role and local Administrators group for the target server
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 |
|---|---|---|---|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.RoutingGroupConnectorIdParameter |
Use the Identity parameter to specify the name or the 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 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. |
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
Use the DomainController parameter to specify the host name or 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. |
Instance |
Optional |
Microsoft.Exchange.Data.Directory.SystemConfiguration.RoutingGroupConnector |
Use the Instance parameter to pass a complete object to the command to be processed. It is mainly used in scripts where a complete object must be passed to the command. |
MaxMessageSize |
Optional |
Microsoft.Exchange.Data.Unlimited |
Use the MaxMessageSize parameter to specify 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 |
Name |
Optional |
System.String |
Use the Name parameter to modify the name of the routing group connector. |
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 |
SourceTransportServers |
Optional |
Microsoft.Exchange.Data.MultiValuedProperty |
Use the SourceTransportServers parameter to specify the host name or 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. For more information about how to add or remove values from multivalued properties, see Modifying Multivalued Properties. |
TargetTransportServers |
Optional |
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. 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 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
This example uses the Set-RoutingGroupConnector cmdlet to modify the cost of a routing group connector and set a maximum message size limit of 10 MB. The command also overwrites the source server and target server for the connector.
Set-RoutingGroupConnector -Identity "Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\Ex2007 to 2003 RGC" -Cost 70 -MaxMessageSize 10MB -SourceTransportServers 2007Hub1.contoso.com -TargetTransportServers 2003BH1.contoso.com