EDIT 06/18/2010: Few post changes to match the newest version of the script.
Working in Exchange Customer Service and Support, we often see cases where user performance, or overall server perf...
Updated Apr 29, 2020
Version 3.0
Blog Post
I actually did not meant to block the number of the messages. Even I compared that to mailbox quotas. Reasons are the same as you describes. More likely my point was, that Outlook is capable to detect when the responses are coming slowly and it will know the number of the items, so why it does not report that to user? At least it might cause less calls to help desk when users are aware of this.
By the enterprise level, I meant, how many times you have forgot to run some scripts (yes you could schedule them, for that you need account which password never ends etc..). I hope that your target is not to run Exchange with scripts ;-)
And no doubt, this is great script and it gives very useful informative, but still I like to see this in normal daily maintenance process which Exchange is running by itself. And monitored with SCOM.
By the enterprise level, I meant, how many times you have forgot to run some scripts (yes you could schedule them, for that you need account which password never ends etc..). I hope that your target is not to run Exchange with scripts ;-)
And no doubt, this is great script and it gives very useful informative, but still I like to see this in normal daily maintenance process which Exchange is running by itself. And monitored with SCOM.