Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1
Topic Last Modified: 2007-06-28

Use the New-EdgeSubscription cmdlet to export an Edge Subscription file from a computer that has the Edge Transport server role installed and to import the Edge Subscription file to a computer that has the Hub Transport server role installed.

Syntax

New-EdgeSubscription -FileName <LongPath> [-Confirm [<SwitchParameter>]] [-CreateInboundSendConnector <$true | $false>] [-CreateInternetSendConnector <$true | $false>] [-DomainController <Fqdn>] [-Force <SwitchParameter>] [-Site <AdSiteIdParameter>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter Required Type Description

FileName

Required

Microsoft.Exchange.Data.LongPath

Use the FileName parameter to specify the full path of the Edge Subscription file.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm parameter 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 parameter.

CreateInboundSendConnector

Optional

System.Boolean

Use the CreateInboundSendConnector parameter to specify whether to create the Send connector from the Edge Transport server to the Hub Transport servers. The default value is $True. The Send connector address space will be set to "--", the smart hosts will be set to "--", the Edge Transport server will be set as the source server, and Domain Name System (DNS) routing will be disabled. This parameter is only used when you run the command on the Hub Transport server.

CreateInternetSendConnector

Optional

System.Boolean

Use the CreateInternetSendConnector parameter to specify whether to create the Send connector to the Internet. The default value is $true. The Send connector address space will be set to all domains (*), the Edge Transport server will be set as the source server, and DNS routing will be enabled. This parameter is only used when you run the command on the Hub Transport server.

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 will process this command. This parameter is used only when you run the command on a Hub Transport server.

Force

Optional

System.Management.Automation.SwitchParameter

Use the Force parameter to bypass the confirmation prompt when you run the New-EdgeSubscription command on an Edge Transport server. This parameter also causes the command to overwrite an existing Edge Subscription file with the same name as the file you are creating. This parameter is useful when you script the Edge Subscription command and when you resubscribe an Edge Transport server.

Site

Optional

Microsoft.Exchange.Configuration.Tasks.AdSiteIdParameter

Use the Site parameter to specify the name of the Active Directory site that contains the Hub Transport servers with which the Edge Transport servers will be associated. This parameter is used only when you run the command on a Hub Transport server and it is a required parameter when the command is run on a Hub Transport server.

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, 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 parameter.

Detailed Description

The Edge Transport server role does not have access to the Active Directory directory service. All configuration and recipient information is stored in the Active Directory Application Mode (ADAM) directory service. To perform recipient lookup and message security tasks, the Edge Transport server requires data that resides in Active Directory. The Edge Subscription process establishes one-way replication of recipient and configuration information from Active Directory to ADAM. Edge Subscription copies only the information that is required for the Edge Transport server to perform anti-spam and message security configuration tasks, and information about the connector configuration that is required to enable end-to-end mail flow. Edge Subscription performs scheduled updates so that the information in ADAM remains current.

The Edge Subscription process requires that you export an Edge Subscription file from each Edge Transport server that will be subscribed to an Active Directory site. The Edge Transport servers will be associated with the Hub Transport servers in that site for connector configuration. Import the Edge Subscription file on the Hub Transport server to complete the Edge Subscription process.

Run the New-EdgeSubscription cmdlet on the Edge Transport server to export the Edge Subscription file. This command creates the ADAM account that is used to help secure Lightweight Directory Access Protocol (LDAP) communications during data transfer, retrieves those credentials, and exports the Edge Subscription file. This procedure removes the existing configuration for objects on the Edge Transport server that are replicated to ADAM from Active Directory. After you perform this procedure, you must import the Edge Subscription file on a Hub Transport server. After the Edge Subscription is imported, the Edge Transport server receives its configuration information through replication from Active Directory. The controls that are used to edit those configuration settings on the Edge Transport server are disabled during the subscription process. Copy this file to removable media so that the file can be imported on the Hub Transport server, and then delete the file from the Edge Transport server.

Run the New-EdgeSubscription cmdlet on the Hub Transport server to import the Edge Subscription file and subscribe the Edge Transport server to an Active Directory site. The Active Directory site to which the Edge Transport server is subscribed must contain at least one Hub Transport server. This command imports the Edge Subscription file, establishes an authenticated communication channel, and completes the Edge Subscription process by starting the initial replication. By default, this process also creates the Send connector that is used to send messages to the Internet through the Edge Transport server and the Send connector that is used to send messages from the Edge Transport server to the Exchange organization.

To run the New-EdgeSubscription cmdlet, the account you use must be delegated the following:

  • Exchange Organization Administrator role

To run the New-EdgeSubscription cmdlet on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

Input Types

Return Types

Errors

Error Description

 

 

Exceptions

Exceptions Description

 

 

Example

You must run the New-EdgeSubscription cmdlet on both the Edge Transport server and the Hub Transport server to complete the Edge Subscription process.

The following code example shows how to use the New-EdgeSubscription cmdlet on the Edge Transport server to create the Edge Subscription file. Transfer the resulting file to the Hub Transport server, and then run the command in the second example on the Hub Transport server to import the Edge Subscription file and to subscribe the Edge Transport server to the specified Active Directory site.

Copy Code
New-EdgeSubscription -FileName "c:\EdgeServerSubscription.xml"
New-EdgeSubscription -FileName "c:\EdgeServerSubscription.xml" -site "Default-First-Site-Name"