Export (0) Print
Expand All

Set-ForeignConnector

Applies to: Exchange Server 2010

Topic Last Modified: 2011-03-19

Use the Set-ForeignConnector cmdlet to modify an existing Foreign connector on a computer running Microsoft Exchange Server 2010 that has the Hub Transport server role installed.


Set-ForeignConnector -Identity <ForeignConnectorIdParameter> [-AddressSpaces <MultiValuedProperty>] [-Comment <String>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-DropDirectory <String>] [-DropDirectoryQuota <Unlimited>] [-Enabled <$true | $false>] [-Force <SwitchParameter>] [-IsScopedConnector <$true | $false>] [-MaxMessageSize <Unlimited>] [-Name <String>] [-RelayDsnRequired <$true | $false>] [-SourceTransportServers <MultiValuedProperty>] [-WhatIf [<SwitchParameter>]]

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.ForeignConnectorIdParameter

The Identity parameter specifies the Foreign connector that you want to modify. The Identity parameter can take any of the following values for the Foreign connector object:

  • GUID
  • Connector name
  • ServerName\ConnectorName

AddressSpaces

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is as follows: <AddressSpaceType>:<AddressSpace>;<AddressSpaceCost>

  • AddressSpaceType   The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
  • AddressSpace   For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, *, *.com, and *.contoso.com are permitted, but *contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space.
  • AddressSpaceCost   The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains a semicolon (;), you must specify the address space cost.

If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("). For example, the following address space entries are equivalent:

  • "SMTP:contoso.com;1"
  • "contoso.com;1"
  • "SMTP:contoso.com"
  • contoso.com

You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3".

Comment

Optional

System.String

The Comment parameter specifies an optional comment for the Foreign connector. You must enclose the Comment parameter in quotation marks ("), for example: "this is an admin note".

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.

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.

DropDirectory

Optional

System.String

The DropDirectory parameter specifies the name of the Drop directory used by this Foreign connector. All outbound messages sent to address spaces defined by this Foreign connector are put in the specified Drop directory. The location of the Drop directory for each Foreign connector is controlled by the following two items:

  • RootDropDirectoryPath parameter in the Set-TransportServer cmdlet   This option is used for all Foreign connectors that exist on the Hub Transport server. The value of the RootDropDirectoryPath parameter may be a local path or a Universal Naming Convention (UNC) path to a remote server.
  • DropDirectory parameter in the Set-ForeignConnector cmdlet   This value is set for each Foreign Connector that exists on the Hub Transport server.

By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange 2010 installation folder. The default Exchange 2010 installation folder is C:\Program Files\Microsoft\Exchange Server\. By default, the value of the DropDirectory parameter is the name of the Foreign connector.

If the value of the DropDirectory parameter doesn't contain absolute path information, the location of the Drop directory is defined by the combination of the DropDirectory parameter and the RootDropDirectoryPath parameter. If the value of the DropDirectory parameter contains absolute path information, the value of the RootDropDirectoryPath must be unspecified. The location of the Drop directory is defined only by the value of the DropDirectory parameter.

The Drop directory isn't created for you. Therefore, you have to manually create each Drop directory folder.

The Drop directory must have the following permissions assigned to it:

  • Network Service: Full Control
  • System: Full Control
  • Administrators: Full Control

DropDirectoryQuota

Optional

Microsoft.Exchange.Data.Unlimited

The DropDirectoryQuota parameter specifies the maximum size of all message files in the Drop directory. When the specified value is reached, no new message files can be copied into the Drop directory until the existing messages are delivered and deleted. When you enter a value for the DropDirectoryQuota parameter, qualify the value with one of the following units:

  • B (bytes)
  • KB (kilobytes)
  • MB (megabytes)
  • GB (gigabytes)
  • TB (terabytes)

Unqualified values are treated as bytes. The valid input range for this parameter is from 1 through 2147483647 bytes. If you enter a value of unlimited, no message size limit is imposed on the Drop directory. The default value is unlimited.

Enabled

Optional

System.Boolean

The Enabled parameter specifies whether to enable the Foreign connector. The valid values are $true or $false. The default value is $true.

Force

Optional

System.Management.Automation.SwitchParameter

The Force parameter specifies whether to suppress the warning or confirmation messages that appear during specific configuration changes.

IsScopedConnector

Optional

System.Boolean

The IsScopedConnector parameter specifies the availability of the connector to other Hub Transport servers. When the value of this parameter is $false, the connector can be used by all Hub Transport servers in the Exchange organization. When the value of this parameter is $true, the connector can only be used by Hub Transport servers in the same Active Directory site. The default value is $false.

MaxMessageSize

Optional

Microsoft.Exchange.Data.Unlimited

The MaxMessageSize parameter specifies the maximum size of a message that can pass through this Foreign connector. When you enter a value for the MaxMessageSize parameter, qualify the value with one of the following units:

  • B (bytes)
  • KB (kilobytes)
  • MB (megabytes)
  • GB (gigabytes)
  • TB (terabytes)

Unqualified values are treated as kilobytes. If you enter a value of unlimited, no message size limit is imposed on this Foreign connector. The default value is unlimited. The valid input range for this parameter is from 0 through 2147483647 kilobytes. If you set the value of the MaxMessageSize parameter to 0, you effectively disable the Foreign connector. However, if you set the value of the MaxMessageSize parameter to 0 when the value of the Enabled attribute is $true, you generate event log errors. The preferred method to disable the Foreign connector is to use the Enabled parameter.

Name

Optional

System.String

The Name parameter specifies a descriptive name for the Foreign connector.

RelayDsnRequired

Optional

System.Boolean

The RelayDsnRequired parameter specifies whether a Relay delivery status notification (DSN) is required by the Foreign connector when messages are written to the Drop directory. The valid input values for this parameter are $true or $false. The default value is $false.

SourceTransportServers

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The SourceTransportServers 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.

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.

A Foreign connector uses a Drop directory on a Hub Transport server to send messages to a local messaging server that doesn't use 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 assigned to a Foreign connector can be SMTP or non-SMTP.

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 "Foreign connectors" entry in the Transport Permissions topic.

This example configures a 10 MB message size limit on the existing Foreign connector Fax Connector.

Set-ForeignConnector "Fax Connector" -MaxMessageSize 10MB
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft