For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Dan_Sheehan_841's avatar
Dan_Sheehan_841
Icon for Nimbostratus rankNimbostratus
Sep 28, 2012

"Drain stopping" an Exchange 2010 CAS array w/o user getting prompts.

Greetings,   My team has established an Exchange 2010 load balanced presence using the template in our F5 3600 LTM HA Pair. Everything is working as we would expect, except for the ability to remo...
microsoft
partner
John_Matlock_42's avatar
John_Matlock_42
Icon for Nimbostratus rankNimbostratus
Dec 28, 2012

Agreed, this is one of the reasons they made the architectural changes they did in Exchange 2013-- sessionless/stateless CASs solve a lot of issues. They've also substantially decreased the impact of moving databases between DAG members.

 

 

As for sessions not timing out after 8 hours, the timer is reset everytime a packet is matched to the persistence record. If the client checks in atleast once every 8 hours their persistence record will never expire. When I mentioned we were 24/7, I meant that we have a 3rd shift that works overnight and they do a lot of our maintenances. Obviously, this is a rare situation.

 

 

John