Comments on: Exchange 2010 Client Throttling

By: Nima

Nima — Thu, 30 Dec 2010 23:13:48 +0000

I am not sure but it seems to me based on your description of MaxConcurrency, the following line should correctly read ..

So if a user has let’s say 15 connections open, 5 of those connections should BE disconnected.

By: David Sterling

David Sterling — Thu, 05 Nov 2009 17:05:32 +0000

Thanks for the post. A few comments:

1. CPUStart is *only* used by EWS. Once the average CPU utilization of EWS exceeds this percentage value, inbound requests will be delayed to keep EWS process CPU utilization down. This was added so that EWS would not create poor user experience for OWA users being serviced from the same box.
2. MaxConcurrency has nothing to do with CPUStart. If the current caller tries to exceed their concurrency limit, then the new requests will be killed – this is a hard limit. So with a MaxConcurrency limit of 10 you could never have a case where the caller has 15 connections.

David Sterling [MSFT]

By: Elan Shudnow

Elan Shudnow — Mon, 28 Sep 2009 19:27:09 +0000

If you want to limit their connections regardless of how much CPU utilization your Exchange Server has, then yes. If you want to limit only certain users, then you can create a new policy and apply this policy only to those specific users.

By: Mike Crowley

Mike Crowley — Mon, 28 Sep 2009 18:47:45 +0000

So if we want to ensure one person doesnt use a million connections, regardless of server load, we should set cpustart to zero?

By: brent

brent — Sun, 27 Sep 2009 11:17:39 +0000

cool post. Only issue with throttling isnt you wont be alerted to users doing the *dodgy* things on your system. (althought a crippled exchange server isn't really the best way of finding out about your dodgy users)

By: Tweets that mention Exchange 2010 Client Throttling | Elan Shudnow's Blog -- Topsy.com

Sun, 27 Sep 2009 10:57:11 +0000

[...] This post was mentioned on Twitter by NGN NetGeNoten. NGN NetGeNoten said: Goed artikel: Exchange 2010 Client Throttling http://bit.ly/148eUH [...]