That would have been an accurate assessment for Exchange 2010 where stickiness
was necessary, but with the significant changes in Exchange 2013's
architecture, there's no need for session stickiness with round robin being
sufficient, and for client connectivity, now only port 443 needs to be load
balanced because all client access communication happens entirely over HTTPS.
My experience with ZLB has been better today, after I failed over to an
alternative node on the ZLB and recreated the Farm for 443 as TCP. This seems
to have settled things down significantly, so I suspect that ZLB is still a
little buggy with certain things and can't always be guaranteed to create
things correctly. This is concerning, but fixable.
However, I'd still like to know how to deal with setting up HTTP farms
correctly, because technically this is what I should be using and not just TCP.
Problem is, even with the pem certificates properly converted and installed, I
can't seem to things working properly, no matter configuration I have in place.
Any assistance in this regard would be greatly appreciated.
Kerry
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
