How to get ActiveSync working with Exchange 2016 mailbox server when Exchange 2010 server is Transport Hub and Client Access

Quentin Roberts 106 Reputation points

In the process of migrating from Exchange 2010 to Exchange 2016.

Exchange 2010 currently has all our production mailboxes and is working with ActiveSync, Outlook Anywhere, and OWA.

When I move a mailbox from the Exchange 2010 server to the Exchange 2016 server I am unable to connect to ActiveSync as I normally would. I assume this is because Exchange 2010 cannot read Exchange 2016 mailboxes.

What would be the best way to move mailboxes from Exchange 2010 to Exchange 2016 and allow ActiveSync to still work without having to reconfigure our devices to point to a different mail server internet domain for the Exchange 2016 server? Is this possible without reconfiguring the end user ActiveSync devices or moving all of our mailboxes at the same time to the Exchange 2016 server and keeping the same domain settings, just changing the internal routing to the Exchange 2016 server?

I haven't tested Outlook on the LAN to see if autodiscover will pick up the Exchange 2016 server and work that way nor have I tested Outlook Anywhere yet. I assume getting ActiveSync to work will be a similar process for autodiscover and Outlook Anywhere (pointing the mail server domain to the Exchange 2016 server).

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,227 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Yuki Sun-MSFT 40,406 Reputation points

    Hi @Quentin Roberts ,

    When I move a mailbox from the Exchange 2010 server to the Exchange 2016 server I am unable to connect to ActiveSync as I normally would.

    Is there any detailed error message when this occurs? Are you able to connect normally if reconfiguring the decive(Although noramally this is not necessary as I know.)?
    Any clues if performing an Exchange ActiveSync test using Microsoft Remote Connectivity Analyzer?

    In case it is due to the delay after moving the mailbox, please try to manually recycle the following two applications pools in IIS on Exchange 2016 server and see if it works:

    • MSExchangeAutodiscoverAppPool
    • MSExchangeSyncAppPool

    Furthermore, after Exchange 2016 was introduced into the environment, have you completed the post-installation configurations like updating the autodiscover SCP, configuring the URLs for Exchange 2016 virtual directories, updating the DNS records to point to Exchange 2016 server and so on? For more details, you may generate a checklist using the official tool Exchange Deployment Assistant or refer to the guidance in the links below:
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Addtionally, if you have any anti-virus software or firewall configured in the environment, it's suggested to try temporarily disabling it to help troubleshoot the issue. As based on my research, similar issues could be related to the NAT policy that still pointing to Exchange 2010, see:
    Activesync Authentication Fails after Mailbox Move

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.