A hotfix is available for Exchange 2013 CU6 database crashes/failovers in Exchange 2007 co-existence environments.
Version 1.09 of Test-ExchangeServerHealth.ps1 is now available, fixing a bug in the use of Test-ReplicationHealth for mixed Exchange 2010/2013 organizations.
Configuring the Exchange 2013 Mailbox servers during a migration from Exchange Server 2010.
While adding Exchange Server 2013 DAG members an error "Some or All Identity References Could Not Be Translated" occurs.
Ever wondered why your Exchange Server databases didn't failover in order of activation preference?
When activating a database copy in an Exchange Server 2010 Database Availability Group it may fail with an error message that catalog index files are in a failed state.
Answering a reader question on whether the DAG server maintenance scripts are really necessary when performing maintenance or installing updates on database availability group members.
How to use the Exchange 2013 management tools to reseed a failed database copy in a database availability group.
The step by step process for how to remove an Exchange 2013 Mailbox server from a Database Availability Group.
An Exchange database may failover when the Exchange replication service is unable to access a transaction log file that is in use by another process.
Exchange Server 2013 can be installed on either Windows Server 2008 R2 or Windows Server 2012. Some organizations may decide to install on Windows Server 2008 R2 because that is their standard server build and to remain consistent with the rest of their server fleet. However, doing that will mean they miss out on the […]
Version 1.2 of the Test-ExchangeServerHealth.ps1 script is available, which includes a number of bug fixes as well as adding the DAG health check.