Update 4/9/2019: to read about additional features released in the Hybrid Agent, please go here.
The moment you’ve all been waiting for has arrived! We are pleased to announce the Microsoft Hybrid...
Updated Jul 01, 2019
Version 2.0
Blog Post
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 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, any suggestions on how we should proceed? Also, here is an article from MVP Jaap Wesselius on his workaround: https://jaapwesselius.com/2018/12/04/the-version-of-the-client-access-server-selected-is-not-supported/
I really could use some official answers on this one, because I want to ensure a safe transition to O365!
Cheers,
Trey
Hi Trey,
No need to run the Hybrid Configuration Wizard on your Exchange server, can you run it on a different server in your environment? It will discover the Exchange server during the installation.
Regards,