Managing Communicator Web Access Performance

Topic Last Modified: 2009-02-27

Communicator Web Access ships with a number of performance objects and performance counters that enable you to monitor the performance of your Communicator Web Access servers. For example, you can monitor the following: the total (or current) number of logons, the total (or current) number of instant messages sent, and the total number of failed authentications.

The performance counters that ship with Communicator Web Access fall into one of the following four categories, with each category corresponding to a performance object:

• Communicator Web Access Directory Search (counters related to Active Directory searches)
• Communicator Web Access Authentication Module (counters related to logon attempts)
• Communicator Web Access Security (counters related to service requests rejected due to an invalid security ticket)
• Communicator Web Access User Session Service (counters related to a user’s individual Communicator Web Access session)

For details about the performance counters available created specifically for monitoring Communicator Web Access servers, see Communicator Web Access Performance Counters.

You can use the following procedures to optimize the performance of Communicator Web Access:

• Using the Communicator Web Access Snap-in to Monitor Performance
• Creating a Custom Performance Monitor for Communicator Web Access
• Modifying the Managed Pipeline Mode in IIS 7.0