Link to home
Start Free TrialLog in
Avatar of J D
J DFlag for United States of America

asked on

Edge Server Subscription

We are implementing a new Edge server into our environment, and are running the New-EdgeSubscription -FileName "C:\EdgeSubscriptionInfo.xml" script to create an Edge subscription.  When we try to do so, we get the error message that is attached into the screen shot.  This is a brand new server, never on the domain, I manually keyed in the dns suffix for the name, we have the dns pointers in place, as well as the ports open on the firewall.  I followed the instructions here, https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=3227-W-FwCEAgAAQACIAAEBAQAAAAQAAAAAwAMAAAA~, but am stuck.  Any suggestions are appreciated.
edge.jpg
Avatar of J D
J D
Flag of United States of America image

ASKER

I was able to get the file created, but now I'm getting another error when trying to run Start-EdgeSynchronization.  Please see the attached screen shot.  Thank you.
edge.jpg
ASKER CERTIFIED SOLUTION
Avatar of Peter Hutchison
Peter Hutchison
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of J D

ASKER

Thank you for your comment Peter.  We are migrating from Exchange 2007 to Exchange 2013, and I am at the step in my migration steps to start the Edge subscription synchronization.  I have done what you have suggested, four times now, and it still gives me a warning that it cannot talk to LDAP server.  I can ping from Edge to EXMBX, and vice versa, I can ping via FQDN.  We have firewall rules in place allowing the 50636 and 50389 ports.  We are running out of options at this point, not sure what else to troubleshoot.
Is the Active Directory LDS role installed and running on the Exchange Edge server? This is required to store the Active Directory configuration settings sync'd from the Domain.
Avatar of J D

ASKER

Yes, we do have the role installed.
Check what SSL/TLS certificates you have on the Edge server. They can be either self-signed or third party ones ,but NOT the same as the ones on Hub Transport servers, and check expiry dates.