Forum Discussion
John_Matlock_42
Dec 28, 2012Nimbostratus
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