Read time 5 minutes
When you have installed the new Exchange Server 2016 on your Windows Server and want to configure the Exchange account in Outlook, there is a useful feature called Autodiscover. The Autodiscover feature facilitates the user to only input the user ID, and password and the account gets configured automatically. The Autodiscover finds the EWS (Exchange Web Services) endpoint in the URL for the clients. The automatic configuration using Autodiscover is possible as:
But if Autodiscover is not active, then the account will not be set, and you will have to face the following error –
OR
Your account was redirected to this website for settings. You should only allow settings from sources you know and trust.
The cause behind the error is the IIS Services is not active by default in the server manager. The Autodiscover feature is the sub-service of the IIS Server, and it will be activated only when the IIS Server is in the activated state. It is possible that:
Also, you can check some points to make sure the error is not occurring due to them:
The Autodiscover service will only work when the IIS Services is active. So, you need to start the IIS for it. Follow the below procedure –
There are some end-user-level solutions to fix Autodiscover issues. However, these are mainly considered as workarounds only as the real solution needs to be on server-level. So, we are just mentioning them only.
There is a ‘ClientAccessServer’ PowerShell cmdlet in Exchange that you can run in Exchange Management Shell and check the default Autodiscover URL for your network. Here is the basic example of running the ClientAccessServer command.
The result will inform the default URL of Autodiscover service, its scope, and the name of Exchange Server.
If your registry settings for Autodiscover are incorrect, you need to edit them to provide correct values. If there are no settings, you need to create them.
If the account is still not configuring automatically, the problem may be different, and you need to run other diagnostics tools to check corruption in the database. You can try the ESEUTIL tool to repair the database. But the ESEUTIL tool can further damage the situation by deleting the corrupted data and creating blank spaces. That’s why you should use a trustworthy professional Exchange Recovery tool that can remove the corruption and recover the complete data.
It is a special EDB to PST converter tool which scans the EDB file of any version of Exchange Server and repairs it using a suitable scan mode based on the level of corruption. It repairs corrupt Exchange Database and retrieves the mailboxes as they were in the database. You can save the data in a useful Outlook PST file or directly migrate it to live Exchange or Office 365 cloud platform.