Applies to: Exchange Server 2007
Topic Last Modified: 2007-06-11
Use the Set-AdSiteLink cmdlet to assign an Exchange-specific cost to an Active Directory IP site link.
Syntax
Set-AdSiteLink -Identity <AdSiteLinkIdParameter>
[-DomainController <Fqdn>] [-ExchangeCost <Nullable>]
[-Name <String>]
|
Set-AdSiteLink [-DomainController <Fqdn>]
[-ExchangeCost <Nullable>] [-Instance <ADSiteLink>]
[-Name <String>]
|
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.AdSiteLinkIdParameter |
Use the Identity parameter to specify the name or GUID of the IP site link for which you want to set an Exchange-specific cost. |
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
Use the DomainController parameter to specify the host name or the fully qualified domain name (FQDN) of the domain controller that will process this query. |
ExchangeCost |
Optional |
System.Nullable |
Use the ExchangeCost parameter to assign an
Exchange-specific cost to the IP site link. This cost is used
instead of the Active Directory-assigned cost when the Hub
Transport servers calculate the least cost routing paths. To clear
the value of the ExchangeCost parameter and revert to using
the value of the ADCost parameter, set the
ExchangeCost parameter to |
Instance |
Optional |
Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSiteLink |
Use the Instance parameter to pass a complete object to the cmdlet to be processed. This parameter is useful in scripts where an entire object must be passed to the cmdlet. |
Name |
Optional |
System.String |
Use the Name parameter to assign a name to the IP site link. The name that you assign will overwrite the current identity of the IP site link. You must be an Enterprise Administrator to modify this value. |
Detailed Description
In Microsoft Exchange Server 2007, computers that have the Hub Transport server role installed use Active Directory sites and the costs that are assigned to the Active Directory IP site links to determine the least cost routing path from each Hub Transport server in the organization to every other Hub Transport server in the organization. After the least cost routing path is determined, the source Hub Transport servers relay messages to the target Hub Transport servers. By default, the Hub Transport servers that are located in Active Directory sites along the path between the source server and the target server do not process or relay the messages in any way.
However, you can configure an Active Directory site as a hub site so that messages are routed to the hub site to be processed before the messages are relayed to the target server. For this routing behavior to occur, the hub site must exist along the least cost routing path between two Hub Transport servers.
The least cost routing path is also used if a message cannot be delivered to the target site. In this case, message delivery queues at the Hub Transport servers in the closest reachable site along the least cost routing path of the target site.
By default, Exchange 2007 determines the least cost routing path by using the cost that is assigned to the Active Directory IP site. You can use the Set-AdSiteLink cmdlet to configure an Exchange-specific cost to the Active Directory IP site link. The Exchange-specific cost is a separate attribute that is used instead of the Active Directory-assigned cost to determine the Exchange routing path.
To run the Set-AdSiteLink 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 Server 2007, see Permission Considerations.
Input Types
Return Types
Errors
Error | Description |
---|---|
|
|
Exceptions
Exceptions | Description |
---|---|
|
|
Example
The following example uses the Set-AdSiteLink cmdlet to assign an Exchange-specific cost of 25 to the specified IP site link.
Copy Code | |
---|---|
Set-AdSiteLink -Identity DEFAULTIPSITELINK -ExchangeCost 25 |