Forum Discussion
iApp with 11.4.1 and Exchange 2010
We made a lot of progress on this. We ended up deploying with dedicated RPC CAS ports. This made the health monitoring much better. We also know that a service failing is very different that someone shutting down a server. We did a lot of testing on this. We would stop various Exchange services or shutdown NICs. F5 did the job perfectly. The only way users ever saw an auth prompt was if the admin shutdown the CAS server without first downing it in LTM. The Exchange team now knows and accepts this as normal. Drain-stopping the node before maintenance is now part of the standard procedure.
--Patrick Brown
- Sam_HallNov 21, 2013
Nimbostratus
That's really the only option since Exchange 2010 requires persistent connections per session (it's not really very load balancer friendly).
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com