Applies to: Exchange Server 2007
Topic Last Modified: 2007-07-18
Use the New-RemoteDomain cmdlet to create a managed connection for a remote domain. When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies, and specify acceptable character sets for messages that are sent to and received from the remote domain.
For more information about how to configure the remote domain, see Set-RemoteDomain (RTM).
Syntax
New-RemoteDomain -Name <String> -DomainName
<SmtpDomainWithSubdomains> [-DomainController <Fqdn>]
[-TemplateInstance <PSObject>]
|
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
To specify the fully qualified domain name (FQDN) of the domain controller that writes this configuration information from the Active Directory directory service, include the DomainController parameter on the command. The DomainController parameter is not supported on computers that have the Edge Transport server role installed. The Edge Transport server role writes and reads only to the Active Directory Application Mode (ADAM) instance. |
|
DomainName |
Required |
Microsoft.Exchange.Data.SmtpDomainWithSubdomains |
Valid input for the DomainName parameter is a Simple Mail
Transfer Protocol (SMTP) domain. Enter the SMTP domain that you
want to establish as a remote domain. You can use a wildcard
character to specify all subdomains of a given domain, as shown in
the following example: |
|
Name |
Required |
System.String |
Use the Name parameter to create a unique name for remote domain object. |
|
TemplateInstance |
Optional |
System.Management.Automation.PSObject |
When an existing object is supplied to the TemplateInstance parameter, the command uses the configuration of that object to create an identical copy of the object on a local or target server. |
Detailed Description
To run the New-RemoteDomain 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 Microsoft Exchange Server 2007, see Permission Considerations.
Example
The following examples show how to use the New-RemoteDomain cmdlet to create a managed connection for a remote domain.
The first example shows how to create a new remote domain named Contoso.
The second example shows how to create a new remote
domain named Adatum. On the Set-RemoteDomain cmdlet, the
AllowedOOFType parameter is set to None, and
the DisplaySenderName parameter is set to
$False on Adatum. Adatum is then assigned to a
variable named $Example. The variable
$Example is passed through the TemplateInstance
parameter when a new remote domain named Contoso is created. This
creates an exact copy of the remote domain object Adatum on
Contoso. Because the TemplateInstance parameter creates an
exact copy of the remote domain object, the values on the
AllowedOOFType parameter and DisplaySenderName
parameter on Contoso match the values on Adatum.
For more information about how to set additional configuration options on a remote domain object, see Set-RemoteDomain (RTM). For more information about how to view configuration information for remote domain objects in your organization, see Get-RemoteDomain (RTM).
 Copy Code |
|
|---|---|
New-RemoteDomain -DomainName Contoso.com -Name Contoso New-RemoteDomain -DomainName Adatum.com -Name Adatum Set-RemoteDomain Adatum -AllowedOOFType None -DisplaySenderName $False $Example = Get-RemoteDomain Adatum New-RemoteDomain -DomainName Contoso.com -Name Contoso -TemplateInstance $Example |
|