How do I force Exchange Server 2010 to use the custom throttling policy?
In this scenario, Exchange Server 2010 does not recognize the settings in the custom throttling policy. Instead, Exchange Server 2010 uses the settings in the default throttling policy.
This issue can occur if the throttling policy reference in the BudgetCache is not refreshed. This issue can also occur if the mailbox for a frequently used account is stored in the cache, and the cache never expires.
To work around this issue, use the following methods, as appropriate for your situation.
Method 1 for RPC Client Access clients
To resolve this issue for RPC Client Access clients, restart the following services:
- Microsoft RPC Client Access service
- Microsoft Exchange Address Book service
Method 2 for Exchange Web Services clients
To resolve this issue for Exchange Web Services (EWS) clients, restart the MSExchangeServicesAppPool application pool on the Microsoft Exchange Server 2010 Client Access server (CAS).
After this has been completed, an IIS reset is recommended (or an MSExchangeServicesAppPool restart within IIS to minimize impact to other components possibly on the server, e.g., a company's website or CRM web application running on the same IIS server as Exchange).
Note: This also applies to Exchange 2013 and 2016.