Exchange PC Status Test

When using Outlook clients in MAPI mode, clients’ actions in Outlook translate to remote procedure calls (RPCs) between the clients and the server. If the client is running in online mode, these RPC calls occur synchronously. Any delay by the server in fulfilling these synchronous requests directly affects user experience and the responsiveness of Outlook. Conversely, if the client is running in cached mode, the majority of these requests will be handled asynchronously. Asynchronous processing means that the performance of the RPC mechanism does not affect the overall user experience.

This test monitors the performance of RPC mechanisms between the clients and the Exchange server.

Target of the test : A server configured with the Mailbox role

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Mailbox server being monitored.

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.


The IP address of the machine configured with the Mailbox server role.


The port number through which the Mailbox server communicates. The default is 6001.


If the value chosen is Yes, then the Exchange server under consideration is a passive server in an Exchange cluster. No alerts will be generated if the server is not running. Measures will be reported as "Not applicable" by the agent if the server is not up.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

RPC operations

Indicates the rate of RPC operations handled by the Exchange information store during the last measurement period.


Generally, spikes in RPC requests that do not increase RPC operations/sec indicate that there are bottlenecks preventing the store from fulfilling the requests in a timely manner. It is relatively simple to identify where the bottlenecks are occurring with regards to RPC requests and RPC operations/sec. If the client experiences delays, but the RPC requests are zero and the RPC operations/sec are low, the performance problem is happening before Exchange processes the requests (that is, before the Microsoft Exchange Information Store service actually gets the incoming requests). All other combinations point to a problem either while Exchange processes the requests or after Exchange processes those requests.

Current RPC requests

Indicates the number of MAPI RPC requests presently being serviced by the Microsoft Exchange Information Store service.


The Exchange server is configured with a pre-set maximum number of RPC requests that can be handled simultaneously (default is 100). If this value is exceeded, client requests to the server will be rejected. This measure should be below 30 most of the time.

RPC traffic

Indicates the number of MAPI RPC packets being handled by the Exchange Information Store during the last measurement period.



RPC latency

Indicates the RPC latency in milliseconds, averaged for the past 1024 packets.


This value should be below 50ms at all times.  A slowdown in RPC packet processing can adversely impact the user experience.