Testing cmdlets

Exchange 2010 includes a set of test cmdlets that you can use to verify that different aspects of servers are working correctly. The cmdlets were first introduced in Exchange 2007 and have been updated to take account of changes in Exchange 2010. For example, the Test-SystemHealth cmdlet doesn’t complain about circular logging if it detects that this is enabled for a database because the impact of circular logging is very different in Exchange 2010, especially when databases are protected by multiple copies. There’s no need to run these cmdlets unless some suspicion exists that a server is not performing as expected or there is evidence that some problems exist, such as user complaints about server responsiveness when using an ...

Get Microsoft® Exchange Server 2010 Inside Out now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.