Hi,
I wanted to take a stab at this here because I feel this is something configurable via IIS as opposed to Exchange. Truth be told, I've exhausted all Exchange-side tweaks, but I've had success at resolving some other Exchange issues by tweaking or adding settings to the web.config files for various virtual directories. Exchange server itself serves all it's data via client-connectivity to various IIS virtual directories tied to application pools. The main one being /mapi since that is how Outlook clients connect.
I have a few very heavily used shared resources. During peak usage, I see client backoffs in the connectivity logs. Today there were 70,000. That obviously causes client-side problems for people. People can access that resource without issue using other connectivity methods which are tied to different virtual directories and app pools. The server itself also does not experience any noticeable load. It's simply an issue with that virtual directory. Everything else is fine.
I'm a pretty high level and experienced Exchange admin. I've exhausted everything server side that is Exchange specific. I've also run this through max escalations to Microsoft Exchange support on two continents to no avail. I've also posted in the technet forums only to be suggested things I tried months prior. At the outset of this, I imagined it was an IIS thing, but despite being experienced with Exchange, my experience with IIS outside of Exchange usage is very limited. I don't know where to begin looking.
I've managed a similar issue on another connectivity method by adding a key <add key="MaxRequestsQueued" value="5000" /> to the web.config for that directory. However I could see the cause of that using perfmon. I could see the queue build until 500 when issues started happening. I don't see similar queue building here, so I'm not saying it's not the case, but the evidence isn't the same.
Any input at all or places to look to troubleshoot this is appreciated. Thanks.