After migrating mailboxes to Exchange 2016 or Office 365, Archive Manager fails to use Autodiscover. (4305554)

After migrating mailboxes from Exchange 2010 to 2016 or Office 365, the Exchange Store Manager fails to scan the mailboxes or the Dataloader cannot connect to the journal mailbox.

The following error may be seen in the mailbox wlog:

Before attempting the workarounds listed here, please first ensure you are running a supported version of Outlook on the archive server. Information about prerequisites and supported versions of Outlook can be found in the Archive Manager Administration Manual here: https://support.quest.com/technical-documents/archive-manager/5.7/administration-guide

WORKAROUND 1

Open the Archive Manager Configuration Console | Advanced settings and add the following:

If the Exchange Store Manager is failing to connect to mailboxes add:

Exchange Store Manager Use AutoDiscover

Set the value to True

If the Dataloader is failing to connect to the Journal mailbox add:

MAPI Data Loader Use AutoDiscover

Set the value to True

Restart the Archive Manager Exchange Store Manager and the Archive Manager Data Load services and monitor the logs for errors.

WORKAROUND 2

If WORKAROUND1 does not work, try setting the following locally on the Archive Manager Server. 

Note: You may need to remove MAPI Data Loader User AutoDiscover and Exchange Store Manager User AutoDiscover 

We cannot bypass autodiscover, otherwise the outlook will not function well, but we do have some other ways to make autodiscover following the local xml file or bypass the local cache.

Troubleshooting for autodiscover:

1. Autodiscover priority :

1. SCP

For domain joined users, they should follow the local SCP result first, but not public DNS result.

2. Public DNS

If the SCP failed, or it is not a domain joined machine, it will follow the public DNS. 

2. For next, I would like to suggest if we can check the SCP result first.

Exchange management PowerShell: >Get-ClientAccessServer |fl autodiscover*

               To make sure if the Uri and site scope are correct

3. Test the autodiscover uri from client machine. We can visit the uri from any browser and it should return 600 error, otherwise we will need to focus on fixing autodiscover services.

Bypass last known good url (local cache for autodiscover result):

1. Sometimes the issue was caused by local cache.

Here is the key to bypasss the local cache and outlook will ask server to get new result from autodiscover.

2. Create a key from local machine or deploy it by GPO.

HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\Autodiscover
DWORD: ExcludeLastKnownGoodUrl
Value: 1

*In the above registry path corresponds to the Outlook version:

16.0 - Outlook 2016, 2019, Office 365

15.0 - Outlook 2013

To use local autodiscover result (.xml):

1. If SCP still not able to get through, we could use local .xml file to modify the autodiscover result.

Sample: Exchange SCP: https://serverFQDN/autodiscover/autodiscover.xml

2. Create GPO to bypass Autodiscover (simulate AutoDiscover record) by replicating the required RegKey below.

HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover
*same as bypass last known good url, please remove all the existing key from the above path

3. And add the keys below.
   1. 1. Domain -> File path
      2. Pferferlocal xml -> Value: 1

XML file:

http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">

      email

      redirectUrl

      https://SERVERFQDN/autodiscover/autodiscover.xml>