none
Exchange 2010&16 coexistence problem RRS feed

  • Question

  • I'm currently using Exchange 2010 and planning to install Exchange 2016. Decide to make the following changes to avoid problems.

    I decide to modify the configuration of autodiscover to point to existing Exchange 2010 autodiscover url. Is that all right?

    Mails won't queue since Exchange 2010&2016 are in the same network and there are no restrictions on connectors?

    Tuesday, November 19, 2019 3:49 PM

Answers

  • Hi Hanal_,

    For suggestions on autodiscover configuration. Configure it before changing your DNS records. When you install Exchange 2016, you need to update the SCP object to point to the Exchange 2016 server. This is necessary because Exchange 2016 servers provide additional Autodiscover information to clients to improve the discovery process.

    After changing your DNS, Exchange server act as a proxy server until you migrate databases and your mailboxes to new Exchange. There won't any issue and your sending/receiving must works well if you config them correctly.

    It is also recommended to migrate with the help of Exchange Deployment Assistant. It is your source for Exchange deployment technical guidance. Tell us what kind of deployment you’re interested in, answer a few questions about your environment, and then view Exchange deployment instructions created just for you.

    Regards,

    Beverly Gao


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

    • Marked as answer by Hanal_ Wednesday, November 20, 2019 3:00 PM
    Wednesday, November 20, 2019 6:34 AM

All replies

  • For Exchange 2010 you'll want to insure Outlook anywhere is enabled and the exchange internal and external URL's are unified.  You'll also want to insure the default receive connectors are present in 2010.  As soon as 2016 is installed, you'll want to immediately point the SCP service point at the new Exchange 2016 autodiscover and point all access at Exchange 2016.  Exchange 2016 will proxy all requests to 2010 as needed.

    Tuesday, November 19, 2019 4:38 PM
  • Hi Hanal_,

    For suggestions on autodiscover configuration. Configure it before changing your DNS records. When you install Exchange 2016, you need to update the SCP object to point to the Exchange 2016 server. This is necessary because Exchange 2016 servers provide additional Autodiscover information to clients to improve the discovery process.

    After changing your DNS, Exchange server act as a proxy server until you migrate databases and your mailboxes to new Exchange. There won't any issue and your sending/receiving must works well if you config them correctly.

    It is also recommended to migrate with the help of Exchange Deployment Assistant. It is your source for Exchange deployment technical guidance. Tell us what kind of deployment you’re interested in, answer a few questions about your environment, and then view Exchange deployment instructions created just for you.

    Regards,

    Beverly Gao


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

    • Marked as answer by Hanal_ Wednesday, November 20, 2019 3:00 PM
    Wednesday, November 20, 2019 6:34 AM
  • I’m pleased to know that the information is helpful to you.

    Here I will provide a brief summary of this post so that other forum members could easily find useful information here:

    [Exchange 2010&16 coexistence problem— Summary]

    Issue Symptom:
    Install Exchange 2016 in Exchange 2010 and plan for a migration.
    How to configure Autodiscover and mailflow?

    Solution:
    Configure Autodiscover before changing your DNS records. When you install Exchange 2016, you need to update the SCP object to point to the Exchange 2016 server.
    After changing your DNS, Exchange server act as a proxy server until you migrate databases and your mailboxes to new Exchange.
    Friday, December 6, 2019 10:34 AM