Assume that you configure a Microsoft System Center Operations Manager (SCOM) server to monitor Microsoft Exchange Server 2010 Client Access servers in an Exchange 2010 organization. Additionally, assume that the SCOM server executes multiple Test-*Connectivity cmdlets. In this situation, the Microsoft.Exchange.Monitoring.exe process consumes excessive CPU resources on the Client Access servers. When this issue occurs, all requests that are sent to the Client Access servers receive slow responses.
This issue occurs because multiple threads of the Microsoft Exchange Monitoring service access unprotected data at the same time. This behavior causes data corruption and high CPU usage.
To resolve this issue, install Exchange Server 2010 Service Pack 3 (SP3) on the Exchange Server 2010 servers. For more information about Exchange Server 2010 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2808208 Description of Exchange Server 2010 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.