Jump to content

Recommended Posts

Posted

Hi,

 

A third party set up our Exchange 2010 server some years ago (an upgrade from 2003). We have OWA configured and everything works great. We are now performing a hybrid migration to Office 365.

 

We have been advised to test connection to autodiscover via the Microsoft Connectivity Analyser. This fails (the autodiscover service cannot be contacted)

Microsoft Connectivity Analyser looks for autodiscover.xml in a number of variants on our domain name : https://autodiscover/ourdomain.com/autodiscover/autodiscover.xml etc.

 

Our mail server URL is mail.ourdomain.com

If I manually go to https://mail.ourdomain.com/autodiscover/autodiscover.xml, I do get an XML file open in the browser.

 

Our ISP have no DNS records for autodiscover...

 

I'm a bit stuck, is it possible that autodiscover isn't set up?

Posted
You will need autodiscover as a San on your public as cert though as it runs over https

 

All sorted thanks - I've tested it with the Microsoft Connectivity Analyser & I've now successfully run the 'manage hybrid configuration' wizard from within Exchange without errors... although it does throw a warning : Unable to verify the Certificate on Client Access Server MY-EXCHANGE-SERVER with Thumbprint ***** against a trusted Certificate Authority.

 

I have a feeling this is because the FQDN of Exchange (when accesses locally) is MY-EXCHANGE-SERVER.MYDOMAIN.INTERNAL

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...