eG Help

Since all Outlook connectivity in Exchange 2013 takes place over Outlook Anywhere by default, at any given point in time, the Exchange server will be inundated with requests from remote Outlook Anywhere clients. To be able to handle this load, the back-end Exchange server should be sized with adequate server and network resources. To determine the resource requirement, administrators should first figure out how much load is imposed by Outlook Aywhere clients on the server and the network. The Exc2013RPCProTest test helps administrators with this.

This test reports the number of users currently connected to the Exchange server over Outlook Anywhere, the rate at which requests are sent to the back-end Exchange server, and the bandwidth used by the back-end server when processing and responding to the requests. In the process, the test sheds light on the load imposed by Outlook Anywhere clients on the back-end server and the network.

Measurement	Description	Measurement Unit	Interpretation
Cur_uni_user	Indicates the number of unique users currently connected to the back-end Exchange server over RPC/HTTP.	Number	This is a good measure of the current user load on the server over Outlook Anywhere.
No_conn_att	Indicates the rate at which Outlook Anywhere clients attempted to establish a connection to a back-end server via RPC/HTTP.	Attempts/Sec
Rpc_req_sec	Indicates the rate at which RPC/HTTP requests were sent to the back-end servers.	Reqs/Sec
Tot_inc_band	Indicates the bandwidth consumed by RPC/HTTP requests received by the Exchange server.	Kbps	These measures are good indicators of the bandwidth consumption of RPC/HTTP traffic. By observing variations to these measures over time, administrators can figure out if the Exchange servers have to be sized with more network resources to handle this traffic.
Tot_out_band	Indicates the bandwidth consmed when the Exchange server sent data over RPC/HTTP to the Outlook Anyhwere clients.	Kbps