References > Template Reference > Exchange 2007 - 2013 > Exchange 2013 Client Access Role Services and Counters (Basic)

Exchange 2013 Client Access Role Services and Counters (Basic)

This template contains basic performance counters and services for monitoring the Exchange 2013 Client Access Role. This template is designed to work out of the box and does not require any additional configuration. If you need more detailed monitoring, you should use it in combination with the Exchange 2013 Client Access Role Counters (Advanced) template.

Prerequisites

RPC and WMI access to the Exchange server.

Credentials

Windows Administrator on target server.

Monitored Components

For details on monitors, see SAM Component Monitor Types.

Service: Microsoft Exchange Active Directory Topology

This service provides Active Directory topology information to Exchange services. If this service is stopped, most Exchange services will be unable to start.

Service: Microsoft Exchange Service Host

This service provides a host for several Microsoft Exchange services.

Service: Microsoft Exchange POP3

This service provides Post Office Protocol version 3 service to clients. If this service is stopped, clients cannot connect to this computer using the POP3 protocol.

This monitor is disabled by default.

Service: Microsoft Exchange IMAP4

This service provides Internet Message Access Protocol service to clients. If this service is stopped, clients will be unable to connect to this computer using the IMAP4 protocol.

This monitor is disabled by default.

Service: Microsoft Exchange Unified Messaging

This service enables Microsoft Exchange Unified Messaging features. This allows voice and fax messages to be stored in Microsoft Exchange and gives users telephone access to e-mail, voice mail, calendar, contacts, or an auto attendant. If this service is stopped, Unified Messaging will not be available.

OWA: Average Search Time

This monitor returns the average time that elapsed while waiting for a search to complete. The returned value should be less than 5,000 milliseconds (5 seconds) at all times.

ASP.NET Applications: Requests In Application Queue

This monitor returns the number of requests in the application request queue. The returned value should be 0 at all times. Values greater than 0 should be investigated.

Availability Service: Average Time to Process a Free Busy Request

This monitor returns the average time to process a free/busy request, in seconds. One request may contain multiple mailboxes. Free/busy responses do not have meeting suggestions. The returned value should always be less than 5.

Rpc Client Access: RPC Averaged Latency

This monitor returns the latency, in ms, averaged for the past 1,024 packets. The returned value should be below 250 ms.

Rpc Client Access: RPC Requests

This monitor returns the number of client requests currently being processed by the RPC Client Access service. This returned value should not be over 40.

UM Availability: Directory Access Failures

This monitor returns the number of times that attempts to access Active Directory failed. The returned value should be 0 at all times.

UM Availability: Total Inbound Calls Rejected by the UM Service

This monitor returns the total number of inbound calls that were rejected by the Microsoft Exchange Unified Messaging Service since the service was started. The returned value should be 0 at all times.

This monitor has the Count statistic as difference option enabled. It will only return new values from the last poll.

UM Availability: Total Inbound Calls Rejected by the UM Worker Process

This monitor returns the total number of inbound calls that were rejected by the UM Worker process since the service was started. The returned value should be 0 at all times.

This monitor has the Count statistic as difference option enabled. It will only return new values from the last poll.

UM Performance: Operations over Six Seconds

This monitor returns the number of all UM operations that took more than 6 seconds to complete. This is the time during which a caller was waiting for Unified Messaging to respond. The returned value should be as low as possible.