locked
Exchange 2010 to 2016 Migration: Migrate Autodiscover RRS feed

  • Question

  • We are migrating from Exchange 2010 to Exchange 2016.  I am looking to migrate Autodiscover to Exchange 2016.  

    What could potentially be affected with moving over Autodiscover?  I would like to do some testing prior to cutting over by using HOSTs files to point Autodiscover to Exchange 2016.  
    Wednesday, December 13, 2017 10:22 PM

Answers

  • Why would you want to modify the Host file to point to the Exchange 2016 autodiscover URI? 

    Do you have a VIP that manage your traffic for Exchange?

    If you point the autodiscover in DNS to Exchange 2016 and the mailbox is on Exchange 2010 then 2016 will proxy the request to Exchange 2010 CAS. 

    The below link will explain how it work.

    https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:44 PM
    Thursday, December 14, 2017 12:18 AM
  • Hi,

    Yes, we need change autodiscover from Exchange 2010 to Exchange 2016 (including internal and external if you configure Exchange with an unified namespace).
    Then, all requests will access to Exchange 2016 and do proxy if mailbox in Exchange 2010.

    It's fine for Exchange client after autodiscover record changes.

    One thing to keep in mind is that ActiveSync client need to re-configure profile after mailbox moves.

    Regards,
    Allen Wang


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

    • Proposed as answer by Allen_WangJF Tuesday, December 19, 2017 1:44 PM
    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:44 PM
    Thursday, December 14, 2017 7:29 AM
    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:45 PM
    Thursday, December 14, 2017 11:36 AM
  • Hello,

    As everyone said, you need to change Autodiscover from Exchange 2010 to Exchange 2016( Internally and Externally)

    Make sure SCP is updated as well to Exchange 2016 url and it should work fine for both Exchange 2016 and Exchange 2010 mailbox (it will proxy for Exchange 2010 mailbox)

    if you have any service account configured for Exchange 2010 and if you have registered the (owa & Autodiscover url's) as SPN with Exchange 2010 ASA Account then you have to make sure ASA account is configured for Exchange 2016 and the url's  needs to deregistered from Exchange 2010 ASA account and added to Exchange 2016 ASA account.

    if the above is not performed then you will have issues with autodiscover and it is applicable only if you have service account configured for Exchange 2010 as I said.

    Regards

    Ram

    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:45 PM
    Monday, December 18, 2017 1:14 PM

All replies

  • Why would you want to modify the Host file to point to the Exchange 2016 autodiscover URI? 

    Do you have a VIP that manage your traffic for Exchange?

    If you point the autodiscover in DNS to Exchange 2016 and the mailbox is on Exchange 2010 then 2016 will proxy the request to Exchange 2010 CAS. 

    The below link will explain how it work.

    https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:44 PM
    Thursday, December 14, 2017 12:18 AM
  • Hi,

    Yes, we need change autodiscover from Exchange 2010 to Exchange 2016 (including internal and external if you configure Exchange with an unified namespace).
    Then, all requests will access to Exchange 2016 and do proxy if mailbox in Exchange 2010.

    It's fine for Exchange client after autodiscover record changes.

    One thing to keep in mind is that ActiveSync client need to re-configure profile after mailbox moves.

    Regards,
    Allen Wang


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

    • Proposed as answer by Allen_WangJF Tuesday, December 19, 2017 1:44 PM
    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:44 PM
    Thursday, December 14, 2017 7:29 AM
    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:45 PM
    Thursday, December 14, 2017 11:36 AM
  • Hello,

    As everyone said, you need to change Autodiscover from Exchange 2010 to Exchange 2016( Internally and Externally)

    Make sure SCP is updated as well to Exchange 2016 url and it should work fine for both Exchange 2016 and Exchange 2010 mailbox (it will proxy for Exchange 2010 mailbox)

    if you have any service account configured for Exchange 2010 and if you have registered the (owa & Autodiscover url's) as SPN with Exchange 2010 ASA Account then you have to make sure ASA account is configured for Exchange 2016 and the url's  needs to deregistered from Exchange 2010 ASA account and added to Exchange 2016 ASA account.

    if the above is not performed then you will have issues with autodiscover and it is applicable only if you have service account configured for Exchange 2010 as I said.

    Regards

    Ram

    • Marked as answer by TGIF2011 Friday, January 12, 2018 8:45 PM
    Monday, December 18, 2017 1:14 PM