Topic Last Modified: 2009-11-06
The Microsoft Exchange Server 2010 includes an extensive class model. Diagrams showing the class model are provided in the Appendix: Class Hierarchy later in this guide. Consider the following information about Client Access server classes and site-wide aggregated classes.
Client Access Protocol and Client Access Service Classes
The Client Access server role is strongly associated with Active Directory site boundaries. The class model for client access reflects this association. For most protocol classes hosted on the Exchange/agent computer, there is a class hosted on the Root Management Server (RMS) that represents the health of that protocol for the site. State rolls up from that protocol on each server to the site-wide instance.
Site-Wide Aggregated Classes
The site-wide aggregated classes use an aggregation on their dependency monitors so that the state changes only when all of the Client Access servers detect a protocol failure for a given protocol. This is intended to model the corrective actions taken by load balancing technologies to divert the load to functional servers as protocols/servers fail. In the Appendix: Class Hierarchy in this guide, these classes have the suffix "Service." These classes are represented in the "Service State" view.
For more details about how these site-wide aggregated classes impact availability reporting, see "Appendix: Reports" later in this guide.