Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Exchange Server 2010 : Completing Transport Server Setup (part 4) - Creating an Edge Subscription

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
3/10/2014 9:43:41 PM

6. Subscribing Edge Transport Servers

When your Exchange organization uses Edge Transport servers and you want to use the Edge Synchronization feature, you must subscribe the Edge Transport server to your Exchange organization prior to performing other configuration tasks on the Edge Transport server. Creating a subscription allows the Microsoft Exchange EdgeSync service running on designated Hub Transport servers to establish one-way replication of recipient and configuration information from your internal Active Directory database to the AD LDS database on an Edge Transport server. After you create an Edge subscription, synchronization is automatic. If problems occur, however, you can force synchronization or remove the Edge subscription.

6.1 Creating an Edge Subscription

A subscribed Edge Transport server receives the following from the EdgeSync service:

  • Send connector configurations

  • Accepted domain configurations

  • Remote domain configurations

  • Safe Senders lists

  • Recipients

Any manually configured accepted domains, message classifications, remote domains, and Send connectors are deleted as part of the subscription process, and the related Exchange management interfaces are locked out as well. To manage these features after a subscription is created, you must do so within the Exchange organization and have the EdgeSync service update the Edge Transport server.

Also as part of the subscription process, you must select an Active Directory site for the subscription. The Hub Transport server or servers in the site are the servers responsible for replicating Active Directory information to the Edge Transport server.

You can create a subscription for an Edge Transport server by completing the following steps:

  1. Log on to the Edge Transport server for which you are creating a subscription using an administrator account.

  2. At the Exchange Management Shell prompt, type the following command:

    New-EdgeSubscription -filename "C:\EdgeSubscriptionExport.xml"
  3. When prompted, confirm that it is okay to delete any manually configured accepted domains, message classifications, remote domains, and Send connectors by pressing A (which answers Yes to all deletion prompts).

  4. Copy the EdgeSubscriptionExport.xml file to a Hub Transport server in your Exchange organization.

  5. Log on to a Hub Transport server in your Exchange organization using an account with Exchange administration privileges.

  6. On the Hub Transport server, start the Exchange Management Console. Expand the Organization Configuration node, and then select the Hub Transport node.

  7. In the details pane, the Edge Subscriptions tab lists existing subscriptions by Edge Transport server name and associated Active Directory site.

  8. Right-click an open area of the details pane, and then select New Edge Subscription. This starts the New Edge Subscription Wizard, as shown in Figure 3.

    Create a new Edge subscription.

    Figure 3. Create a new Edge subscription.

  9. On the New Edge Subscription page, click Browse to the right of the Active Directory Site text box. In the Select Active Directory Site dialog box, choose the Active Directory site for replication and then click OK.

    Note

    REAL WORLD Hub Transport servers in the Active Directory site you select must be able to resolve the IP addresses for the Edge Transport server. You need to ensure that subnets have been created in Active Directory Sites And Services and that DNS is configured to resolve the fully qualified domain name of the Edge Transport server. Hub Transport servers in the site must also be able to connect to the Edge Transport server over TCP port 50636.

  10. Click Browse to the right of the Subscription File text box. In the Open dialog box, locate and then select the Edge Subscription file to import. Click Open.

  11. On the New Edge Subscription page, if you don't want to create the required Send connectors now, clear Automatically Create A Send Connector For This Edge Subscription, and then click New to begin the subscription process. If you want to create Send connectors now, just click New to begin the subscription process.

  12. On the Completion page, click Finish.

After you've completed steps 1–5, you can use the New-EdgeSubscription cmdlet to start a subscription. Example 4 provides the syntax and usage. By default, the –CreateInboundSendConnector parameter is set to $true, which ensures that a Send connector from the Edge Transport server to Hub Transport servers is created. By default, the –CreateInternetSendConnector parameter is set to true, which ensures that a Send connector to the Internet is created.

Example 4. New-EdgeSubscription cmdlet syntax and usage

Syntax

New-EdgeSubscription -FileName FilePath
-Site SiteName [-AccountExpiryDuration <TimeSpan>]
[-CreateInboundSendConnector <$true | $false>]
[-CreateInternetSendConnector <$true | $false>]
[-DomainController DCName] [-FileData ByteStr] [-Force <$true | $false>]


Usage

New-EdgeSubscription -FileName "Z:\EdgeSubscriptionExport.xml"
-Site "Default-First-Site-Name"
-CreateInboundSendConnector $true
-CreateInternetSendConnector $true
Other -----------------
- SharePoint 2013 : Health and Monitoring (part 4) - Timer Jobs, The Developer Dashboard
- SharePoint 2013 : Health and Monitoring (part 3) - Analytics, The Health Analyzer
- SharePoint 2013 : Health and Monitoring (part 2) - Correlation IDs, The Logging Database
- SharePoint 2013 : Health and Monitoring (part 1) - Logging
- SharePoint 2013 Request Management (part 2) - Request Management Administration
- SharePoint 2013 Request Management (part 1) - The Request Management Process
- Windows Server 2012 : Deploying Storage Spaces (part 5) - Implementing Storage Spaces, Using Windows PowerShell
- Windows Server 2012 : Deploying Storage Spaces (part 4) - Planning a Storage Spaces deployment - Availability, Management
- Windows Server 2012 : Deploying Storage Spaces (part 3) - Planning a Storage Spaces deployment - Hardware, Performance, Resiliency
- Windows Server 2012 : Deploying Storage Spaces (part 2) - Understanding Storage Spaces - Fixed vs. thin provisioning
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server