Troublshooting Autodiscover (Exchange 2007/2010)

What is Autodiscover?

Exchange Autodiscover is a service which is run on Exchange Client Access Servers. It is one of the new features it included in exchange 2007.
The Autodiscover service makes it easier to configure Outlook 2007 or Outlook 2010 and some mobile phones. Autodiscover Service cannot be used with earlier versions of Outlook, including Outlook 2003. In earlier versions of Microsoft Exchange (Exchange 2003 SP2 or earlier) and Outlook (Outlook 2003 or earlier), you had to configure all user profiles manually to access Exchange.

The Autodiscover service uses a user's e-mail address and password to automatically configure a user's profile. Using the e-mail address, the Autodiscover service provides the following information to the client:

  • The user’s display name.
  • Separate connection settings for internal and external connectivity.
  • The location of the user’s Mailbox server.
  • The URLs for various Outlook features that manage functionality such as OOF, free/busy information, Unified Messaging, and the offline address book.
  • Outlook Anywhere server settings.

How the Autodiscover Service Works

When you install the Client Access server role on a computer running Exchange 2010/2007, a default virtual directory named Autodiscover is created under the default Web site in Internet Information Services (IIS). This virtual directory handles Autodiscover service requests from Outlook 2007 or Outlook 2010 clients and supported mobile phones under the following circumstances:

  • When a new user account is configured or updated.
  • When an Outlook client periodically checks for changes to the Exchange Web Services URLs.
  • When underlying network connection changes occur in your Exchange messaging environment.

Additionally, a new Active Directory object named the service connection point (SCP) is created on the server where you install the Client Access server role. And Autodiscover information is stored in it.

You can view this SCP using Active Directory Sites and Services after you have enabled the “View Services Node” option:

  • The SCP object is used by domain-connected clients to locate the Autodiscover service.
  • The SCP object contains two pieces of information:

                  - The serviceBindingInformation attribute.

               - The keywords attribute

The serviceBindingInformation attribute has the Fully Qualified Domain Name (FQDN) of the Client Access server in the form of:, where is the fully qualified domain name (FQDN) for the Client Access server.

The keywords attribute specifies the Active Directory sites to which this SCP record is associated. By default, this attribute specifies the Active Directory site to which the Client Access server belongs.

When a domain-connected client connects to the Active Directory directory service:
 The Exchange 2007 client authenticates to Active Directory and tries to locate the Autodiscover SCP objects that were created during Setup by using the user's credentials.

      –  In deployments that include multiple Client Access servers, an Autodiscover SCP record is created for each Client Access server. By using the user credentials, the Outlook 2007 client authenticates to Active Directory and searches for the autodiscover SCP objects.

       – After the client obtains and enumerates the instances of the Autodiscover service, the client connects to the first Client Access server in the enumerated and sorted list and obtains the profile information in the form of XML data that is needed to connect to the user's mailbox and available Microsoft Exchange features.

An Outlook 2007/2010 client connects to the Autodiscover service as follows:

1- Outlook 2007/2010 sends a LDAP query to Active Directory looking for all available SCP objects.

2- Outlook 2007/2010 sorts and enumerates the returned results based on the client's Active Directory site by using the keyword attribute of the SCP record. One of two lists is created, an in-site list or an out-of-site list.

3. Outlook first tries to connect to each Autodiscover URL that it had previously generated from either an in-site list or an out-of-site list.

  • If that doesn't work, Outlook will try to connect to the predefined URLs (for example, by using DNS.
  • If that fails also, Outlook will try the HTTP redirect method.
  • If that fails also, Outlook will try to use the SRV record lookup method.
  • If all lookup methods fail, Outlook will be unable to obtain Outlook Anywhere configuration and URL settings.

4. The Autodiscover service queries Active Directory to obtain the connection settings and URLs for the Exchange services that have been configured.

5. The Autodiscover service returns an HTTPS response with an XML file that includes the connection settings and URLs for the available Exchange services.

6. Outlook uses the appropriate configuration information and connection settings to connect to your Exchange messaging environment.

  • When Outlook 2007/2010  is started on a client that is not domain-connected, it first tries to locate the Autodiscover service by looking up the SCP object in Active Directory. Because the client is unable to contact Active Directory, it tries to locate the Autodiscover service by using Domain Name System (DNS). In this scenario, the client will determine right side of the user’s e-mail address, that is,, and check DNS by using two predefined URLs. For example, if your SMTP domain is, Outlook will try the following two URLs to try to connect to the Autodiscover service:


Problems with Autodiscover service or how it’s configured can causes issues such as:

  • Cannot view free/busy information.
  • Cannot download Offline Address Book (OAB) / receive error code: 0x8004010F.
  • The Out Of Office assistant is not working.
  • Prompt for a user name and password during the Autodiscover process.
  • Outlook anywhere stop working.

One of the most common issues I see has to do with certificates, so I will highlight few things about certificates.

Certificates are used to encrypt traffic between exchange servers and clients.

There are three things that need to be true in order for a certificate to be valid:

  1. The name used to access the resource needs match the certificate exactly.
  2. The Certificate date must be valid
  3.  The Certificate Authority which issued the certificate must be trusted by the client. (It needs to exist in the “Trusted Root Certificate Authorities)

Example: If I connect to OWA with, then the certificate also needs to have either on the subject or the subject alternative name field.

The components that are usually affected with certificate name mismatch are Autodiscover, Out of Office, Free Busy and Outlook Anywhere.


1- Not using a trusted certificate

Solution: use a 3rd party cert provider


2- The certificate name does not match the DNS name\s

Solution: create a new cert request containing all the names used to access the server. Minimum of


<InternalName>.domain.local (if using for internal systems also)

3- Can’t resolve fully qualified domain names (FQDN)

Solution: make sure that the FQDNs for your external URLs as well as autodiscover have A records registered in DNS

Verify you can access the autodiscover XML file

It should look like below

4- SCP Record does not contain the correct value.

  1. Test from outlook:

                 - Hold CTRL and Click the outlook Icon in the system tray and select “Test Email Auto Configuration”

                    -  Deselect the “Use Guessmart” and “Secure Guessmart Authentication” and click Test.

        2. Check SCP value returned

                - If you get info on the results tab then AutoDiscover is working


                - If not, go to Log tab and look at the URL that is returned

                - Test the URL (Type it into Internet explorer) if it is not working, change SCP to a valid URL, using Set-ClientAccessServer cmdlet.

                - Set the SCP along with the internal URL: Set-ClientAccessServer CASServerName -AutoDiscoverServiceInternalUri https://mail.domain.local/Autodiscover/Autodiscover.xml

Troubleshooting Free/Busy Information for Outlook 2007/2010

  • The Availability service for Microsoft Exchange Server 2007/2010 provides calendar information for your users, which is known as free/busy information.
  • The Autodiscover service provides information for the Availability service by locating and providing the external and internal URLs for the Outlook 2007/2010 client.
  • There may be problem which involves a failure in either the Autodiscover service or the Availability service.
  • To determine whether the Autodiscover service is unable to provide information to clients by using Outlook 2007, you can enable outlook logging using the following steps:
  1. In Outlook 2007, on the Tools menu, click Options, click the Other tab, and then click Advanced Options.
  2. On the Advanced Options page, select Enable logging (troubleshooting), and then click OK.
  3. Restart Outlook 2007, and then try to view free/busy information for another user.
  4. In Microsoft Windows, click Start, click Run, and then type %temp%.
  5. In Windows Explorer, open the olkdisc.log file and locate the files in the olkas directory.
  6. The information that is contained in this directory can frequently provide information about which service is not functioning correctly.

If you are using outlook 2010, then do the below:

  1. Launch Outlook 2010, Click File, Options, then Click Advanced.
  2. Scroll down to Other, and check the box to enable troubleshooting logging.
  3. Restart Outlook.
  • With logging enabled, a pop up will appear in the system tray reminding you that Outlook logging is enabled, and a header on the top of the outlook window


  • When Outlook launches a log file is generated and updated as the launch occurs. This file is located in your user’s TEMP folder. By default that is in the following location:

Windows XP: C:\Documents and Settings\<User Name>\Local Settings\Temp
Windows Vista and Windows 7: C:\Users\<User Name>\AppData\Local\Temp

You can also use Outlook 2007 to test the AutoConfiguration information that is provided by the Autodiscover service.


  • On the Test E-mail AutoConfiguration page, verify that the check box next to Use AutoDiscover is selected, and then click the Test button.

The following table provides a brief description of error codes that may occur when you test the AutoConfiguration for the Autodiscover service in Outlook 2007.

Exchange 2007 provides two ways for you to determine whether the Availability service is not functioning correctly:

1- Using the Event Log to Troubleshoot the Availability Service

2- Using the Test-OutlookWebServices Cmdlet to Troubleshoot the Availability Service as below:

Test-OutlookWebServices -TargetAddress:

Troubleshooting Autodiscover service

Troubleshooting Autodiscover requires you to understand which part of autodiscover is not working. But generally, It is good practice to find out whether autodiscover working for internal clients or not. Internal clients who are belong to the same network of domain.
Following are some common procedures to check autodiscover configuration:

• Run Test-OutlookWebservices | fl
• Run Test-EmailAutoConfiguration on client to find how autodiscover is connecting and where  exactly it's failing.
• Verify URL for autodiscover. Get-ClientAccessServer | fl
Check for AutodiscoverInternalServerUri attribute.
• You may also access the autodiscover url from IE and in response should get "600 invalid request".
• If autodiscover not working for external client verify authentication on Autodiscover virtual directory and if required you may recreate the virtual directory by running command:

Comments (20)

  1. Anonymous says:

    Nice 1 Malik! Well documented.

  2. Anonymous says:

    Very Helpful and Informative….

  3. Kevin says:

    Thanks for the share.. 🙂



  4. vedha says:

    Can you  explain step by step auto discover configuration with certifications in exchange 2010

  5. Jonathan says:

    "Outlook 2007/2010 sorts and enumerates the returned results based on the client's Active Directory site by using the keyword attribute of the SCP record. One of two lists is created, an in-site list or an out-of-site list."

    Where are the in-site and out-of-site lists stored? I have a situation where an Outlook client has a previously generated out-of-site list, and it keeps wanting to contact the server in that list. That server is still online but it is outside of my control. I want to prevent Outlook from attempting to use that server, so need to flush the out-of-site list.

  6. kas4444 says:

    How do I test email auto-config on Outlook 2011 for Mac?

  7. Manoj says:

    Quite simplified a blog on Autodiscover troubleshoot. It was easy to go thru and understand in one go…


  8. Joe Weaver says:

    I am trying to figure out how all of this complexity actually solves any business problem.  It sure does create some business problems when your vice president's assistant can't schedule a meeting!

  9. John W says:

    We have a new site with domain joined Outlook 2010 clients that are not using SCP. When I run the autodiscover test the logs show it goes straight for the predetermined DNS options, bypassing SCP altogether. In other words, behaving like a non-domain joined client and not bothering to try SCP. Could this be something to do with the keywords attribute? It’s driving me mad!

  10. Jcar says:

    So when mobile clients tries to connect thru autodiscover it first try to use and if it fails tries to use the What if is the the company website which is not the owa of the company? Sometimes our autodiscover will fail when it tries to go to our website for a certificate.

  11. ricardo says:

    Can you explain about troubleshoot when
    •Prompt for a user name and password during the Autodiscover process.

  12. Dhaval Jani says:

    Great Article !!!

  13. Mohammad Athar says:

    Malik This is really great article. Please share more article on Exchange 2010 like mail flow and all. Thank again for this valuable information.

  14. Chris V says:

    We are having the same issues that Jcar mentioned above. Autodiscover is using our domain name but not This is causing several things not to work correctly including OAB and shared mailboxes not showing in Outlook with full access
    permissions (automapping). Any ideas as to what would cause this?

  15. Piotr1 says:

    I fully agree. Many thanks for this very helpful article.

  16. Ankush Kalvikattekar says:

    Thanks. Very helpful

  17. tdi says:

    does anyone have an answer to Jcar ´s question? As this is what happens to us when Mac users with mail or outlook for mac are trying to use autodiscover..

  18. alex says:

    Would anyone know why i can find the settings via Autodiscover for most of my users but there are one or two which fail?
    i get error 0x800C8202

  19. Al Jacobo says:

    Very helpful and informative.

  20. Shyam says:


    we have a single mail server configure with Exchange 2013 CAS & Mailbox. Recently we configured tenant Created autodiscover SRV record in pointing to Earlier Outlook 2013 was not taking the username password for
    and giving credential pop up. After a day also giving the credential pop ups and not authenticating even after putting the password. When tried with owa it gets the password and working ok. What can be the issue?


Skip to main content