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

Common symptoms:

  • public DNS is configured correctly;
  • in Outlook 2007/2010, 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 2007/2010 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. 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
      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
  2. 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
  3. 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
  4. 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.
    The fix is to create the following Registry keys on necessary machines:
    Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\12.0 (14.0, 15.0, 16.0 depending on Outlook version(\Outlook\AutoDiscover 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
    ExcludeSrvLookup 1
    ExcludeSrvRecord 1

    Go back to top