Exchange Autodiscovery Problems
When I run the Exchange Server Remote Connectivity Analyzer, I get these results:
Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name autodiscover.mydomain.com in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.mydomain.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Test Steps
ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml for user testuser@mydomain.com.
ExRCA failed to obtain an Autodiscover XML response.
Additional Details
None of the expected XML elements were found in the XML response.
I ran 'test-outlookwebservices -Identity "Test User" | fl' and received no error or warning messages:
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1006
Type : Information
Message : Contacted the Autodiscover service at https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1016
Type : Information
Message : [EXCH] The AS is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1015
Type : Information
Message : [EXCH] The OAB is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1014
Type : Information
Message : [EXCH] The UM is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1016
Type : Information
Message : [EXPR] The AS is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1015
Type : Information
Message : [EXPR] The OAB is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1014
Type : Information
Message : [EXPR] The UM is configured for this user in the Autodiscover response received from https://roex.mydomain.local/Autodiscover/Autodiscover.xml.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1022
Type : Success
Message : Autodiscover was tested successfully.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1024
Type : Success
Message : [EXCH] Successfully contacted the AS service at https://roex.mydomain.local/EWS/Exchange.asmx. The elapsed time was 70 milliseconds.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1026
Type : Success
Message : [EXCH] Successfully contacted the UM service at https://roex.mydomain.local/EWS/Exchange.asmx. The elapsed time was 40 milliseconds.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1024
Type : Success
Message : [EXPR] Successfully contacted the AS service at https://owa.mydomain.com/EWS/Exchange.asmx. The elapsed time was 451 milliseconds.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1026
Type : Success
Message : [EXPR] Successfully contacted the UM service at https://owa.mydomain.com/EWS/Exchange.asmx. The elapsed time was 39 milliseconds.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1124
Type : Success
Message : [Server] Successfully contacted the AS service at https://roex.mydomain.local/ews/exchange.asmx. The elapsed time was 48 milliseconds.
RunspaceId : 5f3302db-4a12-4cf9-99df-70743048e4c8
Id : 1126
Type : Success
Message : [Server] Successfully contacted the UM service at https://roex.mydomain.local/ews/exchange.asmx. The elapsed time was 39 milliseconds.
The only thing that I could think of that might throw it off is that the Connectivity Analyzer is checking 'autodiscover.mydomain.com' which is an alias for 'owa.mydomain.com', but 'autodiscover.mydomain.com' is not configured on the Exchange server. Is
there anything else I should be looking at?
Thanks.
May 17th, 2011 12:20pm
Hello,
For Internal Outlook clients, it resolve the autodiscover from SCP. And for the External Outlook clients, it uses the DNS “autodiscover.company.com”
to resolve the autodiscover. Therefore, you need to have a public record for the “autodiscover.company.com” and point it to the Internet facing CAS server.
If you have further question, please let us know.
Thanks,
Simon
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2011 11:38pm
Here are some nice Autodiscover reading, the whitepaper is really good!
http://technet.microsoft.com/en-us/library/bb124251.aspx
http://technet.microsoft.com/en-us/library/bb332063%28EXCHG.80%29.aspxJonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog:
http://www.testlabs.se/blog | Follow me on twitter:
jonand82
May 23rd, 2011 3:40am