When checking Edge Synchronization on our Exchange 2010 HUB server (Test-EdgeSynchronization) I get SyncStatus "Failed". I suspect this failed after we had moved all of our Exchange 2010 servers (Except the Edge server which not member of any domain or site) to a new site. In hopes to resolve this, I did the following:
- Removed the Edge Subscription from our HUB server using the EMC.
- Deleted the cert used by ADAM on our Exchange 2010 Edge server (using the Certificates MMC).
- On the Exchange 2010 Edge server created a new Edge subscription file using: “New-EdgeSubscription –FileName "C:\EdgeSubscription20150424.XML"
- Restarted the "Microsoft Exchange ADAM" service on our Edge server.
- Copied the "EdgeSubscription20150424.XML" to our HUB server. Then completed the New Edge subscription import on our HUB server using the MMC (specifying the AD site and location/name of the XML).
After this, I still get syncstatus failed on our HUB. Thought to check the certificate using "Get-ExchangeCertificate | FL" but that results in: "Get-ExchangeCertificate : The Exchange Certificate operation has failed with an exception. The error message is: Access is denied". I tried to create a new certificate on our HUB serve using "New-ExchangeCertificate", but get the exact same "Access is denied" error message again.
I believe we never noticed that the Edge sync wasn't working because we only use our Edge server when our hardware email filter fails (Symantec Message Gateway). Our Edge server has a lower priority in our MX record and lower priority in our send connectors on our HUB servers. The Edge server though does receive email from internal email relay from some servers for notifications. These do get delivered unless the user mailbox is new (suspect ADAM isn't updating - that's why I started looking into this).
This should be simple! What am I missing??? Thanks in advance for any feedback.
PS - this is my first posting here.... I apologize if I posted this in the wrong forum or category. :)