With the many benefits of deploying Exchange 2010 Client Access Server Arrays should all Exchange sites be configured with a CAS Array?
Some businesses who are currently running Exchange Server 2007 wonder whether there are any real benefits to upgrading to Exchange Server 2010
In December 2010 Google launched Google Message Continuity for Exchange Server 2003 and 2007, and now they have announced support for Exchange Server 2010 as well.
Learn which editions of Exchange Server 2010 are required for the different server roles and high availability features.
A week after Google’s launch of Google Message Continuity Microsoft has responded, criticising Google’s ease of use, support, and cost effectiveness compared to Microsoft HA solutions for Exchange.
In this article I describe one method for moving from a single Exchange Server 2010 server into a high availability topology with a CAS array and Database Availability Group.
Microsoft Exchange Server 2010 introduced a new high availability feature called the Database Availability Group (DAG). This tutorial describes how Database Availability Groups work in Exchange Server 2010, as well as demonstrating the steps for deploying a DAG using Exchange Server 2010 SP1 and Windows Server 2008 R2.
In this video I demonstrate the end user experience during different failure scenarios in a highly available Exchange Server 2010 environment.
This tutorial will demonstrate the steps for deploying Exchange Server 2010 as a Client Access Server array using Windows Network Load Balancing.
Scott Schnoll of the Microsoft Exchange Team has released a five part video series on the new Standby Continuous Replication (SCR) feature of Exchange Server 2007 SP1. The videos are available for viewing or download here. Read more about SCR on Technet. Paul CunninghamPaul is a Microsoft MVP for Office Apps and Services and a […]