Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Exchange / Outlook 2016 Slow External Autodiscover with Exchange Server

June 24, 2016 Exchange

Outlook 2016 Slow External Autodiscover with Exchange Server

Starting from Outlook 2007, the client application uses Autodiscover web service to automatically configure the client access settings to Exchange server. For internal clients, the procedure is quite simple: start Outlook and click “Next” till you get access to your mailbox. The external clients have to specify the e-mail address, the password, and UPN if it differs from the e-mail address. During the connection, the external client can face a problem that configuration might delayed for several minutes (up to 10 minutes).

Outlook External autodiscover scheme

It is related to the fact that the client is searching the settings file (Autodiscover.xml) in some ways preconfigured in the Outlook and unchangeable.

Here is what the process looks like on the example of contoso.com domain:

  • The HTTPS request to the domain root (https://contoso.com/Autodiscover/Autodiscover.xml)
  • The HTTPS request to Autodiscover record (https://contoso.com/Autodiscover/Autodiscover.xml)
  • Local XML file
  • HTTP redirection (http://contoso.com/Autodiscover/Autodiscover.xml, waiting for HTTPS URL redirection)
  • Search using SRV DNS record (search of SRV record _autodiscover._tcp.contoso.com)
  • Cached URL in the Outlook profile (if the previous Autodiscover process has been successful)

In real life everybody adds autodiscover.contoso.com record and believes that everything will be ok, but sometimes the expectations are not met. Nobody makes Autodiscover.xml available by the link containing the root of the domain, though this variant is a priority one. It is not clear why the client checks the dead variant first, but it is just the case.

The problem with the long waiting time appears when the name contoso.com leads to some IP address, which either doesn’t respond on the port 443 or is unavailable. Outlook autodiscovering is standing and waiting for the response. Finally, it encounters operation timeout and goes to the next method. Timeout lasts for several minutes and doesn’t make the work convenient.

The problem is eliminated if the name contoso.com leads to a web-site or any web-server with the available port 443. Then it will take Outlook several seconds to make sure that the first variant doesn’t work.

dns a record

If you have faced this issue, just create the record @ leading to the IP of your website in the external area of the root. In case of DNS in Windows Server, create an empty record in the root.

root a record

The situation doesn’t take place often, but make sure if there is a redirection. It is optional, especially if the mail domain is not connected with some website.

In Outlook 2016 developers have decided to completely cut it out the ability to manually configure the connection to the Exchange. Now the Exchange mailbox configuration is possible only through auto-discovery. Active Sync protocols, POP and IMAP are still adjusted manually.

Outlook 2016 may skip certain methods of autodiscover. To do this, create in the registry branch HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\ new DWORD  key with the value 1. The possible key names:

  • ExcludeHttpsRootDomain
  • ExcludeScpLookup
  • ExcludeHttpsAutoDiscoverDomain
  • ExcludeHttpRedirect
  • ExcludeSrvRecord

For example, to disable the HTTPS request to the root domain, you need to create a key with the name ExcludeHttpsRootDomain and value 1.

reg.exe add HKCU\Software\Microsoft\Office\16.0\Outlook\AutoDiscover /v ExcludeHttpsRootDomain /t reg_dword /d 0x1 /f

ExcludeHttpsRootDomain

As a result, when you start Outlook, this check is not performed, and the first launch of the Outlook performed significantly faster.

1 comment
1
Facebook Twitter Google + Pinterest
previous post
Process Priority Management in Windows
next post
How To Run TSADMIN.msc and TSCONFIG.msc Snap-Ins on Windows Server 2012 RDS

Related Reading

Managing Exchange Mailbox Inbox Rules with PowerShell

August 29, 2019

Fix: Outlook 2016/2013 Always Starts in Offline Mode

July 30, 2019

Configuring Anti-Spam Protection on Exchange 2013, 2016 –...

June 5, 2019

How to Blacklist/Block Sender Domain or an Email...

June 3, 2019

How to Import and Export Mailbox to PST...

April 19, 2019

1 comment

J Painter April 13, 2017 - 10:10 pm

We were having this exact problem because our root domain is the same as our website. The issue had started recently though so I was pretty sure it was due to a change. Sure enough, we had enabled Windows firewall on our domain controllers and now the traffic on 443 gets discarded so AutoDiscover does not get any sort of response and gets stuck in a lengthy loop just like described in this article. Allowed 443 on the DCs and the issue was resolved!

Thanks for this post!

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Follow us

woshub.com

Recent Posts

  • VMWare: How to Find VMs by IP or MAC Address?

    December 13, 2019
  • The Disk is Offline Because of Policy Set by an Administrator

    December 12, 2019
  • How to Backup Hyper-V Virtual Machines?

    December 10, 2019
  • How to Change a Network Location from Public to Private on Windows 10/Windows Server 2016?

    December 9, 2019
  • Configuring Storage Replica on Windows Server 2016

    December 4, 2019
  • Windows 10 Install Error 0x80300024

    December 2, 2019
  • Running PowerShell Script (*.PS1) as a Windows Service

    November 27, 2019
  • Creating Multiple Partitions on a USB Drive in Windows 10

    November 26, 2019
  • VMWare vSphere: Failed to Upload Files to Datastore

    November 21, 2019
  • How to Delete Old User Profiles Using GPO and PowerShell?

    November 19, 2019
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Manage Domains and Email Address Whitelist in Exchange Server 2013
  • How to Move and Truncate Logs in Exchange 2013
  • Calculating the Number of Client Access Licenses (CAL) for Exchange Server
  • Export Exchange Global Address List (GAL) to CSV
  • Stellar Exchange Toolkit: All-In-One Admin Utility
  • Managing Disconnected Mailboxes in Exchange Server
  • Sending Email via Telnet Using SMTP Authentication
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top