Unexpected Autodiscover behavior when you have registry settings under the \Autodiscover key

Symptoms
When Microsoft Outlook tries to retrieve Autodiscover information from a server that is running Microsoft Exchange Server, you may experience unexpected results if you are using one or more of the available registry values that can be used to control Autodiscover.
Cause
When Outlook tries to contact the Autodiscover service on the Exchange server with the Client Access Server (CAS) role, it can use several different methods to reach the service, depending on the client-server topology. The currently implemented methods used by Outlook are as follows:

  • SCP lookup
  • HTTPS root domain query
  • HTTPS Autodiscover domain query
  • Local XML file
  • HTTP redirect method
  • SRV record query
  • Cached URL in the Outlook profile (new for Outlook 2010 version 14.0.7140.5001 and later versions)
  • Direct Connect to Office 365 (new for Outlook 2016 version 16.0.6741.2017 and later versions)

By default, Outlook will try one or more of these methods if it is unable to reach Autodiscover. For example, in a scenario with a machine not joined to a domain Outlook will try to connect to the predefined URLs (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.xml) by using DNS. If that fails, Outlook will try the HTTP redirect method and, failing that, 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.

Please see the Exchange Autodiscover Service White Paper appropriate for your version of Exchange for details on all of the different Autodiscover connection methods used by Outlook.

Exchange 2013 Autodiscover service:White Paper: Understanding the Exchange 2010 Autodiscover Service:White Paper: Exchange 2007 Autodiscover Service: In some scenarios, however, you may want to use Autodiscover-related registry/policy values to control the method(s) used by Outlook to reach Autodiscover. However, if you configure the Autodiscover registry/policy values incorrectly, you may prevent Outlook from obtaining Autodiscover information.
Resolution
To resolve this problem, please review the Autodiscover-related registry data you may have on your Outlook client to ensure the data is configured correctly. Also, if you are unsure if the registry data is needed, consider changing the data for any of these registry values to zero (0) and then test Outlook to see if you experience a difference in Autodiscover.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, go to the following article in the Microsoft Knowledge Base:
  1. Start Registry Editor.
    In Windows 10 and Windows 8, press the Windows Key + R to open a Run dialog box. Type regedit.exe and then press OK.
    In Windows 7, click Start , type regedit in the Search programs and files box, and then press Enter.
  2. Locate and then select the following registry subkey:

    HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover

    Notex.0 in this registry path corresponds to the Outlook version (16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007).
  3. Review the following possible DWORD values that may be located under the \Autodiscover subkey.

    • PreferLocalXML
    • ExcludeHttpRedirect
    • ExcludeHttpsAutoDiscoverDomain
    • ExcludeHttpsRootDomain
    • ExcludeScpLookup
    • ExcludeSrvRecord
    • ExcludeLastKnownGoodURL (only applies to Outlook 2010 version 14.0.7140.5001 and later versions)
    • ExcludeExplicitO365Endpoint (only applies to Outlook 2016 version 16.0.6741.2017 and later versions)

    Note Some documentation states that the ExcludeSrvLookup value is used by Outlook in this scenario. Unfortunately, this documentation is incorrect as the ExcludeSrvLookup value does not exist in Outlook code. Only the ExcludeSrvRecord registry value is used by Outlook to control the SRV record lookup for Autodiscover. Therefore, if you find a value called ExcludeSrvLookup under the \Autodiscover subkey, you can safely change its value to 0.

  4. Repeat step 3 by using the following registry subkey:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\x.0\Outlook\AutoDiscover

    Note x.0 in this registry path corresponds to the Outlook version (16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007).
More information
You can use the following steps in Outlook to determine the method by which Outlook is trying to retrieve Autodiscover information from Exchange:

  1. Start Outlook.
  2. Press the CTRL key, right-click the Outlook icon in the notification area, and then click Test E-mail AutoConfiguration.
  3. Verify the e-mail address is correctly entered in the E-mail Address box.
  4. Enter your password if you are not logged into a domain or if you are accessing a mailbox that is different from your mailbox.
  5. Click to clear the Use Guessmart and the Secure Guessmart Authentication check boxes.
  6. Click Test.
  7. Review the details on the Log tab.
The following figure shows the Log tab when the ExcludeScpLookup and ExcludeHttpsAutoDiscoverDomain values have been set to 1.

The screen shot that shows the Log tab when the ExcludeScpLookup and ExcludeHttpsAutoDiscoverDomain values have been set to 1.

Compare this information when only the ExcludeScpLookup value is set to 1.

The screen shot that shows the Log tab when only the ExcludeScpLookup value is set to 1

Note Ignore the failures in these figures because this information is intended only to show you the different lookup attempts that are made by Outlook.

Also, if you enable logging in Outlook (2007 or 2010), the different Autodiscover lookup attempts can be found in the %temp%\Olkdisc.log file. This log file also includes any registry settings you have configured to exclude any of the Autodiscover lookup methods. In the following figure, you can clearly see that the ExcludeScpLookup and ExcludeHttpsAutoDiscoverDomain values are both set to 1.

The screen shot for the content in the Olkdisc.log file.

For more information about the client-side management and administration of Autodiscover, go to the following Knowledge Base article:

2612922 How to control Outlook AutoDiscover by using Group Policy
Ιδιότητες

Αναγνωριστικό άρθρου: 2212902 - Τελευταία αναθεώρηση: 11/17/2016 16:01:00 - Αναθεώρηση: 15.0

Outlook 2016, Microsoft Outlook 2013, Microsoft Outlook 2010, Microsoft Office Outlook 2007

  • KB2212902
Σχόλια