Share via

New-ForeignConnector (RTM)

  • Article

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007

Use the New-ForeignConnector cmdlet to create a new Foreign connector on a computer that is running Microsoft Exchange Server 2007 and that has the Hub Transport server role installed. A Foreign connector uses a Drop directory on a Hub Transport server to send messages to a local messaging server that doesn't use the Simple Mail Transfer Protocol (SMTP) as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Third-party fax gateway servers are examples of foreign gateway servers. The address spaces that are assigned to a Foreign connector can be SMTP or non-SMTP.

Syntax

New-ForeignConnector -Name <String> -AddressSpaces <MultiValuedProperty> [-DomainController <Fqdn>] [-SourceTransportServers <MultiValuedProperty>] [-TemplateInstance <PSObject>]

Detailed Description

The New-ForeignConnector cmdlet creates a new Foreign connector. To be prompted for the required parameters of a new Foreign connector, enter New-ForeignConnector. After this task is completed, a Foreign connector is created.

To run the New-ForeignConnector cmdlet, the account you use must be delegated the 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

AddressSpaces

Required

Microsoft.Exchange.Data.MultiValuedProperty

This parameter specifies the domain names to which the Foreign connector sends messages. You may specify multiple address spaces by separating the address spaces with commas. The complete syntax for entering each address space is as follows:

<ConnectorScope>:<AddressSpaceType>:<AddressSpace>;<AddressSpaceCost>

  • ConnectorScope   If you specify a value of Local, the connector can only be used by other Hub Transport servers that exist in the same Active Directory site as the source Hub Transport server on which you are running the New-SendConnector cmdlet. If you omit the ConnectorScope qualifier, the connector can be used by all Hub Transport servers that exist in the whole Exchange 2007 organization.

  • AddressSpaceType   For SMTP address spaces, this value must be SMTP. For non-SMTP address spaces, this value may be any descriptive text string, such as "Lotus Notes".

  • AddressSpace   For SMTP address spaces, the domain name system (DNS) wildcard character (*) as defined in RFC 1035 can be used, such as "*", "*.com.", or "*.contoso.com", for example. For non-SMTP address spaces, wildcard characters (*) and other characters can be used, such as "*contoso.com" or "@contoso", for example.

  • AddressSpaceCost   The valid input range for the cost is 1 to 100. A lower cost indicates a better route. This parameter is optional. If you omit the AddressSpaceCost qualifier when you enter an address space by using the complete syntax, a cost of 1 is assumed.

You must use the complete syntax for the AddressSpaces parameter only for the following conditions:

  • Scoped connectors that have the Local qualifier

  • Non-SMTP address spaces

  • SMTP address spaces with a cost that is not 1

If you enter a domain name or a comma-separated list of domain names for the value of the AddressSpaces parameter, the address space type of SMTP and a cost of 1 are assumed for each domain name.

Name

Required

System.String

This parameter specifies a name for the Foreign connector.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

To specify the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to the Active Directory directory service, include the DomainController parameter. The DomainController parameter is not supported on computers that run the Edge Transport server role. The Edge Transport server role reads and writes only to the local ADAM instance.

SourceTransportServers

Optional

Microsoft.Exchange.Data.MultiValuedProperty

This parameter specifies the names of the Hub Transport servers that use this Foreign connector. You may specify multiple Hub Transport servers by separating the server names with commas. Having a single Foreign connector homed on multiple Hub Transport servers provides fault tolerance and high availability if one of the Hub Transport servers fails. The default value of this parameter is the name of the Hub Transport server on which this Foreign connector was first installed.

TemplateInstance

Optional

System.Management.Automation.PSObject

When an existing object is supplied to this parameter, the cmdlet uses the configuration of that object to create a copy of the object.

Example

The following code example shows a New-ForeignConnector command that creates a new Foreign connector with the following properties:

  • Connector name: Contoso Foreign Connector

  • Address space: "Contoso.com"

  • Address space type: SMTP

  • Address space cost: 5

  • Source Transport Servers: Hub01 and Hub02

New-ForeignConnector -Name "Contoso Foreign Connector" -AddressSpaces "SMTP:*contoso.com;5" -SourceTransportServers "Hub01,Hub02"