Hi everyone,
I am seeking advice on how to best set up autodiscover in our scenario for exchange 2013.
We have a number of users who configure outlook on non-domain joined machines and they currently receive a certificate issue when configuring outlook. This is because the first URL outlook tries to contact for autodiscover is:
https://domain.com.au/AutoDiscover/AutoDiscover.xml
Now, our web services team have a catchall on the 'domain.com.au' website, so when you browse to the URL above, it actually does respond with a '404 not found' page that was designed by our web team. Also, because there is a certificate associated, it returns a certificate error to outlook.
If the user clicks 'Yes' to the certificate, outlook then tries the next URL which is:
https://autodiscover.domain.com.au/AutoDiscover/AutoDiscover.xml
This URL works fine because we have autodiscover.domain.com.au set up to resolve to our load balancer (which load balances the CAS machines).
My question is, what do we do about outlook (and maybe other devices) always trying the first URL and failing because the website does actually respond? Is the easiest thing to do to se if our web services team will stop the default '404 not found' for that URL and let it not actually resolve to anything, so that outlook will silently move on and try the next autodiscover URL?