locked
Exchange 2010 and 2016 coexistence mail flow RRS feed

  • Question

  • There is one question if you guys can answer it would be helpful.

    I have deployed exchange 2016 and 2010 ,

    I want to configure co existence till the time all users are not migrated to 2016 server .

    1: when I am changing internal records Auto discover and mail to Exchange 2016 server internal owa redirection works fine .

    2: Test account in 2010 is not able to connect .

    3: externally outlook 2010 works fine

    What should I do so that this mail flow cos existence should work fine till the time this migration  is going on .?


    Regards Abhay

    Thursday, August 15, 2019 5:34 AM

All replies

  • Hi Abhay84, 

    How did you configure the virtual directories and DNS records in your environment?

    We can configure the Coexistence URLs by the following suggestions:

    Virtual Directories

    Exchange 2010

    Exchange 2016

    OWA

    internalURL: https://CAS2010FQDN/owa
      externalURL: $Null

    internalURL: https://webmail.domain.com/owa
      externalURL: https://webmail.domain.com/owa

    ECP

    internalURL: https://CAS2010FQDN/ecp
      externalURL: $Null

    internalURL: https://webmail.domain.com/ecp
      externalURL: https://webmail.domain.com/ecp

    ActiveSync

    internalURL:https://CAS2010FQDN/Microsoft-server-Activesync
      externalURL: $Null

    internalURL:https://webmail.domain.com/Microsoft-server-Activesync
      externalURL: https://webmail.domain.com/Microsoft-server-Activesync

    Outlook Anywhere

    externalHostName: webmail.domain.com

    externalHostName: webmail.domain.com

    EWS

    internalURL:https://CAS2010FQDN/EWS/Exchange.aspx
      externalURL: $Null

    internalURL:https://webmail.domain.com/EWS/Exchange.aspx
      externalURL: https://webmail.domain.com/EWS/Exchange.aspx

    Autodiscover

    AutoDiscoverServiceInternalURI: 
      https://autodiscover.domain.com/ 
      Autodiscover/Autodiscover.xml

    AutoDiscoverServiceInternalURI: 
      
    https://autodiscover.domain.com/ 
      Autodiscover/Autodiscover.xml

    For DNS configuration, we need to publish the following DNS records:

    Internal DNS

    webmail.domain.com

    Point to Exchange 2016 server

    autodiscover.domain.com

    Point to Exchange 2016 server

    External DNS

    webmail.domain.com

    Point to Exchange 2016 server

    autodiscover.domain.com

    Point to Exchange 2016 server

    Then for Exchange 2010 users, Exchange 2016 would proxy the service request to Exchange 2010.

    Also notice that: In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the Exchange Deployment Assistant. Specifically, you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.

    For more information about Client Connectivity in an Exchange 2016 Coexistence Environment, please refer to:

    Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010

    Regards, 

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, August 16, 2019 2:04 AM
  • Hi,

    Is there any update about your issue?

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Tuesday, August 20, 2019 6:12 AM
  • Hi,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.
    Thanks for your understanding.

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, August 26, 2019 9:03 AM