Exchange 2010 - Throttling During a Migration

We're all for progress as much as the next techno uber-geeks, even though sometimes it bites/kicks/stabs us in the neck/butt/back. Such is the case with throttling in Exchange 2010.

So -- when doing a migration of about any non-trivial size into 2010 you're going to have to set a new throttling policy here called "SuPolicy":

New-ThrottlingPolicy SuPolicy

Set-ThrottlingPolicy SuPolicy -RCAMaxConcurrency $null

-RCAPercentTimeInAD $null

-RCAPercentTimeInCAS $null

-RCAPercentTimeInMailboxRPC $null

-EWSMaxConcurrency $null

-EWSPercentTimeInAD $null

-EWSPercentTimeInCAS $null

-EWSPercentTimeInMailboxRPC $null

-EWSMaxSubscriptions $null

-EWSFastSearchTimeoutInSeconds $null

-EWSFindCountLimit $null

Set-Mailbox myserviceaccount@mydomain.com -ThrottlingPolicy SuPolicy

ResourceWatch Online Capability Beta

Anybody who has done a migration with us has gotten one of our "Shock and Awe" reports showing what your calendar use looks like.
No surprise we've been developing this capability.
If you go to our on-line beta, you'll be able to generate a really cool report on your conference room or resource use.
We've used it on ICS format files from Exchange 'natch, but Oracle Calendar seems to work just as well. We're using Microsoft SilverLight, so working with anything other than Internet Explorer we do not guarantee, but if it works for you just let us know.

Microsoft Expands Effort to Protect Nonprofit Groups

There are very few occasions when we would say this -- but this is one of them.

Microsoft Expands Effort to Protect Nonprofit Groups - NYTimes.com

GO MICROSOFT!

BlackBerry Enterprise Server - Stay on Top of It!

If you are planning on migrating and use the BES server. Please stay up to date with your BES versions.
How to Enable BlackBerry Enterprise Server 5.0 Sp1 and SP2 to use Microsoft Exchange Web Services is required reading.
Here's the issue: BES still relies on CDO 1.2.1, which is a little like a 2011 model year hybrid still needing a Model T crank. BES requires pretty much the same kinds of permissions we do in order to act on calendar objects in Exchange, so after migrating if you flip on BES and notice issues with setting up or responding to meeting invitations as a Delegate -- the first place to look is your BES configuration.