locked
Exchange 2010 to 2016 migration RRS feed

  • Question

  • Hi,

    I have been following this guide in upgrading my exchange 2010 to 2016 

    http://www.msexchange.org/articles-tutorials/exchange-2016-articles/migration-deployment/migrating-small-organization-exchange-2010-exchange-2016-part1.html

    Everything has worked fine, no errors everything was smooth sailing until i pointed my DNS to the new exchange 2016. When i open outlook it wont connect, out 2010 clients get an error that the exchange administrator has made a change and needs to close. Outlook 2013 and 2016 clients open and are "disconnected"

    Outlook web access connects and works fine, mailboxes on the 2010 server redirect as they are suppose to and mobile devices using active sync connect as expected.

    Other than outlook not connecting everything else works, mail send/recieve etc.

    I need some help on where to look next as its the only thing stopping my migration.

    Saturday, October 8, 2016 4:06 AM

Answers

  • Hi,

    The issue may occur because when a mailbox is moved to Exchange 2016 from Exchange 2010, the mailbox itself still has a cache entry that points the client back to the 2010 server.

    Please try recycling the following Application Pools to force Outlook to connect to Exchange 2016:
    On Exchange 2016 Server: MSExchangeAutodiscoverAppPool ,MSExchangeRpcProxyFrontEndAppPool
    ,MSExchangeRpcProxyAppPool
    Then restart the IIS service to test.
    Also refer to the following articles to install Outlook update: 

    https://support.microsoft.com/en-in/kb/2934750

    Regards,


    David Wang
    TechNet Community Support


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by David Wang_ Monday, October 24, 2016 9:15 AM
    • Marked as answer by David Wang_ Wednesday, November 2, 2016 9:27 AM
    Monday, October 10, 2016 6:32 AM

All replies

  • Hi Gonzoiderous

    What error you are getting from Outlook? Did you configured Autodiscover and enabled Outlook Anywhere setting in Exchange 2016? Some more insight you need to check from these below links.

    https://support.microsoft.com/en-us/kb/3097392

    https://dilshansaminda.wordpress.com/2016/02/01/outlook-client-stays-disconnected-once-the-mailbox-migrated-to-exchange-2016-from-2010-and-error-to-configure-outlook-clients-with-migrated-mailboxes/

    Thanks

    Prabodha

    Saturday, October 8, 2016 10:52 AM
  • Hi,

    I have been following this guide in upgrading my exchange 2010 to 2016 

    http://www.msexchange.org/articles-tutorials/exchange-2016-articles/migration-deployment/migrating-small-organization-exchange-2010-exchange-2016-part1.html

    Everything has worked fine, no errors everything was smooth sailing until i pointed my DNS to the new exchange 2016. When i open outlook it wont connect, out 2010 clients get an error that the exchange administrator has made a change and needs to close. Outlook 2013 and 2016 clients open and are "disconnected"

    Outlook web access connects and works fine, mailboxes on the 2010 server redirect as they are suppose to and mobile devices using active sync connect as expected.

    Other than outlook not connecting everything else works, mail send/recieve etc.

    I need some help on where to look next as its the only thing stopping my migration.

    What is the FQDN for the 2010 CAS Array set to? The same as the URLs you set to the 2016 Servers?


    Blog:    Twitter:   

    Saturday, October 8, 2016 6:46 PM
  • As a workaround, please check the certificate installed properly on the DAG servers.

    Also refer to below resources:

    Outlook 2010/2013 showing disconnected

    Exchange Server 2016 Client Access Namespace Configuration

    Here's a article to get in detailed about Client Connectivity in an Exchange 2010 and Exchange 2016 coexistence, for your reference: https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

    For mailbox migration you may also get help from this article to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center.

    Still having issue, you may also get help from below informative resources might helps you to get in more detailed:

    https://support.microsoft.com/en-in/kb/2934750
    https://support.microsoft.com/en-us/kb/3097392
    https://support.microsoft.com/en-in/kb/2591913

    https://www.experts-exchange.com/questions/28939646/Outlook-2013-Microsoft-Exchange-Administrator-has-made-a-change-that-requires-you-quit-and-restart-Outlook-error-can't-make-it-stop.html

    Migrate from an older Exchange to Exchange 2016:
    http://exchangemigrationsolution.blogspot.in/2016/01/migrate-from-older-exchange-to-exchange-2016.html


    Hope this helps!


    Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange


    Monday, October 10, 2016 5:45 AM
  • Hi,

    The issue may occur because when a mailbox is moved to Exchange 2016 from Exchange 2010, the mailbox itself still has a cache entry that points the client back to the 2010 server.

    Please try recycling the following Application Pools to force Outlook to connect to Exchange 2016:
    On Exchange 2016 Server: MSExchangeAutodiscoverAppPool ,MSExchangeRpcProxyFrontEndAppPool
    ,MSExchangeRpcProxyAppPool
    Then restart the IIS service to test.
    Also refer to the following articles to install Outlook update: 

    https://support.microsoft.com/en-in/kb/2934750

    Regards,


    David Wang
    TechNet Community Support


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by David Wang_ Monday, October 24, 2016 9:15 AM
    • Marked as answer by David Wang_ Wednesday, November 2, 2016 9:27 AM
    Monday, October 10, 2016 6:32 AM
  • Please check following articles: http://www.msexchange.org/articles-tutorials/exchange-2016-articles/migration-deployment/migrating-small-organization-exchange-2010-exchange-2016-part1.html

    http://www.stellarinfo.com/blog/exchange-2010-to-exchange-2016-migration/

    Hope it will work in your case!!


    Monday, October 10, 2016 10:01 AM