Manage Learn to apply best practices and optimize your operations.

Monitoring Exchange 2007 Client Access Server role-specific counters

You can set up several role-specific counters to monitor Exchange 2007 client access servers. Learn which counters you should watch, what they do and what their threshold values are in this tip from our Microsoft Exchange Server expert.

There are several role-specific counters available to monitor Exchange 2007's Client Access Server (CAS) role, some of which trigger alerts when set threshold vales are exceeded. In this tip from Microsoft Exchange expert Brien Posey, you'll learn about CAS counters that monitor disk performance, Outlook Web Access and offline address books, as well as their threshold values.

Disk performance counters -- Although all transactional I/O happens on the mailbox server, monitoring disk activity is a good way to watch for excessive paging on the CAS. With that in mind, the first counter I recommend monitoring is the LogicalDisk(_Total)/Disk Reads/Sec counter.

If you were monitoring a mailbox server, a high number of disk reads per second would typically be a good thing. In contrast, a client access server doesn't have much reason to access the hard disk -- besides the overhead that the Windows operating system caused. Excessive reads usually indicate excessive paging . This often means that the server has insufficient RAM. Microsoft recommends that this counter never exceed 50 on a CAS.

A related counter -- LogicalDisk(_Total)\Disk Writes/Sec -- is also worth monitoring. Microsoft recommends that this counter also remain at 50 or lower.

Outlook Web Access (OWA) counters -- The MSExchange OWA\Average Response Time counter is a good indication of latency that OWA users are experiencing. Microsoft recommends that the average response time always be less than 100 milliseconds. Longer response times usually indicate that the CPU can't keep up with the workload, which is often due to an excessive number of users accessing OWA at a given time.

Remember that excessive CPU usage isn't the only thing that can slow response times. Bandwidth congestion and similar factors can also cause excessive latency.

A similar counter -- MSExchange OWA\Average Search Time counter -- indicates the average amount of time it takes for searches to complete. Normally, you can't get away with triggering an alert against a counter that is based on averages. However, Microsoft tells us that this counter should never exceed 100 milliseconds, giving us a threshold value that we can work with when creating an alert.

Offline address book (OAB) counters -- The client access server also makes the offline address book available to users. There are two OAB-related counters that you may want to check out.

More on monitoring Exchange Server performance:
Exchange Server capacity planning with Performance Monitor 

Why too much memory can hurt Exchange 2007 performance
Microsoft Exchange Server 2007 performance tutorial

The MSExchangeFDS:OAB(*)\Download Task Queued counter informs you whether or not the server is waiting for the OAB to be downloaded. A value of one indicates that the server is waiting to download address book data from the mailbox servers but the download has not been executed.

A value of zero indicates that the download has completed. According to Microsoft, this value should always be zero; higher values may indicate communications problems or excessive latency between the CAS and the mailbox server.

The MSExchangeFDS:OAB(*)\Download Tasks Completed counter gives you the number of times that the File Distribution Service (FDS) has downloaded OAB updates since the service started.

It's a bit tricky to set up alerts for this counter, since it should show a steady increase. By default, the FDS downloads updates every eight hours (three times a day). I don't know of a way to trigger an alert if downloads aren't happening, but this counter gets reset if the FDS restarts. Therefore, you might want to create an alert that looks for low values, which would indicate that the service has restarted.

About the author: Brien M. Posey, MCSE, is a five-time recipient of Microsoft's Most Valuable Professional (MVP) award for his work with Exchange Server, Windows Server, Internet Information Services (IIS), and File Systems and Storage. Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal website at

Do you have comments on this tip?  Let us know.

Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server, Microsoft Outlook or SharePoint tip, timesaver or workaround? Email the editors to talk about writing for

Dig Deeper on Exchange Server setup and troubleshooting

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.