When running ExBPA against a Windows 2008 cluster (either CCR or SCC) the following best practices may be flagged:

• “Cluster dedicated heartbeat network priority set incorrectly” – http://technet.microsoft.com/en-us/library/aa997088.aspx
• “Dedicated cluster heartbeat not found” – http://technet.microsoft.com/en-us/library/aa998726.aspx
• “Quorum log too small” – http://technet.microsoft.com/en-us/library/aa995830.aspx

These rules only apply to Windows 2003 clusters and the recommendations should not be followed for Exchange 2007 / Windows 2008 clusters.

This is scheduled to be corrected in a future ExBPA rules update.

As many probably already know Microsoft has announced the next version of Exchange – Exchange Server 2010.

Since I like to write about high availability, I thought I’d let you know of two things that are no longer present in Exchange 2010 from a high availability standpoint.

• Local Continuous Replication
• Single Copy Clusters

In Exchange 2010 the high availability landscape has changed to something known as the Database Availability Group. 

I’ll write more about Exchange 2010 later and as things progress…but keep this information in mind as you think about your HA and Exchange 2010 deployments.