Form is now closed but ill sit back and vocalize my main issues .... (brace yourself!)
1. Throttle Policies. Now that this is enabled by default in 2010 SP1 and it impacts almost ANYTHING that uses MAPI to open mulitple mailboxes or companies that like to run in online mode instead of cache, this really should have a tab in the Org -> CAS section.
2. Sense we're talking about CAS, why don't the EWS services have an internal/external URL tab just like OAB/OWA/ECP? It's not too big of a deal for the one-off CAS Array config, but when a client pays for "e,emergency help" telling him where to click is much less painful then telling him what to type down to the syntax. Bonus points for the SCP record.
3. Ditto for Outlook Anywhere. Why do I have to right click the server instead of just another tab? Breaks the flow of the GUI. Yeah you have to install a piece, but you have to remember to start things like POP so I dont think that's a big deal.
4. Final nail in the CAS coffin: the configure external domain right-click wizard is handy .... let me do the same for internal URLs.
5. Moving on HTS: I like the receive connector processing rules EXCEPT I personally find the "most explicit gets processed first" a little difficult at times, especially if the client has LOTS of rules. Copy the firewall world and simply have them process in order instead and let us increase/decrease the order. More control, more inline with what admins experience ... better everything really.
6. Bigger deal in HTS: You SERIOUSLY need an extra check box in the GUI for anonymous relaying. This has to be the most common custom configuration on the planet, yet it's a powershell command and arguably buried as an AD permission on top of all of that, at least allow an "-allowanonrelay:$true" flag in set-recieveconnector cmdlet. I've YET to visit a single client that didn't need this in some capacity, and it's easily a a daily admin task to add new scanners with email capabilities and custom what have yous.
7. Not directly your area, but talk to the AD folks over in charge of ADAC and extend it to include Exchange management. Telling clients they can't use the MMC as a one-stop admin point anymore and having _nothing_ to offer as a replacement .... well ... blows.
8. Security Group Support. We need this. Badly. There are tons of custom policies available to the average user object and all of them must be explicitly defined. From Throttle Controls, to Retention Policies, to OWA/ActiveSync policies, there is no easy way to carve out a group of people and have the right policy assigned. Instead we have to create a ps1 script that enumerates group membership then applies the policy to all the members and then store that as a scheduled task to run each night .... it's silly. If security groups are too much due to query load/nested group complications at least let us do something similar to recipient policies where we can create a search filter via opath then prioritize it. Id be fine explaining that to a client.
That's a good place to start I think. :)
Microsoft