Exchange 2013 - looking for guidance with owa issues

put a cookie persistence and source addr failback and test.

I deployed that few months ago and based all config in the deployment guide. When testing,i noted the session breaking issue.Then added persistence to virtual servers and started working as a charm.

Guide says it's not needed but seems like persistence solves the problem.

In order to know if persistence is the thing, disable all pool members but one and do some test. If you add another one and session breaks, then you have to config persistence on it.

it's only my point of view.

regards, hheredia