I rebuilt my domain controller and my Exchange server,
but I hadn’t touched my Edge Transport Server hanging around out there in the
DMZ. Before continuing with my Exchange configuration, I thought I’d better
create a new Edge server or somehow wipe it clean and then continue with the
- Get-EdgeSubscription(note the NAME returned)
- Remove-EdgeSubscription NAME
new subscription file on the Edge server:
- New-EdgeSubscription -file
subscription file to your internal Exchange box.
new Edge subscription to your Exchange server:
- Organization Configuration -> Hub Transport ->
Create a new Edge Subscription.
- Browse to your subscription.xml file. Click New.
- Resubscribing your Edge connection will probably
reset your Send Connectors. Verify they are as they should be.
- I had to reconfigure mine to send
all mail through my ISP.
Active Directory Data to Edge Transport Server:
- Start-EdgeSynchronization (this forces a sync now,
otherwise it happens automatically every 4 hours)
Communication on Edge machine:
- Management Console -> Edge Transport -> Send
Connectors Tab -> Should contain something like:edgesync – default-first-site-name to internetedgesync – inbound to default-first-site-name
- On Edge and Exchange machines, open powershell and
run Get-AcceptedDomain. Verify they match.
Anti-Spam Content Filtering:
- On your edge server, you can modify all the filter
to suit your needs.
Mailboxes for your Domain Users:
- On the Exchange server, Management Console -> Recipient
Configuration -> Mailbox -> New Mailbox.
encounter sync issues within your mailboxes related to OAB (offline address
book) errors. I don’t know how to clear it up immediately, but if you wait up
to 24 hours these issues will resolve themselves.