This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have just stood up an exchange 2019 server in a domain with a 2013 server and have everything working except the autodiscover virtual directory.
when I try to access I get an access denied after authenticating.
I have tried removing and recreating it. tried various authentication configurations. I am at a loss as to what to try next.
Hi @Jonathan P. Foster ,
I understand that you are encoutering issues about Autodiscover in Exchange 2019, in order to further confirm your issue, please provide us with the steps to reproduce the problem and the screenshot of your error(Notice: Please hide your personal information in the screenshot for security.)
Also, when autodiscover couldn't work normally, we could test Email Auto-configuration in Outlook client to further confirm which step has error(press "ctrl" + right-click outlook icon in the bottom right corner>choose test Email Auto-configuration>type your email address and password, uncheck other option other than "use Autodiscover">test ).
more information
I tried what you suggested but only got back "Autoconfiguation was unable to detirmine your settings"
when I try to use a browser to log into https://mail.sitename.com/autodiscover/autodiscover.xml I do not get anything. it just hangs there usually.
when I do get a response its usually Error: 503 service unavailable or 403 access denied
even viewer just returned this:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
here is the output of the test email autoconfiguration
Success!
I wound up getting all the settings correct and I was sure it should be working.
I realized that the account I was testing with had its mailbox on another server.
So on a hunch I migrated a mailbox to the new 2019 server and restested and it worked flawlessly.
Hi @Jonathan P. Foster ,
Thanks for your sharing, looks like it‘s raleted to the unmigrated mailbox and has been fixed after you migrated it, is it right?
If so, due to the issue has been resolved, it's recommended to mark your solution to an answer, which would benefit others who also have similar issues find relevant information. Thanks for your understanding.