Hello, Need help on "MSExchangeIS Client (Exchange Monitoring Task)" the task is reaching 70 and flat lining for at least 1 hour. We dont have any other issues in our servers (disk, processor, memory and whatnot). The task is also showing to servers with passive copies (servers hosting passive copies only) as well as some of our active . The problem here is that we do not have any users yet on the server that may cause any potential load on the server. in addition, the counter often times resolve itself (goes down to zero) after a few days or weeks. version: Exchange 2010 SP1 Mailbox role Nicolo

Nicolo Please check this http://blogs.technet.com/b/exchange/archive/2005/09/28/411674.aspx Sumanth G

Hello Sumanth, Thank you for your reply, but i have gone through all of those even using (PAL) to check for performance, as for the counters there are all zero since there are no users in it. It would also help me alot if you can point me to a document or link than can help me understand what "Exchange Monitoring Task" process does or its function that way i can understand more why it is causing these high latencies. Nicolo

Hi, The passive node need to sync with the active copy using continuous replication, also known as log shipping. Then replay these logs into its own database by the store.exe. This will interim increase the RPC average latency.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hello, In our case Online maintenance and MS Search indexing caused this problem (disk and CPU load was high), but we did not use MOM for monitoring. when does this increase? Isn't it during online maintenance window? Do you have 24/7 online maintenance set? I would disable 24/7 online maintenance and set online maintenance window for night time and monitor issue again. RegardsZbynk

Thanks Gen and Zbynek, i will check both suggestions. Nicolo

Hello Zbynek, the increase in latency does not coincide with the the online maintenance schedule. Also it is scheduled 1am to 5am Im leaning more on the replication but would need to analyze my data. Thanks, Nicolo

confirmed.. cause of the latency was the during the replay of the transaction logs