Hi, With Exchange 2010, we have get/set-ThrottlingPolicyAssociation cmdlets,we can use get-throttlingpolicyassociation to check which throttling policy has been applied to user,contact,machine. For failback, it is hard coded. It will fallback to the default throttling policy. More related information to share with you: Throttling Policy Associations in Exchange 2010 SP1 http://blogs.technet.com/b/exchange/archive/2010/08/02/3410563.aspxXiu Zhang TechNet Community Support

Hi, Yes, As I understand that if the configured policy corrupt, it will fallback to default policy. If the policy is found but a particular value (RCAMaxConcurrently for example) in the policy cant be found, it will use the FallBack Policy. We can not find the effective policy that has been applied on users. I recommend you to modify the threshold on MaxConcurrency to let it fall back to the default throttling policy. Xiu Zhang TechNet Community Support

Exchange 2010 sp2 and current Throttling Policy. How can I determine which Throttling Policy who is current and running? Configured a throttling policy A for user A This shows the configured policy, not necessary the active one as far I understand: Get-Mailbox “A” | fl Name,ThrottlingPolicy Name: A ThrottlingPolicy : A How to determine which throttling policy is current? How to be sure that not Default Throttling Policy or Fallback Policy had kicked in? 1. Throttling Policy A (Configured and preferd) 2. Default Throttling Policy 3. Fallback Policy More Fallback information here: http://blogs.msdn.com/b/exchangedev/archive/2010/03/13/throttling-policy-fallback-logic.aspx Snipped from link above: “If the non-default policy is corrupt or missing, it will first fall back to the default throttling policy for the organization in question. Aha! What if the default policy is corrupt? Well, then it falls back to a special policy defined in code called the "fallback policy". Given that this policy is embedded in the Exchange assemblies, there is little chance that such a read will fail. What are the values of the fallback policy? They are the exact values that default policies are assigned when Exchange is first installed. “ Fallback Policy example: Source: MSExchange ADAccess Event ID: 2915 Process Microsoft.Exchange.RpcClientAccess.Service.exe (PID=xx). User 'A~RCA~false' has gone over budget 'x' times for component 'RCA' within a one minute period. Info: 'Policy:[Fallback], Parts:MaxConcurrency:x;'. Threshold value: '100'.

Hi, Just a tip to find the default throttling policy: Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}Regards from www.windowsadmin.info | www.blog.windowsadmin.info

Hi, With Exchange 2010, we have get/set-ThrottlingPolicyAssociation cmdlets,we can use get-throttlingpolicyassociation to check which throttling policy has been applied to user,contact,machine. For failback, it is hard coded. It will fallback to the default throttling policy. More related information to share with you: Throttling Policy Associations in Exchange 2010 SP1 http://blogs.technet.com/b/exchange/archive/2010/08/02/3410563.aspxXiu Zhang TechNet Community Support

Hi, Yes, As I understand that if the configured policy corrupt, it will fallback to default policy. If the policy is found but a particular value (RCAMaxConcurrently for example) in the policy cant be found, it will use the FallBack Policy. We can not find the effective policy that has been applied on users. I recommend you to modify the threshold on MaxConcurrency to let it fall back to the default throttling policy. Xiu Zhang TechNet Community Support

Just to clarify, a throttling policy A was defined, with few limits. For some reasons this one failed, and Default Throttling was automatically applied. Since Default Throttling Policy had some limitations, this one reported in Eventlog RCA~false has gone over budget 348 timesfor component 'RCA' within a one minute period. Info: 'Policy:[Fallback], Parts:MaxConcurrency:347;'. Threshold value: '100'. As a result of this the effectiveThrottling Policy was Fallback. If I understand right, configured Throttling Policy Afailed, dropped down to Default Throttling Policy,this one went over budget, and finally dropped to hardcoded Fallback Throttling Policy. EMS showed configured and preferred Throttling Policy at this moment: Get-Mailbox A | fl Name,ThrottlingPolicy Name: A ThrottlingPolicy : A Question is: How to show the effectiveThrottling Policy in EMS?