There are a lot of pieces involved in autodiscover. There are some other places you also need to look. The entire process is explained fairly well here:
https://msdn.microsoft.com/en-us/library/office/jj900169(v=exchg.150).aspx From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Beahm, Keith Sent: Thursday, November 17, 2016 1:15 PM To: exchange@lists.myitforum.com Subject: [Exchange] Autodiscover redirect behavior We have Autodiscover working internally via SCP for Outlook clients, but when I test with our primary mail domain (i.e., x...@stinson.com<mailto:x...@stinson.com>) externally I keep getting redirect responses that reference a legacy mail domain URL (stinsonleonard.com), and if I use the same account with a legacy mail domain SMTP the MCA test yields reverse results (i.e., sameu...@stinsonleonard.com<mailto:sameu...@stinsonleonard.com> yields MCA results with a redirect to https://www.stinson.com/...). I have checked all my CAS servers, and all the OWA and EWS virtual directories and found nothing that explains this redirect behavior. I verified that my load balancers don’t have URL redirect configured for this, though they do have an 80->443 redirects. I cannot figure out what element is issuing the redirect URL, and specifically how to correct the behavior. Exchange 2010 SP2 RU4, Netscaler MPX8005, with single Content Switch for OA, EAS, and OWA. The Content Switch references two LB servers, one for EAS and the other for OA & OWA. Thank you for your time and effort, any suggestions would be appreciated. A segment of the MCA test results; The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://stinson.com:443/Autodiscover/Autodiscover.xml for user malcolm.reyno...@stinson.com<mailto:malcolm.reyno...@stinson.com>. The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. Additional Details A redirect response was received, but only HTTPS redirect URLs are supported in response to a POST request. The URL that was received was http://www.stinsonleonard.com?aspxerrorpath=/Autodiscover/Autodiscover.xml. HTTP Response Headers: Cache-Control: private Content-Type: text/html; charset=utf-8 Location: http://www.stinsonleonard.com?aspxerrorpath=/Autodiscover/Autodiscover.xml Set-Cookie: EktGUID=57515121-45fa-4305-90fd-9aacd39089a4; expires=Fri, 17-Nov-2017 15:14:24 GMT; path=/,EkAnalytics=0; expires=Fri, 17-Nov-2017 15:14:24 GMT; path=/,ecm=user_id=0&isMembershipUser=0&site_id=&username=&new_site=/&unique_id=0&site_preview=0&langvalue=0&DefaultLanguage=1033&NavLanguage=1033&LastValidLanguageID=1033&DefaultCurrency=840&SiteCurrency=840&ContType=&UserCulture=1033&dm=stinson.com&SiteLanguage=1033&dvcMdl=Generic&dvcOs=Generic&dvcType=1; path=/ Server: X-Powered-By: ASP.NET Date: Thu, 17 Nov 2016 15:14:24 GMT Content-Length: 191 Keith D. Beahm | Messaging and Storage Architect | Stinson Leonard Street LLP 1201 Walnut Street, Suite 2900 | Kansas City, MO 64106-2150 T: 816.691.3374 | M: 816.808.8983 | F: 816.412.1022 kbe...@stinson.com<mailto:kbe...@stinson.com> | www.stinson.com<http://www.stinson.com> This communication (including any attachments) is from a law firm and may contain confidential and/or privileged information. If it has been sent to you in error, please contact the sender for instructions concerning return or destruction, and do not use or disclose the contents to others.
