TL;DR — Resumo Rápido

Microsoft Exchange Server 2010 brought improvements in high availability with Database Availability Groups (DAGs), role-based access control, and enhanced...

Nota: Este artigo foi publicado originalmente em 2013. Alguns passos, comandos ou versões de software podem ter mudado. Consulte a documentação atual de Exchange 2010 para as informações mais recentes.

Pré-requisitos

Antes de começar, certifique-se de ter:

  • Exchange Server 2010 SP3 or later
  • Exchange Management Console or Exchange Management Shell access
  • Appropriate administrative permissions

How to: Subscribe and Synchronize an (https://www.microsoft.com/exchange “Microsoft Exchange Server”) Edge Server to an Exchange 2013 Server

As you start migrating towards Exchange 2013 you’ll run across some scenarios like:

  • How to synchronize your existing Edge server with your new (https://www.microsoft.com/exchange “Microsoft Exchange Server”) 2013
  • How to synchronize a new Edge server with your Exchange server 2013

From what I’ve gathered on the Internet, about 30% of organizations use the Edge server while many others don’t. Moving forward it seems like (<https://maps.google.com/maps?ll=47.6395972222,-122.12845&spn=0.01,0.01&q=47.6395972222,-122.12845 (Microsoft)&t=h> “Microsoft”) is tilting towards not continuing the Edge server product, but has allowed for the previous Edge servers (2007 and 2010) to still work on a 2013 environment. Below are the more likely commands you will need in order to subscribe your Edge server to your Active Directory site:

UPDATE : With the Exchange Server 2013 SP1 release, Microsoft has made the Exchange Edge Server available once again. Because it lowers the surface area of attack against a mail server it seems that a lot of organizations have requested for this feature to return and Microsoft listened.

(<void(0)> “Collapse”)

This example creates the Edge Subscription file. It should be run on your Edge Transport server.

New-EdgeSubscription -(https://en.wikipedia.org/wiki/Filename “Filename”) “c:\EdgeServerSubscription.xml”

(<void(0)> “Collapse”)

This example imports the Edge Subscription file generated in EXAMPLE 1 to the (https://en.wikipedia.org/wiki/Active_Directory “Active Directory”) Default-First-Site-Name. Importing the Edge Subscription file completes the Edge Subscription process. You must run this command on the (https://en.wikipedia.org/wiki/Email_box “Email box”) server. The first command reads the data from the Edge Subscription file and stores it in a temporary variable as a byte-encoded data object. The second command completes the Edge subscription process.

]$Temp = Get-Content -Path “C:\Root\EdgeSub_ATMG2010_TMG2010.xml” -ReadCount 0 -Encoding Byte

New-EdgeSubscription -FileData $Temp -Site “Default-First-Site-Name”

(<void\(0\)> "Collapse")

This example also imports the Edge Subscription file generated in EXAMPLE 1 to the Active Directory site Default-First-Site-Name; however, the end result is accomplished in a single line of code. You must run this command on the Mailbox server.

New-EdgeSubscription -FileData (]$(Get-Content -Path “C:\EdgeServerSubscription.xml” -ReadCount 0 -Encoding Byte)) -Site “Default-First-Site-Name”

One important thing to keep in mind is that in previous versions for some reason the Default First Site was named “Default-First-Site” instead of “Default-First-Site-Name” so if you get an error on the site name try that one or use the get command to pull it.

Also, here are a few more shell commands that will help you with your Edge Synchronization:

How to: Force an Edgesync synchronization

This example starts EdgeSync synchronization with the following options:

  • The synchronization is initiated from the Hub Transport server Hub01.
  • All Edge Transport servers are synchronized.
  • Only the changes since the last replication are synchronized.

Start-EdgeSynchronization -Server Hub01

This example starts EdgeSync synchronization with the following options:

  • The synchronization is initiated from the Hub Transport server Hub01.
  • Only the Edge Transport server Edge03 is synchronized.
  • All recipient and configuration data are fully synchronized.

Start-EdgeSynchronization -Server Hub01 -TargetServer Edge03 -ForceFullSync

To remove an Edge Subscription, use the following syntax.

Remove-EdgeSubscription -Identity -DomainController

How to: Verify EdgeSync Results for a Recipient

Use the Test-EdgeSynchronization cmdlet to verify EdgeSync results for a single recipient. This cmdlet is also used to verify configuration replication. To verify a single recipient, you need to use the VerifyRecipient parameter. The following command verifies EdgeSync results for the user (mailto:someuser@mydomain.com):

Test-EdgeSynchronization -VerifyRecipient someuser@mydomain.com

 

Resumo

Artigos Relacionados