When migrating from an in-house Exchange to Intermedia Exchange, you may encounter issues with Outlook still trying to retrieve Autodiscover configuration from local Active Directory.

Common symptoms:

  • public DNS is configured correctly;
  • in Outlook users get a password prompt for their old server (it may come up after prompting the user for Intermedia Exchange server or when the user is trying to access out of office assistant settings);
  • users cannot send folder sharing invitations;
  • running Autodiscover test in the user’s Outlook shows links to the old server;
  • a common fix to put a record for the Autodiscover server into the hosts file does not work (read the Knowledge Base article on How To Find And Modify Entries In The HOSTS File for more information).

Possible fixes:

The cause for the issue is that Outlook is trying to access the Autodiscover settings from the local Active Directory. Below are a few possible fixes:

1. Adding Registry values for Outlook to exclude SCP object check 
If you have users on the in-house Exchange server that are not supposed to be migrated to Intermedia at all, this can sometimes result in inability to really remove SCP object from Active Directory completely or update AutoDiscoverServiceInternalUri (because some users users are located on the old server). The fix also applies if you don't have access to the in-house servers.

Note: Public Autodiscover DNS record should be pointing to Intermedia.

Important: Back up the registry first and be careful when making any changes to it as any incorrect action may result in the OS crash.

The fix is to create the following Registry keys on necessary machines:

Open regedit: to do so, click the Start button and then in the Start Menu, either in the Run box or in the Search box, type regedit and press EnterRegedit

Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover (x.0 corresponds to the Outlook version: 16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007) and create these DWORD values to excude all checks before ExcludeHttpRedirect which is used in Intermedia:

PreferLocalXML 0
ExcludeHttpRedirect 0
ExcludeHttpsAutodiscoverDomain 1
ExcludeHttpsRootDomain 1
ExcludeScpLookup 1
ExcludeSrvRecord 1

For Outlook 2010 version 14.0.7140.5001 and later versions, please also add the following DWORD:

ExcludeLastKnownGoodURL 1

For Outlook 2016 version 16.0.6741.2017 and later versions, please also add the following DWORD:

ExcludeExplicitO365Endpoint 1

Note: You may also need to add the same DWORD values to the following registry path: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\x.0\Outlook\AutoDiscover 

You can also export this set of records into a .reg file and import it to Registry on another affected machine.

Go back to top

      2. Setting Autodiscover settings through PowerShell 
      Run the following cmdlets on the in-house server to adjust its behaviour:

      • Get-WebServicesVirtualDirectory

        Run the following cmdlets:
        Set-WebServicesVirtualDirectory -Identity yourservername\EWS* -InternalUrl https://ExchangeProxyServer/EWS/Exchange.asmx
        Set-WebServicesVirtualDirectory -Identity yourservername\EWS* -ExternalUrl https://ExchangeProxyServer/EWS/Exchange.asmx
        Note: if you have more than 1 server running, use a full EWS path to the necessary instance instead of EWS*.  For example: -identity "yourservername\EWS (Default Web Site)"
        The Exchange Proxy Server settings can be found under Home > Exchange Servers & Settings > Exchange Proxy Setting.
      • Get-ClientAccessServer

        Run the following cmdlet:
        Set-ClientAccessServer –Identity yourservername –AutoDiscoverServiceInternalUri https://ExchangeProxyServer/Autodiscover/Autodiscover.xml

      Go back to top

        3. Fixing the local DNS records 
        If you have a local DNS server and a pop up for the old Exchange server appears, the cause of the issue might be the local DNS overriding Intermedia Autodiscover settings. Set autodiscover.yourdomainname.com on the local DNS server to the IP for the Autodiscover record as shown in HostPilot:

        Go back to top

          4. Redirecting to Intermedia Autodiscover server in IIS 
          If a password prompt for the old server pops up and the Test Email Autoconfiguration utility shows the local server's URLs, that means the Autodiscover settings were pulled directly from AD. To fix that, navigate to IIS manager > Default Web Site > Autodiscover > Properties (or IIS manager > Default Web Site > Autodiscover > HTTP Redirect)  and set the page to redirect to https://ExchangeProxyServer/autodiscover (you can try https://ExchangeProxyServer/autodiscover/autodiscover.aspx as well)..

          Go back to top