regarding the custom xml for autodiscover. I heard the autodiscover service will also work if there is a mail-user or contact in place, representing a subdomain for user B. can you comment on this?
24 Apr 2010 8:54 AM
that is correct, as described in the link you provided, the use of the xml file could be a solution in these cases
Ilse
Greg Mohr
16 Feb 2011 2:06 AM
I have a client using Win 7 Pro 64bit and Outlook 2010. The host server is Win 2K, running Exchange 2003. The autodiscover worked fine until the physical office moved two weeks ago. The model the company wants is to access the exchange server over the VPN. IT worked for the last 4 months with the new laptop, now the Wan IP changed and it does not work at all. The vpn is using a dynip naming so there is no issue, it finds the new Wan IP fine. The internal network and naming has not changed at all. I can;t figure this out. I am also currently waiting for a call back from a major impact tech support and have been waiting over 6 hrs with no call back and 4 follow up calls to try and get an engineer on the phone. I am pulling my hair out. Any suggestions would be greatly appreciated!
Ben
13 Jan 2015 10:12 PM
Sorry for the legacy commenting ! Hopefully my 5 cents can give some additional help to someone.
Reading over 20 articles, this is by far the best one !
Our Internal/ExternalUrl is webmail.domain.com. For some reason when our server was setup 6 years ago (Exchange 2007), the Autodiscover path was set to webmail.domain.com/Autodiscover/Autodiscover.xml. The certificate issued only included this name. After going
through the above steps, autodiscover worked but I got error 401 like this poor chap:
https://social.technet.microsoft.com/forums/exchange/en-US/4630d29f-75d4-4340-bb1b-c19cd130ab30/autodiscover-error-401
I managed to fix this by when asked for credentials I chose "other user" and used "domain\user" instead of standard "user".