In this blog post we will discuss hybrid migration endpoints in both Classic and Modern hybrid topologies, explain what migration endpoints are and how you can find them. In Part 2 of this post (now ...
Updated Oct 25, 2019
Version 6.0
Blog Post
Mirela_Buru
Microsoft
MicrosoftFor the first question, our documentation says that you cannot point the Hybrid Agent to LoadBalancer for Ex2010 version anyway: https://docs.microsoft.com/en-us/exchange/hybrid-deployment/hybrid-agent#direct-your-hybrid-agents-to-the-load-balancer-instead-of-a-specific-server
But I believe you can still install multiple Hybrid Agents in Ex2010 environment just that they will point to single Ex2010 CAS at a time. Looking at the prerequisites in the same article I pasted above, if you want to install it on Exchange 2010 CAS itself, you need the Windows Server 2012 R2 OS running on it. What is important is that the Internal URI (you can see it in Get-HybridApplication cmdlet available in Hybrid Management module OR in the HCW log in the Connector Route) to be resolved internally (hosts file or internal DNS) to single Exchange 2010 CAS servers IP address.
I am not sure I understand your second question, can you elaborate on that?
But I believe you can still install multiple Hybrid Agents in Ex2010 environment just that they will point to single Ex2010 CAS at a time. Looking at the prerequisites in the same article I pasted above, if you want to install it on Exchange 2010 CAS itself, you need the Windows Server 2012 R2 OS running on it. What is important is that the Internal URI (you can see it in Get-HybridApplication cmdlet available in Hybrid Management module OR in the HCW log in the Connector Route) to be resolved internally (hosts file or internal DNS) to single Exchange 2010 CAS servers IP address.
I am not sure I understand your second question, can you elaborate on that?