none
New Hybrid Config Wizard not compatible with Exchange 2010? RRS feed

  • Question

  • We're in the midst of a Server 2008R2 Exchange 2010(UR 25) migration of a single server to Office 365 and are trying to leverage hybrid configuration, but are running into an issue because it's now requiring .NET 4.6.2 to install the HCW. This version of .NET isn't supported for Exchange 2010 according to the Exchange supportability matrix. We've contacted Office 365 support and they have not been able to provide any concrete answers...some are recommending we install 4.6.2 (or even 4.7.x) on the Exchange server. We're hesitant to do so for obvious reasons. Can .NET 3.5 and 4.6.x operate side-by-side without impacting Exchange functionality? We've done 2010 hybrids before without issue...so this appears to be a new development, any suggestions on how we should proceed?

    Any additional insight from others who have ran into this before would be extremely helpful!

    Cheers, Trey


    Friday, February 8, 2019 3:10 AM

All replies

  • Also, here is an article from MVP Jaap Wesselius on his workaround:

    jaapwesselius. com/2018/12/04/the-version-of-the-client-access-server-selected-is-not-supported/

    Friday, February 8, 2019 3:12 AM
  • Hi Trey,

    Thanks for sharing the workaround!

    Based on my search, I could not find any official document related to this issue. So I would just share you two options to work around this:

    1. Use the method Jaap Wesselius provided.
    2. Use the Exchange 2013 and 2016 supported versions as the "hybrid" server. While you need to deploy a new Exchange server in your organization before running the HCW. 

    Refer to Exchange Deployment Assistant to have a step-by-step guidance.

    Hope it helps.

    Regards,

    Manu Meng


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

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, February 11, 2019 6:42 AM
    Moderator
  • Just checking in to see if above information was helpful. Please let us know if you would like further assistance.

    Regards, 

    Manu Meng


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

    Click here to learn more. Visit the dedicated forum to shareexplore and talk to experts about Microsoft Teams.

    Thursday, February 14, 2019 9:56 AM
    Moderator