As usual Microsoft has put all the sessions from this years TechEd online at www.msteched.com.
I have compiled a list of interesting UC sessions within:
GFI has done a blog post about the 15 Popular Exchange Server Blogs according to them.
I agree with most of them, here’s a link to the full GFI listing, there are some great Exchange blogs in there.
Read the full here: 15 Popular Exchange Server Blogs
In most transition phases from Exchange 2003, it is often a tedious process of adding the new Exchange 2010 servers (it also works for Exchange 2007), as additional Replicas on all existing Public Folders.
Previous using bulk operations with PFDAVADMIN was the fastest way forward. But why not use the script tools that comes with Exchange 2007 and 2010, it is even faster and more simple to use.
AddReplicaToPFRecursive.ps1 is in my opinion THE tool to use! 
The script is located together with the Exchange binaries, under: C:\Program Files\Microsoft\Exchange Server\Scripts.
The script recursively goes through and updates your public folders replicas for every public folder in a hierarchy that you specify.
To add an additional Exchange server for your default public folders run:
AddReplicaToPFRecursive.ps1 -TopPublicFolder "\" -ServerToAdd Servername
To add an additional Exchange server for your system public folders run:
AddReplicaToPFRecursive.ps1 -TopPublicFolder "\NON_IPM_SUBTREE" -ServerToAdd Servername
With a lot of Public Folders the command can run for a long time, but just be patience, if there is problems, it will fail.
Confirm that Replication Partners on either the System Manager on Exchange 2003 or run this command on the Exchange 2010 environment:
Get-PublicFolder "\" -Recurse | ft name,replicas
or
Get-PublicFolder "\" -Recurse | fl name,replicas
The announced ASP.NET vulnerability (Microsoft Security Advisory (2416728) from Microsoft is also affecting Exchange Server. The Exchange Team has tested the patch for this vulnerability and has approved it and it’s recommended to apply this to your Exchange servers as soon as possible.
The Exchange Server team has completed validation of this fix against Microsoft Exchange Server 2010, 2007 and 2003 and we are pleased to report that we have not identified any issues related to the application of this patch on an Exchange Server.
We recommend that Exchange customers consider applying this fix to all of their Exchange Servers which have an affected version of ASP.NET installed on the underlying Operating System in a timely manner to help protect against any attempts to exploit this vulnerability within their environment.
Details of the fix and its application, along with download links can be found here:
Microsoft Security Bulletin MS10-070 – Important: Vulnerability in ASP.NET Could Allow Information Disclosure (2418042)
For more information and direct download links, read Scott Guthrie’s blog post: ASP.NET Security Update Now Available
Ever needed at full comparison sheet of ActiveSync clients. Get a nice detailed full listing here at wikipedia:
More info. about Exchange ActiveSync (EAS) protocol in general:
Here is a quick tip on using the Exchange Management Shell to enable Auto Accept on all of your Room or Equipment mailboxes with a single command in Exchange Server 2010.
This is useful when you have just created a bunch of new Room or Equipment mailboxes for a new environment and want to save time configuring the meeting processing settings.
Ever experienced a disconnected mailbox, that doesn’t show up in Disconnected Mailbox, after the mailbox has be disabled or removed ? If you disable a mailbox within the Exchange Management Console or EMS and you for some reason want to reconnect it again, soon after. But are unable to find the disconnected mailbox within Disconnected Mailbox. There is a reason for it, it will show up in Disconnected Mailbox after the nightly maintenance. But it is possible to force this, like it was in Exchange 2003. Read more…
Microsoft has released a new troubleshooting tool for Exchange 2010 Unified Messaging.
The Exchange 2010 UM Troubleshooting Tool is an Exchange Management Shell cmdlet that you can use to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in both on-premises and cross-premises UM deployments. You can use this cmdlet in deployments with Microsoft Office Communications Server 2007 R2 or Microsoft Communications Server “14″ or in UM deployments with IP gateways or IP PBXs.
This cmdlet emulates calls and runs a series of diagnostic tests that help on-premises administrators to identify misconfigurations in telephony equipment, Exchange Server 2010 SP1 Unified Messaging settings, and connectivity issues between on-premises and cross-premises deployment of Exchange 2010 SP1 Unified Messaging.
When you run the cmdlet, it states the reason and possible solutions for issues that have been detected. It also outputs general audio quality metrics for diagnosing audio quality issues related to network connectivity such as jitter and average packet loss.
Read more and download it here.
Follow Me