store interface workspace.........57 resource scheduling details workspace ....57 availability...

IBM Tivoli Composite Application Manager for MicrosoftApplications: Microsoft Exchange Server AgentvNext

User’s Guide: Beta 1 Draft

SC23-6593-06

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 347

This edition applies to version vNext of IBM Tivoli Composite Application Manager for Microsoft Applications:Microsoft Exchange Server Agent (product number 5724-U17) and to all subsequent releases and modifications untilotherwise indicated in new editions.

© Copyright IBM Corporation 2007, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

Chapter 1. Overview of the agent . . . . 1New in this release . . . . . . . . . . . . 2Components of the IBM Tivoli Monitoringenvironment . . . . . . . . . . . . . . 2Agent Management Services . . . . . . . . . 3User interface options . . . . . . . . . . . 3Data sources . . . . . . . . . . . . . . 4

Chapter 2. Agent installation andconfiguration . . . . . . . . . . . . 9Language pack installation . . . . . . . . . 9

Installing language packs on Windows systems. . 9Installing language packs on UNIX or Linuxsystems. . . . . . . . . . . . . . . 10Silent installation of language packs on Windows,UNIX, or Linux systems . . . . . . . . . 11

Prerequisites checking . . . . . . . . . . . 12Agent-specific installation and configuration . . . 13

Creating users . . . . . . . . . . . . 13Assigning administrator rights to the MicrosoftExchange Server user . . . . . . . . . . 16Making the Microsoft Exchange Server user alocal administrator . . . . . . . . . . . 17Creating an MAPI profile for each server . . . 18Configuring the Microsoft Exchange Server forreachability . . . . . . . . . . . . . 19Configuring the agent to run under the domainuser . . . . . . . . . . . . . . . . 20

Local installation and configuration . . . . . . 21Configuring the agent locally . . . . . . . 21Configuration parameters in the Exchange ServerProperties tab. . . . . . . . . . . . . 22Configuration parameters in the ExchangeServices Monitoring tab . . . . . . . . . 25Configuration parameters in the AdvancedConfiguration Properties tab. . . . . . . . 27Validation of configuration values . . . . . . 28

Remote installation and configuration . . . . . 29Remote configuration parameters . . . . . . 31Validation of remotely configured values . . . 37

Exchange services . . . . . . . . . . . . 38Attribute groups affected by configurationparameters . . . . . . . . . . . . . . 40Starting and stopping the Microsoft ExchangeServer agent . . . . . . . . . . . . . . 42

Starting the agent from the Manage TivoliEnterprise Monitoring Services window . . . . 42Tivoli Enterprise Portal . . . . . . . . . 42tacmd command line . . . . . . . . . . 42

Microsoft Exchange Server agent in a clusterenvironment . . . . . . . . . . . . . . 43

Setting up the agent startup as manual . . . . 43Addition of the agent service as a resource . . . 43Adding the script as a resource . . . . . . . 45Configuration of cluster parameters . . . . . 45

Chapter 3. Workspaces reference . . . 47Predefined workspaces . . . . . . . . . . 47

Attribute groups used by predefined workspaces 49Workspace descriptions . . . . . . . . . . 51

Activity workspace . . . . . . . . . . . 51Activity workspace . . . . . . . . . . . 51Database workspace . . . . . . . . . . 52Database Logs workspace . . . . . . . . 52Information Store Historical workspace . . . . 52Information Store workspace . . . . . . . 52IS Client workspace . . . . . . . . . . 52Storage Group Detail workspace . . . . . . 52Microsoft Exchange Server workspace . . . . 52MTA workspace . . . . . . . . . . . . 53Mailbox Server workspace . . . . . . . . 53Client Access Server workspace. . . . . . . 53Edge Transport Server workspace . . . . . . 53Forefront Security workspace . . . . . . . 53Hub Transport Server workspace . . . . . . 53Filter Reports workspace . . . . . . . . . 53Topology workspace . . . . . . . . . . 53Unified Messaging Server workspace . . . . . 54SMTP workspace . . . . . . . . . . . 54Status workspace . . . . . . . . . . . 54Status workspace . . . . . . . . . . . 54Public Folder Detail workspace . . . . . . . 54Usage workspace . . . . . . . . . . . 54IS Private workspace . . . . . . . . . . 54Mailbox Detail workspace . . . . . . . . 55Database Availability Group workspace . . . . 55Exchange Disk Space Utilization workspace . . 55Exchange Information Store workspace . . . . 55Exchange LDAP Utilization workspace . . . . 55Exchange .Net Processes workspace . . . . . 55Exchange Server Utilization workspace . . . . 55Forefront Exchange On Demand and TransportScanner workspace . . . . . . . . . . . 55Forefront Exchange Realtime and ScheduledScanner workspace . . . . . . . . . . . 56Services Detail workspace . . . . . . . . 56Reachability workspace . . . . . . . . . 56Store Driver workspace . . . . . . . . . 56Assistants workspace . . . . . . . . . . 56Active Directory Activity workspace . . . . . 56IS Public workspace . . . . . . . . . . 56Server Information workspace . . . . . . . 56Replication workspace . . . . . . . . . . 57Mailbox Replication (Exchange Server 2010)workspace . . . . . . . . . . . . . . 57Event Logs workspace. . . . . . . . . . 57

© Copyright IBM Corp. 2007, 2013 iii

Store Interface workspace. . . . . . . . . 57Resource Scheduling Details workspace . . . . 57Availability Service Details workspace . . . . 57Address Book Service Details workspace . . . 57Web Service Details workspace . . . . . . . 57Authentication workspace . . . . . . . . 57DSN workspace . . . . . . . . . . . . 58Mail Submission workspace . . . . . . . . 58Mailbox Search Cache workspace . . . . . . 58

Chapter 4. Attributes reference . . . . 59Attribute groups and Microsoft Exchange 2007 and2010 Server roles . . . . . . . . . . . . 59Attributes in each attribute group . . . . . . . 62

Forefront Exchange On Demand Scannerattributes . . . . . . . . . . . . . . 64Forefront Exchange Realtime Scanner attributes 66Forefront Exchange Scheduled Scanner attributes 67Forefront Exchange Transport Scanner attributes 68Mailbox Server Cluster State attributes . . . . 70Microsoft Forefront Server Security Scanattributes . . . . . . . . . . . . . . 70MS Exchange Active Manager attributes . . . . 71MS Exchange Active Manager Client attributes 72MS Exchange Active Manager Server attributes 73MS Exchange Active Sync attributes . . . . . 74MS Exchange ADAccess Caches attributes . . . 79MS Exchange ADAccess Domain Controllersattributes . . . . . . . . . . . . . . 81MS Exchange ADAccess Forest Discovery . . . 82MS Exchange ADAccess Processes attributes . . 83MS Exchange Address Book attributes . . . . 84MS Exchange Assistants attributes . . . . . . 86MS Exchange Assistants Per Database attributes 87MS Exchange Attachment Filtering attributes . . 88MS Exchange Authentication attributes . . . . 89MS Exchange Autodiscover Service attributes . . 90MS Exchange Availability Service attributes. . . 90MS Exchange Calendar Attendant attributes . . 91MS Exchange Connection Filtering Agentattributes . . . . . . . . . . . . . . 92MS Exchange Content Filter Agent attributes . . 93MS Exchange Control Panel (RBAC) attributes. . 95MS Exchange Database Availability Groupattributes . . . . . . . . . . . . . . 97MS Exchange DB attributes . . . . . . . . 98MS Exchange DB Instance attributes. . . . . 101MS Exchange Delivery DSN . . . . . . . 103MS Exchange DS attributes . . . . . . . . 104MS Exchange Event Details attributes . . . . 105MS Exchange Extensibility Agents attributes . . 106MS Exchange FDS OAB attributes . . . . . 107MS Exchange IS attributes . . . . . . . . 107MS Exchange IS Client attributes . . . . . . 112MS Exchange IS HA Active Database attributes 113MS Exchange IS Private attributes . . . . . 114MS Exchange IS Public attributes . . . . . . 117MS Exchange IS Public Replication attributes 120MS Exchange IS Store attributes . . . . . . 121MS Exchange Lotus Notes Connector Summaryattributes . . . . . . . . . . . . . . 125

MS Exchange Mail Submission attributes . . . 126MS Exchange Mail Tips attributes . . . . . 127MS Exchange Mailbox Replication Serviceattributes . . . . . . . . . . . . . . 129MS Exchange Mailbox Replication Service perMdb attributes . . . . . . . . . . . . 130MS Exchange Mailbox Detail attributes . . . . 133MS Exchange Managed Folder Assistantattributes . . . . . . . . . . . . . . 134MS Exchange MAPI Connectivity Detailsattributes . . . . . . . . . . . . . . 135MS Exchange MTA attributes . . . . . . . 136MS Exchange MTA Connections attributes. . . 137MS Exchange NLB Status attributes . . . . . 139MS Exchange OWA attributes . . . . . . . 139MS Exchange Protocol Analysis Agent attributes 141MS Exchange Public Folder Detail attributes . . 142MS Exchange Reachability attributes . . . . 143MS Exchange Recipient Cache attributes . . . 143MS Exchange Recipient Filter Agent attributes 144MS Exchange Replication attributes . . . . . 145MS Exchange Replication attributes(Superseded) . . . . . . . . . . . . 150MS Exchange Replica Seeder attributes . . . . 151MS Exchange Replication Server attributes . . 152MS Exchange Resource Booking attributes. . . 153MS Exchange Resource Health attributes . . . 153MS Exchange Rights Management Serviceattributes . . . . . . . . . . . . . . 155MS Exchange Role Based Services attributes . . 157MS Exchange Role Topology attributes . . . . 157MS Exchange RPC Client Access attributes . . 158MS Exchange Search Indices attributes . . . . 159MS Exchange Search Mailbox Operators . . . 160MS Exchange Search Mailbox Session Cache . . 161MS Exchange Sender Filter Agent attributes . . 162MS Exchange Sender ID Agent attributes . . . 163MS Exchange Server attributes . . . . . . 164MS Exchange Services Detail attributes . . . . 171MS Exchange Storage Group Detail attributes 172MS Exchange Store Driver attributes . . . . 173MS Exchange Store Driver Database attributes 174MS Exchange Store Driver Server attributes . . 175MS Exchange Store Interface attributes . . . . 175MS Exchange Submission . . . . . . . . 177MS Exchange Submission DSN . . . . . . 178MS Exchange Text Messaging attributes . . . 179MS Exchange Throttling attributes . . . . . 179MS Exchange Transport Database attributes . . 183MS Exchange Transport Dumpster attributes 185MS Exchange Transport Queues attributes . . . 186MS Exchange Transport Rules attributes . . . 188MS Exchange Transport Shadow Redundancyattributes . . . . . . . . . . . . . . 188MS Exchange Transport SMTP Availabilityattributes . . . . . . . . . . . . . . 189MS Exchange Transport SmtpReceive attributes 190MS Exchange Transport SmtpSend attributes 191MS Exchange UM Auto Attendant attributes 193MS Exchange UM Availability attributes . . . 194MS Exchange UM Call Answer attributes . . . 195

iv Microsoft Exchange Server agent: User’s Guide

MS Exchange UM Enabled User Detailsattributes . . . . . . . . . . . . . . 196MS Exchange UM General attributes . . . . 197MS Exchange UM Subscriber Access attributes 198MS Exchange Web Services attributes . . . . 200RPC/HTTP Proxy attributes . . . . . . . 201SMTP attributes . . . . . . . . . . . 202

Disk capacity planning for historical data . . . . 206

Chapter 5. Situations reference. . . . 211Predefined situations . . . . . . . . . . . 212Situation descriptions. . . . . . . . . . . 214

EX_DB_Log_Record_Stalls_Warn . . . . . . 215EX_DB_Log_Threads_Waiting_Warn. . . . . 215EX_IS_Pri_Avg_Delvry_Warn . . . . . . . 215EX_IS_Pri_Avg_Local_Delvry_Warn . . . . . 215EX_IS_Pri_Message_Delvrd_Crit . . . . . . 215EX_IS_Pri_Message_Delvrd_Warn . . . . . 215EX_IS_Pri_Receive_Queue_Warn . . . . . . 215EX_IS_Pri_Send_Queue_Warn . . . . . . . 215EX_IS_Pub_Receive_Queue_Warn . . . . . 215EX_IS_Pub_Send_Queue_Warn . . . . . . 216EX_IS_RPC_Operations_Warn . . . . . . . 216EX_IS_RPC_Requests_Warn . . . . . . . 216EX_MTA_Conn_Queue_Warn . . . . . . . 216EX_MTA_Work_Queue_Warn . . . . . . . 216EX_Server_Down . . . . . . . . . . . 216EX_SMTP_Local_Queue_Warn. . . . . . . 216EX_SMTP_Remote_Queue_Warn . . . . . . 216EX_Cache_Pg_Stall_Sec_Warn . . . . . . . 216EX_Cache_Pg_Fault_Sec_Warn . . . . . . 216EX_Cache_Pg_Fault_Sec_Crit . . . . . . . 217EX_DB_Log_Rec_Stall_Sec_Warn . . . . . . 217EX_DB_Log_Rec_Stall_Sec_Crit . . . . . . 217EX_Server_Status_Critical . . . . . . . . 217EX_Server_Attendant_Stat_Crit . . . . . . 217EX_Server_MTA_Status_Critical . . . . . . 217EX_Server_IS_Status_Critical . . . . . . . 217EX_Server_Res_Status_Critical . . . . . . . 217EX_Server_SMTP_Status_Cirtical . . . . . . 217EX_Server_WWW_Status_Critical. . . . . . 217EX_Server_App_Pct_Free_Warn . . . . . . 217EX_Server_App_Pct_Free_Critical . . . . . 218EX_Server_Log_Pct_Free_Warn . . . . . . 218EX_Server_Log_Pct_Free_Critical . . . . . . 218EX_SMTP_Dir_PickupQ_Warn. . . . . . . 218EX_SMTP_Queue_Len_Warn . . . . . . . 218EX_SMTP_Retry_QLen_Warn . . . . . . . 218EX_SMTP_Remote_RetryQ_Warn . . . . . . 218EX_SMTP_Categorizer_QLen_Warn . . . . . 218EX_DB_Log_Gen_CkPt_Depth_Warn . . . . 218EX_DB_Log_Gen_CkPt_Depth_Crit . . . . . 218EX_SMTP_Mess_Pend_Rt_Warn . . . . . . 218EX_SMTP_Mess_Pend_Rt_Critical . . . . . 219EX_TQ_Act_RD_QLen_Warn . . . . . . . 219EX_TQ_Act_RD_QLen_Crit. . . . . . . . 219EX_TQ_Retry_RD_QLen_Warn . . . . . . 219EX_TQ_Retry_RD_QLen_Crit . . . . . . . 219EX_TQ_ActMail_Delivey_Q_Warn . . . . . 219EX_TQ_ActMail_Delivey_Q_Crit . . . . . . 219EX_TQ_RtryMailDeliver_QLen_Warn . . . . 219

EX_TQ_RtryMailDeliver_QLen_Crit . . . . . 219EX_TQ_Act_nSMTP_Q_Len_Warn . . . . . 220EX_TQ_Act_nSMTP_Q_Len_Crit . . . . . . 220EX_TQ_Rtry_nSMTP_Q_Len_Warn . . . . . 220EX_TQ_Rtry_nSMTP_Q_Len_Crit. . . . . . 220EX_TQ_Agg_Delivery_Q_Len_Warn . . . . . 220EX_TQ_Agg_Delivery_Q_Len_Crit . . . . . 220EX_Service_State_Critical . . . . . . . . 220EX_Service_Status_Critical . . . . . . . . 221EX_Service_Start_Critical . . . . . . . . 221EX_IS_Mail_Store_State_Critical . . . . . . 221EX_Rep_Failed_Warn. . . . . . . . . . 221EX_Rep_Suspended_Warn . . . . . . . . 221Messages_Bypassed_Scan_Crit. . . . . . . 221Messages_Bypassed_Scan_Warn . . . . . . 221Cluster_Mailbox_State_Crit . . . . . . . . 221EX_NLB_Status_Crit . . . . . . . . . . 221EX_Replication_Failed_Warn . . . . . . . 222EX_Replication_Suspended_Warn . . . . . 222EX_Error_Event . . . . . . . . . . . 222EX_Asst_Avg_Evt_Proc_Time_Crit . . . . . 222EX_ASync_Request_Queued_Crit . . . . . . 222EX_ASync_Request_Queued_Warn . . . . . 222EX_DB_Log_Write_Avg_Lat_Crit . . . . . . 222EX_IS_Cli_RPC_Avg_Lat_Crit . . . . . . . 222EX_IS_Cli_RPC_Fail_ServBsy_Crit . . . . . 222EX_IS_Pri_Msg_Queue_Sub_Crit . . . . . . 222EX_IS_Pri_Search_Task_Rate_Crit. . . . . . 222EX_IS_Pri_Slow_FdRw_Rate_Crit . . . . . . 223EX_IS_Pub_Msg_Queue_Sub_Crit . . . . . 223EX_IS_RPC_Avg_Latency_Crit . . . . . . . 223EX_IS_RPC_Requests_Crit . . . . . . . . 223EX_IS_Slow_QP_Threads_Crit . . . . . . . 223EX_IS_Slow_Search_Threads_Crit. . . . . . 223EX_RBAC_OBPrxy_Avg_RTime_Crit. . . . . 223EX_OWA_Avg_Search_Time_Crit . . . . . . 223EX_Rep_Copy_Queue_Length_Crit . . . . . 223EX_RBAC_Req_Avg_Resp_Time_Crit . . . . 223EX_Rsc_Book_Requests_Failed_Crit . . . . . 224EX_Store_Int_RPC_Avg_Lat_Crit . . . . . . 224EX_Store_Int_RPC_Req_OutSt_Crit . . . . . 224EX_Store_Int_RPC_Req_Fail_Crit . . . . . . 224EX_Store_Int_RPC_Slow_Req_Crit . . . . . 224EX_TQ_Lar_Dlv_Q_Len_Crit . . . . . . . 224EX_TQ_Lar_Dlv_Q_Len_Warn. . . . . . . 224EX_TQ_Poison_Q_Len_Crit. . . . . . . . 224EX_TQ_Sub_Queue_Len_Crit . . . . . . . 224EX_TQ_Sub_Queue_Len_Warn . . . . . . 224EX_TQ_Unreach_Q_Len_Crit . . . . . . . 224EX_TQ_Unreach_Q_Len_Warn . . . . . . 225EX_CAS_RPC_Avg_Latency_Crit . . . . . . 225EX_CAS_RPC_Avg_Latency_Warn . . . . . 225EX_CAS_RPC_Requests_Crit . . . . . . . 225EX_CAS_RPC_Requests_Warn . . . . . . . 225EX_AB_NSPI_RPC_Br_Avg_Lat_Crit. . . . . 225EX_AB_NSPI_RPC_Req_Avg_Lat_Crit . . . . 225EX_AB_REF_RPC_Req_Avg_Lat_Crit . . . . 225EX_FDS_OAB_Dwnld_Task_Que_Warn. . . . 225EX_AVSER_Avg_Proc_Free_Bsy_Crit . . . . 225EX_HTTP_Pxy_Fail_Bknd_Con_Crit . . . . . 225EX_SI_Avg_Doc_Idx_Time_Warn . . . . . . 226

Contents v

EX_SI_Full_Crawl_Mod_Sta_Warn . . . . . 226EX_IS_Mailbox_Store_State_Crit . . . . . . 226

Chapter 6. Take Action commandsreference . . . . . . . . . . . . . 227Predefined Take Action commands . . . . . . 227Take Action command descriptions . . . . . . 228

Start Exchange Services action . . . . . . . 228Stop Exchange Services action . . . . . . . 229Mount Mailbox Database action . . . . . . 230Mount Public Folder Database action . . . . 230

Chapter 7. Policies reference. . . . . 231Predefined policies . . . . . . . . . . . 231

Chapter 8. Tivoli Common Reportingfor the monitoring agent . . . . . . 233Cognos-based report packages. . . . . . . . 233

Prerequisites. . . . . . . . . . . . . 233Importing Cognos report packages . . . . . 235Cognos data models and reports . . . . . . 236

Chapter 9. Troubleshooting . . . . . 249Trace logging . . . . . . . . . . . . . 250

Overview of log file management . . . . . 250Principal trace log files . . . . . . . . . 251Examples of trace logging . . . . . . . . 253Setting RAS trace parameters . . . . . . . 254

Problems and workarounds . . . . . . . . 256Installation and configuration troubleshooting 256Remote deployment troubleshooting . . . . 259Agent troubleshooting . . . . . . . . . 260Workspace troubleshooting . . . . . . . . 262Situation troubleshooting . . . . . . . . 264Take Action commands troubleshooting . . . 267Tivoli Common Reporting troubleshooting . . 268

Support information . . . . . . . . . . . 269

Appendix A. Upgrading for warehousesummarization . . . . . . . . . . . 271Tables in the warehouse . . . . . . . . . . 271Effects on summarized attributes . . . . . . . 271Upgrading your warehouse with limited userpermissions . . . . . . . . . . . . . . 272

Table summary . . . . . . . . . . . . . 273

Appendix B. Event mapping . . . . . 275

Appendix C. Discovery LibraryAdapter for the Microsoft ExchangeServer agent . . . . . . . . . . . . 333DLA data model class types represented in CDM 333DLA data model classes for Microsoft ExchangeServer agent . . . . . . . . . . . . . . 333

ExchangeServer class . . . . . . . . . . 334ExchangeStorageGroup class . . . . . . . 335ExchangePublicFolderStore class . . . . . . 335ExchangeMailBoxStore class . . . . . . . 336TMSAgent class . . . . . . . . . . . 336

Appendix D. Integration with TivoliBusiness Service Manager . . . . . 339Components for integrating with Tivoli BusinessService Manager . . . . . . . . . . . . 339Tasks to integrate the agent with Tivoli BusinessService Manager . . . . . . . . . . . . 340

Installing the Discovery Library Toolkit on theTivoli Business Service Manager . . . . . . 340Configuring the Tivoli Event Integration Facility(EIF) probe to enrich events . . . . . . . 340Creating a service in Tivoli Business ServiceManager . . . . . . . . . . . . . . 341Creating a data source mapping for each datasource . . . . . . . . . . . . . . . 342Configuring additional IBM Tivoli Monitoringweb services. . . . . . . . . . . . . 342Viewing data in the Tivoli Enterprise Portal . . 342

Appendix E. Documentation library 343Prerequisite publications. . . . . . . . . . 343Related publications . . . . . . . . . . . 344Other sources of documentation . . . . . . . 344

Notices . . . . . . . . . . . . . . 347Trademarks . . . . . . . . . . . . . . 349

Index . . . . . . . . . . . . . . . 351

vi Microsoft Exchange Server agent: User’s Guide

Figures

1. Exchange Server Properties tab . . . . . . 232. Exchange Services Monitoring tab . . . . . 263. Advanced Configuration Properties tab 274. Message displayed when the Agent Server

Logon validation fails . . . . . . . . . 29

5. Message displayed when the Exchange username is not specified . . . . . . . . . 29

© Copyright IBM Corp. 2007, 2013 vii

viii Microsoft Exchange Server agent: User’s Guide

Tables

1. Mechanisms used to gather attributes . . . . 42. Names and descriptions of configuration

settings in the Exchange Server Properties tab . 243. Names and descriptions of configuration

settings in the Exchange Services Monitoringtab . . . . . . . . . . . . . . . 26

4. Names and descriptions of configurationsettings in the Advanced ConfigurationProperties tab . . . . . . . . . . . . 28

5. Validation tests . . . . . . . . . . . 286. Names and descriptions of configuration

settings for remote configuration . . . . . 317. Microsoft Exchange services in Microsoft

Exchange Server 2007 and 2010 . . . . . . 388. Microsoft Exchange services in Microsoft

Exchange Server 2010 . . . . . . . . . 399. Microsoft Exchange services in Microsoft

Exchange Server 2013 . . . . . . . . . 3910. Effect of configuration parameters on attributes 4011. Interfaces for starting and stopping the

Microsoft Exchange Server agent locally andremotely . . . . . . . . . . . . . 42

12. Relationships between the predefinedworkspaces and the attribute groups. . . . . 49

13. Attribute groups and Microsoft Exchange 2007and 2010 Server roles . . . . . . . . . 59

14. Capacity planning for historical data loggedby the Microsoft Exchange Server agent. . . 207

15. Exchange Server OWA Login Activity report 23616. Exchange Server Services Status Details report 23717. Exchange Server IS Public and IS Private

Availability report . . . . . . . . . . 239

18. Exchange Server IS Private Activity report 23919. Exchange Server I/O Log Details report 24020. Exchange Server Database Performance report 24121. Exchange Server Resource Utilization report 24222. Exchange Server Mailbox Replication Service

per MDB Activity report . . . . . . . . 24323. Exchange Server Database Log Activity report 24524. Exchange Server Categorization Count report 24625. Information to gather before contacting IBM

Software Support . . . . . . . . . . 24926. Trace log files for troubleshooting agents 25127. Log files for the attribute groups . . . . . 25328. Problems and solutions for installation and

configuration . . . . . . . . . . . 25629. General problems and solutions for

uninstallation . . . . . . . . . . . 25830. Remote deployment problems and solutions 26031. Agent problems and solutions . . . . . . 26032. Workspace problems and solutions . . . . 26233. Situation problems and solutions . . . . . 26434. Take Action commands problems and

solutions . . . . . . . . . . . . . 26735. Tivoli Common Reporting for Microsoft

Exchange Server agent problems andsolutions . . . . . . . . . . . . . 268

36. Time periods and suffixes for summary tablesand views. . . . . . . . . . . . . 271

37. Additional columns to report summarizationinformation . . . . . . . . . . . . 272

38. Primary key and warehouse changes for theMicrosoft Exchange Server agent . . . . . 273

39. Overview of event slots to event classes 276

© Copyright IBM Corp. 2007, 2013 ix

x Microsoft Exchange Server agent: User’s Guide

Chapter 1. Overview of the agent

The IBM® Tivoli® Composite Application Manager for Microsoft Applications: Microsoft Exchange ServerAgent provides you with the capability to monitor Microsoft Exchange Server agent. You can also use theagent to take basic actions with the Microsoft Exchange Server.

IBM Tivoli Monitoring

IBM Tivoli Monitoring is the base software for the Microsoft Exchange Server agent. IBM TivoliMonitoring provides a way to monitor the availability and performance of all the systems in yourenterprise from one or several designated workstations. It also provides useful historical data that youcan use to track trends and to troubleshoot system problems.

You can use IBM Tivoli Monitoring to do the following tasks:v Monitor for alerts on the systems that you are managing by using predefined situations or custom

situations.v Establish your own performance thresholds.v Trace the causes leading to an alert.v Gather comprehensive data about system conditions.v Use policies to perform actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. By providing aconsolidated view of your environment, the Tivoli Enterprise Portal permits you to monitor and resolveperformance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” on page 343 for completeinformation about IBM Tivoli Monitoring and the Tivoli Enterprise Portal.

Features of the Microsoft Exchange Server agent

The Microsoft Exchange Server agent offers a central point of management for your Microsoft ExchangeServer agent. It provides a comprehensive means for gathering exactly the information you need to detectproblems early and to prevent them.

By using this monitoring agent, you can easily collect and analyze the following Microsoft ExchangeServer server-specific information:v Address book activityv Cache statisticsv Connection statisticsv Internet mail statisticsv Message traffic statistics

The Microsoft Exchange Server agent is an intelligent, remote monitoring agent that is located onmanaged systems. It assists you in anticipating trouble and warns system administrators when criticalevents take place on their systems. With the Microsoft Exchange Server agent, system administrators canset threshold levels as desired and set flags to alert them when the system reaches these thresholds.

The Microsoft Exchange Server agent provides the following benefits:v Enhances efficiency and simplifies application and system management by managing diverse

applications and resources across your enterprise.

© Copyright IBM Corp. 2007, 2013 1

v Increases profits by providing you with real-time access to reliable, up-to-the-minute data that allowsyou to make faster, better informed operating decisions.

v Enhances system performance by letting you integrate, monitor, and manage your environment,networks, console, and mission-critical applications. The monitoring agent alerts the Tivoli EnterpriseConsole® when conditions in your environment meet threshold-based conditions. These alerts notifyyour system administrator to limit and control system traffic. You can view data gathered by themonitoring agent in reports and charts that inform you of the status of your managed systems.

The Microsoft Exchange Server agent helps you monitor and gather consistent, accurate, and timelyinformation that you need to effectively perform your job.

New in this releaseFor the Microsoft Exchange Server agent, the following enhancements have been made since version 6.3,including the fix packs:v New attribute groups:

– MS Exchange ADAccess Forest Discovery– MS Exchange Authentication– MS Exchange Delivery DSN– MS Exchange Submission– MS Exchange Submission DSN– MS Exchange IS HA Active Database– MS Exchange Search Mailbox Operators– MS Exchange Search Mailbox Session Cache

v Updated kex.baroc file to support Tivoli Enterprise Console event mapping

Components of the IBM Tivoli Monitoring environmentAfter you install and set up the Microsoft Exchange Server agent, you have an environment that containsthe client, server, and monitoring agent implementation for IBM Tivoli Monitoring.

This IBM Tivoli Monitoring environment contains the following components:

Tivoli Enterprise Portal clientThe portal has a user interface based on Java™ for viewing and monitoring your enterprise.

Tivoli Enterprise Portal ServerThe portal server is placed between the client and the Tivoli Enterprise Monitoring Server andenables retrieval, manipulation, and analysis of data from the monitoring agents. The TivoliEnterprise Portal Server is the central repository for all user data.

Tivoli Enterprise Monitoring ServerThe monitoring server acts as a collection and control point for alerts received from themonitoring agents, and collects their performance and availability data. The Tivoli EnterpriseMonitoring Server is also a repository for historical data.

IBM Tivoli Enterprise ConsoleThe Tivoli Enterprise Console is an optional component that acts as a central collection point forevents from a variety of sources, including events from other Tivoli software applications, Tivolipartner applications, custom applications, network management platforms, and relationaldatabase systems. You can view these events through the Tivoli Enterprise Portal (by using theevent viewer), and you can forward events from IBM Tivoli Monitoring situations to the TivoliEnterprise Console component.

IBM Tivoli Netcool/OMNIbusTivoli Netcool/OMNIbus is an optional component and the recommended event management

2 Microsoft Exchange Server agent: User’s Guide

component. The Netcool/OMNIbus software is a service level management (SLM) system thatdelivers real-time, centralized monitoring of complex networks and IT domain events. Eventinformation is tracked in a high-performance, in-memory database and presented to specific usersthrough individually configurable filters and views. The software includes automation functionsthat you can use to perform intelligent processing on managed events. You can use this softwareto forward events for Tivoli Monitoring situations to Tivoli Netcool/OMNIbus.

Tivoli Common ReportingTivoli Common Reporting is a separately installable feature available to users of Tivoli softwarethat provides a consistent approach to generating and customizing reports. Some individualproducts provide reports that are designed for use with Tivoli Common Reporting and have aconsistent look and feel.

Tivoli Application Dependency Discovery Manager (TADDM)TADDM delivers automated discovery and configuration tracking capabilities to build applicationmaps that provide real-time visibility into application complexity.

IBM Tivoli Business Service ManagerThe Tivoli Business Service Manager component delivers real-time information to help yourespond to alerts effectively based on business requirements. Optionally, you can use thiscomponent to meet service-level agreements (SLAs). Use the Tivoli Business Service Managertools to help build a service model that you can integrate with Tivoli Netcool/OMNIbus alerts oroptionally integrate with data from an SQL data source. Optional components provide access todata from other IBM Tivoli applications such as Tivoli Monitoring and TADDM.

Agent Management ServicesYou can use IBM Tivoli Monitoring Agent Management Services to manage the Microsoft ExchangeServer agent.

Agent Management Services is available for the following IBM Tivoli Monitoring OS agents: Windows,Linux, and UNIX. The services are designed to keep the Microsoft Exchange Server agent available, andto provide information about the status of the product to the Tivoli Enterprise Portal. For moreinformation about Agent Management Services, see "Agent Management Services" in the IBM TivoliMonitoring Administrator's Guide. IBM Tivoli Monitoring V6.2.2, Fix Pack 2 or later provides support forAgent Management Services.

User interface optionsInstallation of the base IBM Tivoli Monitoring software and other integrated applications provides avariety of interfaces that you can use to work with your resources and data.

The following interfaces are available:

Tivoli Enterprise Portal user interfaceYou can run the Tivoli Enterprise Portal as a desktop application or a browser application. Theclient interface is a graphical user interface (GUI) based on Java on a Windows or Linuxworkstation. The browser application is automatically installed with the Tivoli Enterprise PortalServer. The desktop application is installed by using the Tivoli Monitoring installation media orwith a Java Web Start application. To start the Tivoli Enterprise Portal browser client in yourInternet browser, enter the URL for a specific Tivoli Enterprise Portal browser client installed onyour Web server.

Command-line interfaceYou can use IBM Tivoli Monitoring commands to manage the Tivoli Monitoring components andtheir configuration. You can also run commands at the Tivoli Enterprise Console event server orthe Tivoli Netcool/OMNIbus ObjectServer to configure event synchronization for enterprisesituations.

Chapter 1. Overview of the agent 3

Manage Tivoli Enterprise Monitoring Services windowYou can use the window for the Manage Tivoli Enterprise Monitoring Services utility to configurethe agent and start Tivoli services not designated to start automatically.

IBM Tivoli Enterprise ConsoleYou can use the Tivoli Enterprise Console to help ensure the optimal availability of an IT servicefor an organization. The Tivoli Enterprise Console is an event management application thatintegrates system, network, database, and application management.

IBM Tivoli Netcool/OMNIbus event listYou can use the event list to monitor and manage alerts. An alert is created when theObjectServer receives an event, alarm, message, or data item. Each alert is made up of columns(or fields) of information that are held in a row in the ObjectServer alerts.status table. The TivoliNetcool/OMNIbus web GUI is also a web-based application that processes network events fromone or more data sources and presents the event data in various graphical formats.

Tivoli Common ReportingUse the Tivoli Common Reporting web user interface for specifying report parameters and otherreport properties, generating formatted reports, scheduling reports, and viewing reports. Thisuser interface is based on the Tivoli Integrated Portal.

Data sourcesMonitoring agents collect data from specific data sources.

The Microsoft Exchange Server agent agent collects data from the following sources:

WMI You can use Windows Management Instrumentation (WMI) to monitor and control managedresources throughout the network. Resources include hard drives, file systems, operating systemsettings, processes, services, shares, registry settings, networking components, event logs, users,and groups. WMI is built into clients with Windows 2000 or later, and can be installed on any32-bit Windows client.

PerfmonYou can use the Windows Performance Monitor, or Perfmon, to view various system andapplication performance metrics for collection and use by management applications. You typicallyview system metrics on a Windows system through the 'perfmon' application.

Windows Event LogYou can use the agent to collect Windows Event Log entries that are related to the monitoredresource and forwards them to IBM Tivoli Monitoring.

The following table shows each Microsoft Exchange Server agent attribute group and the mechanism thatis used to gather the attributes.

Table 1. Mechanisms used to gather attributes

Attribute group Collection source

Forefront Exchange On Demand Scanner Perfmon

Forefront Exchange Realtime Scanner Perfmon

Forefront Exchange Scheduled Scanner Perfmon

Forefront Exchange Transport Scanner Perfmon

Mailbox Server Cluster State Exchange Server

Microsoft Forefront Server Security Scan Perfmon

MS Exchange Active Manager Perfmon

MS Exchange Active Manager Client Perfmon

MS Exchange Active Manager Server Perfmon


Table 1. Mechanisms used to gather attributes (continued)


MS Exchange Active Sync Perfmon

MS Exchange ADAccess Caches Perfmon

MS Exchange ADAccess Domain Controllers Perfmon

MS Exchange ADAccess Forest Discovery Perfmon

MS Exchange ADAccess Processes Perfmon

MS Exchange Address Book Perfmon

MS Exchange Assistants Perfmon

MS Exchange Assistants Per Database Perfmon

MS Exchange Attachment Filtering Perfmon

MS Exchange Authentication Perfmon

MS Exchange Autodiscover Service Perfmon

MS Exchange Availability Service Perfmon

MS Exchange Calendar Attendant Perfmon

MS Exchange Connection Filtering Agent Perfmon

MS Exchange Content Filter Agent Perfmon

MS Exchange Control Panel (RBAC) Perfmon

MS Exchange Database Availability Group Active Directory Service Interfaces

MS Exchange DB Perfmon

MS Exchange DB Instance Perfmon

MS Exchange Delivery DSN Perfmon

MS Exchange DS Perfmon

MS Exchange Event Details Windows Event Log

MS Exchange Extensibility Agents Perfmon

MS Exchange FDS OAB Perfmon

MS Exchange IS Perfmon, Active Directory Service Interfaces

MS Exchange IS Client Perfmon

MS Exchange IS HA Active Database Perfmon

MS Exchange IS Private Perfmon, Active Directory Service Interfaces, ExchangeServer

MS Exchange IS Public Perfmon, Active Directory Service Interfaces, ExchangeServer

MS Exchange IS Public Replication Perfmon

MS Exchange IS Store Perfmon, Active Directory Service Interfaces, ExchangeServer

MS Exchange Lotus Notes Connector Summary Perfmon

MS Exchange Mail Submission Perfmon

MS Exchange Mail Tips Perfmon

MS Exchange Mailbox Replication Service Perfmon

MS Exchange Mailbox Replication Service per Mdb Perfmon

MS Exchange Mailbox Detail Perfmon, Active Directory Service Interfaces, ExchangeServer




MS Exchange Managed Folder Assistant Perfmon

MS Exchange MAPI Connectivity Details Active Directory Service Interfaces, Exchange Server

MS Exchange MTA Perfmon

MS Exchange MTA Connections Perfmon

MS Exchange NLB Status Windows Systems API

MS Exchange OWA Perfmon

MS Exchange Protocol Analysis Agent Perfmon

MS Exchange Public Folder Detail Perfmon, Active Directory Service Interfaces, ExchangeServer

MS Exchange Reachability Active Directory Service Interfaces, Exchange Server

MS Exchange Recipient Cache Perfmon

MS Exchange Recipient Filter Agent Perfmon

MS Exchange Replication Perfmon, Exchange Server

MS Exchange Replica Seeder Perfmon

MS Exchange Replication Server Perfmon

MS Exchange Resource Booking Perfmon

MS Exchange Resource Health Perfmon

MS Exchange Rights Management Service Perfmon

MS Exchange Role Based Services Exchange Server

MS Exchange Role Topology Active Directory Service Interfaces, Exchange Server

MS Exchange RPC Client Access Perfmon

MS Exchange Search Indices Perfmon

MS Exchange Search Mailbox Operators Perfmon

MS Exchange Search Mailbox Session Cache Perfmon

MS Exchange Sender Filter Agent Perfmon

MS Exchange Sender ID Agent Perfmon

MS Exchange Server Active Directory Service Interfaces, Windows SystemsAPI

MS Exchange Services Detail Windows Systems API

MS Exchange Storage Group Detail Active Directory Service Interfaces, Windows SystemsAPI

MS Exchange Store Driver Perfmon

MS Exchange Store Driver Database Perfmon

MS Exchange Store Driver Server Perfmon

MS Exchange Store Interface Perfmon

MS Exchange Submission Perfmon

MS Exchange Submission DSN Perfmon

MS Exchange Text Messaging Perfmon

MS Exchange Throttling Perfmon

MS Exchange Transport Database Perfmon

MS Exchange Transport Dumpster Perfmon




MS Exchange Transport Queues Perfmon

MS Exchange Transport Rules Perfmon

MS Exchange Transport Shadow Redundancy Perfmon

MS Exchange Transport SMTP Availability Perfmon

MS Exchange Transport SmtpReceive Perfmon

MS Exchange Transport SmtpSend Perfmon

MS Exchange UM Auto Attendant Perfmon

MS Exchange UM Availability Perfmon

MS Exchange UM Call Answer Perfmon

MS Exchange UM Enabled User Details Active Directory Service Interfaces

MS Exchange UM General Perfmon

MS Exchange UM Subscriber Access Perfmon

MS Exchange Web Services Perfmon

RPC/HTTP Proxy Perfmon

SMTP Perfmon


Chapter 2. Agent installation and configuration

Agent installation and configuration requires the use of the IBM Tivoli Monitoring Installation and SetupGuide and agent-specific installation and configuration information.

Before installing and configuring the agent, ensure your environment meets the requirements for the IBMTivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent. Seethe Prerequisites topic for the agent in the ITCAM for Microsoft Applications Information Center(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html).

To install and configure the Microsoft Exchange Server agent, use the procedures for installing monitoringagents in the IBM Tivoli Monitoring Installation and Setup Guide along with the agent-specific installationand configuration information.

If you are doing a silent installation by using a response file, see that information in the IBM TivoliMonitoring Installation and Setup Guide.

With the self-describing agent capability, new or updated IBM Tivoli Monitoring agents can becomeoperational after installation without having to perform additional product support installation steps. Totake advantage of this capability, see "Enabling self-describing agent capability at the hub monitoringserver" in the IBM Tivoli Monitoring Installation and Setup Guide. Also, see the IBM Tivoli MonitoringAdministrator's Guide for additional information about using this capability.

Language pack installationThe steps for installing language packs depend on which operating system and mode of installation youare using.

To install a language pack for the agent support files on the Tivoli Enterprise Monitoring Server, theTivoli Enterprise Monitoring Agent, and the Tivoli Enterprise Portal Server, make sure that you installedthe product in the English language. Then use the steps for the operating system or mode of installationyou are using:v “Installing language packs on Windows systems”v “Installing language packs on UNIX or Linux systems” on page 10

Installing language packs on Windows systemsYou can install the language packs on a Windows system.

Before you begin

Ensure that you have installed the product in English.

Procedure

To install language packs on Windows systems, complete the following steps:1. On the language pack CD, double-click the lpinstaller.bat file to start the installation program.2. Select the language of the installer and click OK.3. In the Introduction panel, click Next.4. Click Add/Update and click Next.


http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html

5. Select the folder where the National Language Support package (NLSPackage) files are located.

Note: The NLSPackage files are located in the nlspackage folder that contains the installerexecutable file.

6. Select the language support for the required agent and click Next.

Note: To select multiple languages, press Ctrl and select the required languages.7. Select the languages that you want to install and click Next.8. Examine the installation summary page and click Next to begin installation.9. After installation is completed, click Finish.

10. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any ofthese components are installed.

Installing language packs on UNIX or Linux systemsYou can install the language packs on a UNIX or Linux system.

Before you begin

Ensure that you have installed the product in English.

Procedure

To install language packs on UNIX or Linux systems, complete the following steps:1. Run the following command to create a temporary directory on the computer. Ensure that the full

path of the directory does not contain any spaces: mkdir dir_name

2. Mount the language pack CD to the temporary directory that you created.3. Run the following command to start the installation program: cd dir_name lpinstaller.sh -c

install_dirwhere install_dir is where you installed IBM Tivoli Monitoring. Typically, the directory name is/opt/IBM/ITM for AIX and Linux systems.

4. Select the language of the installer and click OK.5. In the Introduction panel, click Next.6. Click Add/Update and click Next.7. Select the folder where the National Language Support package (NLSPackage) files are located.

Note: Usually, the NLSPackage files are located in the nlspackage folder where the installerexecutable file is located.

8. Select the language support for the agent and click Next.

Note: To select multiple languages, press Ctrl and select the required languages.9. Select the languages that you want to install and click Next.

10. Examine the installation summary page and click Next to begin installation.11. After installation is completed, click Finish.12. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any of

these components are installed.


Silent installation of language packs on Windows, UNIX, or LinuxsystemsYou can use the silent-mode installation method to install the language packs. In silent mode, theinstallation process obtains the installation settings from a predefined response file. It does not promptyou for any information.

Before you begin

First, make sure that you installed the product in the English language.

Procedure1. Copy and paste the ITM_Agent_LP_silent.rsp response file template as shown in “Response file

example.”2. Change the following parameter settings:

NLS_PACKAGE_FOLDERFolder where the National Language Support package (NLSPackage) files are located.Typically, the NLSPackage files are located in the nlspackage folder, for example:NLS_PACKAGE_FOLDER = //tmp//LP//nlspackage.

PROD_SELECTION_PKGName of the language pack to install. Several product components can be included in onelanguage package. You might want to install only some of the available components in alanguage pack.

BASE_AGENT_FOUND_PKG_LISTAgent for which you are installing language support. This value is usually the same asPROD_SELECTION_PKG.

LANG_SELECTION_LISTLanguage you want to install.

3. Enter the command to install the language pack with a response file (silent installation):v For Windows systems:

lpinstaller.bat -f path_to_response_file

v For UNIX or Linux systems:lpinstaller.sh -c candle_home -f path_to_response_file

where candle_home is the IBM Tivoli Monitoring base directory.

Response file example# IBM Tivoli Monitoring Agent Language Pack Silent Installation Operation##This is a sample response file for silent installation mode for the IBM Tivoli#Monitoring Common Language Pack Installer.#.#This file uses the IBM Tivoli Monitoring Common Agent Language Pack with the#install package as an example.#Note:#This response file is for the INSTALLATION of language packs only.#This file does not support UNINSTALLATION of language packs in silent mode.#-------------------------------------------------------------------------------#-------------------------------------------------------------------------------#To successfully complete a silent installation of the the example of Common Agent#localization pack, complete the following steps:##1.Copy ITM_Agent_LP_silent.rsp to the directory where lpinstaller.bat or#lpinstaller.sh is located (IBM Tivoli Monitoring Agent Language Pack build#location).

Chapter 2. Agent installation and configuration 11

##2.Modify the response file so that it is customized correctly and completely for#your site.# Complete all of the following steps in the response file.##3.After customizing the response file, invoke the silent installation using the#following command:#For Windows:# lpinstaller.bat -f <path_to_response_file>#For UNIX and Linux:# lpinstaller.sh -c <candle_home> -f <path_to_response_file>#Note:<candle_home> is the IBM Tivoli Monitoring base directory.#--------------------------------------------------------------------------------#--------------------------------------------------------------------------------#Force silent install mode.#--------------------------------------------------------------------------------INSTALLER_UI=silent#---------------------------------------------------------------------------------#Run add and update actions.#---------------------------------------------------------------------------------CHOSEN_INSTALL_SET=ADDUPD_SET#---------------------------------------------------------------------------------#NLS Package Folder, where the NLS Packages exist.#For Windows:# Use the backslash-backslash(\\) as a file separator (for example,#C:\\zosgmv\\LCD7-3583-01\\nlspackage).#For UNIX and Linux:# Use the slash-slash (//) as a file separator (for example,#//installtivoli//lpsilenttest//nlspackage).#---------------------------------------------------------------------------------#NLS_PACKAGE_FOLDER=C:\\zosgmv\\LCD7-3583-01\\nlspackageNLS_PACKAGE_FOLDER=//tmp//LP//nlspackage#---------------------------------------------------------------------------------#List the packages to process; both variables are required.#Each variable requires that full paths are specified.#Separate multiple entries with a semicolon (;).#For Windows:# Use the backslash-backslash(\\) as a file separator.#For Unix and Linux:# Use the slash-slash (//) as a file separator.#---------------------------------------------------------------------------------#PROD_SELECTION_PKG=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkg#BASE_AGENT_FOUND_PKG_LIST=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkgPROD_SELECTION_PKG=//tmp//LP//nlspackage//kex_nls.nlspkg;//tmp//LP//nlspackage//koq_nls.nlspkgBASE_AGENT_FOUND_PKG_LIST=//tmp//LP//nlspackage//kex_nls.nlspkg;//tmp//LP//nlspackage//koq_nls.nlspkg#--------------------------------------------------------------------------------#List the languages to process.#Separate multiple entries with semicolons.#--------------------------------------------------------------------------------LANG_SELECTION_LIST=pt_BR;fr;de;it;ja;ko;zh_CN;es;zh_TW

Prerequisites checkingThe prerequisite checker utility verifies whether all the prerequisites that are required for the agentinstallation are met. The prerequisite checker creates a log file that contains a report of all theprerequisites checks when the prerequisite checker was run.

For the Microsoft Exchange Server agent, the prerequisite checker verifies the following requirements:v Memoryv Diskv Operating systems


v Microsoft Exchange Server versions

Additionally, the prerequisite checker verifies whether the user, who installs the agent, is a member of theAdministrators group.

For detailed information about installation prerequisites, see the Prerequisites topic for the agent in theIBM Tivoli Composite Application Manager for Microsoft Applications Information Center(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html).

You can run the prerequisite checker in stand-alone mode or remotely. For more information about theprerequisite checker, see "Prerequisite Checking for IBM Tivoli Monitoring Agents" in the IBM TivoliMonitoring Installation and Setup Guide.

Agent-specific installation and configurationBefore configuring the agent to monitor the Exchange Server resources, you must configure the MicrosoftExchange Server to communicate with the Microsoft Exchange Server agent.

To configure the Microsoft Exchange Server to communicate with the Microsoft Exchange Server agent,complete the following tasks:v “Creating users”v “Assigning administrator rights to the Microsoft Exchange Server user” on page 16v “Making the Microsoft Exchange Server user a local administrator” on page 17v “Creating an MAPI profile for each server” on page 18v “Configuring the Microsoft Exchange Server for reachability” on page 19v “Configuring the agent to run under the domain user” on page 20

Creating usersYou can create a user for the agent on the Exchange Server manually or by running the New User utility.You must create the user on each Microsoft Exchange Server that you want to monitor.

Use one of the following methods to create users:v “Creating users manually on Exchange Server 2007 or later”v “Creating users by running the New User utility” on page 15

Creating users manually on Exchange Server 2007 or laterYou must create a user for the agent on Exchange Server 2007, or later so that the agent can communicateand authenticate with the Exchange Server that you want to monitor.

Before you begin

Install the monitoring agent for Microsoft Exchange Server. For information about installing the agent, see"Installing monitoring agents" in the IBM Tivoli Monitoring Installation and Setup Guide. To create a user,you must be a domain administrator with full administrator rights on the Microsoft Exchange Server.

Procedure

To create a user on Exchange Server 2007, or later, complete the following steps:1. Click Start > Programs > Microsoft Exchange Server 2007 > Exchange Management Console. The

Exchange Management Console window opens.2. In the Console tree, click Mailbox in Recipient Configuration.3. In the Action pane, click New Mailbox. The New Mailbox wizard opens.



4. On the Introduction page, click User Mailbox.5. On the User Type page, click New User.6. On the User Information page, specify the following information:

Organizational unitBy default, the users container in the Active Directory is displayed. Click Browse to changethe default organizational unit.

First nameType the first name of the user.

InitialsType the initials of the user.

Last nameType the last name of the user.

Name By default, the user's first name, initials, and last name are displayed in this field. You canmodify the name.

User logon name (User Principal Name)Type the name that the user must use to log on to the mailbox.

User logon name (pre-Windows 2000, or earlier)Type the user name that is compatible with Microsoft Windows 2000 Server, or earlier.

PasswordType the password that the user must use to log on to the mailbox.

Confirm passwordRetype the password that you entered in the Password field.

User must change password at next logonSelect this check box if you want the user to reset the password.

7. On the Mailbox Settings page, specify the following information:

Alias By default, the value for this field is identical to the value that you specified in the Userlogon name (User Principal Name) field.

Mailbox databaseClick Browse to open the Select Mailbox Database window. Select the mailbox database thatyou want to use and click OK.

Managed folder mailbox policySelect this check box to specify a messaging records management (MRM) policy. Click Browseto select the MRM mailbox policy that you want to associate with this mailbox.

Exchange ActiveSync mailbox policySelect this check box to specify an Exchange ActiveSync mailbox policy. Click Browse to selectthe Exchange ActiveSync mailbox policy that you want to associate with this mailbox.

8. On the New Mailbox page, review the configuration summary. Click New to create a mailbox. On theCompletion page, the Summary section shows whether the mailbox was created.

9. Click Finish.

What to do next

Assign administrator rights to the Exchange user that you created. For information about assigningadministrator rights, see “Assigning administrator rights to the Microsoft Exchange Server user” on page16.


Creating users by running the New User utilityYou can run the New User utility to create users on Exchange Server 2007, or later. The user that iscreated by running this utility has all the required permissions to run the agent. This utility is installedwhen you install the agent.

Before you begin

Ensure that the agent is installed. To run the New User utility, you must be a domain administrator withfull administrator rights on the Exchange Server.

About this task

This task provides information about running the New User utility to create a user on the ExchangeServer that you want to monitor. After you run this utility, the user is created in the Users group of theActive Directory, and has the following permissions:v On Exchange Server 2007:

– Local administrator– Remote desktop user– Exchange recipient administrator– Exchange view-only administrator

v On Exchange Server 2010, or later:– Local administrator– Remote desktop user– Recipient management– View-Only organization management

Procedure

To run the New User utility, complete the following steps:1. Double-click the kexnewuser.exe file that is available at the following locations:

v CANDLE_HOME\TMAITM6 (for the 32-bit agent)v CANDLE_HOME\TMAITM6_x64 (for the 64-bit agent)

2. In the New User window, complete the following steps:a. Enter the first name and the last name of the user in the appropriate fields.

Restriction: The length of the first and the last name must not exceed 28 characters.b. In the User Logon Name field, enter the name that the user must type whenever the user logs in.

Restriction: The length of the user logon name must not exceed 256 characters.c. In the Password field, enter your password.d. In the Confirm Password field, enter the password again.e. Select User Must Change Password at Next Logon if you want the specified password to be reset

the next time when the user logs on.f. Click Next.

The configuration values that you specify are validated, and error messages are displayed forincorrect values.

3. From the list of mailbox databases, select the required mailbox database, and click Next. A summaryof configuration values is displayed.

4. Click Finish. The settings are saved, and the user is created.


What to do next

Create an MAPI profile for each user. For information about creating an MAPI profile, see “Creating anMAPI profile for each server” on page 18.

Assigning administrator rights to the Microsoft Exchange Server userThe user that you created for the Microsoft Exchange Server agent must be a domain administrator withfull administrator rights on Microsoft Exchange Server. The administrator rights are required to access theMicrosoft Exchange Server components.

Before you begin

Create a Microsoft Exchange Server user who has the mailbox on the Exchange Server that is beingmonitored.

About this task

Use one of the following methods to assign administrator rights to the user:v “Assigning administrator rights on Exchange Server 2007”v “Assigning administrator rights on Exchange Server 2010”

Assigning administrator rights on Exchange Server 2007You must assign Exchange Recipient Administrator rights to the user on Exchange Server 2007.

Before you begin

Create a Microsoft Exchange Server user.

Procedure

To assign Exchange Recipient Administrator rights to the user on Exchange Server 2007, complete thefollowing steps:1. Click Start > Programs > Microsoft Exchange Server 2007 > Exchange Management Console. The

Exchange Management Console window opens.2. In the Console tree, click Organization Configuration.3. In the Action pane, click Add Exchange Administrator.4. On the Add Exchange Administrator page, click Browse. Select the new user that you created, and

then select Exchange Recipient Administrator role.5. Click Add.6. On the Completion page, click Finish.

What to do next

Make the user a local administrator of the computer where the Microsoft Exchange Server is installed.For information about making the user a local administrator, see “Making the Microsoft Exchange Serveruser a local administrator” on page 17.

Assigning administrator rights on Exchange Server 2010You must provide Exchange Recipient Management rights to the user on Exchange Server 2010.

Before you begin



Procedure

To assign Exchange Recipient Management rights to the user on Exchange Server 2010, complete thefollowing steps:1. Click Start > Programs > Microsoft Exchange Server 2010 > Exchange Management Console. The

Exchange Management Console window opens.2. In the Console tree, click Toolbox.3. In the Work pane, double-click the Role Based Access Control (RBAC) User Editor tool. The

Exchange Control Panel window opens.4. Enter the user credentials for the account with permissions to open the user editor in the Exchange

Control Panel. Click Sign in.5. Click the Administrator Roles tab.6. Select the Recipient Management role group, and then click Details.7. In the Members area, click Add.8. Select the user that you want to add to the role group, and then click OK.9. Click Save to save the changes to the role group.

What to do next

Make the user a local administrator of the computer where the Microsoft Exchange Server is installed.For information about making the user a local administrator, see “Making the Microsoft Exchange Serveruser a local administrator.”

Making the Microsoft Exchange Server user a local administratorTo access the Microsoft Exchange Server data, the user that you created for the Microsoft Exchange Serveragent must be a local administrator of the computer where the Microsoft Exchange Server is installed.

Before you begin


About this task

Use one of the following methods to make the user a local administrator:v “Making the user a local administrator on Windows 2003 computer”v “Making the user a local administrator on Windows 2008 computer” on page 18

Note: You can make a user a local administrator on a computer by different methods, such as use ofgroup policies. Use the specified methods so that the Tivoli component software functions properly.

Making the user a local administrator on Windows 2003 computerYou must make the user that you created for the Microsoft Exchange Server agent a local administrator ofthe computer that runs on the Windows 2003 operating system, and where the Microsoft Exchange Serveris installed.

Before you begin


Procedure

To make the user a local administrator on the computer that runs on the Windows 2003 operating system,complete the following steps:


1. Right-click My Computer on the computer desktop and click Manage.2. Expand Local Users and Groups.3. Click Groups.4. Double-click Administrators to display the Administrators Properties window.5. Click Add.6. Select Entire Directory from the Look in list.7. Select the name of the user that you created and click Add.8. Click OK.9. Click OK.

What to do next

Create an MAPI profile for each user. For information about creating an MAPI profile, see “Creating anMAPI profile for each server.”

Making the user a local administrator on Windows 2008 computerYou must make the user that you created for the Microsoft Exchange Server agent a local administrator ofthe computer that runs on the Windows Server 2008 operating system, and where the Microsoft ExchangeServer is installed.

Before you begin


Procedure

To make the user a local administrator on the computer that runs on the Windows Server 2008 operatingsystem, complete the following steps:1. Click Start > Administrative Tools > Server Manager.2. In the left pane, expand Configuration.3. Double-click Local Users and Groups.4. Click Groups.5. Right-click the group to which you want to add the user account, and then click Add to Group.6. Click Add and type the name of the user account.7. Click Check Names and then click OK.

What to do next

Create an MAPI profile for each user. For information about creating an MAPI profile, see “Creating anMAPI profile for each server.”

Creating an MAPI profile for each serverA Messaging Application Programming Interface (MAPI) profile is a set of MAPI configuration settingsthat are stored in the registry. With an MAPI profile, you can connect to various messaging services, suchas Microsoft Exchange Server, Microsoft Outlook, and Outlook Express.

Before you begin

Before you create an MAPI profile, ensure that you have:v Created a user with administrative rights on each Microsoft Exchange Server that you want to monitor.v Made the user a local administrator on the computer where the Exchange Server is installed.


About this task

This task provides information about creating an MAPI profile for each Microsoft Exchange Server thatyou want to monitor.

Note: Do not create an MAPI profile if any of the following conditions is true:v You are using a 32-bit Microsoft Exchange Server agent to monitor Microsoft Exchange Server 2010.v You are using a 64-bit Microsoft Exchange Server agent to monitor Microsoft Exchange Server 2007 and

2010.

Procedure

To create an MAPI profile, complete the following steps:1. Log on to the computer by specifying the credentials of the user that you created.2. Download and install the MFCMAPI editor from the Microsoft supported website

(http://www.codeplex.com/MFCMAPI).To run the Microsoft Exchange Server agent on Microsoft Exchange Server 2007, installMSExchangeMAPIcdo, MAPI and CDO support from the Microsoft supported website(http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en).

3. Open the MFCMAPI editor.4. Create a MAPI profile.

Note: Specify a name that identifies the purpose of the profile, such as TivoliProfile. Do not use aspace in the profile name.

5. Enter the Mailbox Server name for the specified user.

Note: You must create the MAPI profile with the user that you created for the Microsoft ExchangeServer agent.

6. Resolve the mailbox name by selecting check names.

Note: Note the profile name because it is required when you configure the Microsoft Exchange Serveragent.

Configuring the Microsoft Exchange Server for reachabilityTo verify reachability, the Microsoft Exchange Server agent sends an email message to the server, andmeasures the amount of time to receive an automated response. Before you start the agent, you mustconfigure the Microsoft Exchange Server to automatically respond to email messages.

Before you begin

Before you configure the Microsoft Exchange Server, ensure that:v A mailbox is created for the user on the Microsoft Exchange Server that you want to monitor.v The user that you created for the agent is a domain user.v The servers in your Microsoft Exchange organization are configured for mail flow between servers.

About this task

This task provides information about configuring the Microsoft Exchange Server to automatically respondto email messages.


http://www.codeplex.com/MFCMAPI

http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en

Procedure

Complete the following steps for each Microsoft Exchange Server for which you want to verifyreachability:1. Log in to Microsoft Outlook by specifying credentials of the user that you created.2. Click Next on the Startup window.3. Select Yes and click Next.4. In the Microsoft Exchange Server field, type the name of the Microsoft Exchange Server.5. In the Mailbox field, type the name of the user that you created.6. Click Finish.7. Click OK.8. Click Tools > Rules and Alerts > New Rule.9. Select Start from a blank rule.

10. Select Check messages when they arrive and click Next.11. Select the following options:

v Where my name is in the To: box

v With specific words in the subject or body

12. Under Step 2 in the window, click Specific words.13. In the Specify words or phrases to search for in the subject or body field, type AVAILABILITY

CHECK.14. Click Add.15. Click OK and then click Next.16. Select Have the server reply using a specific message and click a specific message.17. In the email message editor, type the following text in the subject field of the message:

CHECK RECEIVED: MAILBOX AVAILABLE.

18. Close the email message editor and click Yes to save these changes.19. Click Next.20. When you are asked about exceptions, do not specify any restrictions.21. Click Next.22. Click Finish and then click OK.

What to do next

Configure the Microsoft Exchange Server agent.

Configuring the agent to run under the domain userBy default, the Microsoft Exchange Server agent is configured to run under the local user. The agent mustbe run under the domain user that you created.

Before you begin

Ensure that the following tasks are complete:v The user that you created is a domain user with local administrator rights.v An MAPI profile is created for the user.v The user has administrator rights on the server where the monitoring agent is installed.


About this task

The domain user that you created has administrator rights on the Exchange Server that you want tomonitor. When the agent is run under the domain user, the agent can monitor all the components of theExchange Server. This task provides information about configuring the monitoring agent to run under thedomain user.

Note: You can use the Tivoli Enterprise Portal or the tacmd command line to configure the user underwhich the agent runs. For information about the configuration parameters that are used when youconfigure the user for the agent, see “Remote installation and configuration” on page 29. You can alsoconfigure the user for the agent by using Windows services for the Microsoft Exchange Server agent.

Procedure

To change the user under which the agent runs, complete the following steps:1. Run the following command to verify which user ID is being used for starting the agent.

install_dir\InstallITM\KinCinfo.exe –r

2. If the monitoring agent was started with a user ID that does not belong to the Administrator group,stop the agent.

3. Open the Manage Tivoli Enterprise Monitoring Services window.4. Right-click the agent instance, and click Change Startup.5. Specify the fully qualified user ID as <Domain\Userid>, and then specify the password.

Note: The user must have administrator rights and must be the owner of the MAPI profile that isused to connect to the Exchange Server.

6. Start the monitoring agent. For information about starting the agent, see “Starting and stopping theMicrosoft Exchange Server agent” on page 42.

Local installation and configurationYou can install and configure the Microsoft Exchange Server agent locally.

If you are installing the agent locally, see the "Installing monitoring agents" topic in the IBM TivoliMonitoring Installation and Setup Guide.

Silent installation

If you are performing a silent installation, see the "Performing a silent installation of IBM TivoliMonitoring" topic in the IBM Tivoli Monitoring Installation and Setup Guide.

Local configuration

For configuring the agent locally, see the following topics:v “Configuring the agent locally”v “Configuration parameters in the Exchange Server Properties tab” on page 22v “Configuration parameters in the Exchange Services Monitoring tab” on page 25v “Configuration parameters in the Advanced Configuration Properties tab” on page 27v “Validation of configuration values” on page 28

Configuring the agent locallyYou can configure the agent locally by using the Manage Tivoli Enterprise Monitoring Services window.


Before you begin

Ensure that you complete all the tasks that are specified in the “Agent-specific installation andconfiguration” on page 13 topic.

Procedure

To configure the agent locally, complete the following steps:1. Click Start > All Programs > IBM Tivoli Monitoring.2. Click Manage Tivoli Enterprise Monitoring Services.3. In the Manage Tivoli Enterprise Services window, right-click Monitoring Agent for Microsoft

Exchange Server.4. Click Reconfigure.5. In the Monitoring Agent for Microsoft Exchange Server: Agent Advance Configuration window, click

OK.6. In the Agent Configuration window, complete the following steps:

a. Click the Exchange Server Properties tab, and specify values for the configuration parameters.When you click OK, the specified values are validated.

b. Click the Exchange Services Monitoring tab, and specify values for the configuration parameters.When you click OK, the specified values are validated.

c. Click the Advanced Configuration Properties tab, and specify values for the configurationparameters. When you click OK, the specified values are validated.

7. Recycle the agent.

Configuration parameters in the Exchange Server Properties tabThe Agent Configuration window for the Microsoft Exchange Server agent contains the Exchange ServerProperties tab. This tab contains the parameters to configure Exchange Server properties, such as servername, domain name, and user name.

The following figure shows the contents in the Exchange Server Properties tab:


Table 2 on page 24 contains detailed descriptions of the configuration settings in the Exchange ServerProperties tab.

Figure 1. Exchange Server Properties tab


Table 2. Names and descriptions of configuration settings in the Exchange Server Properties tab

Parameter name DescriptionMandatoryfield Examples

Exchange ServerName

Name of the Exchange Server.During installation of the Exchange Server, thedefault Exchange Server name is the WindowsServer host name. If you change the defaultExchange Server name, you must use the changedname when you configure the Exchange Serveragent.Note: In clustered and distributed environments,specify the Mailbox Server name for ExchangeServer 2007.

YesNote: Donot specify avalue if theagent isinstalled ona server thathas a singlecopy clusterwith morethan twonodes.

If the Exchange Servername is popcorn, enterpopcorn in the ExchangeServer Name field.

Exchange DomainName

Name of the domain where the Exchange Server isinstalled.

Yes If the Exchange Server isin the LAB.XYZ.comdomain, enter the namethat is to the left of thefirst dot, for example,LAB.

Exchange User Name Name of the user who is configured to access theExchange Server.Note: User must have a mailbox on the sameExchange Server.

Yes

Exchange UserPassword

Password of the user who is configured to accessthe Exchange Server.

Yes

Confirm Password Same password that you specify for the ExchangeServer user.

Yes

Exchange MAPIProfile Name

MAPI profiles are the primary configurationsettings that are required for accessing theExchange Server.

For information about creating an MAPI profile,see “Creating an MAPI profile for each server” onpage 18.Note: The Exchange MAPI Profile Name field isdisabled if any of the following conditions is true:

v You are using a 32-bit Microsoft ExchangeServer agent to monitor Microsoft ExchangeServer 2010.

v You are using a 64-bit Microsoft ExchangeServer agent to monitor Microsoft ExchangeServer 2007 and 2010.

An MAPI profile must be created with the sameuser that you specified in the Exchange UserName field.

NoNote: Thisfield ismandatory ifreachabilitymonitoringor mailboxdetailmonitoringis enabled.

Configuration incluster

Select this check box if you want to configure theExchange Server agent in a cluster environment.

Notapplicable

Cluster Server Name Name of the Cluster Server.

This field is enabled when you select theConfiguration in cluster check box.

Yes, if thefield isenabled.

For example, SCCCluster


Table 2. Names and descriptions of configuration settings in the Exchange Server Properties tab (continued)

Parameter name DescriptionMandatoryfield Examples

Exchange SubsystemID

Name of the Cluster Server node.



For example, node1

Exchange AgentHistorical DataDirectory

Location on the disk where the historical data isstored.



For example, c:\history

Configuration parameters in the Exchange Services Monitoring tabThe Agent Configuration window for the Microsoft Exchange Server agent contains the ExchangeServices Monitoring tab. This tab contains a list of Exchange services that you can select to know theExchange Server status.

The following figure shows the contents in the Exchange Services Monitoring tab:


Table 3 contains detailed descriptions of the configuration settings in the Exchange Services Monitoringtab.

Table 3. Names and descriptions of configuration settings in the Exchange Services Monitoring tab

Parameter name DescriptionMandatoryfield

Exchange Services Select the Exchange services that the Exchange Server agent mustmonitor from the list of available Exchange services.Note: The list of available services changes according to theExchange Server version and the roles that you install.

Not applicable

Services Configured forServer Status

The selected services are displayed in this list. The selected servicesdetermine the status of the Exchange Server.

Not applicable

Figure 2. Exchange Services Monitoring tab


Configuration parameters in the Advanced Configuration PropertiestabThe Agent Configuration window for the Microsoft Exchange Server agent contains the AdvancedConfiguration Properties tab. This tab contains the parameters related to reachability, such as targetemail address and reachability interval.

The following figure shows the contents in the Advanced Configuration Properties tab:Table 4 on page 28 contains detailed descriptions of the configuration settings in the Advanced

Configuration Properties tab.

Figure 3. Advanced Configuration Properties tab


Table 4. Names and descriptions of configuration settings in the Advanced Configuration Properties tab

Parameter name Description Mandatory field

Enable MailboxReachability Monitoring

Select this check box if you want the agent to capture thereachability metrics data.

Not applicable

Target Email Address An email address to verify reachability. Separate multiple emailaddresses with a semicolon (;).Note: The total number of characters in this field must not exceed1023.

Yes, if this field isenabled

Email TransmissionInterval (seconds)

The waiting time (in seconds) of the Exchange Server agentbetween sending emails.

Yes, if this field isenabled

Email TransmissionTimeout (seconds)

The interval (in seconds) for which the Exchange Server agentwaits for a response to the email that was sent to test whether theMailbox Server is reachable.

No

Enable Mailbox DetailMonitoring

Select this check box to collect data for the mailbox detail metrics. Not applicable

Mailbox Detail CollectionStart time

The time (in hh:mm:ss format) when mailbox detail metrics arecollected.

No

Mailbox Detail CollectionInterval (seconds)

The interval (in seconds) between collections of mailbox detailmetrics.

No

Event Logs CollectionTime (minutes)

The duration (in minutes) for which the Exchange Server agentcollects event records.

No

Maximum Number ofEvents

The maximum count up to which event records are collected. Thecollection of event records stops when the number of collectedevent records exceeds the maximum count.

No

Collection Interval(seconds)

The interval (in seconds) between the Exchange Server agentcycles.

No

Exchange TopologyInterval (seconds)

The interval (in seconds) between collections of topology detailinformation.

No

Validation of configuration valuesThe values that you specify for configuring the agent are validated. The validation ensures that thevalues are specified for all the mandatory parameters and certain conditions are met, such as localadministrator rights for the user.

Table 5 shows the validation tests that are performed on the specified configuration values.

Table 5. Validation tests

Validation test Verifies

Exchange Server Name Whether the Mailbox Server name of the user matches with the specified ExchangeServer name.

Exchange Server Rights Whether the user has the required Exchange Server rights. On Exchange Server 2003,the user must have full administrator rights. On Exchange Server 2007, the user musthave recipient administrator rights, and on Exchange Server 2010 and 2013, the usermust have recipient management rights.

Local Admin Whether the user has local administrator rights.

MAPI Profile Whether the specified MAPI profile is available.

Agent Service Logon Whether the agent service is configured to run with the specified user account.

If any of the specified validation tests fails, an error message is generated. Figure 1 shows the validationmessage that is generated when the Agent Service Logon validation test fails.


You must specify values for all the mandatory parameters. Otherwise, you cannot save the configuredvalues. Figure 2 shows the validation message that is generated when you leave the Exchange UserName field blank.

Remote installation and configurationYou can install and configure the agent remotely.

Figure 4. Message displayed when the Agent Server Logon validation fails

Figure 5. Message displayed when the Exchange user name is not specified


If you are installing and configuring the agent remotely, see the "Deploying non-OS agents" topic in theIBM Tivoli Monitoring Installation and Setup Guide. Also, use the agent-specific configuration information inthis section. You can install and configure the agent remotely by using the following interfaces:v Tivoli Enterprise Portalv tacmd command line

For information about the configuration parameters for configuring the agent remotely, see the followingtopics:v “Remote configuration parameters” on page 31v “Validation of remotely configured values” on page 37

Tivoli Enterprise Portal

To deploy the monitoring agent remotely by using the Tivoli Enterprise Portal, use the “Deployingthrough the portal” procedure in the IBM Tivoli Monitoring Installation and Setup Guide.

Also, use the agent-specific configuration information in the “Remote configuration parameters” on page31.

tacmd command line

To deploy this monitoring agent remotely by using the command line, use the “Deploying through thecommand line” procedure in the IBM Tivoli Monitoring Installation and Setup Guide. Also, use theagent-specific configuration information in “Remote configuration parameters” on page 31 for the tacmdaddSystem command. The IBM Tivoli Monitoring Command Reference has complete information about thetacmd addSystem command.

Use the -t or --type TYPE parameter to specify the Microsoft Exchange Server agent that you areconfiguring: EX.

Specify the properties with the -p or -property option.

For example:tacmd addSystem -t EX -n Primary:myhostname:NT -pEXCHSETTINGS.exchange_server=ESservernameEXCHSETTINGS.exchange_reach_enable=1EXCHSETTINGS.exchange_password=itm@123EXCHSETTINGS.exchange_reach_threshold=60EXCHSETTINGS.exchange_mailbox_runtime=02:00:00EXCHSETTINGS.exchange_user=tivoliuserEXCHSETTINGS.exchange_interval=120EXCHSETTINGS.exchange_targets=us2k3x2k3@ibm.comEXCHSETTINGS.exchange_profile=TivoliMapiProfileEXCHSETTINGS.exchange_domain=LABEXCHSETTINGS.exchange_reach_interval=600EXCHSETTINGS.exchange_mailbox_interval=1800EXCHSETTINGS.exchange_mailbox_enable=1EXCHSETTINGS.exchange_topology_interval=300SERVICESSETTINGS.exch_service_conncont=1SERVICESSETTINGS.exch_service_lotus=1SERVICESSETTINGS.exch_service_event=0SERVICESSETTINGS.exch_service_imap=0CLUSTERSETTINGS.exch_cluster_server= mbxserverCLUSTERSETTINGS.exch_history=C:\HistoryCLUSTERSETTINGS.exch_subsystem=CCRNode1_WIN32_STARTUP_.Username=domain\justin_WIN32_STARTUP_.Password=lotus15@#


If you want to select a service, specify the following value:SERVICESETTINGS.ServiceID=1. If you want to remove a service that is already selected, specify thefollowing value:SERVICESETTINGS.ServiceID=0.

The parameters in the example are shown on separate lines for clarity. When you type the command,type all of the parameters on one line.

The configureSystem command is used to configure the agent. For more information about using thiscommand, see IBM Tivoli Monitoring Command Reference Guide.

When you configure the agent, specify the property that you want to change and the INSTANCEproperty.

Remote configuration parametersYou must specify values for the configuration parameters when you configure the agent remotely byusing the command line or Tivoli Enterprise Portal.

Note: Before you configure the agent remotely, ensure that you complete all the tasks that are specified inthe “Agent-specific installation and configuration” on page 13 topic.Table 6 contains descriptions of configuration parameters for each of the interfaces.

Table 6. Names and descriptions of configuration settings for remote configuration

Interfaces where configuration settings arespecified

Description ExamplesTivoli EnterprisePortal tacmd command line

Exchange ServerName1

EXCHSETTINGS.exchange_server

Name of the Exchange Server.During installation of theExchange Server, the defaultExchange Server name is theWindows Server host name. Ifyou change the default ExchangeServer name, you must use thechanged name when configuringthe Exchange Server agent.Note: In clustered anddistributed environments,provide the Mailbox Server namefor Exchange Server 2007.

If the Exchange Server name ispopcorn, enter popcorn in theExchange Server name field.

ExchangeDomain Name1

EXCHSETTINGS.exchange_domain

Name of the domain where theExchange Server is located.

If the Exchange Server is locatedin domain LAB.XYZ.com, enter thename that is to the left of the firstdot, for example, LAB.

Exchange UserName1

EXCHSETTINGS.exchange_user

Name of the user who isconfigured to access theExchange Server.Note: User must have a mailboxon the same Exchange Server.

Exchange UserPassword1

EXCHSETTINGS.exchange_password

Password of the user who isconfigured to access theExchange Server.


Table 6. Names and descriptions of configuration settings for remote configuration (continued)



Exchange MAPIProfile Name1

EXCHSETTINGS.exchange_profile does not apply

MAPI profiles are the primaryconfiguration settings that arerequired for accessing theExchange Server.

See “Creating an MAPI profilefor each server” on page 18 formore information.Note: The Exchange MAPIProfile Name field is disabled ifany of the following conditions istrue:

v You are using a 32-bitMicrosoft Exchange Serveragent to monitor MicrosoftExchange Server 2010.

v You are using a 64-bitMicrosoft Exchange Serveragent to monitor MicrosoftExchange Server 2007 and2010.

The MAPI profile must becreated with the same user thatyou have specified in theExchange User Name field.

Enable MailboxReachabilityMonitoring

EXCHSETTINGS.exchange_reach_enable

This setting enables or disablesthe collection of reachabilitymetrics. The following settingsare used:

v 0 = Disabled

v 1 = Enabled

To enable reachability:

v On the Tivoli Enterprise Portal,select Yes.

v On the command line, specifyEXCHSETTINGS.exchange_reach_enable=1

Target EmailAddress1

EXCHSETTINGS.exchange_targets

An email address to verifyreachability. Separate multipleemail addresses with a semicolon(;).Note: Total number of charactersin this field must not exceed1023.

Use the following format forspecifying multiple emailaddresses:

[email protected];[email protected]

EmailTransmissionInterval(seconds)1

EXCHSETTINGS.exchange_reach_interval

The waiting time (in seconds) ofthe Exchange Server agentbetween sending emails.Note: If you specify the intervalin the range 0 - 300, the value ischanged to 300.





ExchangeTransmissionTimeout(seconds)1

EXCHSETTINGS.exchange_reach_threshold

The interval (in seconds) forwhich the Exchange Server agentwaits for a response to the emailthat was sent to test whether theMailbox Server is reachable.Note: If you specify the intervalin the range 0 - 60, the value ischanged to 60.

Enable MailboxDetailMonitoring

EXCHSETTINGS.exchange_mailbox_enable

This enables or disables thecollection of mailbox detailmetrics. The following settingsare used:

v 0 = Disabled

v 1 = Enabled

To enable mailbox details:

v On the Tivoli Enterprise Portal,select yes.

v On the command line, specifyEXCHSETTINGS.exchange_mailbox_enable=1

Mailbox DetailCollection StartTime1

EXCHSETTINGS.exchange_mailbox_runtime

The time (in hh:mm:ss format)when mailbox detail metrics arecollected. The hours are based onthe 24-hour clock format.

For example:

02:30:0030 minutes past 2 AM.

14:30:0030 minutes past 2 PM.

Mailbox DetailCollectionInterval(seconds)

EXCHSETTINGS.exchange_mailboxinterval

The interval (in seconds) betweencollections of mailbox detailmetrics.Note: If you specify the intervalin the range 0 - 1800, the value ischanged to 1800.

Event LogsCollection Time(minutes)

EXCHSETTINGS.exch_event_interval

The interval (in minutes) forwhich the Exchange Server agentcollects event records.Note: A value 0 is saved as 1440.

MaximumNumber ofEvents

EXCHSETTINGS.exch_event_count

The maximum count up to whichevent records are collected. Thecollection of event records isstopped when the number ofcollected event records exceedsthe maximum count.Note: A value 0 is saved as 50.

CollectionInterval(seconds)1

EXCHSETTINGS.exchange_interval

The interval (in seconds) betweenthe Exchange Server agent cycles.Note: If you specify the intervalin the range 0 - 120, the value ischanged to 120.





ExchangeTopologyInterval(seconds)

EXCHSETTINGS.exchange_topology_interval

The interval (in seconds) betweencollections of topology detailinformation.Note: The agent does not collectinformation if you specify 0 forthe interval. If you specify aninterval in the range 1 - 300, thevalue is changed to 300, which isthe default collection interval.Any value that is greater than300 is used as it is.

Use thisaccount2 Ifselecting thisoption completethe followingfields asdescribed:

v Account: IDunder whichthe agentinstance is torun

v Password andConfirmpassword:password

_WIN32_STARTUP_.Usernameand_WIN32_STARTUP_.Password

For more information see“Configuring the agent to rununder the domain user” on page20.





ExchangeServicesMonitoring

SERVICESSETTINGS.exch_service_conncont,SERVICESSETTINGS.exch_service_lotus,SERVICESSETTINGS.exch_service_event,SERVICESSETTINGS.exch_service_imap,SERVICESSETTINGS.exch_service_is,SERVICESSETTINGS.exch_service_mgmt,SERVICESSETTINGS.exch_service_mtastacks,SERVICESSETTINGS.exch_service_pop3,SERVICESSETTINGS.exch_service_re,SERVICESSETTINGS.exch_service_srs,SERVICESSETTINGS.exch_service_sa,SERVICESSETTINGS.exch_service_search,SERVICESSETTINGS.exch_service_adts,

Exchange Windows services to bemonitored to determine theserver status (Up or Down).

Select any of the followingWindows services that theExchange agent monitors todetermine if Microsoft ExchangeServer is active:

v Microsoft ExchangeConnectivity Controller

v Microsoft Exchange Connectorfor Lotus® Notes®

v Microsoft Exchange Event

v Microsoft Exchange IMAP4

v Microsoft ExchangeInformation Store

v Microsoft ExchangeManagement

v Microsoft Exchange MTAStacks

v Microsoft Exchange POP3

v Microsoft Exchange RoutingEngine

v Microsoft Exchange SiteReplication Service

v Microsoft Exchange SystemAttendant

v Microsoft Search

v Microsoft Exchange ActiveDirectory Topology Service

v Microsoft Exchange Anti-spamUpdate

v Microsoft Exchange EdgeSync

(Continued on next page)

To select a service, specify:SERVICESSETTINGS.exch_service_conncont=1

To remove a selected service,specify:SERVICESSETTINGS.exch_service_conncont=0





ExchangeServicesMonitoring(Continued)

SERVICESSETTINGS.exch_service_asu,SERVICESSETTINGS.exch_service_edgesync,SERVICESSETTINGS.exch_service_fd,SERVICESSETTINGS.exch_service_mailsub,SERVICESSETTINGS.exch_service_mailassist,SERVICESSETTINGS.exch_service_monitor,SERVICESSETTINGS.exch_service_rep,SERVICESSETTINGS.exch_service_si,SERVICESSETTINGS.exch_service_servhost,SERVICESSETTINGS.exch_service_transport,SERVICESSETTINGS.exch_service_translog,SERVICESSETTINGS.exch_service_addbook,SERVICESSETTINGS.exch_service_fbauth,SERVICESSETTINGS.exch_service_mailboxrep,SERVICESSETTINGS.exch_service_protservhost,SERVICESSETTINGS.exch_service_rpcclientaccess,SERVICESSETTINGS.exch_service_throttling

(Continued)

v Microsoft Exchange FileDistribution

v Microsoft Exchange MailSubmission

v Microsoft Exchange MailboxAssistants

v Microsoft Exchange Monitoring

v Microsoft Exchange ReplicationService

v Microsoft Exchange SearchIndexer

v Microsoft Exchange ServiceHost

v Microsoft Exchange Transport

v Microsoft Exchange TransportLog Search

v Microsoft Exchange AddressBook

v Microsoft ExchangeForms-Based Authenticationservice

v Microsoft Exchange MailboxReplication

v Microsoft Exchange ProtectedService Host

v Microsoft Exchange RPC ClientAccess

v Microsoft Exchange Throttling





ClusterProperties

CLUSTERSETTINGS.exch_cluster_server,CLUSTERSETTINGS.exch_history,CLUSTERSETTINGS.exch_subsystem

The cluster environment for theagent. The following settings areused:

v Cluster Server Name = Nameof the Exchange Cluster Server

v Exchange Agent History DataDirectory = Directory to storehistorical data of the MicrosoftExchange Server (if the historyfor Microsoft Exchange Serveris configured to be stored atthe monitoring agent)

v Exchange Subsystem ID =Name of the Cluster Servernode.

Note: The cluster environmentsettings are mandatory if youspecify a value for any of thecluster parameters. For ExchangeServer 2010, do not specify anyvalue in these fields.

For example:

v Cluster Server name =SCCCluster

v Exchange Agent History DataDirectory = c:\history

v Exchange Subsystem ID = node1

Validation of remotely configured valuesWhen you configure the agent remotely, the configuration values that you specify are validated. Thevalidation ensures that the values are specified for all the mandatory parameters.

The validation results are stored in a log file that is saved at the following locations on the ExchangeServer where the agent is installed:v ibm\itm\tmaitm6\logs (for the 32-bit agent)v ibm\itm\tmaitm6_x64\logs (for the 64-bit agent)

The agent configuration fails if any of the mandatory parameters are not configured. For informationabout mandatory parameters, see “Local installation and configuration” on page 21.When the agent configuration fails, the appropriate error message is displayed on the Tivoli EnterprisePortal or on the tacmd command line, in the following format:validation_test_name:error_messageThe message is also saved in the log file in the same format. The name of log file has the followingformat:kexconfig_hostname_timestamp.log

All the mandatory parameters are validated sequentially, and only one error code and message isdisplayed on the portal at a time. For example, if more than one mandatory parameters are notconfigured, the error code and the message for the first mandatory parameter is displayed on the portal.If all the mandatory parameters are configured, the other optional parameters are validated and the agentis configured. A confirmation message about the agent configuration is displayed on the portal.

You can view the log file to see the invalid configuration values. You can again configure the agent withcorrect configuration values.


Exchange servicesThe Microsoft Exchange Server provides services for each server role. You can view the services for eachserver role in the Exchange Configuration panel.

Microsoft Exchange Server 2003 provides the following Microsoft Exchange services:v MSExchangeISv MSExchangeMTAv RESvcv MSExchangeSAv SMTPSVCv W3SVC

Table 7 provides the Microsoft Exchange services for Microsoft Exchange Server 2007 and 2010.

Table 7. Microsoft Exchange services in Microsoft Exchange Server 2007 and 2010

Microsoft Exchange services Server roles

MSExchangeADTopology v Client Access role

v Mailbox role

v Unified Messaging role

v Hub Transport role

MSExchangeFDS v Client Access role


MSExchangeServiceHost v Client Access role


MSExchangeTransport v Hub Transport role

v Edge Transport role

MSExchangeAntispamUpdate v Edge Transport role


ADAM_MSExchange v Edge Transport role

EdgeCredentialSvc v Edge Transport role

MSExchangeMailboxAssistants v Mailbox role

MSExchangeMailSubmission v Mailbox role

MSExchangeRepl v Mailbox role

MSExchangeSearch v Mailbox role


MSExchangeSA v Mailbox role

W3Svc v All roles

MSSpeechService v Unified Messaging role

MSExchangeUM v Unified Messaging role

MSExchangeEdgeSync v Hub Transport role


Table 7. Microsoft Exchange services in Microsoft Exchange Server 2007 and 2010 (continued)


MSExchangeTransportLogSearch v Hub Transport role

v Mailbox role


MSExchangeMonitoring All roles

MSExchangePOP3 v Client Access role

MSExchangeIMAP4 v Client Access role

Table 8 provides the Microsoft Exchange services for Microsoft Exchange Server 2010.

Table 8. Microsoft Exchange services in Microsoft Exchange Server 2010

Microsoft Exchange services Server Roles

MSExchangeAB v Client Access role

MSExchangeFBA v Client Access role

MSExchangeMailboxReplication v Client Access role

MSExchangeProtectedServiceHost v Client Access role


MSExchangeRPC v Client Access role

v Mailbox role

MSExchangeThrottling v Mailbox role

Table 9 provides the Microsoft Exchange services in Microsoft Exchange Server 2013.

Table 9. Microsoft Exchange services in Microsoft Exchange Server 2013


MSExchangeAntispamUpdate v Edge Transport role


MSExchangeADTopology v Client Access role

v Mailbox role



MSExchangeEdgeSync Hub Transport role

IISAdmin All roles

MSExchangeIMAP4 Client Access role

MSExchangeIS Mailbox role

MSExchangeMailboxAssistants Mailbox role

MSExchangeRepl Mailbox role

MSExchangeMonitoring All roles

MSExchangePOP3 Client Access role

MSExchangeServiceHost v Client Access role



Table 9. Microsoft Exchange services in Microsoft Exchange Server 2013 (continued)


MSExchangeTransport v Hub Transport role


MSExchangeTransportLogSearch v Hub Transport role

v Mailbox role


MSExchangeUM Unified Messaging role

W3Svc All roles

MSExchangeMailboxReplication Client Access role

MSExchangeRPC v Client Access role

v Mailbox role

MSExchangeThrottling Mailbox role

MSExchangeDiagnostics v Client Access role

v Mailbox role

MSExchangeFrontEndTransport Client Access role

MSExchangeHM v Client Access role

v Mailbox role

MSExchangeIMAP4BE Mailbox role

MSExchangeDelivery Mailbox role

MSExchangeSubmission Mailbox role

MSExchangePOP3BE Mailbox role

MSExchangeFastSearch Mailbox role

HostControllerService Mailbox role

Wsbexchange Mailbox role

MSExchangeUMCR Client Access role

SearchExchangeTracing v Client Access role

v Mailbox role

FMS Mailbox role

Note: If you do not select a specific service in the Agent Configuration panel, the Microsoft ExchangeServer agent monitors all services that are available in Microsoft Exchange Server 2003, or later.

Attribute groups affected by configuration parametersWhen you configure the agent, some of the attribute groups are affected.

Table 10 provides information about the attribute groups that are affected by each configurationparameter, and the agent behavior when values are not specified for the parameters.

Table 10. Effect of configuration parameters on attributes

Parameter Affected attribute groupAgent behavior when parametervalue is not specified

Exchange Agent Interval MS Exchange IS Public, MS ExchangeIS Private

Default value of 2 minutes is used.


Table 10. Effect of configuration parameters on attributes (continued)

Parameter Affected attribute groupAgent behavior when parametervalue is not specified

Exchange Server Name Mailbox Detail, Reachability, PublicFolder Detail

No attribute data is returned.

Exchange Domain Name Mailbox Detail, Reachability, PublicFolder Detail, Role Based Topology


Exchange User Name

Exchange User Password

Mailbox Detail, Reachability, PublicFolder Detail, MAPI ConnectivityDetail


Exchange MAPI Profile Name Mailbox Detail, Reachability, PublicFolder Detail, MAPI ConnectivityDetail

No attribute data is returned.Note: Do not specify a value in theExchange MAPI Profile Name fieldif any of the following conditions istrue:

v You are using a 32-bit MicrosoftExchange Server agent to monitorMicrosoft Exchange Server 2010.

v You are using a 64-bit MicrosoftExchange Server agent to monitorMicrosoft Exchange Server 2007and 2010.

Enable Mailbox ReachabilityMonitoring

Reachability Reachability is considered asdisabled.

Target E-mail Addresses Reachability No attribute data is returned.

Email Transmission Interval(seconds)

Reachability Default value of 300 seconds is used.

Email Transmission Timeout(seconds)

Reachability Default value of 60 seconds is used.

Enable Mailbox Detail Monitoring Mailbox Detail Mailbox detail monitoring isconsidered as disabled.

Mailbox Detail Collection Start Time Mailbox Detail No attribute data is returned if thevalue is not updated after you startthe agent.

Mailbox Detail Collection Interval(seconds)

Mailbox Detail Default value of 86400 seconds isused.

Event Logs Collection Time(minutes)

Event Details Default value of 1440 minutes isused.

Maximum Number of Events Event Details Default value of 50 is used.

Exchange Topology Interval(seconds)

Role Based Topology Default value of 300 seconds is used.

Exchange Services Monitoring MS Exchange Server See the description of the ServerStatus attribute in the “MS ExchangeServer attributes” on page 164 fordefault settings and monitoredservices.

Cluster Properties All attribute groups The agent does not work as a clusterresource.


Starting and stopping the Microsoft Exchange Server agentYou can start and stop the Microsoft Exchange Server agent locally or remotely.

Table 11 shows the interfaces that you can use on Windows operating systems to start or stop themonitoring agent locally or remotely.

Table 11. Interfaces for starting and stopping the Microsoft Exchange Server agent locally and remotely

Local Remote

v Manage Tivoli Enterprise Monitoring Services

v tacmd startAgent

v tacmd stopAgent

v tacmd restartAgent

v Tivoli Enterprise Portal

v tacmd startAgent

v tacmd stopAgent

v tacmd restartAgent

For information about starting and stopping the agent, see the following topics:v “Starting the agent from the Manage Tivoli Enterprise Monitoring Services window”v “Tivoli Enterprise Portal”v “tacmd command line”

Starting the agent from the Manage Tivoli Enterprise MonitoringServices windowYou can start and stop the Microsoft Exchange Server agent from the Manage Tivoli EnterpriseMonitoring window.

Procedure

To start the Microsoft Exchange Server agent from the Manage Tivoli Enterprise Monitoring Serviceswindow, complete the following steps:1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services.2. In the Manage Tivoli Enterprise Monitoring Services window, right-click the instance of the Microsoft

Exchange Server agent, and click Start. Similarly, you can stop the agent.

Tivoli Enterprise PortalYou can use the Tivoli Enterprise Portal to start and stop the Microsoft Exchange Server agent.

See the "Working with monitoring agents" and "Starting and stopping a monitoring agent" topics in theIBM Tivoli Monitoring Installation and Setup Guide for information about using the Tivoli Enterprise Portalto start or stop the monitoring agent.

tacmd command lineYou can use the tacmd command line to start and stop the Microsoft Exchange Server agent.

In the following examples, the tacmd command is used to start, stop, or restart the Microsoft ExchangeServer instance named Primary. The instance is on a Windows system where myhostname is the short hostname for the system where the monitoring agent is running:v Local

– tacmd startAgent -t ex

– tacmd stopAgent -t ex

– tacmd restartAgent -t ex

v Remote


– tacmd stopagent -t ex -n Primary:myhostname:NT

– tacmd startagent -t ex -n Primary:myhostname:NT

– tacmd restartagent -t ex -n Primary:myhostname:NT

For information about using the tacmd commands, see the IBM Tivoli Monitoring Command Reference.

Microsoft Exchange Server agent in a cluster environmentYou can configure the Microsoft Exchange Server agent in a cluster environment.

The Microsoft Exchange Server agent can be configured in any of the following cluster environments:v Single Copy Cluster (SCC)v Cluster Continuous Replication (CCR)v Local Continuous Replication (LCR)v Single Continuous Replication (SCR)v Database Availability Group (DAG) for Exchange Server 2010, or later

Information in this topic is specific to configuring the Exchange Server agent in the SCC and CCR clusterenvironments.

To configure the agent in the cluster environment, complete the following tasks:v Install the agent on each node in the cluster.v Change the startup type for the agent to manual.v Add the agent as a cluster resource.v Configure the cluster parameters.

When the resources are moved from node to node, the server down situation event is triggered. Thisevent is triggered because the Microsoft Exchange Server agent comes online faster than the ExchangeServer. When the Exchange Server comes online, the server down event is cleared.

Note: When the agent is configured in a cluster environment, do not use Start and Stop Take Actioncommands because the use of these commands conflicts with the actions performed by the Cluster Server.

For more information about clustering, see IBM Tivoli Monitoring Installation and Setup Guide.

Setting up the agent startup as manualSet the startup parameter for the agent to manual so that the cluster resource can start or stop the agent.

Procedure

To configure the startup parameter, complete the following steps:1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services.2. In the Manage Tivoli Enterprise Monitoring Services window, right-click the instance of the Microsoft

Exchange Server agent, and click Change Startup.3. In the Service Startup for Microsoft Exchange Server agent window, select Manual.4. Click OK.

Addition of the agent service as a resourceYou must add the agent service as a resource in the cluster. You can start or stop the agent by using thecluster administrator after you add the agent service as a resource.


The cluster resource that you create for the agent service must be associated with the same clusterresource group that controls the Microsoft Exchange Server instance. For information about adding theagent service as a resource, see the following topics:v “Adding the agent service as a resource in Windows 2003 cluster”v “Adding the agent service as a resource in Windows 2008 cluster”

Adding the agent service as a resource in Windows 2003 clusterYou must add the agent service as a resource in the Windows 2003 cluster.

Before you begin

Ensure that the following tasks are completed:v Set up the cluster.v Install the Exchange Server on each node in the cluster.

Procedure

To add the agent service as a resource in Windows 2003 cluster, complete the following steps:1. Open the Cluster Administrator window.2. Right-click the resource group that is created for the agent, and click New > Resource.3. In the New Resource window, complete the following steps:

a. In the Name field, type a resource name.b. In the Description field, specify a description for the resource.c. From the Resource Type list, select Generic Service.d. Click Next.

4. In the Modify Possible Owners window, select all the nodes from the Available nodes list and clickthe arrow to move the nodes to the Possible owners list.

5. In the Dependencies window, do not select any dependencies, and click Next.6. Specify the service name as kexcma_Primary.7. Retain the default settings in all the other windows, and click Finish in the Summary window. The

agent service is added as a resource.8. Right-click Monitoring Agent for Microsoft Exchange Server, and click Bring Resource Online.

Adding the agent service as a resource in Windows 2008 clusterYou must add the agent service as a cluster resource in the Windows 2003 cluster.

Before you begin

Ensure that you complete the following tasks:v Set up the cluster.v Install the Exchange Server on each node in the cluster.

Procedure

To add the agent service as a resource in the Windows Server 2008 cluster, complete the following steps:1. Open the Failover Cluster Management window.2. In the left pane, right-click Services and Applications, and then click More Actions > Create Empty

Service or Application. The new service is displayed in the Services and Applications list.3. Rename the newly created service.4. Right-click the new service and click Add Resource > Generic Service.


5. In the New Resource Wizard window, select Monitoring Agent for Microsoft Exchange Server andclick Next.

6. Click Next in the subsequent windows until you see the Finish button.7. Click Finish. The agent service is added as a resource.8. Right-click Monitoring Agent for Microsoft Exchange Server and click Bring Resource Online.

Adding the script as a resourceYou must add the customized VB script as a resource in the cluster. This VB script is used for configuringthe cluster parameters in the SCC cluster environment with more than 2 nodes.

Before you begin

The shared disk on each active node in the cluster must contain this script, and the name of all the scriptsmust be the same.

Procedure

To add the VB script as a resource, complete the following steps:1. Click Start > Admin Tools > Cluster Administrator.2. Right-click the agent resource group, and click New > Resource.3. Select Generic Script as a resource type, and specify a name for the resource.4. Do not specify any owners for the resource, and click Next.5. Select the shared disk as a dependency, and click Next.6. Specify the path of the script on the shared disk of the Exchange Server.7. Click Finish.8. Right-click the resource, and click Bring Resource Online.

Results

The script is run and the cluster parameters are configured. Also, the agent is started on the currentactive node in the cluster.

Configuration of cluster parametersYou must configure the cluster parameters so that the agent works in the SCC and CCR clusterenvironments.

Before you configure the cluster parameters, ensure that you complete the following tasks:v Install and configure the Microsoft Exchange Server agent on each node in the cluster.v Add the agent service and the script as cluster resources.v Change the startup parameter for the agent to manual.

You can configure the following cluster parameters:

Cluster Server nameThe name of the Cluster Server. This name must be same for each node in the cluster.

Exchange subsystem IDThe name of the Cluster Server node.

Exchange agent history directoryThe location to store historical data files. If the historical data is stored at the Tivoli EnterpriseMonitoring Server, you can ignore this parameter. However, it is recommended that you do notstore the history at the Tivoli Enterprise Monitoring Server.


Note: The directory that you select for storing historical data must be on a local drive or a sharedphysical disk. Shared directory or mapped drives are not supported for this parameter.

For information about configuring cluster parameters, see “Local installation and configuration” on page21. A VB script is used for configuring the cluster parameters in the SCC cluster environment with morethan two nodes. The same VB script is used for configuring the cluster parameters of the agent on eachnode. Before you use the VB script for configuring the cluster parameters, ensure that no value isspecified for the cluster parameters, and the VB script is added as a resource in the cluster. Forinformation about adding the VB script as a resource, see “Adding the script as a resource” on page 45.

Before you run the VB script, you must update the values of the following variables in the VB script:v strCluster - The name of the cluster.v strSubSystemID - The host name of the active node.v strHistDir - The history directory location on the shared disk.

The VB script is the agent configuration utility. When the agent configuration utility is used to configurecluster parameters, the utility stops the monitoring agent. In a cluster environment, the agent service thatis added as a cluster resource controls the starting and stopping of the Exchange Server agent. When anagent is configured in a cluster environment, you must preferably start or stop the agent from the clustermanagement tool.

To start or stop the agent, the status of the agent service is changed from the online state to the offlinestate. If the agent configuration utility stops the agent, the Cluster Server notices that the agent isstopped. If other cluster resources in the cluster are in the online state, the Cluster Server tries to start theagent. If the agent fails to start, no data is displayed on the Tivoli Enterprise Portal.


Chapter 3. Workspaces reference

A workspace is the working area of the Tivoli Enterprise Portal application window. The Navigator treecontains a list of the workspaces provided by the agent.

About workspaces

Use the Navigator tree to select the workspace you want to see. As part of the application window, thestatus bar shows the Tivoli Enterprise Portal Server name and port number to which the displayedinformation applies and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed. When you right-click aNavigator item, a menu that includes a Workspace item is displayed. The Workspace item contains a listof workspaces for that Navigator item. Each workspace has at least one view. Some views have links toother workspaces. You can also use the Workspace Gallery tool as described in the Tivoli Enterprise PortalUser's Guide to open workspaces.

The workspaces in the Navigator are displayed in a Physical view that shows your enterprise as aphysical mapping or a dynamically populated logical view that is agent-specific. You can also create aLogical view. The Physical view is the default view.

This monitoring agent provides predefined workspaces. You cannot modify or delete the predefinedworkspaces, but you can create new workspaces by editing them and saving the changes with a differentname.

Workspace views can be any combination of query-based views, event views, and special purpose views.

Additional information about workspaces

For more information about creating, customizing, and working with workspaces, see the Tivoli EnterprisePortal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a description of each workspace,refer to the Predefined workspaces and the information about each individual workspace.

Predefined workspacesThe Microsoft Exchange Server agent provides predefined workspaces, which are organized by Navigatoritem.v Database Navigator item

– Database workspace– Database Logs workspace

v Events Navigator item– Event Logs workspace

v Information Store Navigator item– Information Store workspace– Information Store Historical workspace– IS Client workspace– Storage Group Detail workspace

v IS Mailbox Navigator item


– Activity workspace– Status workspace– Usage workspace– IS Private workspace– Mailbox Detail workspace– Database Availability Group workspace

v IS Public Navigator item– Activity workspace– Status workspace– Public Folder Detail workspace– IS Public workspace

v Microsoft Exchange Server Navigator item– Microsoft Exchange Server workspace

v MTA navigator item– MTA workspace

v Replication Navigator item– Replication workspace– Mailbox Replication (Exchange Server 2010) workspace

v Roles Navigator item– Mailbox Server workspace– Client Access Server workspace– Edge Transport Server workspace– Forefront Security workspace– Hub Transport Server workspace– Filter Reports workspace– Topology workspace– Unified Messaging Server workspace– Forefront Exchange On Demand and Transport Scanner workspace– Forefront Exchange Realtime and Scheduled Scanner workspace

v SMTP Navigator item– SMTP workspace

v Server Navigator item– Services Detail workspace– Reachability workspace– Store Driver workspace– Assistants workspace– Active Directory Activity workspace– Server Information workspace– Resource Scheduling Details workspace– Availability Service Details workspace– Address Book Service Details workspace– Web Service Details workspace

v Windows Systems Navigator item– Exchange Disk Space Utilization workspace– Exchange Information Store workspace


– Exchange LDAP Utilization workspace– Exchange .Net Processes workspace– Exchange Server Utilization workspace

Attribute groups used by predefined workspacesIn most cases, a workspace contains data or columns that have similar attributes in an attribute group.The following table shows the relationships between the predefined workspaces and the attribute groups.

Table 12. Relationships between the predefined workspaces and the attribute groups.

Workspace Related attribute group

Activity (IS Mailbox Navigator item) For all views, see “MS Exchange IS Private attributes” onpage 114.

Activity (IS Public Navigator item) For all views, see “MS Exchange IS Public attributes” onpage 117.

Client Access Server (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.

Database (Database Navigator item) For all views, see “MS Exchange DB attributes” on page98.

Database Availability Group (IS Mailbox Navigator item) For all views, see “MS Exchange Database AvailabilityGroup attributes” on page 97.

Database Logs (Database Navigator item) For all views, see “MS Exchange DB attributes” on page98.

Edge Transport Server (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.

Filter Reports (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.

Forefront Exchange On Demand and Transport Scanner(Roles Navigator item)

For the Forefront On Demand Scanner view, see“Forefront Exchange On Demand Scanner attributes” onpage 64.

For the Forefront Transport Scanner view, see“ForefrontExchange Transport Scanner attributes” on page 68.

Forefront Exchange Realtime and Scheduled Scanner(Roles Navigator item)

For the Forefront Realtime Scanner view, see “ForefrontExchange Realtime Scanner attributes” on page 66.

For the Forefront Scheduled Scanner view, see “ForefrontExchange Scheduled Scanner attributes” on page 67.

Forefront Security (Roles Navigator item) For all views, see “Microsoft Forefront Server SecurityScan attributes” on page 70.

Hub Transport Server (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.

Information Store Historical (Information Store Navigatoritem)

For all views, see “MS Exchange IS attributes” on page107.

Information Store (Information Store Navigator item) For all views, see “MS Exchange IS attributes” on page107.

IS Client (Information Store Navigator item) For all views, see “MS Exchange IS Client attributes” onpage 112.

Mailbox Server (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.

Chapter 3. Workspaces reference 49

Table 12. Relationships between the predefined workspaces and the attribute groups. (continued)


Microsoft Exchange Server (Microsoft Exchange ServerNavigator item)

For the MTA Connections Queue view, see “MSExchange MTA Connections attributes” on page 137.

For the MTA Work Queue view, see “MS Exchange MTAattributes” on page 136.

For the Server Status view, see “MS Exchange Serverattributes” on page 164.

For the SMTP Queues view, see “SMTP attributes” onpage 202.

MTA (MTA Navigator item) For the MTA Connection Message Rates view, see “MSExchange MTA Connections attributes” on page 137.

For the MTA LAN Rates and MTA Message Totals view,see “MS Exchange MTA attributes” on page 136.

SMTP (SMTP Navigator item) For all views, see “SMTP attributes” on page 202.

Status (IS Mailbox Navigator item) For all views, see “MS Exchange IS Private attributes” onpage 114.

Status (IS Public Navigator item) For all views, see “MS Exchange IS Public attributes” onpage 117.

Usage (IS Mailbox Navigator item) For all views, see “MS Exchange IS Private attributes” onpage 114.

Storage Group Detail (Information Store Navigator item) For all views, see “MS Exchange Storage Group Detailattributes” on page 172.

IS Private (IS Mailbox Navigator item) For all views, see “MS Exchange IS Private attributes” onpage 114.

Mailbox Detail (IS Mailbox Navigator item) For all views, see “MS Exchange Mailbox Detailattributes” on page 133.

Public Folder Detail (IS Public Navigator item) For all views, see “MS Exchange Public Folder Detailattributes” on page 142.

Topology (Roles Navigator item) For all views, see “MS Exchange Server attributes” onpage 164

Services Detail (Server Navigator item) For all views, see “MS Exchange Services Detailattributes” on page 171.

Reachability (Server Navigator item) For all views, see “MS Exchange Reachability attributes”on page 143.

Store Driver (Server Navigator item) For all views, see “MS Exchange Store Driver attributes”on page 173.

Assistants (Server Navigator item) For all views, see “MS Exchange Assistants attributes” onpage 86.

Active Directory Activity (Server Navigator item) For all views, see “MS Exchange ADAccess Processesattributes” on page 83.

IS Public (IS Public Navigator item) For all views, see “MS Exchange IS Public attributes” onpage 117.

Server Information (Server Navigator item) For all views, see “MS Exchange Server attributes” onpage 164.


Table 12. Relationships between the predefined workspaces and the attribute groups. (continued)


Unified Messaging Server (Roles Navigator Item) For the Services Details view, see “MS Exchange Serverattributes” on page 164.

For the UM Enabled Mailbox Details view, see “MSExchange UM Enabled User Details attributes” on page196.

For the Current Call Status view, see “MS Exchange UMGeneral attributes” on page 197.

For the Call Statistics view, see “MS Exchange UMGeneral attributes” on page 197.

For the Unified Messaging Availability view, see “MSExchange UM Availability attributes” on page 194.

Replication (Replication Navigator item) For all views, see “MS Exchange Replication attributes”on page 145.

Mailbox Replication (Exchange Server 2010) (ReplicationNavigator item)

For the Mailbox Replication Service view, see “MSExchange Mailbox Replication Service attributes” onpage 129.

For the Mailbox Replication Service Per Mdb view, see“MS Exchange Mailbox Replication Service per Mdbattributes” on page 130.

Event Logs (Events Navigator item) For all views, see “MS Exchange Event Detailsattributes” on page 105.

Store Interface (Server Navigator item) For all views, see “MS Exchange Store Interfaceattributes” on page 175.

Resource Scheduling Details (Server Navigator item) For the Resource Booking Statistics view, see “MSExchange Resource Booking attributes” on page 153.

For the Calendar Attendant Details view, see “MSExchange Calendar Attendant attributes” on page 91.

Workspace descriptionsEach workspace description provides information about the workspace such as the purpose and a list ofviews in the workspace.

Activity workspaceMonitors the activity of the Mailbox Information Store. This workspace provides the following views:v IS Mailbox Active Client Logonsv IS Mailbox Folders Openv IS Mailbox Messages Open

Activity workspaceMonitors the activity of the Public Information Store. This workspace provides the following views:v IS Public Folder Openv IS Public Messages Openv IS Public Size of Recoverable Items


Database workspaceMonitors database metrics. This workspace provides the following views:v Database Cache % Hitv Database Cache Sizev Database Tables Open

Database Logs workspaceMonitors database logs. This workspace provides the following views:v Database Logs Threads Waitingv Database Log Records Stallsv Database Log Writes

Information Store Historical workspaceMonitors Information Store historical metrics. This workspace provides the following views:v Information Store Connectionsv Information Store RPC Statusv Information Store User Information

The views contain data for a 24-hour period. You must enable historical data collection for the agent sothat data is available to populate this workspace. See the IBM Tivoli Monitoring User's Guide for moreinformation about historical data collection.

Information Store workspaceMonitors Information Store metrics. This workspace provides the following views:v Information Store Connectionsv Information Store RPC Statusv Information Store User Information

IS Client workspaceMonitors IS client metrics. This workspace provides the following views:v Top 10 Information Store Client RPC Statusv Top 10 Information Store Client Average Latency

Note: Top 10 Information Store Client RPC status view will display the data based on the top 10 RPCBytes Received/Sec and Top 10 IS Client Average Latency view will display the data based on the top 10RPC_Average_Latency

Storage Group Detail workspaceMonitors the storage groups that form the Exchange Server. This workspace provides the followingviews:v Storage Group Sizev Storage Group Information

Microsoft Exchange Server workspaceMonitors the key metrics for the server. This workspace provides the following views:v Server Statusv MTA Connections Queue (returns no data on Microsoft Exchange Server 2007 and 2010)v MTA Work Queue (returns no data on Microsoft Exchange Server 2007 and 2010)


v SMTP Queues (returns no data on Microsoft Exchange Server 2007 and 2010)

MTA workspace

Note: This workspace returns no data on Microsoft Exchange Server 2007, 2010.

Monitors MTA and MTA Connections. This workspace provides the following views:v MTA Connection Message Ratesv MTA LAN Ratesv MTA Message Totals

Mailbox Server workspaceMonitors Mailbox Server metrics. This workspace provides the following views:v Mailbox State Detailsv Service Details

Client Access Server workspaceMonitors Client Access Server metrics. This workspace provides the following views:v NLB Status Detailsv Services Detailsv Client RPC Statusv Client Connection Status

Edge Transport Server workspaceMonitors Edge Transport Server metrics. This workspace provides the following views:v Attachment Filteringv Services Details

Forefront Security workspaceMonitors Forefront Security metrics. This workspace provides the Forefront Security Plot chart view.

Hub Transport Server workspaceMonitors Hub Transport Server metrics. This workspace provides the Services Details views.

Filter Reports workspaceMonitors Filter Reports metrics. This workspace provides the following views:v Connection Filteringv Protocol Analysis Detailsv Content Filteringv Sender Filterv Recipient Filter

Topology workspaceMonitors Topology metrics. This workspace provides the Topology view.


Unified Messaging Server workspaceMonitors Unified Messaging Server metrics. This workspace provides the following views:v Services Detailsv UM Enabled Mailbox Detailsv Current Call Statusv Call Statisticsv Unified Messaging Availability

SMTP workspace

Note: This workspace returns no data on Microsoft Exchange Server 2007, and Exchange Server 2010.

Monitors SMTP metrics. This workspace provides the following views:v SMTP Current Connectionsv SMTP Message Ratesv SMTP NDRs Generatedv SMTP Retry Queues

Status workspaceMonitors the status of Mailbox Information Store messages. This workspace provides the following views:v IS Mailbox Average Delivery Timev IS Mailbox Message Ratev IS Mailbox Queue Status

Status workspaceMonitors the status of IS Public messages. This workspace provides the following views:v IS Public Average Delivery Timev IS Public Message Statusv IS Public Queue Status

Public Folder Detail workspaceProvides details about the IS Public folder. This workspace provides the following views:v Public Folder Sizev Public Information Store Detail

Usage workspaceMonitors the Mailbox Information Store messages. This workspace provides the following views:v IS Mailbox Count of Recoverable Itemsv IS Mailbox Single Instance Ratiov IS Mailbox Size of Recoverable Items

IS Private workspaceProvides the Exchange Server Information Store Private statistics. This workspace provides the followingviews:v Mailbox Information Store Sizev Mailbox Information Store Details


Mailbox Detail workspaceProvides detail information about mailbox utilization with a storage group. This workspace provides thefollowing views:v Mailbox Sizev Mailbox Details

Database Availability Group workspaceProvides detail information about database availability group. This workspace provides the followingviews:v DAG Configurationv Mailbox Database Copies

Exchange Disk Space Utilization workspaceProvides information about the disk space utilization on the Exchange Servers. This workspace providesthe Free Disk Space Availability view.

Exchange Information Store workspaceProvides information about the Microsoft Exchange Information store. This workspace provides thefollowing views:v User Countv RPC Requestsv Private Average Local/Remote Delivery Timev Public Average Local/Remote Delivery Time

Exchange LDAP Utilization workspaceProvides information about the LDAP utilization of the Exchange Servers. This workspace provides thefollowing views:v Exchange LDAP Searchesv Exchange Instantaneous LDAP Searches

Exchange .Net Processes workspaceProvides information about the processes of the Exchange .net. This workspace provides the followingviews:v Exchange .Net Processes

Exchange Server Utilization workspaceProvides information about the utilization of the Exchange server. This workspace provides the followingviews:v % Processor Time(store.exe)v % Processor Time(inteinfo.exe)v % Processor Time(mad.exe)

Forefront Exchange On Demand and Transport Scanner workspaceProvides information about Forefront Exchange On Demand and Transport Scanner attribute group. Thisworkspace provides the following views:v Forefront On Demand Scannerv Forefront Transport Scanner


Forefront Exchange Realtime and Scheduled Scanner workspaceProvides information about Forefront Exchange Realtime and Scheduled Scanner attribute group. Thisworkspace provides the following views:v Forefront Realtime Scannerv Forefront Scheduled Scanner

Services Detail workspaceProvides details about the services that form the Microsoft Exchange Server. This workspace provides thefollowing views:v Situation Event Consolev Services Detail

Reachability workspaceProvides details about mailbox reachability. This workspace provides the following views:v Situation Event Consolev Reachability Detail

Store Driver workspaceProvides details about messages from the transport pipeline. This workspace provides the followingviews:v Inbound Recipientsv Store Driver Information

Assistants workspaceMonitors the Microsoft Exchange Server Assistants services activity. This workspace provides thefollowing views:v Situation Event Consolev Exchange Assistants Information

Active Directory Activity workspaceMonitors the Microsoft Exchange Server Active Directory activity. This workspace provides the followingviews:v Situation Event Consolev Active Directory Activity

IS Public workspaceMonitors the public folders and stores. This workspace provides the following views:v Public Information Store Sizev Public Information Store Detail

Server Information workspaceMonitors the server status and status of some key services. This workspace provides the following views:v Server Informationv Server Status


Replication workspaceProvides information about the replication activity on the Exchange Server. This workspace provides thefollowing views:v Replication on Current Nodev Replication on Remote Nodev Copy Status

Mailbox Replication (Exchange Server 2010) workspaceProvides information about the replication activity on Exchange Server 2010. This workspace provides thefollowing views:v Mailbox Replication Servicev Mailbox Replication Service Per Mdb

Event Logs workspaceProvides information about the event logs on Exchange Server 2003, 2007, and 2010. This workspaceprovides the Event Log Details view.

Store Interface workspaceProvides information about the interface between the Exchange Information Store service on the MailboxServer and the Hub Transport servers. This workspace provides the Store Interface Information view.

Resource Scheduling Details workspaceProvides information about the activities of the Resource Booking Attendant and the Calendar Attendant.This workspace provides the following views:v Resource Booking Statisticsv Calendar Attendant Details

Availability Service Details workspaceProvides information about the status of the Availability service on Exchange Server 2007 and 2010. Thisworkspace provides the Availability Service Details view.

Note: This workspace provides information only when the Client Access Server (CAS) role is installed onthe server.

Address Book Service Details workspaceProvides information about the status of the Address Book service on Exchange Server 2010. Thisworkspace provides the Address Book Service Details view.

Note: This workspace provides information only when the CAS role is installed on the server.

Web Service Details workspaceProvides information about the status of the Exchange Web Services (EWS) on Exchange Server 2007 and2010. This workspace provides the Web Service Details view.

Note: This workspace provides information only when the CAS role is installed on the server.

Authentication workspaceProvides information about the user authentication activities on the Exchange Server. This workspaceprovides the following views:


v Authentication Requestsv Authentication Details

DSN workspaceProvides information about the delivery status notifications (DSN) for messages that are sent to theMailbox Transport Delivery service and the Mailbox Transport submission service. This workspaceprovides the following views:v Delivery DSNv Submission DSN

Mail Submission workspaceProvides information about the submission of messages from the Mailbox server to the Hub Transportserver. This workspace provides the following views:v Submissionsv Submission Details

Mailbox Search Cache workspaceProvides information about the cache activities that occur when you search content on the ExchangeServer. This workspace provides the following views:v Mailbox Search Cache Statisticsv Mailbox Search Cache Details


Chapter 4. Attributes reference

Attributes are the application properties that are being measured and reported by the IBM TivoliComposite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent.

About attributes

Attributes are the application properties being measured and reported by the Microsoft Exchange Serveragent, such as queue size or message throughput.

Attributes are organized into groups according to their purpose. The attributes in a group can be used inthe following two ways:v Chart or table views

Attributes are displayed in chart and table views. The chart and table views use queries to specifywhich attribute values to request from a monitoring agent. You use the Query editor to create a newquery, modify an existing query, or apply filters and set styles to define the content and appearance ofa view based on an existing query.

v SituationsYou use attributes to create situations that monitor the state of your operating system, database, orapplication. A situation describes a condition you want to test. When you start a situation, the TivoliEnterprise Portal compares the values you have assigned to the situation attributes with the valuescollected by the Microsoft Exchange Server agent and registers an event if the condition is met. You arealerted to events by indicator icons that appear in the Navigator.

Additional information about attributes

For more information about using attributes and attribute groups, see the Tivoli Enterprise Portal User'sGuide.

For a list of the attributes groups, a list of the attributes in each attribute group, and descriptions of theattributes for this monitoring agent, refer to the Attribute groups and attributes section in this chapter.

Attribute groups and Microsoft Exchange 2007 and 2010 Server rolesThis section provides a list of attribute groups that require Microsoft Exchange 2007 and 2010 Server rolesto enable attribute values to be displayed when monitoring a Microsoft Exchange Server 2007 and 2010environment.

Table 13 contains the name of the Microsoft Exchange 2007 and 2010 Server role to be used with eachattribute group. If the required role is not configured, no data, or -1 ("Undefined"), is returned.

Table 13. Attribute groups and Microsoft Exchange 2007 and 2010 Server roles

Attribute group Microsoft Exchange 2007 Server role Microsoft Exchange 2010 Server role

Forefront Exchange On DemandScanner

CAS role CAS role

Forefront Exchange Realtime Scanner Mailbox role Mailbox role

Forefront Exchange ScheduledScanner

Mailbox role Mailbox role

Forefront Exchange TransportScanner

Hub Transport role and EdgeTransport role

Hub Transport role Edge Transportrole


Table 13. Attribute groups and Microsoft Exchange 2007 and 2010 Server roles (continued)


Mailbox Server Cluster State Mailbox Server role Not applicable

Microsoft Forefront Server SecurityScan

Edge Transport role and HubTransport role

Not applicable

MS Exchange Active Sync Client Access role Client Access role

MS Exchange ADAccess Caches Client Access role, Edge Transportrole, or Mailbox Server role, orUnified Messaging role, or HubTransport role

Client Access role, Edge Transportrole, or Mailbox Server role, orUnified Messaging role, or HubTransport role

MS Exchange ADAccess DomainControllers

Mailbox Server role Mailbox Server role

MS Exchange ADAccess Processes Client Access role, Edge Transportrole, or Mailbox Server role, orUnified Messaging role, or HubTransport role

Client Access role, Edge Transportrole, or Mailbox Server role, orUnified Messaging role, or HubTransport role

MS Exchange Address Book Not applicable Client Access Server role

MS Exchange Assistants Mailbox Server role Mailbox Server role

MS Exchange Assistants Per Database Not applicable Mailbox role

MS Exchange Attachment Filtering Edge Transport role Edge Transport role

MS Exchange Availability Service Client Access Server role Client Access Server role

MS Exchange Autodiscover Service Client Access Server role Client Access Server role

MS Exchange Calendar Attendant Mailbox Server role Mailbox Server role

MS Exchange Connection FilteringAgent

Edge Transport role or Hub Transportrole


MS Exchange Content Filter Agent Edge Transport role or Hub Transportrole


MS Exchange Control Panel (RBAC) Not applicable Mailbox role, Unified Messaging role,CAS role, Hub role

MS Exchange Database AvailabilityGroup

Not applicable Mailbox role

MS Exchange DB Edge Transport role, Hub Transportrole, or Mailbox Server role

Edge Transport role, Hub Transportrole, or Mailbox Server role

MS Exchange DB Instance Edge Transport role, Hub Transportrole, or Mailbox role

Edge Transport role, Hub Transportrole, or Mailbox role

MS Exchange Event Details Edge Transport role, Hub Transportrole, Client Access Server role,Mailbox Server role, or UnifiedMessaging role

Edge Transport role, Hub Transportrole, Client Access Server role,Mailbox Server role, or UnifiedMessaging role

MS Exchange Extensibility Agents Edge Transport role or Hub Transportrole


MS Exchange FDS OAB Client Access Server role Client Access Server role

MS Exchange IS Mailbox Server role Mailbox Server role

MS Exchange IS Client Mailbox Server role Mailbox Server role

MS Exchange IS Private Mailbox Server role Mailbox Server role

MS Exchange IS Public Mailbox Server role Mailbox Server role

MS Exchange IS Public Replication Mailbox Server role Mailbox Server role




MS Exchange Mail Submission Mailbox Server role Mailbox Server role

MS Exchange Mailbox ReplicationService


MS Exchange Mailbox ReplicationService per Mdb


MS Exchange Mailbox Detail Mailbox Server role Mailbox Server role

MS Exchange Managed FolderAssistant

Mailbox role Mailbox role

MS Exchange NLB Status Client Access role Client Access role

MS Exchange OWA Client Access role Client Access role

MS Exchange Protocol AnalysisAgent



MS Exchange Public Folder Detail Mailbox Server role Mailbox Server role

MS Exchange Recipient Cache Hub Transport role Hub Transport role

MS Exchange Recipient Filter Edge Transport role or Hub Transportrole


MS Exchange Replication Mailbox Server role Mailbox Server role

MS Exchange Replica Seeder Mailbox Server role Mailbox Server role

MS Exchange Resource Booking Mailbox Server role Mailbox Server role

MS Exchange Rights ManagementService

Not applicable Mailbox role, Unified Messaging role,CAS role, Hub role

MS Exchange Role Based Service Mailbox Server role, Edge Transportrole, Hub Transport role, UnifiedMessaging role, or CAS role

Mailbox Server role, Edge Transportrole, Hub Transport role, UnifiedMessaging role, or CAS role

MS Exchange Role Topology Not applicable Not applicable

MS Exchange RPC Client Access Not applicable Client Access Server role

MS Exchange Search Indices Mailbox Server role Mailbox Server role

MS Exchange Sender Filter Agent Edge Transport role or Hub Transportrole


MS Exchange Sender ID Agent Edge Transport role or Hub Transportrole


MS Exchange Server Not applicable Not applicable

MS Exchange Services Detail Mailbox Server role, Edge Transportrole, Hub Transport role, UnifiedMessaging role, or CAS role

Mailbox Server role, Edge Transportrole, Hub Transport role, UnifiedMessaging role, or CAS role

MS Exchange Storage Group Detail Mailbox Server role Not applicable

MS Exchange Store Driver Hub Transport role Hub Transport role

MS Exchange Store Interface Mailbox Server role or Hub Transportrole

Mailbox Server role or Hub Transportrole

MS Exchange Text Messaging Not applicable Hub Transport role

MS Exchange Throttling Mailbox Server role Mailbox Server role

MS Exchange Transport Database Hub Transport Server role, Edge role Hub Transport Server role, Edge role

MS Exchange Transport Dumpster Hub Transport Server role, Edge role Hub Transport Server role, Edge role

Chapter 4. Attributes reference 61



MS Exchange Transport Queues Edge Transport role or Hub Transportrole


MS Exchange Transport Rules Hub Transport role Hub Transport role

MS Exchange Transport ShadowRedundancy

Not applicable Hub Transport Server role, Edge role

MS Exchange Transport SmtpReceive Edge Transport role or Hub Transportrole


MS Exchange Transport SmtpSend Edge Transport role or Hub Transportrole


MS Exchange UM Auto Attendant Unified Messaging role Unified Messaging role

MS Exchange UM Availability Unified Messaging role Unified Messaging role

MS Exchange UM Call Answer Unified Messaging role Unified Messaging role

MS Exchange UM General Unified Messaging role Unified Messaging role

MS Exchange UM Enabled UserDetails

Mailbox Server role Mailbox Server role

MS Exchange UM Subscriber Access Unified Messaging role Unified Messaging role

MS Exchange Web Services Client Access Server role Client Access Server role

RPC/HTTP Proxy Client Access Server role Client Access Server role

Attributes in each attribute groupAttributes in each Microsoft Exchange Server agent attribute group collect data that the agent uses formonitoring.

This monitoring agent contains the following attribute groups:v Forefront Exchange On Demand Scanner attributesv Forefront Exchange Realtime Scanner attributesv Forefront Exchange Scheduled Scanner attributesv Forefront Exchange Transport Scanner attributesv Mailbox Server Cluster State attributesv Microsoft Forefront Server Security Scan attributesv MS Exchange Active Manager attributesv MS Exchange Active Manager Client attributesv MS Exchange Active Manager Server attributesv MS Exchange Active Sync attributesv MS Exchange ADAccess Caches attributesv MS Exchange ADAccess Domain Controllers attributesv MS Exchange ADAccess Forest Discoveryv MS Exchange ADAccess Processes attributesv MS Exchange Address Book attributesv MS Exchange Assistants attributesv MS Exchange Assistants Per Database attributesv MS Exchange Attachment Filtering attributesv MS Exchange Authentication


v MS Exchange Autodiscover Service attributesv MS Exchange Availability Service attributesv MS Exchange Calendar Attendant attributesv MS Exchange Connection Filtering Agent attributesv MS Exchange Content Filter Agent attributesv MS Exchange Control Panel (RBAC) attributesv MS Exchange Database Availability Group attributesv MS Exchange DB attributesv MS Exchange DB Instance attributesv MS Exchange Delivery DSNv MS Exchange DS attributesv MS Exchange Event Details attributesv MS Exchange Extensibility Agents attributesv MS Exchange FDS OAB attributesv MS Exchange IS attributesv MS Exchange IS Client attributesv MS Exchange IS HA Active Databasev MS Exchange IS Private attributesv MS Exchange IS Public attributesv MS Exchange IS Public Replication attributesv MS Exchange IS Store attributesv MS Exchange Lotus Notes Connector Summary attributesv MS Exchange Mail Submission attributesv MS Exchange Mail Tips attributesv MS Exchange Mailbox Replication Service attributesv MS Exchange Mailbox Replication Service per Mdb attributesv MS Exchange Mailbox Detail attributesv MS Exchange Managed Folder Assistant attributesv MS Exchange MAPI Connectivity Details attributesv MS Exchange MTA attributesv MS Exchange MTA Connections attributesv MS Exchange NLB Status attributesv MS Exchange OWA attributesv MS Exchange Protocol Analysis Agent attributesv MS Exchange Public Folder Detail attributesv MS Exchange Reachability attributesv MS Exchange Recipient Cache attributesv MS Exchange Recipient Filter Agent attributesv MS Exchange Replication attributesv MS Exchange Replication attributes (Superseded)v MS Exchange Replica Seeder attributesv MS Exchange Replication Server attributesv MS Exchange Resource Booking attributesv MS Exchange Resource Health attributesv MS Exchange Rights Management Service attributes


v MS Exchange Role Based Services attributesv MS Exchange Role Topology attributesv MS Exchange RPC Client Access attributesv MS Exchange Search Indices attributesv MS Exchange Search Mailbox Operatorsv MS Exchange Search Mailbox Session Cachev MS Exchange Sender Filter Agent attributesv MS Exchange Sender ID Agent attributesv MS Exchange Server attributesv MS Exchange Services Detail attributesv MS Exchange Storage Group Detail attributesv MS Exchange Store Driver attributesv MS Exchange Store Driver Database attributesv MS Exchange Store Driver Server attributesv MS Exchange Store Interface attributesv MS Exchange Submissionv MS Exchange Submission DSNv MS Exchange Text Messaging attributesv MS Exchange Throttling attributesv MS Exchange Transport Database attributesv MS Exchange Transport Dumpster attributesv MS Exchange Transport Queues attributesv MS Exchange Transport Rules attributesv MS Exchange Transport Shadow Redundancy attributesv MS Exchange Transport SMTP Availability attributesv MS Exchange Transport SmtpReceive attributesv MS Exchange Transport SmtpSend attributesv MS Exchange UM Auto Attendant attributesv MS Exchange UM Availability attributesv MS Exchange UM Call Answer attributesv MS Exchange UM Enabled User Details attributesv MS Exchange UM General attributesv MS Exchange UM Subscriber Access attributesv MS Exchange Web Services attributesv RPC/HTTP Proxy attributesv SMTP attributes

Forefront Exchange On Demand Scanner attributesThis group of data monitors the activity of the Forefront Exchange On Demand Scanner. The _Totalinstance name displays values for all process instances that are currently active. If a process exits, the_Total instance does not display the data. _RunningTotal and _CumulativeTotal instances display the datasince Microsoft Forefront Protection 2010 for Exchange Server was installed.

Note: The attribute group is available only in Exchange Server 2007 and its service packs and ExchangeServer 2010. This attribute group is a multi-instance attribute group.


On Demand Scanner Job Name The name of the Forefront Exchange On Demand Scanner instance. Thevalue format is an alphanumeric string with a maximum length of 600 characters.

Malware Message Parts Cleaned The number of message parts that are removed because they aredetected as malware. The value format is a 4-byte integer.

Malware Message Parts Deleted The number of message parts that are deleted because they are detectedas malware. The message parts are deleted because the delete action is configured or because a cleaningoperation failed. The value format is a 4-byte integer.

Malware Message Parts Detected The number of message parts that are detected as malware. The valueformat is a 4-byte integer.

Malware Message Parts Quarantined The number of message parts that are quarantined because theyare detected as malware. The value format is a 4-byte integer.

Message Parts Scanned The number of message parts that are scanned. The value format is a 4-byteinteger.

Message Parts Scanned/sec The number of message parts that are scanned per second. The value formatis a 4-byte float.

Messages Scanned/sec The number of messages that are scanned per second. The value format is a4-byte float.

Sender Filter Messages Detected The number of messages that are detected because the sender of themessages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Messages Quarantined The number of messages that are quarantined because the sender ofthe messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Messages Skipped The number of messages that are detected because the sender of themessages matches a sender-domain filter, but the messages are routed normally. The skip action is usedwhen the scanner is configured and when the license exceeds the grace period. The value format is a4-byte integer.

Subject Filter Messages Detected The number of messages that are detected because the subject linematches a subject line filter. The value format is a 4-byte integer.

Subject Filter Messages Quarantined The number of messages that are quarantined because the subjectline matches a subject line filter. The value format is a 4-byte integer.

Subject Filter Messages Skipped The number of messages that are detected because the subject linematches a subject line filter, but the messages are routed normally. The skip action is used when thescanner is configured and when the license exceeds the grace period. The value format is a 4-byte integer.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is an alphanumeric string with amaximum length of 64 characters.

Timestamp The time when the data was collected. The format is MM/DD/YY HH:mm:SS, where thefollowing measures apply:

MM Month

DD Day


YY Year

HH Hour

mm Minute

SS Second

Forefront Exchange Realtime Scanner attributesThis group of data monitors the Forefront Exchange Realtime Scanner activity. The _Total instance namedisplays values for all process instances that are currently active. If a process exits, the _Total instancedoes not display the data. _RunningTotal and _CumulativeTotal instances display the data since MicrosoftForefront Protection 2010 for Exchange Server was installed.


Realtime Scanner Job Name The name of the Forefront Exchange Realtime Scanner instance. The value isan alphanumeric string with a maximum length of 600 characters.


Malware Message Parts Deleted The number of message parts that are deleted because they are detectedas malware. The message parts are deleted because the delete action was configured or because acleaning operation failed. The value format is a 4-byte integer.






Sender Filter Message Parts Detected The number of message parts that are detected because the senderof the messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Message Parts Quarantined The number of message parts that are quarantined because thesender of the messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Message Parts Skipped The number of message parts that are detected because the senderof the messages matches a sender-domain filter, but the message parts are routed normally. The skipaction is used when the scanner is configured and when the license exceeds the grace period. The valueformat is a 4-byte integer.

Subject Filter Message Parts Detected The number of message parts detected because the subject linematches a subject line filter. The value format is a 4-byte integer.


Subject Filter Message Parts Quarantined The number of message parts quarantined because the subjectline matches a subject line filter. The value format is a 4-byte integer.

Subject Filter Message Parts Skipped The number of message parts that are detected because the subjectline matches a subject line filter, but the message parts are routed normally. The skip action is used whenthe scanner configured and when the license exceeds the grace period. The value format is a 4-byteinteger.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Forefront Exchange Scheduled Scanner attributesThis group of data Monitors the activity of the Forefront Exchange Scheduled Scanner. The _Totalinstance name displays values for all process instances that are currently active. If a process exits, the_Total instance does not display the data. _RunningTotal and _CumulativeTotal instances display the datasince Microsoft Forefront Protection 2010 for Exchange Server was installed.


Scheduled Scanner Job Name The name of the Forefront Exchange Scheduled Scanner instance. Thevalue is an alphanumeric string with a maximum length of 600 characters.


Malware Message Parts Deleted The number of message parts that are deleted because they are detectedas malware. A deletion occurs because the delete action was configured or because a cleaning operationfailed. The value format is a 4-byte integer.







Sender Filter Message Parts Detected The number of message parts that are detected because the senderof the messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Message Parts Quarantined The number of message parts that are quarantined because thesender of the messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Message Parts Skipped The number of message parts that are detected because the senderof the messages matches sender-domain filter, but the message parts are routed normally. The skip actionis used when the scanner is configured and when the license exceeds the grace period. The value formatis a 4-byte integer.

Subject Filter Message Parts Detected The number of message parts that are detected because the subjectline matches a subject line filter. The value format is a 4-byte integer.

Subject Filter Message Parts Quarantined The number of message parts that are quarantined becausethe subject line matches a subject line filter. The value format is a 4-byte integer.

Subject Filter Message Parts Skipped The number of message parts that are detected because the subjectline matches a subject line filter, but the message parts are routed normally. The skip action is used whenthe scanner is configured and when the license exceeds the grace period. The value format is a 4-byteinteger.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Forefront Exchange Transport Scanner attributesThis group of data represents Forefront Exchange Transport Scanner. The _Total instance name displaysvalues for all process instances that are currently active. If a process exits, the _Total instance does notdisplay the data. _RunningTotal and _CumulativeTotal instances display the data since MicrosoftForefront Protection 2010 for Exchange Server was installed.


Transport Scanner Job Name The name of the Forefront Exchange Transport Scanner instance. The valueformat is an alphanumeric string with a maximum length of 600 characters.

Malware Message Parts Cleaned The number of message parts that are cleaned because they aredetected as malware. The value format is a 4-byte integer.


Malware Message Parts Deleted The number of message parts that are deleted because they are detectedas malware. A deletion occurs because the delete action was configured or because a cleaning operationfailed. The value format is a 4-byte integer.






Sender Filter Messages Detected The number of messages that are detected because the sender of themessages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Messages Quarantined The number of messages that are quarantined because the sender ofthe messages matches a sender-domain filter. The value format is a 4-byte integer.

Sender Filter Messages Skipped The number of messages that are detected because the sender of themessages matches sender-domain filter, but the messages are routed normally. The skip action is usedwhen the scanner is configured and when the license exceeds the grace period. The value format is a4-byte integer.

Subject Filter Messages Detected The number of messages that are detected because the subject linematches a subject line filter. The value format is a 4-byte integer.

Subject Filter Messages Quarantined The number of messages that are quarantined because the subjectline matches a subject line filter. The value format is a 4-byte integer.

Subject Filter Messages Skipped The number of messages that are detected because the subject linematches a subject line filter, but the messages are routed normally. The skip action is used when thescanner is configured and when the license exceeds the grace period. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


Mailbox Server Cluster State attributesThis group of data provides details about mailbox server state in the cluster.

Note: This attribute group is available only in Exchange Server 2007. You must configure this attributegroup in a cluster environment.

Clustered Mailbox Server Name Provides the name of the clustered mailbox server.

Mailbox State Gives the current state of the mailbox server. The following table gives the possible Enumvalues of the attribute.

Internal value External value Meaning

0 Online The server is completely online.

1 Partially Online One or more resources of the server are not online.

2 Online Pending One or more resources of the server are still coming online.

3 Offline The server is completely offline.

4 Offline Pending One or more resources of the server are still going offline.

5 Failed One or more resources have failed.

Operational Machines Gives the list of computers that are a part of the mailbox server cluster.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric with a maximum of 64characters.

Timestamp The time when this data was collected. The format is MM/DD/YY HH:mm:SS, where thefollowing measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Microsoft Forefront Server Security Scan attributesThis group of data provides details about SMTP Send Service.

Note: This attribute group is available only in Exchange Server 2007. This attribute group is amulti-instance attribute group.

Attachments Cleaned Rate The rate at which the cleaned attachments are scanned.

Attachments Detected Rate The rate at which the detected attachments are scanned.

Attachments Removed Rate The rate at which the removed attachments are scanned.

Attachments Scanned Rate The rate at which attachments are scanned.

Scan Job Name The name of the scan job instance.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Attachments Cleaned The total number of cleaned attachments that were scanned.

Total Attachments Detected The total number of detected attachments that were scanned.

Total Attachments Removed The total number of removed attachments that were scanned.

Total Attachments Scanned The total number of attachments that were scanned.

Total Messages Detected The total number of detected messages that were scanned.

Total Messages Purged The total number of purged messages that were scanned.

Total Messages Scanned The total number of messages that were scanned.

Total Messages Tagged The total number of tagged messages that were scanned.

MS Exchange Active Manager attributesThis attribute group contains attributes that are related to the Active Manager.

Note: The attribute group is available in Exchange Server 2010, or later. This attribute group is amulti-instance attribute group.

Active Manager Instance Name The name of the Active Manager instance. The value format is analphanumeric string with a maximum length of 600 characters.

Database Copy Role Active A numeric value that indicates whether the database copy is active. Thevalue is Yes for an active copy and No for a passive copy. The value format is a 4-byte integer. Thefollowing table gives the possible Enum values of the attribute:

Enum Value Value

0 No

1 Yes

-1 Undefined

Note: This attribute is available in Microsoft Exchange Server 2010 SP1 only.

Database Mounted A numeric value that indicates whether the database is mounted. The value is Yes ifthe database is mounted and No if the database is not mounted. The value format is a 4-byte integer.


Enum Value Value

0 No

1 Yes

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value format is an alphanumeric string with amaximum length of 64 characters.

Timestamp The time when data was collected. The format is MM/DD/YY HH:mm:SS, where thefollowing measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Active Manager Client attributesThis attribute group contains attributes that are related to the Active Manager client.


Active Manger Client Instance Name The name of the Active Manager client instance. The value formatis an alphanumeric string with a maximum length of 600 characters.

Client Side Cache Hits The total number of GetServerForDatabase calls that have been processed by thecache without making a remote procedure call to the Microsoft Exchange Information Store since theservice was started. The value format is a 4-byte integer.

Client Side Cache Misses The total number of GetServerForDatabase calls that require a remoteprocedure call to the Microsoft Exchange Information Store since the service was started. The remoteprocedure calls are required because the cache does not contain the updated server information. Thevalue format is a 4-byte integer.

Client Side Calls The total number of GetServerForDatabase calls to the Microsoft Exchange InformationStore between the start and end of the process since the service was started. The value format is a 4-byteinteger.

Client Side Calls ReadThrough The number of GetServerForDatabase calls using the ReadThrough flagsince the service was started. The value format is a 4-byte integer.

Client Side Calls/Sec The current rate (per second) at which remote clients are querying for the serverthat hosts a specific mailbox database. The value format is a 4-byte float.

Client Side RPC Calls The sum of Client Side Calls Read Through and Client Side Cache Missesattribute values since the service was started. The value format is a 4-byte integer.

Location Cache Entries The total number of entries in the location cache since the service was started.The value format is a 4-byte integer.


Server Information Cache Entries The total number of entries in the server information cache since theservice was started. The value format is a 4-byte integer.

Server Information Cache Hits The total number of GetServerForDatabase calls that have been processedby the cache without querying the Active Directory since the service was started. The value format is a4-byte integer.

Server Information Cache Misses The total number of GetServerForDatabase calls that have queried theActive Directory since the service was started. The queries to Active Directory are required because thecache does not contain the updated server information. The value format is a 4-byte integer.

Unique Databases Queried The total number of unique databases that have been returned by theGetServerForDatabase requests since the service was started. The value format is a 4-byte integer.

Unique Servers Queried The total number of unique servers that have been returned by theGetServerForDatabase requests since the service was started. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Active Manager Server attributesThis attribute group contains attributes that are related to the Active Manager server.

Note: The attribute group is available in Exchange Server 2010, or later. This attribute group is a singleinstance attribute group.

Active Manager Database State Writes To Persistent Storage The number of write operations to apersistent storage between the start and end of a process. The write operations update the database stateinformation. The value format is a 4-byte integer.

Active Manager Database State Writes To Persistent Storage/Sec The current rate at which the databasestate information is written to persistent storage per second. The value format is a 4-byte float.

GetServerForDatabase Server Side Calls The number of GetServerForDatabase calls between the startand end of a process since the service was started. The value format is a 4-byte integer.

Server Side Calls/Sec The rate at which remote clients are querying the current server that hosts aspecific mailbox database. The value format is a 4-byte float.

Total Number Of Databases The current number of databases on the computer where the MicrosoftExchange Server is configured. The value format is a 4-byte integer.





MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Active Sync attributesThis attribute group monitors the Exchange Server integrated support for mobile devices.

Average Request Time The average time (in milliseconds) that elapsed waiting for a request to complete.The value format is a 4-byte integer.

Note: This attribute is not available on Microsoft Exchange Server 2003 SP2. The Enum value isdisplayed as Undefined for Microsoft Exchange Server 2003 SP2.

Busy Threads The number of worker threads that are busy processing requests. The value format is a4-byte integer.

Note: This attribute is not available in Exchange Server 2003 Service Pack 2, 2010 Service Pack 1, and2013. The Undefined enumeration value is displayed on the Tivoli Enterprise Portal for Exchange Server2003 Service Pack 2, 2010 Service Pack 1, and 2013.

Client Item Adds/Sec The number of client item adds (by the sync command) that are currentlyprocessed by Exchange ActiveSync per second. The value format is a 4-byte float.

Note: This attribute is available only in Microsoft Exchange Server 2003 SP2.

Client Item Changes/Sec The number of client item changes (by the sync command) that are currentlyprocessed by Exchange ActiveSync per second. The value format is a 4-byte float.


Client Item Deletes/Sec The number of client item deletes (by the sync command) that are currentlyprocessed by Exchange ActiveSync per second. The value format is a 4-byte float.


Client Item Fetches/Sec The number of client item fetches (by the sync command) that are currentlyprocessed by Exchange ActiveSync per second. The value format is a 4-byte float.



Client Sync Items/Sec The number of client item adds, changes, deletes, and fetches (by the synccommand) that are currently processed by Exchange ActiveSync per second. The value format is a 4-bytefloat.


CreateCollection Commands/Sec The number of CreateCollection commands that are currently processedby Exchange ActiveSync per second. The value format is a 4-byte float.

Note: This attribute is available in Microsoft Exchange Server 2003 SP2, 2010, and 2010 SP1. The Enumvalue is displayed as Undefined for Microsoft Exchange Server 2007 SP2.

Current Active Directory Requests The current number of Active Directory requests that are pending.The value format is a 4-byte integer.


Current Requests The number of HTTP requests that are received from ASP NET. The value format is a4-byte integer.


Empty Folder Contents Total The total number of requests of Empty Folder Contents that are processedsince the service started. The value format is a 4-byte integer.

Note: This attribute is not available in Microsoft Exchange Server 2003 SP2.

Exchange Mailbox Server I/O Requests/Sec The current number of input/output requests that arecurrently sent by Exchange ActiveSync to the Exchange mailbox server per second. The value format is a4-byte float.


Exchange Mailbox Server Item Adds/Sec The number of Exchange mailbox server item adds (by thesync command) that are currently processed by Exchange ActiveSync per second. The value format is a4-byte float.


Exchange Mailbox Server Item Changes/Sec The number of Exchange mailbox server item changes (bythe sync command) that are currently processed by Exchange ActiveSync per second. The value format isa 4-byte float.


Exchange Mailbox Server Item Deletes/Sec The number of Exchange mailbox server item deletes (by thesync command) that are currently processed by Exchange ActiveSync per second. The value format is a4-byte float.


Exchange Mailbox Server Item Soft Deletes/Sec The number of Exchange mailbox server item softdeletes that are currently processed by Exchange ActiveSync per second. The value format is a 4-bytefloat.



Exchange Mailbox Server Sync Items/Sec The number of Exchange mailbox server adds, changes,deletes, and soft deletes (by the sync command) that are currently sent to the client by ExchangeActiveSync per second. The value format is a 4-byte float.


Failed Item Conversion Total The total number of items that fail to convert due to modifications madeby the server since the service started. The value format is a 4-byte integer.


Folder Create Commands/Sec The number of FolderCreate commands that are processed per second. Thevalue format is a 4-byte float.

Folder Create Total The total number of FolderCreate requests that are processed since the servicestarted. The value format is a 4-byte integer.

Folder Delete Commands/Sec The number of FolderDelete commands that are processed per second. Thevalue format is a 4-byte float.

Folder Delete Total The total number of FolderDelete commands that are processed since the servicestarted. The value format is a 4-byte integer.

Folder Sync Commands/Sec The number of FolderSync commands that are processed per second. Thevalue format is a 4-byte float.

Folder Sync Total The total number of FolderSync requests that are processed since the service started.The value format is a 4-byte integer.

Folder Update Commands/Sec The number of FolderUpdate commands that are processed per second.The value format is a 4-byte integer.

Folder Update Total The total number of FolderUpdate requests that are processed since the servicestarted. The value format is a 4-byte integer.

GAL Search Total The total number of GAL Search requests that are processed since the service started.The value format is a 4-byte integer.


GAL Searches/sec The number of times the global address list is searched per second. The value formatis a 4-byte float.


GetHierarchy Commands/Sec The number of GetHierarchy commands that are currently processed byExchange ActiveSync per second. The value format is a 4-byte float.

Get Attachment Commands/Sec The number of GetAttachment commands that are processed eachsecond. Clients who are running earlier versions of the Exchange ActiveSync protocol use this commandto download email attachments. The value format is a 4-byte integer.

Get Attachment Total The total number of GetAttachments requests that are processed since the servicewas started. The value format is a 4-byte integer.


Get Item Estimate Commands/Sec The number of GetItemEstimate commands that are processed eachsecond. Clients use this command to display synchronization progress. The value format is a 4-byteinteger.

Idle Threads The number of worker threads that are currently idle. The value format is a 4-byte integer.


Mailbox Attachment Fetch Commands/Sec The number of Mailbox Attachment Fetches that areprocessed per second. The value format is a 4-byte float.


Mailbox Attachment Fetch Total The total number of Mailbox Attachment Fetch commands that areprocessed since the service is started. The value format is a 4-byte integer.


Mailbox Item Fetch Commands/Sec The number of times that clients download the entire Exchangeitems per second. The value format is a 4-byte integer.


Mailbox Item Fetch Total The total number of mailbox item fetch requests that are processed since theservice was started. The value format is a 4-byte integer.


Mailbox Searches/Sec The number of times that mailboxes are searched per second. The value format isa 4-byte integer.


Mailbox Search Total The total number of mailbox search requests that are processed since the servicewas started. The value format is a 4-byte integer.


Meeting Response Commands/Sec The number of Meeting Response commands that are processed persecond. The client uses this command to designate a meeting as Accepted, Declined, or Tentative. Thevalue format is a 4-byte integer.

Meeting Response Total The total number of MeetingResponse commands that are received since theservice was started. The value format is a 4-byte integer.

Move Collection Commands/Sec The number of MoveCollection commands that are processed persecond. The value format is a 4-byte float

Move Collection Total The total number of MoveCollections requests that are processed since the servicestarted. The value format is a 4-byte integer.

Move Items Commands/Sec The number of MoveItems commands that are processed per second. Thevalue format is a 4-byte float.

Move Items Total The total number of MoveItems commands that are received since the service started.The value format is a 4-byte integer.


Notify Commands/Sec The number of Notify commands that are currently processed by ExchangeActiveSync per second.


PID The process ID that is hosting ActiveSync. The value format is a 4-byte integer.

Note: This attribute is available in Microsoft Exchange Server 2007 SP2, 2010, and 2010 SP1. The Enumvalue is displayed as Undefined for Microsoft Exchange Server 2003 SP2.

Ping Commands Dropped/Sec The number of ping commands per second whose connection to the clientwas dropped before a response could be issued. The value format is a 4-byte integer.

Ping Commands Pending The number of ping commands that are currently pending on the server. Thevalue format is a 4-byte integer.

Ping Dropped Total The total number of ping commands whose connection to the client was droppedbefore a response could be issued. The value format is a 4-byte integer.

Ping Total The total number of ping commands that are processed since the service was started. Thevalue format is a 4-byte integer.

Provision Commands/Sec The number of Provision commands that are processed per second. The valueformat is a 4-byte float.

Requests Queued The number of HTTP requests that are waiting to be assigned to a thread. The valueformat is a 4-byte integer.

Note: This attribute is not available in Exchange Server 2003 Service Pack 2, 2010 Service Pack 1, and2013. The Undefined enumeration value is displayed on the Tivoli Enterprise Portal for Exchange Server2003 Service Pack 2, 2010 Service Pack 1, and 2013.

Requests Total The total number of HTTP requests that are received from ASP NET since the service wasrestarted. The value format is a 4-byte integer.


Requests/Sec The number of HTTP requests that are received from the client through ASP NET persecond. The value format is a 4-byte integer.


ResolveRecipients Commands/Sec The number of ResolveRecipients commands that are currentlyprocessed by Exchange ActiveSync per second. The value format is a 4-byte float.


Search Commands/Sec The number of Search commands that are processed per second. The value formatis a 4-byte integer.

Search Total The total number of Search requests that are processed since the service started. The valueformat is a 4-byte integer.


Send Mail Commands/Sec The number of SendMail commands that are processed per second. The valueformat is a 4-byte integer.

Send Mail Total The total number of SendMail commands that are processed. The value format is a4-byte integer.

Smart Forward Commands/Sec The number of SmartForward commands that are currently processed byExchange ActiveSync per second. The value format is a 4-byte integer.

Sync Commands/Sec The number of Sync commands that are processed per second. Clients use thiscommand to synchronize items within a folder. The value format is a 4-byte integer.

Sync Commands Pending The number of synchronous commands that are currently pending to beexecuted on the server. The value format is a 4-byte integer.

Sync Total The total number of Sync requests that are processed since the service was started. The valueformat is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange ADAccess Caches attributesThis group of data provides details about the Exchange internal component that controls how allExchange components access Active Directory.

Note: This attribute group is available in Exchange Server 2007, or later. This attribute group is amulti-instance attribute group.

ADAccess Caches Instance Name This is the name of AD Access Cache Instance Name. The value formatis an alphanumeric string with a maximum of 384 characters.

Cache Expiries/Sec (Configuration Data) The number of configuration data objects that expire from thecache per second. The value format is a 4-byte float.

Cache Expiries/Sec (User Data) The number of user data objects that expire from the cache per second.The value format is a 4-byte float.

Cache Expiries Total (Configuration Data) The total number of configuration data objects that expirefrom the cache since the system was initialized. The value format is a 4-byte integer.

Cache Expiries Total (User Data) The total number of user data objects that expire from the cache sincethe system was initialized. The value format is a 4-byte integer.


Cache Hits/Sec The number of object found in cache events per second. The value format is a 4-bytefloat.

Cache Hits Total The total number of objects found in cache events since system was initialized. Thevalue format is a 4-byte integer.

Cache Misses/Sec The number of objects not found in cache events per second. The value format is a4-byte float.

Cache Misses Total The total number of objects not found in cache events since system was initialized.The value format is a 4-byte integer.

DN Entries (Configuration Data) The total number of Configuration Data DN Object type entries in thecache. The value format is a 4-byte integer.

DN Entries Memory Configuration Data (MB) The memory (in MB) occupied by all Configuration DataDN Entries in the cache. The value format is a 4-byte float.

DN Entries Memory User Data (MB) The memory (in MB) occupied by all user Data DN Entries in thecache. The value format is a 4-byte float.

DN Entries (User Data) The total number of user data DN object type entries in the cache. The valueformat is a 4-byte integer.

LDAP Searches/Sec The total LDAP searches per second since the server was started. The format of thevalue is a 4-byte integer.

LDAP Searches Total The total number of LDAP search requests issued since the system was initialized.The value format is a 4-byte integer.

Not Found DN Entries (Configuration Data) The total number of Configuration Data Not Found DNtype entries in the cache. The value format is a 4-byte integer.

Not Found DN Entries Memory Configuration Data (MB) The memory (in MB) occupied by allConfiguration Data Not Found DN Entries in the cache. The value format is a 4-byte float.

Not Found DN Entries Memory User Data (MB) The memory (in MB) occupied by all user Data NotFound DN Entries in the cache. The value format is a 4-byte float.

Not Found DN Entries (User Data) The total number of User Data Not Found DN type entries in thecache. The value format is a 4-byte integer.

Outstanding Async Notifies The number of outstanding LDAP notification requests. The value format isa 4-byte integer.

Outstanding Async Reads The number of outstanding LDAP read requests. The value format is a 4-byteinteger.

Outstanding Async Searches The number of outstanding LDAP search requests. The value format is a4-byte integer.

Search Entries (Configuration Data) The total number of configuration data search type entries in thecache. The value format is a 4-byte integer.

Search Entries (User Data) The total number of user data search type entries in the cache. The valueformat is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Entries (Configuration Data) The total number of configuration data entries in the cache. Thisnumber includes DN, Search, Not Found DN, and Not Found GUID type entries. The value format is a4-byte integer.

Total Entries Memory Configuration Data (MB) The memory (in MB) occupied by all configuration dataentry objects in the cache. The value format is a 4-byte float.

Total Entries Memory User Data (MB) The memory (in MB) occupied by all user data entry objects inthe cache. The value format is a 4-byte float.

Total Entries (User Data) The total number of user data entries in the cache. This number includes DN,Search, Not Found DN, and Not Found GUID type entries. The value format is a 4-byte integer.

MS Exchange ADAccess Domain Controllers attributesThis attribute group monitors the communication between the Exchange Server and the domaincontrollers.


Critical Data Flag A numeric value that indicates whether a domain controller has an Exchange Serveraccount. A value of 1 indicates that the domain controller contains the Exchange Server account. A valueof 0 indicates that the domain controller does not have the Exchange Server account. The value format isa 4-byte integer.

Domain Controller Name The name of the domain controller that hosts the Exchange Server. The valueformat is an alphanumeric string with a maximum of 600 characters.

DsGetDcName Elapsed Time The total time (in milliseconds) that has been spent to retrieve the domaincontroller by using the DsGetDcName API call since the service was started. The value format is a 4-byteinteger.

LDAP Pages/Sec The number of additional pages that are retrieved from the domain controller persecond. The value format is a 4-byte float.

Note: This attribute is not available in Exchange Server 2003.

LDAP Read Calls/Sec The number of LDAP read calls per second. The value format is a 4-byte float.


LDAP Read Time The time (in milliseconds) that is spent in sending an LDAP read request and receivinga response. The value format is a 4-byte integer.

LDAP Search Calls/Sec The number of Depth 1 or 2 LDAP search calls that are made per second. Thevalue format is a 4-byte float.

LDAP Search Time The time (in milliseconds) that is spent in sending an LDAP search request andreceiving a response. The value format is a 4-byte integer.

LDAP Searches Timed Out/Min The number of LDAP search requests that were timed out per minute.The value format is a 4-byte integer.

Long Running LDAP Operations/Min The number of LDAP operations per minute on the domaincontroller that run longer than the specified threshold. The default threshold is 15 seconds. The valueformat is a 4-byte integer.


System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value format is an alphanumeric string with amaximum of 64 characters.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange ADAccess Forest DiscoveryThis attribute group monitors the activities to discover Active Directory forests on the Exchange Server.

Note: This attribute group is available in Exchange Server 2013. This attribute group is a multi-instanceattribute group.

Average Discovery Time The average time (in seconds) that is taken to complete the forest discoveryprocess during the sampling period. The value format is a 4-byte float.

Average Time to Discover Servers for Roles The average time (in seconds) that is taken to discover theservers according to the roles during the sampling period. The value format is a 4-byte float.

Discovery Failures The total number of discovery attempts that failed to discover the forests since theprocess was started. The value format is a 4-byte integer.

Domain Controller Name The name of the domain controller. The value format is an alphanumericstring with a maximum of 600 characters.

In-site Domain Controllers The total number of suitable domain controllers that were discovered in thelocal site since the process was started. The value format is a 4-byte integer.


In-site Global Catalogs The total number of suitable global catalogs that were discovered in the local sitesince the process was started. The value format is a 4-byte integer.

Max Discovery Duration The maximum time (in seconds) that was taken to complete the forestdiscovery since the process was started. The value format is a 4-byte float.

Maximum Time to Discover Servers for Roles The maximum time (in seconds) that was taken todiscover the servers according to the roles since the process was started. The value format is a 4-bytefloat.

Out-of-site Domain Controllers The total number of suitable domain controllers that were discoveredoutside the local site since the process was started. The value format is a 4-byte integer.

Out-of-site Global Catalogs The total number of suitable global catalogs that were discovered outside thelocal site since the process was started. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Topology Discovery Duration The time (in seconds) that is taken to complete the last topology discoveryprocess. The value format is a 4-byte float.

MS Exchange ADAccess Processes attributesThis attribute group monitors the Exchange Server Active Directory activity.


LDAP Not Found configuration read calls/Sec The number of Depth 0 LDAP search calls made by theprocess that failed with 'Not found' per second.

LDAP notifications received/Sec The number of LDAP notification results received by the process persecond. The value format is a 4-byte float.

LDAP notifications Reported/Sec The number of LDAP notification results reported by the process to theusers per second. The value format is a 4-byte float.

LDAP Pages/Sec The number of additional pages that are retrieved by the process per second.

LDAP Read calls/Sec The number of Depth 0 LDAP search calls made by the process per second. It doesnot necessarily equal to the number of notifications reported to the users.


LDAP Read Time The time (in milliseconds) taken to send an LDAP read request and receive a response.

LDAP Search calls/Sec The number of Depth 1 or 2 LDAP search calls made by the process per second.

LDAP Search Time The time (in milliseconds) taken to send an LDAP search request and receive aresponse.

LDAP Timeout errors/Sec The number of LDAP operations made by the process failed because ofexceeded timeout per second.

LDAP Write calls/Sec The number of LDAP add, modify, or delete requests made by the process persecond.

LDAP Write Time The time (in milliseconds) taken to send an LDAP add, modify, or delete request andreceive a response.

Long running LDAP operations/Min The number of LDAP operations made by the process that tooklonger than the specified threshold per minute (default threshold is 15 seconds).

Number of outstanding requests The current number of pending LDAP searches in the process.

Open connections to Domain Controllers Open connections to Domain Controllers in the process.

Open connections to Global Catalogs Open connections to Global Catalogs in the process.

AD Process Name The name of the Microsoft Exchange ADAccess Processes instance.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Topology version The current version of the Active Directory topology data used by the process. Thevalue format is a 4-byte integer.

MS Exchange Address Book attributesThis attribute group monitors the activities of the Name Service Provider Interface (NSPI) service on theMicrosoft Exchange Server.

Note: This attribute group is available in Exchange Server 2010, or later. This attribute group is a singleinstance attribute group.

NSPI Connections/Sec The number of NSPI client connections that are currently made per second to theserver. The value format is a 4-byte integer.


NSPI Connections Current The number of NSPI clients that are currently connected to the server. Thevalue format is a 4-byte integer.

NSPI Connections Total The total number of NSPI clients that have been connected to the server sincethe service was started. The value format is a 4-byte integer.

NSPI RPC Browse Requests The number of NSPI RPC browse requests that are currently processed bythe server. The value format is a 4-byte integer.

NSPI RPC Browse Requests/Sec The number of RPC browse requests that are generated per second bythe NSPI service. The value format is a 4-byte integer.

NSPI RPC Browse Requests Average Latency The average time (in milliseconds) that is taken tocomplete the NSPI browse requests during the sampling period. The value format is a 4-byte float.

NSPI RPC Browse Requests Total The total number of NSPI RPC browse requests that have beenreceived by the server since the service was started. The value format is a 4-byte integer.

NSPI RPC Requests The number of NSPI RPC requests that are currently processed by the server. Thevalue format is a 4-byte integer.

NSPI RPC Requests/Sec The number of NSPI requests that occur per second. The value format is a4-byte integer.

NSPI RPC Requests Average Latency The average time (in milliseconds) that the NSPI service takes tocomplete a browse request during the sampling period. The value format is a 4-byte float.

NSPI RPC Requests Total The total number of NSPI requests that have been received by the server sincethe service was started. The value format is a 4-byte integer.

Referral RPC Requests The number of referral RPC requests that are currently being processed by theserver. The value format is a 4-byte integer.

Referral RPC Requests/Sec The number of referral RPC requests that occur per second. The value formatis a 4-byte integer.

Referral RPC Requests Average Latency The average time (in milliseconds) that is required to processreferral RPC requests during the sampling period. The value format is a 4-byte float.

Referral RPC Requests Total The total number of referral requests that have been received by the serversince the service was started. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute


SS Second

MS Exchange Assistants attributesThis attribute group monitors the Exchange Server Assistants services activity, Microsoft Exchange MailSubmission, and Microsoft Exchange Mailbox Assistants.

Note: This attribute group is available only in Exchange Server 2007 and 2010. This attribute group is amulti-instance attribute group.

Average Event Processing Time In Seconds The average processing time (in seconds) of the eventschosen as interesting.

Average Event Queue Time In Seconds The average time (in seconds) that the event stays in thedispatcher queue.

Average Mailbox Processing Time In Seconds The average processing time of mailboxes for time-basedassistants per second.

Note: This attribute is not available in Exchange Server 2010, or later.

Average Queue Size of Event Dispatchers The average queue size of event dispatchers.


Assistant Name The name of the Microsoft Exchange Assistants instance.

Events in queue The number of events currently in the in-memory queue that are waiting to beprocessed by the assistants.

Events Polled The number of events polled by the assistants.


Events Polled/Sec The number of events polled per second.


Events Processed The number of events processed by the assistants.

Highest Event Counter Polled The highest event counter polled from the database. The value format is a4-byte integer.


Mailboxes processed The number of mailboxes processed by time-based assistants.


Mailboxes processed/Sec The number of times that mailboxes are processed by time-based assistants persecond.


Number of Event Dispatchers The number of event dispatchers currently in memory.


Number of events processed /Second The number of events processed per second.

Number of Failed Event Dispatchers The number of event dispatchers that are in the failed state.

Number of Handled Exceptions The number of CLR exceptions handled by the code.

Number of Threads Used The number of threads used from the CLR thread pool.


Percentage of Interesting Events The percentage of events generated in the database that are processedby the assistants. The value format is a 4-byte float.

Polling Delay The latency between the recent MAPI Event that is polled and the event that is created inseconds.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Assistants Per Database attributesThis attribute group monitors the activity of Microsoft Exchange Server Assistants.


Assistant Name Per Database The name of the Microsoft Exchange Assistants Per Database instance. Theformat of the value is an alphanumeric string with a maximum length of 600 characters.

Average Event Processing Time In seconds The average processing time of the events that are chosen asinteresting events. The format of the value is a 4-byte float.

Average Mailbox Processing Time In seconds The average processing time of the mailboxes fortime-based assistants per second. The format of the value is a 4-byte float.

Events in queue The current number of events in the in-memory queue that are waiting to be processedby the assistants. The format of the value is a 4-byte integer.

Events Polled The number of events that are polled by the assistants since the server was started. Theformat of the value is a 4-byte integer.


Events Polled/sec The number of events that are currently polled per second. The format of the value is a4-byte float.

Highest Event Counter Polled The highest event counter that is polled from the database. The format ofthe value is a 4-byte integer.

Mailboxes processed The number of mailboxes that are processed by time-based assistants since theserver was started. The format of the value is a 4-byte integer.

Mailboxes processed/sec The number of mailboxes that are processed by the time-based assistants persecond. The format of the value is a 4-byte float.

Number of Threads Used The number of threads that are currently used from the common languageruntime (CLR) thread pool. The format of the value is a 4-byte integer.

Percentage of Interesting Events The percentage of the events that are processed by the assistants. Theformat of the value is a 4-byte float.

Polling Delay The latency between the most recent MAPI event that is polled and the event created, inseconds. The format of the value is a 4-byte float.


Timestamp The time when the data is collected. The format is MM/DD/YY HH:mm:SS, where thefollowing measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Attachment Filtering attributesThis attribute group represents MS Exchange Attachment Filtering statistics activity.

Note: This attribute group is available only in Exchange Server 2007 and 2010. This attribute group is asingle instance attribute group.

Change in Messages Attachment Filtered The number of messages that were either blocked,attachment-stripped, or silent-deleted (according to configuration) by the attachment filtering agent inthat sampling interval. The agent resets the attribute to its initial value on the startup of the ExchangeServer.

Messages Attachment Filtered The number of messages that were either blocked, attachment-stripped, orsilent-deleted (according to configuration) by the attachment filtering agent.

Messages Filtered/sec The number of messages per second that the attachment filtering agent blocked,attachment-stripped, or silent-deleted.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Authentication attributesThis attribute group monitors the user authentication activities on the Exchange Server.


Accepted Requests The total number of authentication requests that were accepted since the service wasstarted. The value format is a 4-byte integer.

Authentication Instance Name The name of the authentication service provider. The value format is analphanumeric string with a maximum of 600 characters.

Latency The latency of the current authentication request. The value format is a 4-byte float.

Outstanding Requests The number of current outstanding authentication requests. The value format is a4-byte integer.

Rejected Requests The total number of authentication requests that were rejected since the service wasstarted. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Requests The total number of authentication requests that occurred since the service was started.The value format is a 4-byte integer.


MS Exchange Autodiscover Service attributesThis attribute group monitors the activities of the Autodiscover service on the Microsoft Exchange Server.The Autodiscover service provides the following services to Outlook clients:v Configures user profiles automatically.v Provides access to the Exchange Server features.


Error Responses The total number of Autodiscover error responses that have been processed since theservice was started. The value format is a 4-byte integer.

Error Responses/Sec The number of Autodiscover error responses that occurred per second. The valueformat is a 4-byte integer.

Requests/Sec The number of Autodiscover service requests that are currently processed per second. Thevalue format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Requests The total number of Autodiscover service requests that have been processed since theservice was started. The value format is a 4-byte integer.

MS Exchange Availability Service attributesThis attribute group monitors the Availability service on the Microsoft Exchange Server. The Availabilityservice provides free or busy information to the clients to improve scheduling activities for meetings andcalendars.


Availability Requests/Sec The number of free or busy requests that are processed per second. The valueformat is a 4-byte integer. A free or busy request can query multiple mailboxes.

Average Free Busy Request Processing Time The average time (in seconds) that is taken to process a freeor busy request. The value format is a 4-byte float. A free or busy request can query multiple mailboxes.

Average Mailboxes Processed Per Request The average number of mailboxes that are currentlyprocessed per request. The value format is a 4-byte float.


Client Reported Failures AutoDiscover Failures The total number of free or busy requests that havebeen reported by the clients, and that have failed since the service was started because the Autodiscoverservice failed. The value format is a 4-byte integer.

Client Reported Failures Connection Failures The total number of free or busy requests that have beenreported by the clients, and that have failed because the clients could not connect to the Client AccessServer since the service was started. The value format is a 4-byte integer.

Client Reported Failures Total The total number of free or busy requests that have been reported by theclients, and that have failed since the service was started. The value format is a 4-byte integer.

Client Reported Failures Partial Other Failures The total number of free or busy requests that have beenreported by the clients, and that have failed because of the partial or other failures since the service wasstarted. The value format is a 4-byte integer.

Client Reported Failures Timeout Failures The total number of free or busy requests that have beenreported by the clients, and that have failed because the requests timed out since the service was started.The value format is a 4-byte integer.

Current Requests The current number of requests that are being processed. The value format is a 4-byteinteger.

Public Folder Queries/Sec The number of mailboxes for which free or busy information is requested persecond from the public folders. The value format is a 4-byte integer.

Public Folder Request Failures/Sec The number of requests that failed per second to retrieve the free orbusy status of public folders. The value format is a 4-byte integer.

Successful Client Reported Requests Total The total number of free or busy requests that have beenreported by the clients, and that have been processed since the service was started. The value format is a4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Calendar Attendant attributesThis attribute group monitors the activities of the Calendar Attendant on the Microsoft Exchange Server.

Note: This attribute group is available in Exchange Server 2007, or later. This attribute group is asingle-instance attribute group.


Average Calendar Attendant Processing Time The average time that is required for the CalendarAttendant to process requests. The value format is a 4-byte float.

Meeting Cancellations The total number of meeting requests that have been cancelled by the CalendarAttendant since the service was started. The value format is a 4-byte integer.

Meeting Messages Deleted The total number of meeting messages that have been deleted by theCalendar Attendant since the service was started. The value format is a 4-byte integer.

Meeting Messages Processed The total number of meeting messages that have been processed by theCalendar Attendant since the service was started. The value format is a 4-byte integer.

Meeting Requests Invitations The total number of meeting invitations that have been processed by theCalendar Attendant since the service was started. The value format is a 4-byte integer.

Meeting Responses The total number of meeting responses that have been processed by the CalendarAttendant since the service was started. The value format is a 4-byte integer.

Requests Failed The total number of requests that the Calendar Attendant failed to process since theservice was started. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Connection Filtering Agent attributesThis attribute group represents MS Exchange Connection Filtering Agent statistics activity.


Connections on IP Allow List/Sec The number of connections on the IP allow list per second.

Connections on IP Allow List Providers/Sec The number of connections on the IP allow list providersper second. The value format is a 4-byte float.

Connections on IP Block List The total number of connections on the IP block list. The value format is a4-byte integer.

Connections on IP Block List/Sec The number of connections on the IP block list per second.

Connections on IP Block List Providers/Sec The number of connections on the IP block list providers persecond. The value format is a 4-byte float.


Messages with Originating IP on IP Allow List/Sec The number of messages with an originating IPaddress on the IP allow list each second.

Messages with Originating IP on IP Block List The total number of messages with originating IP on theIP block list. The value format is a 4-byte integer.

Messages with Originating IP on IP Block List/Sec The number of messages with an originating IPaddress on the IP block list per second.

Messages with Originating IP on IP Block List Providers/Sec The number of messages with originatingIP on the IP block list providers per second. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Content Filter Agent attributesThis attribute group represents MS Exchange Content Filter Agent statistics.

Note: This attribute group is available in Exchange Server 2007, or later. This attribute group is a singleinstance attribute group.Changes in Messages Bypassed Scanning The number of messages that were bypassed by the contentfilter (according to configuration) in that sampling interval. The agent resets the attribute to its initialvalue on the startup of the Exchange Server.

Change in Messages Bypassed Scanning organization-wide safe sender The number of messages thatwere bypassed by the content filter due to an organization-wide safe sender, in that sampling interval.The agent resets the attribute to its initial value on the startup of the Exchange Server.

Messages Bypassed Scanning The total number of messages that bypass scanning.

Messages Bypassed Scanning organization wide safe sender The total number of messages that bypassscanning due to an organization-wide safe sender.

Messages Deleted The total number of messages that are deleted by the Content Filter Agent. The valueformat is a 4-byte integer.

Messages Outlook Postmark not validated The number of messages that include an Outlook emailpostmark property and are not validated successfully.

Messages Outlook Postmark validated successfully The number of messages that include an Outlookemail postmark property and are validated successfully.


Messages Quarantined The total number of messages that are quarantined by the Content Filter Agent.The value format is a 4-byte integer.

Messages Rejected The total number of messages that are rejected by the Content Filter Agent. The valueformat is a 4-byte integer.

Messages Scanned The total number of messages scanned by the Content Filter Agent. The value formatis a 4-byte integer.

Messages Scanned /Second The number of messages that are scanned per second.

Messages with SCL 0 The total number of messages that are assigned an SCL rating of 0. The valueformat is a 4-byte integer.






Messages_with_SCL_6 The total number of messages that are assigned an SCL rating of 6. The valueformat is a 4-byte integer.






MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


MS Exchange Control Panel (RBAC) attributesThis group of attributes represents Exchange Role-based access.

Note: The attribute group is available in the Exchange Server 2010, or later. This attribute group is asingle instance attribute group.

Activation of Requests/Sec The number of requests that are activated per second in the ExchangeControl Panel. The value format is a 4-byte float.

ASP.NET Request Failures/Sec The current number of ASP.NET requests that failed per second in theExchange Control Panel. The value format a 4-byte integer.

Average Active Time of PowerShell Runspaces The average time (in seconds) for which WindowsPowerShell runspaces are active while executing cmdlets in the Exchange Control Panel during thesampling period. The value format is a 4-byte float.

Average Request Response Time The average time (in milliseconds) for the Exchange Control Panel torespond to a request during the sampling period. The value format is a 4-byte float.

Average Response Time of Outbound Proxy Requests The average time (in milliseconds) for thesecondary Client Access Server to respond to requests during the sampling period. The value format is a4-byte float.

Explicit SignOn Inbound Proxy Requests/Sec The current number of explicit SignOn requests that arereceived per second from the primary Client Access Server. The value format is a 4-byte integer.

Explicit SignOn Inbound Proxy Sessions/Sec The current number of explicit SignOn inbound proxysessions that are loaded per second in the Exchange Control Panel. The value format is a 4-byte integer.

Explicit SignOn Outbound Proxy Requests/Sec The current number of explicit SignOn requests that aresent per second to the secondary Client Access Server. The value format is a 4-byte integer.

Explicit SignOn Outbound Proxy Sessions/Sec The current number of explicit SignOn outbound proxysessions that are loaded per second in the Exchange Control Panel. The value format is a 4-byte integer.

Explicit SignOn Standard RBAC Requests/Sec The current number of requests that are received persecond by the explicit SignOn standard RBAC session. The value format is a 4-byte integer.

Explicit SignOn Standard RBAC Sessions The current number of explicit SignOn standard RBACsessions that are loaded in the Exchange Control Panel. The value format is a 4-byte integer.

Explicit SignOn Standard RBAC Sessions/Sec The current number of explicit SignOn standard RBACsessions that are loaded per second in the Exchange Control Panel. The value format is a 4-byte integer.

Explicit SignOn Standard RBAC Sessions Total The total number of explicit SignOn standard RBACsessions that are loaded in the Exchange Control Panel since the process was started. The value format isa 4-byte integer.

Inbound Proxy Requests/Sec The current number of requests that are received per second from theprimary Client Access Server. The value format is a 4-byte integer.

Inbound Proxy Sessions/Sec The current number of inbound proxy sessions that are loaded per secondin the Exchange Control Panel. The value format is a 4-byte integer.


Outbound Proxy Requests/Sec The current number of requests that are sent per second to the secondaryClient Access Server. The value format is a 4-byte integer.

Outbound Proxy Sessions/Sec The current number of outbound proxy sessions that are loaded persecond in the Exchange Control Panel. The value format is a 4-byte integer.

PowerShell Runspace Activations/Sec The number of Windows PowerShell runspaces that are activatedper second in the Exchange Control Panel. The value format is a 4-byte float.

PowerShell Runspaces/Sec The number of Windows PowerShell runspaces that are created per second inthe Exchange Control Panel. The value format is a 4-byte float.

RBAC Sessions The current number of RBAC sessions that are loaded in the Exchange Control Panelincluding standard sessions, inbound proxy sessions, and outbound proxy sessions. The value format is a4-byte integer.

RBAC Sessions Average Creation Time The average time (in seconds) that the Exchange Control Paneltakes to create an RBAC session during the sampling period. The value format is a 4-byte integer.

RBAC Sessions Peak The highest number of RBAC sessions that are simultaneously loaded in theExchange Control Panel since the process was started. The value format is a 4-byte integer.

RBAC Sessions Total The total number of RBAC sessions that are loaded in the Exchange Control Panelsince the process was started. The value format is a 4-byte integer.

RBAC Sessions/sec The number of RBAC sessions that are currently loaded per second in the ExchangeControl Panel. The value format is a 4-byte float.

Standard RBAC Requests The number of requests that are currently received by a standard RBACsession. The value format is a 4-byte integer.

Standard RBAC Requests Peak The highest number of requests that are simultaneously received by astandard RBAC session since the process was started. The value format is a 4-byte integer.

Standard RBAC Requests Total The total number of requests that are received by a standard RBACsession since the process was started. The value format is a 4-byte integer.

Standard RBAC Requests/sec The number of requests that are currently received by a standard RBACsession per second. The value format is a 4-byte float.

Standard RBAC Sessions The number of standard RBAC sessions that are currently loaded in theExchange Control Panel. The value format is a 4-byte integer.

Standard RBAC Sessions Peak The highest number of standard RBAC sessions that are simultaneouslyloaded in the Exchange Control Panel since the process was started. The value format is a 4-byte integer.

Standard RBAC Sessions Total The total number of standard RBAC sessions that are loaded in theExchange Control Panel since the process was started. The value format is a 4-byte integer.

Standard RBAC Sessions/sec The number of standard RBAC sessions that are currently loaded persecond in the Exchange Control Panel. The value format is a 4-byte float.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Database Availability Group attributesThis group of data represents Exchange Server Database Availability Group.

Note: The attribute group is available in Exchange server 2010, or later. This attribute group is amulti-instance attribute group.

Activation Preference The numeric value used to break ties during database activation when multipledatabase copies meet the same criteria for activating. The value format is a 4-byte integer.

Database Copy Status The copy status of mailbox databases that is available on the monitored node of adatabase availability group setup. The value format is an alphanumeric string with a maximum of 60characters.

DAG Name The name of the database availability group. The value format is an alphanumeric stringwith a maximum of 60 characters.

File Share Witness Directory The name of the directory that is used to store the file share witness data.The value format is an alphanumeric string with a maximum of 384 characters. This directory is locatedon a server that is not a member of the database availability group.

Member Count The number of nodes that are the member of a database availability group setup. Thevalue format is a 4-byte integer.

Mailbox Database Copies The list of mailbox database copies that are available on the monitored node ofa database availability group setup. The value format is an alphanumeric string with a maximum of 332characters.

Replay Lag Time (Min) The amount of time in minutes, to delay log replay for the database copy.

Witness server name The name of the witness server in a database availability group setup. The valueformat is an alphanumeric string with a maximum of 60 characters.



MM Month

DD Day

YY Year


HH Hour

mm Minute

SS Second

Truncation Lag Time The amount of time (in minutes) to delay the truncation of log files that have beenreplayed into the database copy since the replication service was started. The value format is a 4-byteinteger. The time period starts after the log files are replayed into the database copy.

MS Exchange DB attributesThis group of attributes represents MS Exchange Server Database activity.

Cache Size (MB) The size of system memory (in MB) that the database cache manager uses to holdfrequently used information from the database files to prevent file operations.

If the database cache size seems to be too small for optimal performance and there is very little availablememory on the system (see Memory/Available Bytes), adding more memory to the system may increaseperformance. If there is a lot of available memory on the system and the database cache size is notgrowing beyond a certain point, the database cache size may be capped at an artificially low limit.Increasing this limit may increase performance. The value format is a 4-byte integer.

Cache % Hit The percentage of database file page requests that were fulfilled by the database cachewithout causing a file operation since the server was started. If the percentage is too low, the databasecache size might be too small. The value format is a decimal.

Cache Page Fault Stalls/Sec The number of page faults per second that cannot be serviced because nopages are available for allocation from the database cache since the server was started. If this counter isgreater than zero most of the time, the clean threshold might be too low. The value format is a decimal.

Cache Page Faults/Sec The number of database page requests per second that require the database cachemanager to allocate a new page from the database cache since the server was started. If this rate is toohigh, the database cache size might be too small. The value format is a decimal.

Cache Size The amount of system memory in kilobytes that the database cache manager used to holdfrequently accessed information from the database files and prevent file operations.

If the database cache size seems to be too small for optimal performance and very little memory isavailable on the system, add more memory to the system to increase performance. If a lot of memory ison the system and the database cache size is not growing beyond a certain point, the database cache sizemight be capped at an artificially low limit. Increasing this limit might increase performance. The valueformat is a 4-byte integer.

Database Name (Superseded) The name of the database instance. The value format is an alphanumericstring with a maximum of 60 characters.

Database Name The name of the database instance. The value format is an alphanumeric string with amaximum of 332 characters.

I/O Database Reads Average Latency The average length of time (in milliseconds) that each databaseread operation takes to finish. The value format is a 4-byte integer.

Note: This attribute is available in Microsoft Exchange Server 2007 and 2010.


I/O Database Reads (Attached) Average Latency The average time (in milliseconds) that is required forreading data from the attached database. The value format is a 4-byte float. Attached databases are thedatabases that are currently active.

Note: This attribute is available in Microsoft Exchange Server 2010, or later.

I/O Database Reads (Recovery) Average Latency The average time (in milliseconds) that is required forreading data from the database that is used as a backup database. The value format is a 4-byte float. Thisdatabase is part of the database availability group.


I/O Database Reads/Sec The rate of database read operations. The value format is a 4-byte float.

Note: This attribute is available in Microsoft Exchange Server 2003, version sp2, and later.

I/O Database Writes Average Latency The average length of time (in milliseconds) that database writeoperation takes to finish. The value format is a 4-byte integer.


I/O Database Writes (Attached) Average Latency The average time (in milliseconds) that is required forwriting data to the attached database. The value format is a 4-byte float. Attached databases are thedatabases that are currently active.


I/O Database Writes (Recovery) Average Latency The average time (in milliseconds) that is required forwriting data to the database that is used as a backup database. The value format is a 4-byte float. Thisdatabase is part of the database availability group.


I/O Database Writes/Sec The rate of database write operations. The value format is a 4-byte float.


I/O Log Reads/Sec The rate of log file read operations. The value format is a 4-byte float.


I/O Log Read Average Latency The average time (in milliseconds) that is required to read a log file. Thevalue format is a 4-byte float.


I/O Log Writes Average Latency The average length of time (in milliseconds) that each log file writeoperation takes to finish. The value format is a 4-byte float.


I/O Log Writes/sec The rate of log file write operations that are completed. The value format is a 4-bytefloat.



Log Bytes Write/sec The rate at which the bytes are written to the log. The value format is a 4-byte float.


Log Record Stalls/Sec The number of records that cannot be added to the log buffers per second becausethe buffers are full since the server was started. If this counter is greater than zero for most of the time,the log buffer size might be a bottleneck. The value format is a decimal.

Log Threads Waiting The number of threads waiting for their data to be written to the log to completean update of the database since the server was started. If this number is too high, the log might be abottleneck. The value format is a 4-byte integer.

Log Writes/Sec The number of times that log buffers are written to the log files per second since theserver was started. If this number approaches the maximum rate for the media that is holding the logfiles, the log is a bottleneck. The value format is a decimal.

Pages Converted/Sec The rate at which a database page is converted from an older database format. Thevalue format is a 4-byte float.

Note: This attribute is not available in Microsoft Exchange Server 2010 SP1, or later. The Enum value isdisplayed as Undefined for Microsoft Exchange Server 2010 SP1, or later.

Records Converted/Sec The rate at which a database record is converted from an older database format.The value format is a 4-byte float.



Table Open Cache % Hit The percent of operations that return a handle to a previously opened tablesince the server was started. The value format is a decimal.

Table Open Cache Hits/Sec The number of OpenTable operations per second that were issued on tablesthat were previously opened since the server was started. The value format is a decimal.

Table Open Cache Misses/Sec The number of OpenTable operations per second that were issued ontables that were not previously opened since the server was started. The value format is a decimal.

Table Opens/Sec The total number of issued OpenTable operations per second since the server wasstarted. The value format is a decimal.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


Version Buckets Allocated The total number of buckets that are allocated.

Note: This attribute is available only in Microsoft Exchange Server 2007 and 2010.

MS Exchange DB Instance attributesThis group of data provides details about the Exchange database.

Database Instance Name Exchange database name. The value format is an alphanumeric string with amaximum of 384 characters.

I/O Database Reads/Sec The number of times the database read operations are completed per second.The value format is a 4-byte float.

Note: This attribute is available in Microsoft Exchange Server 2003, version SP2, and later.

I/O Database Reads Average Latency The average length of time (in milliseconds) taken per databaseread operation.


I/O Database Writes/Sec The number of times the database write operations are completed per second.The value format is a 4-byte float.


I/O Database Writes Average Latency The average length of time (in milliseconds) taken per databasewrite operation.


I/O Log Reads/Sec The rate of log file read operations.


I/O Log Writes Average Latency The average length of time (in milliseconds) spent per log file writeoperation. The value format is a 4-byte integer.


I/O Log Writes/Sec The rate of log file write operations. The value format is a 4-byte integer.


Log Bytes Write/Sec The rate at which bytes are written to the log. The value format is a 4-byte integer.


Log Files Generated The total number of log files that are generated by an instance since the log fileswere last initialized. The value format is a 4-byte integer.

Log Generation Checkpoint Depth The number of transaction log files that must be added or committedto the Exchange Server Edition (ESE) database. The value format is a 4-byte integer.


Log Record Stalls/Sec The number of log records that are not added to the log buffers per secondbecause they are full. If this counter is non-zero most of the time, the log buffer size can become abottleneck. The value format is a 4-byte float.

Log Threads Waiting The number of threads that are waiting for the data to be written to the log tofinish an update of the database. If the number is too high, the log becomes a bottleneck. The valueformat is a 4-byte integer.

Log Writes/Sec The number of times the log buffers are written to the log files per second. If this numberapproaches the maximum write rate for the media holding the log files, the log becomes a bottleneck.The value format is a 4-byte float.

Pages Converted/Sec The rate at which a database page is converted from an older database format. Thevalue format is a 4-byte float.


Records Converted/Sec The rate at which a database record is converted from an older database format.The value format is a 4-byte float.



Table Open Cache % Hit The percentage of database tables that are opened by using cached schemainformation. If this percentage is low, the table cache size can be small too. The value format is a 4-bytefloat.

Table Open Cache Hits/Sec The number of database tables that are opened by using cached schemainformation per second. If this rate is low, the table cache size can be small too. The value format is a4-byte float.

Table Open Cache Misses/Sec The number of database tables that are opened without using cachedschema information per second. If this rate is too high, the table cache size can be small too. The valueformat is a 4-byte float.

Table Opens/sec The number of database tables that are opened per second. The value format is a 4-bytefloat.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


Version buckets allocated The total number of version buckets that are allocated. The value format is a4-byte integer.

Note: This attribute is available only in Microsoft Exchange Server 2007 and 2010.

MS Exchange Delivery DSNThis attribute group monitors the delivery status notifications (DSN) for messages that are sent to theMailbox Transport Delivery service on the Exchange Server. DSN messages provide non-delivery reportsand other status messages to message senders.


Delay DSNs The total number of delay DSN messages that were generated since the service was started.A delay DSN message is generated after each message delivery failure. The value format is a 4-byteinteger.

Delivered DSNs The total number of DSN messages that were generated for the completed messagedeliveries since the service was started. The value format is a 4-byte integer.

DSN Type The type of DSN. The value format is an alphanumeric string with a maximum of 600characters.

Expanded DSNs The total number of expanded DSN messages that were generated since the service wasstarted. The value format is a 4-byte integer.

Failure DSNs in Last Hour that can be Alerted The number of failure DSN messages that can be alertedwithin the last hour because of message delivery failures. The value format is a 4-byte integer.

Failure DSNs Total The total number of failure DSN messages that were generated because of messagedelivery failures since the service was started. The value format is a 4-byte integer.

Last Hour Delayed DSNs The number of delay DSN messages that are generated within the last hour.The value format is a 4-byte integer.

Last Hour Failure DSNs The number of failure DSN messages that are generated within the last hourbecause of message delivery failures. The value format is a 4-byte integer.

NDRs Generated for Catch-All Recipients The total number of non-delivery reports that were generatedbecause of non-delivery of messages to the catch-all mailbox recipients since the service was started. Thevalue format is a 4-byte integer.

Relay DSNs The total number of relay DSN messages that were generated since the service was started.The value format is a 4-byte integer.



MM Month

DD Day

YY Year


HH Hour

mm Minute

SS Second

MS Exchange DS attributesThis group of attributes represents MS Exchange Server Directory Service activity.

Note: This attribute group is not available in Exchange Server 2013.

AB ANR/Sec The rate at which address book clients perform ambiguous name resolution operations. Thevalue format is a 4-byte float.

AB Browses/Sec The number of times the Address Book clients perform browse operations per secondafter the server started. The format of the value is decimal.

AB Client Sessions The number of connected Address Book client sessions. The value format is a 4-byteinteger.

AB Matches/Sec The rate at which address book clients perform find operations. The value format is a4-byte float.

AB Property Reads/Sec The rate at which address book clients perform property read operations. Thevalue format is a 4-byte float.

AB Proxy Lookups/Sec The rate at which proxy clients perform search operations. The value format is a4-byte float.

AB Searches/Sec The rate at which address book clients perform key search operations. The value formatis a 4-byte float.

DRA Sync Requests Made The number of synchronization requests that are made to the neighbors. Thevalue format is a 4-byte integer.

DRA Sync Requests Successful The number of synchronization requests that are made to the neighborsthat returned successfully. The value format is a 4-byte integer.

LDAP Active Threads The number of threads that are in use by the LDAP subsystem of the localdirectory service. The value format is a 4-byte integer.

LDAP Bind Time The time taken (in milliseconds) for the last successful LDAP bind. The value format isa 4-byte float.

LDAP Client Sessions The number of connected LDAP client sessions. The value format is a 4-byteinteger.

LDAP Closed Connections/Sec The number of LDAP connections that are closed in the last second. Thevalue format is a 4-byte float.

LDAP New Connections/Sec The number of new LDAP connections that arrive per second. The valueformat is a 4-byte float.

LDAP Searches/Sec The number of times the LDAP clients perform search operations per second afterthe server was started. The value format is a decimal.


LDAP Successful Binds/Sec The number of LDAP Binds per second. The value format is a 4-byte float.

LDAP Writes/Sec The rate at which LDAP clients perform write operations. The value format is a 4-bytefloat.


Threads in Use The current number of threads that the directory service is using. This number isdifferent from the number of threads in the directory service process. This attribute represents thenumber of RPC-generated threads that are currently in API calls, and can be used to indicate whetheradditional processors could be beneficial. The value format is a 4-byte integer.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Event Details attributesThis attribute group monitors the events that are triggered on Exchange Servers.


Event Age The age (in minutes) of the event since the event was triggered. The value format is a 4-byteinteger.

Event Category The category of the event. The value format is an alphanumeric string with a maximumof 600 characters.

Event Description The description in the event log. The value format is an alphanumeric string with amaximum of 3072 characters. The enumeration value for this attribute is N/A (not available).

Event ID The ID of the triggered event. The value format is a 4-byte integer.

Event Log User The name of the user who was logged on when the event occurred. The value format isan alphanumeric string with a maximum of 332 characters.

Event Source The name of the event source. The value format is an alphanumeric string with amaximum of 600 characters.

Event Timestamp The time when the event was triggered. The format is MM/DD/YY HH:mm:SS, wherethe following measures apply:

MM Month

DD Day

YY Year


HH Hour

mm Minute

SS Second

Event Type The type of event, such as error, warning, or Failure Audit. The value format is a 4-byteinteger.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Extensibility Agents attributesThis attribute group monitors the activities of transport agents and the time taken by each agent toprocess email messages.


Average Agent Processing Time The average processing time (in seconds) of the agent per event. Thevalue format is a 4-byte float.

Extensibility Agent Name The name of the extensibility agent. The value format is an alphanumericstring with a maximum of 600 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Agent Invocations The total number of agent invocations that have occurred since the agent wasstarted. The value format is a 4-byte integer.


MS Exchange FDS OAB attributesThis attribute group monitors the activities of the File Distribution Service (FDS) on the MicrosoftExchange Server that are related to the Office Address Book (OAB).


Bytes Downloaded The number of bytes that are downloaded by the current download task. The valueformat is a 4-byte integer.

FDS OAB Instance Name The name of the FDS OAB instance. The value format is an alphanumericstring with a maximum of 64 characters.

Download Tasks Completed The number of OAB download tasks that are currently completed. Thevalue format is a 4-byte integer.

Download Task Queued A numeric value that indicates whether the download task is queued forexecution. The value format is a 4-byte integer. The following table provides the enumeration values ofthe attribute:

Enum value Value

1 Yes

0 No



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Bytes To Download The number of bytes that are currently pending to be downloaded by thecurrent download task. The value format is a 4-byte integer.

MS Exchange IS attributesThis group of data represents MS Exchange Server Information Store activity.


Active Anonymous User Count Number of active users. The value format is a 4-byte integer.

Active Connection Count Number of connections that have shown some activity in the last 10 minutes.The value format is a 4-byte integer.


Appointment Instances Created The number of appointment instances that are created. The value formatis a 4-byte integer.

Appointment Instances Deleted The number of appointment instances that are deleted. The value formatis a 4-byte integer.

Active User Count Number of user connections that have shown some activity in the last 10 minutes.The value format is a 4-byte integer.

Anonymous User Count Number of anonymous users that are connected to the information store. Thevalue format is a 4-byte integer.

Client RPCs attempted The total number of RPCs attempted by the users since the store was started. Thevalue format is a 4-byte integer.

Client RPCs attempted/Sec The client-reported rate of RPCs attempted by the users since the store wasstarted. The value format is a 4-byte float.

Client RPCs Failed The number of failed RPCs that are reported by the client since the store was started.The value format is a 4-byte integer.

Client RPCs Failed/Sec The rate of failed RPCs that is reported by the client since the store was started.The value format is a 4-byte float.

Client RPCs succeeded The number of successful RPCs that are reported by the client since the store wasstarted. The value format is a 4-byte integer.

Client RPCs succeeded/sec The rate of successful RPCs that is reported by the client since the store wasstarted. The value format is a 4-byte float.

Connection Count The number of client processes that are connected to the information store. The valueformat is a 4-byte integer.

Database Session Hit Rate Percent hit rate on re-using database sessions since the server was started.The value format is a decimal.

Note: The value is 0 for Exchange Server 2007.

Exchmem Current Bytes Allocated (MB) The current number bytes (in MB) that is allocated throughExchmem (excluding virtual allocations). The value format is a 4-byte integer.

Exchmem Current Number of Virtual Allocations The current number of Exchmem allocations that aredirectly allocated through virtual memory. The value format is a 4-byte integer.

Exchmem Current Virtual Bytes Allocated (MB) The current number bytes (in MB) that is virtuallyallocated through Exchmem. The value format is a 4-byte integer.

Exchmem Maximum Bytes Allocated (MB) The maximum concurrent bytes (in MB) allocated throughExchmem (excluding virtual allocations). The value format is a 4-byte integer.

Exchmem Maximum Virtual Bytes Allocated (MB) The maximum concurrent bytes (in MB) virtuallyallocated through Exchmem. The value format is a 4-byte integer.

Exchmem Number of Additional Heaps The number of Exchmem heaps that are created by the MSExchange IS after startup.


Exchmem Number of heaps with memory errors The total number of Exchmem heaps that were notallocated due to insufficient available memory.

Exchmem Number of memory errors The total number of Exchmem allocations that cannot be satisfiedby the available memory.

Exchmem Total Number of Virtual Allocations The total number of Exchmem allocations that aredirectly allocated from virtual memory. The value format is a 4-byte integer.

Maximum Anonymous Users The maximum number of anonymous users since server startup. The valueformat is a 4-byte integer.

Maximum Connections The maximum number of concurrent connections since server startup. The valueformat is a 4-byte integer.

Maximum Users The maximum number of concurrent users since server startup. The value format is a4-byte integer.

Peak Push Notifications Cache Size The maximum size of the Push Notifications Cache. The valueformat is a 4-byte integer.

Push Notifications Cache Size The current size of the Push Notifications Cache since the server wasstarted. The value format is a 4-byte integer.

Push Notifications Generated/Sec The number of times the notifications are sent to clients, who haveregistered for notifications of changes to tables in the information store, per second. The value format is adecimal.

Push Notifications Skipped/Sec The number of push notifications per second that were skipped bycaching at the server. The value format is a decimal.

Read Bytes RPC Clients /Sec The number of times that bytes are read from RPC clients per second sincethe server was started. The value format is a decimal.

Recurring Appointment Creation Rate The number of recurring appointments that are created persecond. The value format is a 4-byte float.

Recurring Appointment Deletion Rate The number of recurring appointments that are deleted persecond. The value format is a 4-byte float.

Recurring Appointment Modification Rate The number of recurring appointments that are modified persecond. The value format is a 4-byte float.

RPC Averaged Latency The average RPC latency in milliseconds for the past 1024 packets.

RPC Client Backoff/Sec The rate at which the server notifies a client to withdraw. The value format is a4-byte float.

RPC Num of Slow Packets The number of RPC packets in the past 1024 packets that have latencieslonger than 2 seconds. The value format is a 4-byte integer.

RPC Operations/Sec The number of times the RPC operations occur per second since the server wasstarted. The value format is a decimal.

RPC Operations Failed Due to Server Too Busy The number of RPC operations that failed because theserver was too busy since the mailbox store was started. The value format is a 4-byte integer.


RPC Operations Failed per Second Due to Server Too Busy The number of RPC operations that havefailed per second because the server was too busy. The value format is a 4-byte float.

RPC Packets/Sec The number of times the RPC packets are processed per second since the server wasstarted. The value format is a decimal.

RPC Requests The number of client requests that are currently being processed by the information store.The value format is a 4-byte integer.

RPC Requests Peak The maximum number of client requests that were processed simultaneously by theinformation store since it was started. The value format is a 4-byte integer.

Single Appointment Creation Rate The number of single instance appointments that are created persecond. The value format is a 4-byte float.

Single Appointment Deletion Rate The number of single instance appointments that are deleted persecond. The value format is a 4-byte float.

Single Appointment Modification Rate The number of single instance appointments that are modifiedper second. The value format is a 4-byte float.

Single Appointments Created The number of single instance appointments that are created. The valueformat is a 4-byte float.

Single Appointments Deleted The number of single instance appointments that are deleted. The valueformat is a 4-byte float.

Single Appointments Modified The number of single instance appointments that are modified. Thevalue format is a 4-byte float.

Slow QP Threads The number of Query Processor threads that are running unoptimized queries. Thevalue format is a 4-byte float.

Slow Search Threads The number of search threads that currently run queries, which are not optimized.The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

User Count The number of users that are connected to the information store. The value format is a 4-byteinteger.


Virus Scan Files Cleaned The total number of separate files that are cleaned by a virus scanner. Thevalue format is a 4-byte integer.

Virus Scan Files Cleaned/Sec The rate at which separate files are cleaned by a virus scanner. The valueformat is a 4-byte float.

Virus Scan Files Quarantined The total number of files that are shifted into quarantine by a virusscanner. The value format is a 4-byte integer.

Virus Scan Files Quarantined/Sec The rate at which separate files are shifted into quarantine by a virusscanner. The value format is a 4-byte float.

Virus Scan Files Scanned The total number of separate files that are scanned by a virus scanner. Thevalue format is a 4-byte integer.

Virus Scan Files Scanned/Sec The rate at which separate files are scanned by a virus scanner. The valueformat is a 4-byte float.

Virus Scan Folders Scanned in Background The total number of folders that are processed bybackground scanning. The value format is a 4-byte integer.

Virus Scan Messages Cleaned The total number of top-level messages that are cleaned by a virusscanner. The value format is a 4-byte integer.

Virus Scan Messages Cleaned/Sec The rate at which top-level messages are cleaned by a virus scanner.The value format is a 4-byte float.

Virus Scan Messages Deleted The total number of top-level messages that are deleted upon the requestof a virus scanner. The value format is a 4-byte integer.

Virus Scan Messages Deleted/Sec The rate at which top-level messages are deleted upon the request of avirus scanner. The value format is a 4-byte float.

Virus Scan Messages Processed The total number of top-level messages that are processed by a virusscanner. The value format is a 4-byte integer.

Virus Scan Messages Processed/Sec The rate at which top-level messages are processed by a virusscanner. The value format is a 4-byte float.

Virus Scan Messages Quarantined The total number of top-level messages that are shifted intoquarantine by a virus scanner. The value format is a 4-byte integer.

Virus Scan Messages Quarantined/Sec The rate at which top-level messages are shifted into quarantineby a virus scanner. The value format is a 4-byte float.

Virus Scan Messages Scanned in Background The total number of messages that are processed bybackground scanning. The value format is a 4-byte integer.

Virus Scan Queue Length The number of outstanding requests that are currently queued for virusscanning. The value format is a 4-byte integer.

VM Largest Block Size The size of the largest free virtual memory block in megabytes.

VM Total 16 MB Free Blocks The total number of free virtual memory blocks that are larger than orequal to 16 MB.


VM Total Free Blocks The total number of free virtual memory blocks.

VM Total Large Free Block Bytes The total number of megabytes in free virtual memory blocks that arelarger than or equal to 16 MB.

Write Bytes RPC Clients/Sec The number of times that bytes are written to RPC clients per second sincethe server started. The value format is a decimal.

MS Exchange IS Client attributesThis attribute group represents MS Exchange IS Client statistics.


Client Name The name of the client instance.

JET Log Records/Sec The rate at which the database log records are generated while processing requestsfor the client. The value format is a 4-byte float.

JET Pages Read/Sec The rate at which the database pages are read from disk while processing requestsfor the client. The value format is a 4-byte float.

LDAP Reads/Sec The number of LDAP read operations that are performed per second while processingclient requests. The value format is a 4-byte float.

Note: This attribute is not available in Exchange Server 2013. The Undefined enumeration value isdisplayed on the Tivoli Enterprise Portal for Exchange Server 2013.

LDAP Searches/Sec The number of LDAP search operations that are performed per second whileprocessing client requests. The value format is a 4-byte float.

RPC Average Latency The average server RPC latency in milliseconds for the past 1024 packets.

RPC Bytes Received/Sec The number of times that bytes are received from RPC clients per second.

RPC Bytes Sent/Sec The number of times that bytes are sent to RPC clients per second.

RPC Packets/Sec The number of times that the RPC packets are processed per second.

RPC Operations/Sec The number of RPC operations that are currently requested per second from theserver. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute


SS Second

MS Exchange IS HA Active Database attributesThis attribute group monitors the availability of active mailbox databases on the Exchange Server.


Average Emit And Send Latency The average latency (in seconds) for processing messages that are sentto the network. The value format is 4-byte float.

Average Emit Latency The average latency (in seconds) for processing messages. The value format is a4-byte float.

Block Mode Replication Overflows The total number of transitions that occurred out of the continuousreplication - block mode because of the transmit queue overflow. The value format is a 4-byte integer.

Compression Enabled A numeric value that indicates whether log data is compressed before it is sent tothe passive database copies. The value format is a 4-byte integer. The following table provides theenumeration values for the attribute:

External value Internal value

Yes 1

No 0

Current Log Generation Number The generation sequence number of the last log file that is sent by theactive database copy. The value format is a 4-byte integer.

Emit Calls/Sec The number notifications that are generated per second to replicate log files. The valueformat is a 4-byte integer.

Log Generation Rate The amount of log data that is generated per second. The value format is a 4-bytefloat.

Mailbox Database Name The name of the mailbox database. The value format is an alphanumeric stringwith a maximum of 600 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


Total Bytes Input to Compression The total amount of data (in bytes) that was compressed beforereplication since the service was started. The value format is a 4-byte float.

Total Bytes Output from Compression The total amount of compressed data (in bytes) that was queuedfor replication since the service was started. The value format is a 4-byte float.

Total Emit Calls The total number of times the log data was provided to replicate active mailboxdatabase copies for high availability since the service was started. The value format is a 4-byte integer.

Total Log Bytes Generated The total amount of log data (in bytes) that was queued for replication sincethe service was started. The value format is a 4-byte float.

MS Exchange IS Private attributesThis group of data represents MS Exchange IS Private activity.

Note: This attribute group is available in Exchange Server 2003, 2007 and 2010. This attribute group is amulti-instance attribute group.

Active Client Logons The number of clients that performed any action within the last 10 minute interval.The value format is a 4-byte integer.

Average Delivery Time The average time in milliseconds between the submission of a message to themailbox store and submission to other storage providers for the last 10 messages. The value format is adecimal.

Average Local Delivery Time The average time in milliseconds between the submission of a message tothe information store and the delivery to all local recipients on the same server for the last 10 messages.The value format is a decimal.

Note: This attribute is available only in Exchange Server 2000. The Enum value is displayed as Undefinedfor Exchange Server 2003, 2007, and 2010.

Categorization Count The number of categorizations that exist in the private information store.Categorizations are created when a user creates a filtered view or performs a search. When theinformation store must maintain an excessive number of categorizations, performance can be affected.The value format is a 4-byte integer.

Client Logons The number of clients (including system processes) that are currently logged on. The valueformat is a 4-byte integer.

Event History Deletes The number of events that are deleted from the event history of the mailbox storesince the start of the mailbox store. The value format is a 4-byte integer.

Event History Deletes/Sec The rate at which the events are deleted from the event history of the mailboxstore. The value format is a 4-byte float.

Event History Reads The number of events that are read from the event history of the mailbox storesince the start of the mailbox store. The value format is a 4-byte integer.

Event History Reads/Sec The rate at which the events are read from the event history of the mailboxstore. The value format is a 4-byte float.

Event History Writes The number of events that are written to the event history of the mailbox storesince the start of the mailbox store. The value format is a 4-byte integer.


Event History Writes/Sec The rate at which the events are written to the event history of the mailboxstore. The value format is a 4-byte float.

Folder Opens/Sec The number of times that requests to open folders are submitted to the informationstore per second since the server was started. The value format is a decimal.

Local Deliveries Total number of messages delivered locally since the server was started. The valueformat is a 4-byte integer.

Local delivery rate The Rate at which messages are delivered locally since the server started. The formatof the value is decimal.

Logon Operations/Sec The rate of Logon requests in the mailbox store. The value format is a 4-byte float.

Mailbox IS Database Percent Space Used The percent of the total space the Mailbox Database is using.Mailbox Information Store Database takes up a percentage of the total Information Store space used. Thevalue format is a 4-byte integer.

Mailbox IS Percent Growth Mailbox Information Store growth percentage since the last interval samplewas performed. The value format is a 4-byte integer.

Mailbox IS Size The size of the mailbox information store in megabytes. Information Store maintains themessaging databases that contain all server-based mailboxes. Messaging databases are managed instorage groups and include transaction log files, a MAPI-based database file, and a streaming database.The value format is a 4-byte integer.

Mailbox Name The name of the mailbox. The value format is an alphanumeric string with a maximumof 600 characters.

Mailbox Store Distinguished Name The distinguished name of the mailbox database. The value formatis an alphanumeric string with a maximum of 3072 characters.

Mailbox Store State Reports if the Mailbox Store is either mounted or demounted. The Mailbox Store canbe demounted for maintenance. The value format is a 4-byte integer. The following values are possible:


Mounted 0

Dismounted 1

Message Opens/Sec The number of times that requests to open messages are submitted to theinformation store per second since the server was started. The value format is a decimal.

Messages Queued For Submission The current number of submitted messages that are not processed bytransport. The value format is a 4-byte integer.

Message Recipients Delivered The total number of recipients that have received a message since serverstartup. The value format is a 4-byte integer.

Message Recipients Delivered/min The number of messages that recipients receive per minute since theserver was started. The value format is a decimal. The Enum value is displayed as Undefined forMicrosoft Exchange Server 2003 and 2007.

Messages Delivered The total number of messages delivered to all recipients since server startup. Thevalue format is a 4-byte integer.


Messages Delivered/min The number of messages delivered to all recipients per minute since the serverwas started. The value format is a decimal.

Note: This attribute is available only in Exchange Server 2000 and 2003. The Enum value is displayed asUndefined for Exchange Server 2007.

Messages Sent The total number of messages that were sent to the transport since server startup. Thevalue format is a 4-byte integer.

Messages Sent/min The number of messages sent to the transport per minute since the server wasstarted. The value format is a decimal.

Messages Submitted The total number of messages that clients submitted since server startup. The valueformat is a 4-byte integer.

Messages Submitted/min The number of messages submitted by the clients per minute since the serverwas started. The value format is a decimal.

Peak Client Logons The maximum number of concurrent client logons since the service was started. Thevalue format is a 4-byte integer.

Receive Queue Size The number of messages in the private information store receive queue. The valueformat is a 4-byte integer.

Note: This attribute is available only in Microsoft Exchange Server 2000, 2003, and 2007, not on MicrosoftExchange Server 2010.

RPC Average Latency The average time (in milliseconds) of the database RPC latency for the last 1024packets. The value format is a 4-byte float.

Search Task Rate The number of search tasks that are created per second. The value format is a 4-bytefloat.

Send Queue Size The number of messages in the send queue of the private information store. The valueformat is a 4-byte integer. The Enum value is displayed as Undefined for Microsoft Exchange Server 2007and 2010.

Note: This attribute is available only on Microsoft Exchange Server 2000 and 2003, not on MicrosoftExchange Server 2007 and 2010. The Enum value is displayed as Undefined for Microsoft Exchange Server2007 and 2010.

Single Instance Ratio The average number of references to each message in the mailbox store since theserver was started. The value format is a decimal with a valid range from 1 to 2.

Note: This attribute is available only on Microsoft Exchange Server 2000, 2003, and 2007, not onMicrosoft Exchange Server 2010.

Slow FindRow Rate The rate at which the slower findrow must be used in the mailbox store. The valueformat is a 4-byte float.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Count of Recoverable Items The total number of items retained for Item Recovery since the serverwas started. The value format is a 4-byte integer.

Total Size of Recoverable Items The total size in kilobytes of items retained for Item Recovery since theserver was started. The value format is a 4-byte integer.

MS Exchange IS Public attributesThis group of data represents MS Exchange IS Public activity.

Note: If public folder database is demounted, then the value for all the attributes will be displayed as 0.

Active Client Logons The number of clients that are currently logged on. The value format is a 4-byteinteger.

Average Delivery Time The average time in seconds between the submission of a message to the publicfolder store and submission to other storage providers for the last 10 messages. The value format is adecimal.

Average Local Delivery Time The average time in seconds between the submission of a message to thepublic folder store and the delivery to all local recipients (recipients on the same server) for the last 10messages. The value format is a decimal.

Note: This attribute is available only on Microsoft Exchange Server 2000, not on Microsoft ExchangeServer 2003, 2007, and 2010. The Enum value is displayed as Undefined for Microsoft Exchange Server2003, 2007, and 2010.

Categorization Count The number of categorizations that exist in the information store. Categorizationsare created when a user creates a filtered view or performs a search. When the information store mustmaintain an excessive number of categorizations, performance can be affected. The value format is a4-byte integer.

Client Logons The total number of client logons since server startup. The value format is a 4-byte integer.

Event History Deletes The number of events deleted from the event history of the public store since thestart of the public store. The value format is a 4-byte integer.

Event History Deletes/Sec The rate at which events are deleted from the event history of the public store.The value format is a 4-byte float.

Event History Reads The number of events that are read from the event history of the public store sincethe start of the public store. The value format is a 4-byte integer.

Event History Reads/Sec The rate at which events are read from the event history of the public store. Thevalue format is a 4-byte float.


Event History Writes The number of events that are written to the event history of the public store sincethe start of the public store. The value format is a 4-byte integer.

Event History Writes/Sec The rate at which events are written to the event history of the public store.The value format is a 4-byte float.

Folder opens/Sec The number of times that requests to open folders are submitted to the informationstore per second since the server was started. The value format is a decimal.

Logon Operations/Sec The rate of Logon requests in the public store. The value format is a 4-byte float.

Message Opens/Sec The number of times that requests to open messages are submitted to theinformation store per second since the server was started. The value format is a decimal.

Messages Queued For Submission The current number of submitted messages that are not processed bytransport. The value format is a 4-byte integer.

Message Recipients Delivered The total number of recipients that have received a message since serverstartup. The value format is a 4-byte integer.

Message Recipients Delivered/min The number of messages that recipients receive per minute since theserver was started. The value format is a decimal.

Message Submitted/min The number of messages that are submitted by clients per minute since theserver was started. The value format is a decimal. For Microsoft Exchange 2003 environments thefollowing value is possible:


Undefined -1

Messages Delivered The total number of messages delivered to all recipients since server startup. Thevalue format is a 4-byte integer.

Messages Delivered/min The number of messages delivered to all recipients per minute since the serverwas started. The value format is a decimal.

Note: This attribute is available only on Microsoft Exchange Server 2000 and 2003, not on MicrosoftExchange Server 2007. The Enum value is displayed as Undefined for Microsoft Exchange Server 2007.

Messages Sent The total number of messages sent to other storage providers since server startup. Thevalue format is a 4-byte integer.

Messages Sent/min The number of messages sent to other storage providers per minute since the serverwas started. The value format is a decimal.

Messages Submitted The total number of messages submitted by clients since server startup. The valueformat is a 4-byte integer.

Name The name of Microsoft Exchange public folder store. The value format is an alphanumeric stringwith a maximum of 600 characters.

Number of messages expired from public folders Number of messages expired from public folders sincethe server was started. The value format is a 4-byte integer.


Peak Client Logons The maximum number of concurrent client logons since server startup. The valueformat is a 4-byte integer.

Public Folder Distinguished Name The distinguished name of the Public Folder database. The valueformat is an alphanumeric string with a maximum of 3072 characters.

Public IS Database Percent Space Used Public Folder Database takes up a percentage of the totalInformation Store space used. This attribute reports what percent of the total space the Public FolderDatabase is using. The value format is a 4-byte integer.

Public IS Percent Growth Public Folder growth percentage since the last interval sample was performed.The value format is a 4-byte integer.

Public IS Size Size of Public Information Store which maintains the messaging databases that contain allserver-based public folders. Public Folder databases are managed in storage groups and includetransaction log files. This reports the size of the Public Folder Information size in megabytes. The valueformat is a 4-byte integer.

Public Store State This attribute reports if the Public Folder is mounted or demounted. Public Folder canbe demounted for maintenance. The value format is a 4-byte integer. The following values are possible:

External values Internal values

Mounted 0

Dismounted 1

Receive Queue Size The number of messages in the receive queue of the public information store. Thevalue format is a 4-byte integer.


Replication Folder Changes Received The number of changes in the replication folder that are copiedfrom other servers since the service was started. The value format is a 4-byte integer.

Replication Folder Changes Sent The number of messages that are copied due to public folder hierarchychanges that are sent to other servers since the service was started. The value format is a 4-byte integer.

Replication Receive Queue Size The number of copied messages that are to be processed. The valueformat is a 4-byte integer.

Send Queue Size The number of messages in the send queue of the public information store. The valueformat is a 4-byte integer.

Note: This attribute is available only on Microsoft Exchange Server 2000 and 2003, not on MicrosoftExchange Server 2007 and 2010. The Enum value is displayed as Undefined for Microsoft Exchange Server2007 and 2010.

Single Instance Ratio The average number of references to each message in the public store. Valid valuesrange from 1 to 2. The value format is a decimal.





MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Count of Recoverable Items The total number of items retained for Item Recovery since the serverwas started. The value format is a 4-byte integer.

Total Size of Recoverable Items The total size in kilobytes of items retained for Item Recovery since theserver was started. The value format is a 4-byte integer.

MS Exchange IS Public Replication attributesThis group of data represents MS Exchange IS Public Replication activity.

Name The name of the Microsoft Exchange IS Public Replication instance. The value format is analphanumeric string with a maximum of 600 characters.

Replication Backfill Data Messages Received The number of replication messages received from otherservers in response to backfill requests since server startup. The value format is a 4-byte integer.

Replication Backfill Data Messages Sent The number of replication messages sent in response to backfillrequests from other servers since server startup. The value format is a 4-byte integer.

Replication Backfill Requests Received The number of backfill request replication messages that werereceived from other servers since server startup. The value format is a 4-byte integer.

Replication Backfill Requests Sent The number of backfill request replication messages that were sent toother servers since server startup. The value format is a 4-byte integer.

Replication Folder Changes Received The number of folder changes that were replicated from otherservers since server startup. The value format is a 4-byte integer.

Replication Folder Changes Sent The number of replication messages due to public folder hierarchychanges that were sent to other servers since server startup. The value format is a 4-byte integer.

Replication Folder Data Messages Received The number of replication messages due to changes to itemsin public folders that were received from other service since server startup. The value format is a 4-byteinteger.

Replication Folder Data Messages Sent The number of replication messages due to changes to items inpublic folders that were sent to other servers since server startup. The value format is a 4-byte integer.


Replication Folder Tree Messages Received The number of replication messages due to public folderhierarchy changes that were received from other servers since server startup. The value format is a 4-byteinteger.

Replication Folder Tree Messages Sent The number of replication messages due to public folderhierarchy changes that were sent to other servers since server startup. The value format is a 4-byteinteger.

Replication Message Changes Received The number of changes to items in public folders that werereceived from other servers since server startup. The value format is a 4-byte integer.

Replication Message Changes Sent The number of changes to items in public folders that werereplicated to other servers since server startup. The value format is a 4-byte integer.

Replication Messages Received The total number of replication messages received from other serverssince server startup. The value format is a 4-byte integer.

Replication Messages Sent The total number of replication messages that were sent to other servers sinceserver startup. The value format is a 4-byte integer.

Replication Status Messages Received The number of replication status request or response messagesthat were received from other servers since server startup. The value format is a 4-byte integer.

Replication Status Messages Sent The number of replication status request or response messages thatwere sent to other servers since server startup. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange IS Store attributesThis attribute group monitors the Information Store activities on the Exchange Server.


Active Mailboxes The number of mailboxes that are currently active. The value format is a 4-byte integer.

AddressInfo Cache Lookups/Sec The number of times the AddressInfo cache is currently accessed persecond. The value format is a 4-byte integer.

AddressInfo Cache Misses/Sec The number of cache access attempts per second when the required datawas not found in the AddressInfo cache. The value format is a 4-byte integer.


Async Notification Calls in RPC Pools The number of asynchronous notification calls that are currentlywaiting to be processed in all the RPC context handle pools. The value format is a 4-byte integer.

DatabaseInfo Cache Lookups/Sec The number of times the DatabaseInfocache is currently accessed persecond. The value format is a 4-byte integer.

DatabaseInfo Cache Misses/Sec The number of cache access attempts per second when the required datawas not found in the DatabaseInfo cache. The value format is a 4-byte integer.

DistributionListMembership Cache Lookups/Sec The number of times the DistributionListMembershipcache is currently accessed per second. The value format is a 4-byte integer.

DistributionListMembership Cache Misses/Sec The number of cache access attempts per second whenthe required data was not found in the DistributionListMembership cache. The value format is a 4-byteinteger.

Folders Created/Sec The number of folders that are currently created per second in the Information Store.The value format is a 4-byte integer.

Folders Deleted/Sec The number of folders that are currently deleted per second in the InformationStore. The value format is a 4-byte integer.

Folders Opened/Sec The number of folders that are currently opened per second in the InformationStore. The value format is a 4-byte integer.

LogicalIndex Cache Hits/Sec The number of cache access attempts per second when the required datawas found in the LogicalIndex cache. The value format is a 4-byte integer.

Logical IndexCache Lookups/Sec The number of times the LogicalIndex cache is currently accessed persecond. The value format is a 4-byte integer.

LogicalIndex Cache Misses/Sec The number of cache access attempts per second when the required datawas not found in the LogicalIndex cache. The value format is a 4-byte integer.

MailboxInfo Cache Hits/Sec The number of cache access attempts per second when the required datawas found in the MailboxInfo cache. The value format is a 4-byte integer.

MailboxInfo Cache Lookups/Sec The number of times the MailboxInfo cache is currently accessed persecond. The value format is a 4-byte integer.

MailboxInfoCache Misses/Sec The number of cache access attempts per second when the required datawas not found in the MailboxInfo cache. The value format is a 4-byte integer.


Mailbox Database Percent Growth The percentage of Information Store growth since the last query wasprocessed. The value format is a 4-byte integer.

Mailbox Database Percent Space Used The percentage of Information Store space that is currently usedby the mailbox database. The value format is a 4-byte integer.

Mailbox Database Size The current size (in MB) of the mailbox databases in the Information Store. Thevalue format is a 4-byte integer.


Mailbox Database State The state of the mailbox store, such as mounted or dismounted. The followingtable provides the enumeration values of the attribute:


Mounted 0

Dismounted 1

N/A 2

Mailbox Database Distinguished Name The distinguished name of the mailbox database. The valueformat is an alphanumeric string with a maximum of 2000 characters.

Mailbox Level Maintenance Items The number of mailbox maintenance items. The value format is a4-byte integer.

Mailbox Level Maintenances/Sec The number of maintenance tasks that are currently completed persecond for the mailbox. The value format is a 4-byte integer.

MAPI Messages Created/Sec The number of MAPI messages that are currently created per second in thedatabase. The value format is a 4-byte integer.

MAPI Messages Modified/Sec The number of MAPI messages that are currently modified per second inthe database. The value format is a 4-byte integer.

MAPI Messages Opened/Sec The number of MAPI messages that are currently opened per second in thedatabase. The value format is a 4-byte integer.

Messages Created/Sec The number of messages that are currently created per second in the top-levelfolders of the Information Store. The value format is a 4-byte integer.

Messages Deleted/Sec The number of messages that are currently deleted per second in the top-levelfolders of the Information Store. The value format is a 4-byte integer.

Messages Delivered/Sec The number of messages that are currently delivered per second to the database.The value format is a 4-byte integer.

Messages Opened/Sec The number of messages that are currently opened per second in the top-levelfolders of the Information Store. The value format is a 4-byte integer.

Messages Submitted/Sec The number of messages that are currently submitted per second from thedatabase. The value format is a 4-byte integer.

Messages Updated/Sec The number of messages that are currently updated per second in the top-levelfolders of the Information Store. The value format is a 4-byte integer.

Number of Active RPC Context Handle Pools The number of RPC context handle pools that arecurrently active. The value format is a 4-byte integer.

OrganizationContainer Cache Hits/Sec The number of cache access attempts per second when therequired data was found in the OrganizationContainer cache. The value format is a 4-byte integer.

OrganizationContainer Cache Lookups/Sec The number of times the OrganizationContainer cache iscurrently accessed per second. The value format is a 4-byte integer.


OrganizationContainer Cache Misses/Sec The number of cache access attempts per second when therequired data was not found in the OrganizationContainer cache. The value format is a 4-byte integer.

Percent RPC Requests The percentage of MAPI RPC requests that are currently being processed. Thevalue format is a 4-byte integer.

Quarantined Mailbox Count The number of mailboxes that are currently quarantined per database. Thevalue format is a 4-byte integer.

RPC Average Latency The average time (in milliseconds) of the MAPI RPC latency. The value format is a4-byte integer.

RPC Operations/Sec The number of RPC operations that are currently processed per second. The valueformat is a 4-byte integer.

RPC Packets/Sec The number of RPC packets that are currently processed per second. The value formatis a 4-byte integer.

RPC Pool Context Handles The number of RPC context handles that are currently available in all theRPC context handle pools. The value format is a 4-byte integer.

RPC Requests The number of MAPI RPC requests that are currently running. The value format is a4-byte integer.

Search Queries/Sec The number of search queries that are currently processed per second on thedatabase. The value format is a 4-byte integer.

Search Results/Sec The number of search results that are currently generated per second during thedatabase search operations. The value format is a 4-byte integer.

Subobjects Cleaned/Sec The number of message attachments or embedded messages that are currentlycleaned per second. The value format is a 4-byte integer.

Subobjects Created/Sec The number of message attachments or embedded messages that are currentlycreated per second. The value format is a 4-byte integer.

Subobjects Deleted/Sec The number of message attachments or embedded messages that are currentlydeleted per second. The value format is a 4-byte integer.

Subobjects Opened/Sec The number of message attachments or embedded messages that are currentlyopened per second. The value format is a 4-byte integer.

Subobjects Searches/Sec The number of search operations that are currently completed per second on thedatabase. The value format is a 4-byte integer.



MM Month

DD Day

YY Year


HH Hour

mm Minute

SS Second

Total Search Queries Completed in More Than 60 Seconds The number of search queries that arecurrently processed per database, and for which the processing time was greater than 60 seconds. Thevalue format is a 4-byte integer.

Total Search Queries Completed in Less Than 1 Second The number of search queries that are currentlyprocessed per database, and for which the processing time was less than 1 second. The value format is a4-byte integer.

Total Search Queries Completed in Less Than 2 Seconds The number of search queries that arecurrently processed per database, and for which the processing time was less than 2 seconds. The valueformat is a 4-byte integer.

Total Search Queries Completed in 10 to 60 Seconds The number of search queries that are currentlyprocessed per database, and for which the processing time was in the range 10 - 60 seconds. The valueformat is a 4-byte integer.

Total Search Queries Completed in 2 to 10 Seconds The number of search queries that are currentlyprocessed per database, and for which the processing time was in the range 2 - 10 seconds. The valueformat is a 4-byte integer.

Total Searches The total number of search operations per database. The value format is a 4-byte integer.

Total Searches in Progress The number of search operations that are currently being processed perdatabase. The value format is a 4-byte integer.

Total Successful Search Queries The number of search queries that are currently completed per database.The value format is a 4-byte integer.

MS Exchange Lotus Notes Connector Summary attributesThis group of data provides details about Lotus Notes Connector.


Message Queued Inbound The number of messages that are queued to be received from clients and arewaiting to be delivered to Exchange Server. The value format is a 4-byte integer.

Message Queued Outbound The number of messages that are queued to be sent from Exchange Serverand are waiting to be delivered to clients. The value format is a 4-byte integer.

Messages Received The total number of messages received through Lotus Notes Connector since theconnector was started. The value format is a 4-byte integer.

Messages Rejected From Exchange The total number of messages rejected from Exchange Server sincethe connector was started. The value format is a 4-byte integer.

Messages Rejected From Notes The total number of messages rejected from Lotus Notes Connector sincethe connector was started. The value format is a 4-byte integer.


Messages Sent The total number of messages sent by Lotus Notes Connector since the connector wasstarted. The value format is a 4-byte integer.

Rate Of Messages Received The number of messages received from clients per hour since the LotusNotes Connector was started. The rate messages are received by the connector and reported inmegabytes. The value format is a 4-byte integer.

Rate Of Messages Sent The number of messages sent to clients per hour since the Lotus NotesConnector was started. The rate messages are received by the connector and reported in megabytes. Thevalue format is a 4-byte integer.

Rate Of Volume Received The number of bytes received from clients per hour since the Lotus NotesConnector was started. The rate messages are received by the connector and reported in megabytes. Thevalue format is a 4-byte integer.

Rate Of Volume Sent The number of bytes sent to clients per hour since the Lotus Notes Connector wasstarted. The rate messages are received by the connector and reported in megabytes. The value format isa 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Volume Queued Inbound The number of bytes that are queued to be received from clients and arewaiting to be delivered to Exchange Server. The value format is a 4-byte integer.

Volume Queued Outbound The number of bytes that are queued to be sent from Exchange Server andare waiting to be delivered to clients. The value format is a 4-byte integer.

Volume Received The number of message bytes received from the Lotus Notes system during thecollection cycle since the last sampling interval. The value format is a 4-byte integer.

Volume Sent The number of message bytes sent by the Lotus Notes system during the collection cyclesince the last sampling interval. The value format is a 4-byte integer.

MS Exchange Mail Submission attributesThis attribute group contains attributes that are related to the Microsoft Exchange Mail Submissionservice.

Note: The attribute group is available only in Exchange Server 2010 and 2010 Service Pack 1. Thisattribute group is a multi-instance attribute group.


Aggregate Shadow Queue Length The current number of messages in all shadow queues. The valueformat is a 4-byte integer.

Failed Submissions/Sec The number of message submissions that have failed per second. The valueformat is a 4-byte float.

Hub Servers The total number of Hub Transport servers that have been available in the same ActiveDirectory site since the service was started. The value format is a 4-byte integer.

Hub Servers In Retry The number of Hub Transport servers that have been in retry mode since theservice was started. The value format is a 4-byte integer.

Hub Transport Servers Percent Active The current percentage of active Hub Transport servers that areavailable in the same Active Directory site. The value format is a 4-byte float.

Mail Submission Instance Name The name of the Microsoft Exchange Mail Submission instance. Thevalue format is an alphanumeric string with a maximum length of 600 characters.

Shadow Message Resubmissions Total The current number of shadow messages that are waiting forresubmission in all Submission queues. The value format is a 4-byte integer.

Shadow Queue Auto Discards Total The total number of shadow messages that have been deleted fromall shadow queues because the messages have exceeded the auto discard timeout interval since theservice was started. The value format is a 4-byte integer.

Shadow Resubmission Queue Length The current number of shadow messages that are waiting forresubmission in the Submission queue. The value format is a 4-byte integer.

Successful Submissions The total number of successful message submissions to the Hub Transportserver since the service was started. The value format is a 4-byte integer.

Successful Submissions Per Second The total number of successful message submissions to the HubTransport server per second. The value format is a 4-byte float.


Temporary Submission Failures/Sec The number of message submissions that have temporarily failedper second. The value format is a 4-byte float.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Mail Tips attributesThis attribute group contains attributes that are related to the MailTips transport functionality.



Automatic Replies One Second The current percentage of Automatic Replies MailTip queries that arereturned by the Client Access server in 1 second. The queries are returned for the mailboxes for whichAutomatic Replies is turned on. The value format is a 4-byte float.

Automatic Replies Ten Seconds The current percentage of Automatic Replies MailTip queries that arereturned by the Client Access server in 10 seconds. The value format is a 4-byte float.

Automatic Replies Three Seconds The current percentage of Automatic Replies MailTip queries that arereturned by the Client Access server in 3 seconds. The value format is a 4-byte float.

Automatic Replies Turned On The total number of MailTip queries that have been returned by the ClientAccess server on mailboxes with Automatic Replies turned on since the service was started. The valueformat is a 4-byte integer.

Average Active Directory Response Time The average response time (in milliseconds) that the ActiveDirectory takes to respond to the GetMailTips request. The value format is a 4-byte float.

Group Metrics Queries/Sec The number of queries that were sent per second to read the group metricsdata. The value format is a 4-byte float.

GetMailTips Average Recipient Number The average number of recipients that send GetMailTipsrequests. The value format is a 4-byte float.

GetMailTips Average Response Time The average time (in milliseconds) that is spent between the startand end of a MailTips query. The value format is a 4-byte float.

GetMailTips Average Response Time For GroupMetrics Queries The average amount of time (inmilliseconds) that is spent between the start and end of a MailTips GroupMetrics request. The valueformat is a 4-byte float.


GetMailTipsConfiguration Average Response Time The average amount of time (in milliseconds) that isspent between the start and end of a GetMailTipsConfiguration request. The value format is a 4-bytefloat.

GetServiceConfiguration Average Response Time The average amount of time (in milliseconds) that isspent between the start and end of a GetServiceConfiguration request. The value format is a 4-byte float.

Intra Site MailTips Failures/Sec The current number of intrasite mailbox queries that have failed persecond. The value format is a 4-byte integer.

Mailbox Full Answered Within One Second The current percentage of Mailbox Full MailTip queries thatare returned by the Client Access server in 1 second. The value format is a 4-byte float.

Mailbox Full Answered Within Ten Seconds The current percentage of Mailbox Full MailTip queriesthat are returned by the Client Access server in 10 seconds. The value format is a 4-byte float.

Mailbox Full Answered Within Three Seconds The current percentage of Mailbox Full MailTip queriesthat are returned by the Client Access server in 3 seconds. The value format is a 4-byte float.


Mailbox Full With Positive Responses The total number of GetMailTips MailboxFull queries thatreturned the mailbox full status for the recipient since the service was started. The value format is a4-byte integer.

MailTips Accumulated Exception Recipients The total number of email clients that received an exceptionwhile querying the Mail Tips web service extension since the service was started. The value format is a4-byte integer.

MailTips Accumulated Mailbox Sourced Recipients The total number of mailbox sourced MailTipsrecipients that have been processed since the service was started. The value format is a 4-byte integer.

MailTips Accumulated Recipients The total number of MailTips recipients that have been processedsince the service was started. The value format is a 4-byte integer.

MailTips Accumulated Requests The total number of MailTips requests that have been processed sincethe service was started. The value format is a 4-byte integer.


MailTips Current Requests The number of MailTips web service requests that are currently processed.The value format is a 4-byte integer.

MailTips Queries Answered Within One Second The current percentage of all GetMailTips queries thatare returned by the Client Access server in 1 second. The value format is a 4-byte float.

MailTips Queries Answered Within Ten Second The current percentage of all GetMailTips queries thatare returned by the Client Access server in 10 seconds. The value format is a 4-byte float.

MailTips Queries Answered Within Three Second The current percentage of all GetMailTips queriesthat are returned by the Client Access server in 3 seconds. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Mailbox Replication Service attributesThis group of data represents Exchange Server Mailbox Replication Services.

Note: The attribute group is available in Exchange server 2010, or later. This attribute group is a singleinstance attribute group.

Last Scan Duration (msec) The duration of the last scan for jobs. The value format is a 4-byte integer.


Last Scan Timestamp (UTC) The UTC timestamp of the last time this service was scanned for jobs. Thevalue format is a 4-byte integer.

Mailbox databases in Active Directory site The number of active mailbox databases in the activedirectory site that are currently scanned for jobs. The value format is a 4-byte integer.


Mailbox servers in Active Directory site The total number of mailbox servers in the active directory sitethat are currently scanned for jobs. The value format is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Unreachable Databases The number of mailbox databases that are not scanned for jobs. The value formatis a 4-byte integer.

Unreachable Servers The number of unreachable mailbox servers. The value format is a 4-byte integer.


MS Exchange Mailbox Replication Service per Mdb attributesThis group of data represents Exchange Server Mailbox Replication Services per Mdb (mailbox database).

Note: The attribute group is available in Exchange server 2010, or later. This attribute group is amulti-instance attribute group.

Active Moves Total Moves The number of active moves. The value format is a 4-byte integer.

Last Scan Duration (msec) The duration of the last job scan for the database. The value format is a 4-byteinteger.

Last Scan Timestamp (UTC) (Superseded) The UTC timestamp of the last job scan for the database. Thevalue format is a 8-byte integer.

Last Scan Timestamp (UTC) The UTC timestamp of the last job scan for the database. The value formatis a 4-byte integer.


Mailbox Database Name The name of the mailbox database instance. The value format is analphanumeric string with a maximum of 332 characters.

MDB Health Content Indexing Lagging The database health indicator shows that the content indexing islagging. The value format is a 4-byte integer.

MDB Health Database Replication Lagging The database health indicator shows that the databasereplication is lagging. The value format is a 4-byte integer.

MDB Health Scan Failure The database health indicator shows that the MRS has encountered anexception while scanning for jobs. The value format is a 4-byte integer.

MDB Queue Auto Suspended The number of moves that are currently auto-suspended in the mailboxdatabase queue. The value format is a 4-byte integer.


MDB Queue Completed The number of moves that are currently completed in the mailbox databasequeue. The value format is a 4-byte integer.


MDB Queue Completed with Warnings The number of moves that are currently completed withwarnings in the mailbox database queue. The value format is a 4-byte integer.


MDB Queue Completing The number of moves that are currently in the CompletionInProgress state inthe mailbox database queue. The value format is a 4-byte integer.


MDB Queue Failed The number of moves that are currently failed in the mailbox database queue. Thevalue format is a 4-byte integer.


MDB Queue In Progress The number of moves that are currently in progress in the mailbox databasequeue. The value format is a 4-byte integer.


MDB Queue Pull The number of pull moves that are currently in the mailbox database queue. The valueformat is a 4-byte integer.


MDB Queue Push The number of push moves that are currently in the mailbox database queue. Thevalue format is a 4-byte integer.



MDB Queue Queued The number of queued moves that are currently in the mailbox database queue.The value format is a 4-byte integer.


MDB Queue Remote The number of remote (cross-org) moves that are currently in the mailbox databasequeue. The value format is a 4-byte integer.


MDB Queue Remote Legacy The number of remote legacy (cross-org) moves that are currently in themailbox database queue. The value format is a 4-byte integer.


MDB Queue Suspended The number of suspended moves that are currently in the mailbox databasequeue. The value format is a 4-byte integer.


MDB Queue Total The total number of move requests that are in the mailbox database queue. The valueformat is a 4-byte integer.


Move Requests Canceled/hour The average rate of move requests cancellation. The value format is a4-byte float.

Move Requests Completed/hour The average rate of move requests completion. The value format is a4-byte float.

Move Requests Completed with Warnings/hour The average rate of move requests completion withwarnings. The value format is a 4-byte float.

Move Requests Failed Bad Item Limit/hour The average rate of move request failures because abad-item limit was exceeded. The value format is a 4-byte float.

Move Requests Failed Network/hour The average rate of move request failures because of networkissues. The value format is a 4-byte float.

Move Requests Failed Other/hour The average rate of move request failures because of other issues. Thevalue format is a 4-byte float.

Move Requests Failed Stall Content Indexing/hour The average rate of move request failures because ofthe content indexing. The value format is a 4-byte float.

Move Requests Failed Stall Database Replication/hour The average rate of move request failuresbecause of database replication. The value format is a 4-byte float.


Move Requests Failed/hour The average rate of move request failures. The value format is a 4-byte float.

Move Requests Move Stalls Content Indexing/hour The average rate of move stalls because of contentindexing. The value format is a 4-byte float.

Move Requests Move Stalls (Database Replication)/hour The average rate of stalled moves because ofdatabase replication. The value format is a 4-byte float.

Move Requests Move Stalls/hour The average rate of stalled moves. The value format is a 4-byte float.

Move Requests Transient Failures Network/hour The total number of transient failures because ofnetwork issues. The value format is a 4-byte float.

Move Requests Transient Failures Proxy Backoff/hour The average rate of transient failures because ofproxy backoff. The value format is a 4-byte float.

Move Requests Transient Failures/hour The average rate of transient failures. The value format is a4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Mailbox Detail attributesThis group of data provides details about mailbox utilization within a Storage Group.

E-mail Addresses Email addresses in Active Directory naming format suitable for representation andidentification in Exchange Server. Multiple email addresses will be separated by a semicolon. The valueformat is an alphanumeric string with a maximum of 384 characters.

Information Store Name Information Store Name. The value format is an alphanumeric string with amaximum of 384 characters.

Last Logon The last date and time a user logged into a mailbox. The format is MM/DD/YY HH:mm:SS,where the following measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


The following values are also possible:

N/A Not applicable or not available

N/C Not calculated

N/P Not present

Mailbox Max Size The maximum size Mailbox can reach in megabytes. If Mailbox Max Size isconfigured as unlimited, the amount of free space on the hard disk drive is displayed.

Mailbox Name Name assigned to Mailbox Account by Microsoft Exchange Server when mailbox wascreated. The value format is an alphanumeric string with a maximum of 384 characters.

Mailbox Size The size of mailbox in megabytes.

Number Of Messages The total number of messages in mailbox since the server was started.

Storage Group Name Storage Group Name. The value format is an alphanumeric string with amaximum of 384 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Managed Folder Assistant attributesThis group of data monitors the activity of the Exchange Managed Folder Assistant.


Items Deleted but Recoverable The total number of deleted items that the Managed Folder Assistant canrecover through the dumpster since the most recent schedule interval was started. The value format is a4-byte integer.

Items Marked as Past Retention Date The total number of items marked as past their retention date bythe Managed Folder Assistant since the most recent schedule interval was started. The value format is a4-byte integer.

Items Moved The total number of items that are moved by the Managed Folder Assistant since the mostrecent schedule interval was started. The value format is a 4-byte integer.


Items Permanently Deleted The total number of items that are permanently deleted by the ManagedFolder Assistant since the most recent schedule interval was started. The value format is a 4-byte integer.

Items Subject to Retention Policy The total number of items that are subject to retention policy by theManaged Folder Assistant since the most recent schedule interval was started. The value format is a4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange MAPI Connectivity Details attributesThis report describes the status of MAPI Connectivity of the server. This attribute group is asingle-instance attribute group.

Note: This attribute group is not available in Exchange Server 2010.

Connectivity Status The status of MAPI connectivity. The attribute can have one of following values

Enum Value Value Meaning

0 Success The mailbox database is accessible via a MAPI client.

1 Failure The mailbox database is not accessible via a MAPI client.

Database Name The name of the database.

Mailbox Server Name The name of the mailbox server.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


MS Exchange MTA attributesThis group of data represents MS Exchange Message Transfer Agent activity.

Note: The following attributes are not available on Microsoft Exchange Server 2007 and 2010.

Adjacent MTA Associations The number of open associations of MTA with other MTAs. The valueformat is a 4-byte integer.

Admin Connections The number of Microsoft Exchange administrator programs connected to the MTA.The value format is a 4-byte integer.

Deferred Delivery Msgs The number of messages in the deferred queue at the time the sample is taken.When many messages are sent to users who are no longer mailbox-enabled, the messages are deferredevery half hour and can accumulate in large numbers. The messages are constantly cycled through theinformation store and back to the deferred delivery queue. The value format is a 4-byte integer.

Disk File Deletes/Sec The rate of disk files that are deleted. The value format is a 4-byte float.

Disk File Opens/Sec The rate of disk files that are opened. The value format is a 4-byte float.

Disk File Reads/Sec The rate of the disk file read operation. The value format is a 4-byte float.

Disk File Syncs/Sec The rate of disk files that are synchronized. The value format is a 4-byte float.

Disk File Writes/Sec The rate of the disk file write operation. The value format is a 4-byte float.

Inbound KB Total The total number of KB received by the MTA Service since MTA initialization. Thevalue format is a 4-byte integer.

Inbound Messages Total The total number of messages received since MTA initialization. The valueformat is a 4-byte integer.

LAN Receive Bytes per Sec The number of times that bytes are received over a LAN from MTAs persecond since the server was started. The value format is a decimal.

LAN Transmit Bytes per Sec The number of times that bytes are transmitted over a LAN to MTAs persecond since the server was started. The value format is a decimal.

Message Bytes/Sec The rate at which message bytes are processed. The value format is a 4-byte float.

Messages per Sec The number of times that messages are processed by MTA per second since the serverwas started. The value format is a decimal.

Outbound KB Total The total number of KB sent by the MTA Service since MTA initialization since theserver was started. The value format is a 4-byte integer.

Outbound Messages Total The total number of messages transmitted since MTA initialization. The valueformat is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Threads in Use The number of threads that are in use by the MTA. This number does not include RPCthreads. The number can be used to determine whether additional processors are of benefit. The valueformat is a 4-byte integer.

Total Recipients Inbound The total number of recipients inbound since MTA initialization. This valuereflects the number of messages generated for inbound recipients. The value format is a 4-byte integer.

Total Recipients Outbound The total number of recipients outbound since MTA initialization. This valuereflects the number of messages generated for outbound recipients. The value format is a 4-byte integer.

Total Recipients Queued The total number of recipients queued to be processed by the MTA Service atthe time the sample was taken since the server was started. This value reflects the number of messagesgenerated for inbound and outbound recipients. The value format is a 4-byte integer.

Work Queue Bytes (MB) The total volume of messages (in MB) stored in the MTA. The value format is a4-byte float.

Work Queue Length The number of outstanding messages in the Work Queue, which indicates thenumber of messages not yet processed to completion by the MTA. The value format is a 4-byte integer.

MS Exchange MTA Connections attributesThe MS Exchange MTA Connections attribute group describes counters associated with MS ExchangeServer Message Transfer Agent Connections.

Note: This attribute group is available only in Exchange Server 2003.

Associations The number of associations between the MTA and the connected MTA since the server wasstarted. MTAs can open multiple associations, if additional transfer throughput is necessary. The valueformat is a 4-byte integer.

Current Inbound Associations The current number of inbound (remote initiated) associations with theentity. The value format is a 4-byte integer.

Current Outbound Associations The current number of outbound (locally initiated) associations with theentity. The value format is a 4-byte integer.

Failed Outbound Associations The number of failed associations with other MTAs to transmit outboundmessages since the server was started. The value format is a 4-byte integer.

Inbound KB Total Total KB received between this MTA and all associations with other MTAs since theserver was started. The value format is a 4-byte integer.

Inbound Messages Total Total messages received between this MTA and all associations with otherMTAs since server startup. The value format is a 4-byte integer.


Name The name of connections established by the Exchange MTA. The value format is an alphanumericstring with a maximum of 332 characters.

Outbound KB Total Total KB sent between this MTA and all associations with other MTAs since serverstartup. The value format is a 4-byte integer.

Outbound Messages Total Total messages sent between this MTA and all associations with other MTAssince server startup. The value format is a 4-byte integer.

Queue Length The number of outstanding messages queued for transfer to the entity. The value format isa 4-byte integer.

Queued Bytes (MB) The total volume of message content (in MB) that is stored in the queue of theentity. The value format is a 4-byte integer.

Receive Bytes/Sec The rate at which bytes are received from the connected entity. The value format is a4-byte float.

Receive Messages per Sec The number of times that messages are received from the connected entity persecond since the server was started. The value format is a decimal.

Rejected Inbound Associations The total number of inbound (initiated remotely) associations that arerejected since the MTA initialization. The value format is a 4-byte integer.

Send Bytes/Sec The rate at which the bytes are sent to the connected entity. The value format is a 4-bytefloat.

Send Messages per Sec The number of times that messages are sent to the connected entity per secondsince the server was started. The value format is a decimal.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Recipients Inbound The number of recipients received by the MTA Service since server startup.This value reflects the number of messages generated for inbound recipients. The value format is a 4-byteinteger.

Total Recipients Outbound The number of recipients sent by the MTA Service since the server wasstarted. This value reflects the number of messages generated for outbound recipients. The value formatis a 4-byte integer.

Total Recipients Queued The total number of recipients that are stored in the queue of the entity. Thevalue format is a 4-byte integer.


MS Exchange NLB Status attributesThis group describes the Network Load Balancing (NLB) status of the server.

NLB Status The NLB status of the computer. The following table gives the possible Enum values of theattribute:

Enum Value Value Meaning

1005 Stopped Cluster operations have stopped on at least one node.

1006 Converging The cluster is converging.

1007 Converged The cluster has converged successfully.

1008 Default The specified node has converged as the default host.

1009 Draining One or more nodes are draining.

1013 Suspended Cluster operations have been suspended on one or more nodes.

0 Undefined No data

Machine Name The name of the machine.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange OWA attributesThis attribute group represents the MS Exchange Outlook Web Access (OWA) statistics activity.


Active Conversions The number of conversions that are being processed by the WebReady DocumentViewing service. The value format is a 4-byte integer.

AS Queries The total number of Availability Service queries since the process started. The value format isa 4-byte integer.

AS Queries Failure % The percentage of the last 100 Availability Service lookups that failed. The valueformat is a 4-byte float.

Average Response Time The average time (in milliseconds) between the beginning and the end of anOEH or an ASPX request.

Average Search Time The average time (in milliseconds) that is required for a search to complete.


Current Unique Users The number of unique users logged on to Outlook Web Access. This valuemonitors the number of unique active user sessions. When users log off or if their session times out, theyare removed from this count. The value format is a 4-byte integer.

Messages Sent The number of messages that are sent by users since the process restarted. The valueformat is a 4-byte integer.

Names Checked The number of recipient names to be resolved since the process was started. The valueformat is a 4-byte integer.

Queued Conversion Requests The number of requests for conversion that are queued to be processed.The value format is a 4-byte integer.

Proxy Request Bytes The total number of HTTP header and content bytes in requests that are submittedto the proxy server since the beginning of the process.

Proxy Response Bytes The total number of HTTP header and content bytes in responses that aresubmitted to the proxy server since the beginning of the process.

Proxy Response Time Average The average time (in milliseconds) that has elapsed between thebeginning and the end of requests sent to the proxy server.

Proxy User Requests The total number of requests that are made by proxy users since the process wasstarted.

Proxy User Requests/Sec The number of requests sent to the proxy server per second.

Rejected Conversions The total number of conversion requests that are rejected because the documentsare in the block list. The value format is a 4-byte integer.

Request Failed The number of requests that failed since the process was restarted.

Requests The number of requests that were executed since the process was restarted.

Requests/Sec The number of requests handled by Outlook Web Access per second.

Searches The number of searches that are executed since the process restarted. The value format is a4-byte integer.

Searches Executed The total number of times a user requests a search since the process started. The valueformat is a 4-byte integer.


Searches Timed Out The number of searches that did not complete in the maximum time allowed sincethe process restarted. The value format is a 4-byte integer.



MM Month


DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Users The total number of users that are connected to Outlook Web Access since the processstarted. The value format is a 4-byte integer.

MS Exchange Protocol Analysis Agent attributesThis attribute group represents the MS Exchange Protocol Analysis statistics activity.


Change in Senders Blocked Because of Local Open Proxy The total number of senders blocked becauseof a local open proxy in that sampling interval.

Change in Senders Blocked Because of Local SRL The total number of senders blocked because of alocal sender reputation level (SRL) in that sampling interval. The agent resets the attribute to its initialvalue on startup of the Exchange Server.

Change in Senders Blocked Because of Remote Open Proxy The total number of senders blockedbecause of a remote open proxy in that sampling interval. The agent resets the attribute to its initial valueon startup of the Exchange Server.

Change in Senders Blocked Because of Remote SRL The total number of senders blocked because of aremote sender reputation level (SRL) in that sampling interval. The agent resets the attribute to its initialvalue on startup of the Exchange Server.

Senders Blocked Because of Local Open Proxy The total number of senders blocked because of a localopen proxy.

Senders Blocked Because of Local SRL The total number of senders blocked because of a local senderreputation level (SRL).

Senders Blocked Because of Remote Open Proxy The total number of senders blocked because of aremote open proxy.

Senders Blocked Because of Remote SRL The total number of senders blocked because of a remotesender reputation level (SRL).

Senders Processed The total number of senders that are processed. The value format is a 4-byte integer.



MM Month

DD Day


YY Year

HH Hour

mm Minute

SS Second

MS Exchange Public Folder Detail attributesThis group of data provides details about the Public Folder.

Folder Size The size of public folder in megabytes.

Information Store Name Information Store Name. The value format is an alphanumeric string with amaximum of 384 characters.

Last Logon The last date and time a user logged into a public folder. The format is MM/DD/YYHH:mm:SS, where the following measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

The following values are also possible:

N/A Not applicable or not available

N/C Not calculated

N/P Not present

Number Of Messages The total number of messages in public folder.

Public Folder Name Public Folder name. The value format is an alphanumeric string with a maximum of384 characters.

Storage Group Name Storage Group Name. The value format is an alphanumeric string with amaximum of 384 characters.

Note: The attribute is not available in Microsoft Exchange Server 2010.



MM Month

DD Day

YY Year

HH Hour


mm Minute

SS Second

MS Exchange Reachability attributesThis group of data provides details mailbox reachability.

Reachability Test Run Time The last date and time when the response time was captured. The format isMM/DD/YY HH:mm:SS, where the following measures apply:

MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Reachable Yes or No indicator that email address is reachable. The value format is a 4-byte integer. Thefollowing values are possible:


No 0

Yes 1

Round Trip Response Time Reports the round trip response time of email sent to target server inmilliseconds. If the email address is not reachable, the value is zero. The value format is a decimal.


Target E-mail Address Target email address test email is sent to. The value format is an alphanumericstring with a maximum of 384 characters.

Target Server Target server name test email is sent to. The value format is an alphanumeric string with amaximum of 384 characters. When the Target E-mail Address is unreachable, the Target Server Name isset to "unknown."


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Recipient Cache attributesThis group of data provides details about Exchange Recipient Cache.



Address Lookups Pending Number of Address Book Lookups that are queued to be processed since theserver was started. The value format is a 4-byte integer.

Batched Address Lookups Total number of Batch Address Book Lookups that have been processed sincethe server was started. The value format is a 4-byte integer.

Expand Group Requests Total number of requests to Expand Address Group since the server wasstarted. The value format is a 4-byte integer.

Individual Address Lookups Total number of Individual Address Book Lookups that have beenprocessed since the server was started. The value format is 4-byte integer.

Recipient Cache Instance Name Recipient Cache Instance name. The value format is an alphanumericstring with a maximum of 384 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Recipient Filter Agent attributesThis group of data represents MS Exchange Recipient Filter statistics activity.


Recipients Rejected by Block List The total number of recipients rejected by the block list.

Recipients Rejected by Block List/Sec The total number of recipients rejected by the block list persecond.

Recipients Rejected by Recipient Validation The total number of recipients rejected by the recipientvalidation.

Recipients Rejected by Recipient Validation/sec The total number of recipients rejected by the recipientvalidation per second.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Replication attributesThis attribute group monitors the replication activity on the Exchange Server in the cluster environment.

Activation Suspended A numeric value that indicates whether the automatic activation of the databasecopy is suspended. The value format is a 4-byte integer. The following table provides the enumerationvalues of the attribute:

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A

Note: This attribute is available only in Exchange Server 2010, or later.

Copy Generation Number The generation sequence number of the last log file that has been copied. Thevalue format is a 4-byte integer.

Copy Notification Generation Number The generation sequence number of the last log file that isknown to the Microsoft Exchange Replication service. The value format is a 4-byte integer.

Copy Queue Exceeds Mount Threshold A numeric value that indicates whether the copy queue length isgreater than the threshold that is specified by the auto database mount dial. This attribute is used only inthe cluster continuous replication (CCR) environment. In the CCR environment, the value of this attributeis 1 if the auto database mount dial is exceeded. In the local continuous replication (LCR) environment,this attribute value is always 0. The following table provides the enumeration values of the attribute:

Enum value Value

0 CCR_Queue_Good

1 CCR_Queue_High

-1 Undefined


Copy Queue Length The number of log files that are waiting to be copied and inspected. The valueformat is a 4-byte integer.


Disconnected A numeric value that indicates whether the database copy is disconnected. The valueformat is a 4-byte integer. The Disconnected state indicates that no connection exists between the activedatabase and the database copy. The following table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A


Failed and Suspended A numeric value that indicates whether the database copy is failed andsuspended. The value format is a 4-byte integer. The Failed and Suspended state indicates that anunrecoverable difference has been detected between the active mailbox database and the database copy.The following table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A


Inspector Generation Number The generation sequence number of the last log file that was inspected.The value format is a 4-byte integer.

Log Copy KB/Sec The size of the log files (in KB) that are copied per second. The value format is a4-byte integer.


MS Exchange Replication Instance Name The storage group instance name of the Microsoft ExchangeServer. The value format is an alphanumeric string with a maximum of 600 characters.

Node Type The type of node that indicates whether the node is active or passive. The value format is a4-byte integer.

Replay Batch Size The number of log files that are replayed together. The value format is a 4-byteinteger.

Replay Generation Number The generation sequence number of the last log file that was replayed. Thevalue format is a 4-byte integer.

Replay Generations Complete The number of log files that have been replayed in the current replaybatch. The value format is a 4-byte integer.



Replay Generations Per Minute The number of generated log files that are replayed per minute in thecurrent replay batch. The value format is a 4-byte integer.


Replay Generations Remaining The number of log files that remain to be replayed in the current replaybatch. The value format is a 4-byte integer.


Replay Notification Generation Number The generation sequence number of the last log file that isknown to the Microsoft Exchange Replication service. The value format is a 4-byte integer.

Replay Queue Length The number of log files that are waiting to be replayed. The value format is a4-byte integer.

Replica Instance Failed A numeric value that indicates if the continuous replication for the selectedinstance (storage group) has failed. The following table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A

Replication Initializing A numeric value that indicates if the continuous replication for the selectedinstance (storage group) has initialized. The initialization indicates that the storage group performs initialstartup checks or the Microsoft Exchange Replication service performs an incremental reseed. Thefollowing table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A

Replication Status The replication status of the storage group. The value format is a 4-byte integer. Thefollowing table provides the enumeration values of the attribute.

Enumeration value Value

0 Replication_Initializing

1 Replication_Suspended

2 Replication_Failed

3 Replication_Disabled

4 Replication_Healthy

5 Replication_ServiceDown

6 Replication_Resynchronizing


Enumeration value Value

7 Replication_Not_Supported

8 Replication_Stopped

9 Replication_Not_Configured

10 Replication_Seeding

11 Failed_Suspended

12 SinglePageRestore

13 SeedingSource

14 Mounted

15 Dismounted

16 Mounting

17 Dismounting

18 DisconnectedAndHealthy

19 DisconnectedAndResynchronizing

-1 N/A

Replication Suspended A numeric value that indicates if the continuous replication for the selectedinstance (storage group) has suspended. When the continuous replication is suspended, log files are notcopied and replayed into the passive node. The following table provides the enumeration values of theattribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A

Resynchronizing A numeric value that indicates whether the database copy is resynchronizing. The valueformat is a 4-byte integer. The Resynchronizing state indicates that the mailbox database copy is beingcompared with the active mailbox database to check for any differences between the two database copies.The Resynchronizing state remains until all the differences between the two database copies are detectedand resolved. The following table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A


Seeding A numeric value that indicates whether the passive database copy is being seeded. The valueformat is a 4-byte integer. The following table provides the enumeration values of the attribute.

Enum value Value

0 No


Enum value Value

1 Yes

-1 Undefined

-2 N/A

Note: This attribute is available only in Exchange Server 2010 SP1, or later.

Seeding Source A numeric value that indicates whether the passive database copy has been used as asource for seeding. The value format is a 4-byte integer. The following table provides the enumerationvalues of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A


Single Page Restore A numeric value that indicates whether the single page restore operation has beenperformed on the database copy. The value format is a 4-byte integer. The following table provides theenumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A


Suspended and Not Seeding A numeric value that indicates whether the continuous replication for thepassive database copy has been suspended and the database copy has not been seeded. The value formatis a 4-byte integer. When the continuous replication is suspended, log files are not copied and replayedinto the passive database copy. The following table provides the enumeration values of the attribute.

Enum value Value

0 No

1 Yes

-1 Undefined

-2 N/A





MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Replication attributes (Superseded)This attribute group monitors the Exchange Server Mailbox Store replication activity.

Copy Generation Number The generation number of the last log file that is copied. The value format is a4-byte integer.

Copy Notification Generation Number The generation number of the last log file that the copier isaware of. The value format is a 4-byte integer.

Copy Queue Exceeds Mount Threshold Is 1 if the copy queue length is larger than the Mount Thresholdspecified by the Auto Database Mount Dial that is with cluster continuous replication and it will alwaysbe undefined with Local Continuous Replication (LCR). The value format is a 4-byte integer.

Note: This attribute is not available in Microsoft Exchange Server 2010 and 2010 SP1. The Enum value isdisplayed as Undefined for Microsoft Exchange Server 2010 and 2010 SP1.

Copy Queue Length The number of log generations that is waiting to be inspected and copiedsuccessfully. The value format is a 4-byte integer.

Inspector Generation Number The generation number of the last log file that is inspected. The valueformat is a 4-byte integer.

Replay Batch Size The number of log generations that are replayed together. The value format is a 4-byteinteger.

Note: This attribute is not available in Microsoft Exchange Server 2010 SP1. The Enum value is displayedas Undefined for Microsoft Exchange Server 2010 SP1.

Replay Generation Number The generation number of the last log file that is replayed successfully. Thevalue format is a 4-byte integer.

Replay Generations Complete The number of log generations that are already played in the currentreplay batch. The value format is a 4-byte integer.


Replay Generations Per Minute The rate of replay in the log generations per minute in the currentreplay batch. The value format is a 4-byte integer.

Note: This attribute is not available in Microsoft Exchange Server 2010 and 2010 SP1. The Enum value isdisplayed as Undefined for Microsoft Exchange Server 2010 and 2010 SP1.


Replay Generations Remaining The number of log generations that remain to be played in currentreplay batch. The value format is a 4-byte integer.


Replay Notification Generation Number The generation number of the last log file that replay knowsabout. The value format is a 4-byte integer.

Replay Queue Length The number of log generations that is waiting to be replayed. The value format isa 4-byte integer.

Replica Instance Failed Failed is 1 if the replica instance is set to failed, otherwise 0. The value format isa 4-byte integer.

Replication Initializing Initializing has a value of 1 when the Microsoft Exchange Replication serviceperforms initial startup checks or when incremental reseeding occurs for any storage group. Otherwise,initializing has a value of 0. The value format is a 4-byte integer.

Replication Suspended Suspended is 1 if continuous replication is suspended. When continuousreplication is suspended, logs are not copied and replayed into the passive copy.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Replica Seeder attributesThis attribute group monitors the replica seeder.


Database Seeding Progress Percent The percentage of database seeding that has been completed sincethe seeding was started. The value format is a 4-byte integer.


Database Seeding Bytes Read The total amount of data (in KB) that has been read by the databaseseeder since the seeding was started. The value format is a 4-byte integer.



Database Seeding Bytes Written The total amount of data (in KB) that has been written by the databaseseeder since the seeding was started. The value format is a 4-byte integer.


Replica Seeder Instance Name The name of the replica seeder instance. The value format is analphanumeric string with a maximum of 600 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Replication Server attributesThis attribute group contains attributes that are related to the Replication Server.

Note: The attribute group is available in Exchange Server 2010 Service Pack 1, or later. This attributegroup is a single-instance attribute group.

GetCopyStatus Server Side Calls The total number of GetCopyStatus requests to retrieve the status ofdatabase copies that are created on the mailbox server between the start and end of the process. Thevalue format is a 4-byte integer.

GetCopyStatus Server Side Calls/Sec The current rate at which a remote client queries for the status ofdatabase copies on the mailbox server. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


MS Exchange Resource Booking attributesThis attribute group monitors the activities of the Resource Booking Attendant on the Microsoft ExchangeServer.


Average Resource Booking Processing Time The average time that is required for the Resource BookingAttendant to process a resource booking request. The value format is a 4-byte float.

Cancelled Meeting Requests The total number of meeting requests that have been cancelled by theResource Booking Attendant since the service was started. The value format is a 4-byte integer.

Declined Meeting Requests The total number of meeting requests that have been declined by theResource Booking Attendant since the service was started. The value format is a 4-byte integer.

Meeting Requests Failed The total number of requests that have not been processed by the ResourceBooking Attendant since the service was started. The value format is a 4-byte integer.

Meeting Requests Processed The total number of meeting requests that have been processed by theResource Booking Attendant since the service was started. The value format is a 4-byte integer.

Meeting Requests Submitted The total number of meeting requests that have been submitted forprocessing to the Resource Booking Attendant since the service was started. The value format is a 4-byteinteger.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Resource Health attributesThis attribute group contains attributes that include the health information for the resources that are usedby the Exchange Server.

Note: This attribute group is available only in Exchange Server 2010 Service Pack 1. This attribute groupis a multi-instance attribute group.

Resource Health Instance Name The name of the Microsoft Exchange Resource Health instance. Thevalue format is an alphanumeric string with a maximum length of 600 characters.

Fair To Unhealthy Latency Threshold The current latency value at which the resource state changes fromthe Fair state to the Unhealthy state. The value format is a 4-byte integer.


Healthy To Fair Latency Threshold The current latency value at which the resource state changes fromthe Healthy state to the Fair state. The value format is a 4-byte integer.

Max Resource Delay Per Minute The maximum amount of time (in milliseconds) that the server waits toaccess the resource in 1 minute. The value format is a 4-byte float.

Overflow Queue Count The number of new requests that are currently in the overflow queue. The newrequests are redirected to the overflow queue when the count for target queue reaches a maximum value.The value format is a 4-byte integer.

Overflow Queue Count Peak The maximum number of new requests that are redirected to the overflowqueue. The value format is a 4-byte integer.

Overflow Wait Time Peak The maximum amount of time (in milliseconds) that the current request waitsin the overflow queue before being redirected to the target queue. The value format is a 4-byte integer.

Raw Resource Value The parameter that is used to measure the current state of the resource since theservice was started. The value format is a 4-byte integer.

Requests Per Second The total number of requests that are received by the protected resource persecond. The value format is a 4-byte float.

Resource Health Measure The current resource health measure that is determined by the ExchangeServer since the service was started. The value format is a 4-byte integer.

Semaphore Count The current number of semaphores that control access to a shared resource, which isused by the Exchange Server. The value format is a 4-byte integer.

Semaphore Count Peak The maximum number of semaphores that control access to a shared resource,which is used by the Exchange Server. The value format is a 4-byte integer.

Total Semaphore Size The number of processes that can concurrently access the semaphore since theservice was started. The value format is a 4-byte integer.

Total Semaphore Size Peak The maximum number of processes that can concurrently access thesemaphore. The value format is a 4-byte integer.

Total Threads Beyond Acceptable Latency The total number of threads that exceed the predefinedmaximum latency since the service was started. The value format is a 4-byte integer.

Unhealthy Health Measure The server health measure that is returned when the resource that is used bythe Exchange Server is unhealthy. The value format is a 4-byte integer.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric string with a maximumof 64 characters.


MM Month

DD Day

YY Year

HH Hour


mm Minute

SS Second

MS Exchange Rights Management Service attributesThis group of data represents Exchange Server Rights Management Service.


Average time for successful AcquireLicense() The average time that is consumed by a single successfulAcquireLicense() in milliseconds. The value format is a 4-byte integer.

Average time for successful AcquirePreLicense() The average time that is consumed by a singlesuccessful AcquirePreLicense() in milliseconds. The value format is a 4-byte integer.

Average time for successful AcquireTemplates() The average time that is consumed by a singlesuccessful AcquireTemplates() in milliseconds. The value format is a 4-byte integer.

Average time for successful Certify() The average time that is consumed by a single successful Certify()in milliseconds. The value format is a 4-byte integer.

Average time for successful FindServiceLocations() The average time that is consumed by a singlesuccessful FindServiceLocations() in milliseconds. The value format is a 4-byte integer.

Average time for successful GetClientLicensorCert() The average time that is consumed by a singlesuccessful GetClientLicensorCert() in milliseconds. The value format is a 4-byte integer.

Cache-hit of RMS Server Info/sec The number of cache-hits of RMS server information per second. Thevalue format is a 4-byte float.

Cache-miss of RMS Server Info/sec The number of cache-misses of RMS server information per second.The value format is a 4-byte float.

Entries added into RMS License Store/sec The number of entries that are added into the RMS licensestore per second. The value format is a 4-byte float.

Entries added into RMS Server Info cache/sec The number of entries that are added into the RMS serverinformation cache per second. The value format is a 4-byte float.

Entries removed from RMS License Store/sec The number of entries that are removed from the RMSlicense store per second. The value format is a 4-byte float.

Entries removed from RMS Server Info cache/sec The number of entries that are removed from the RMSserver information cache per second. The value format is a 4-byte float.

Failed AcquireLicense()/sec The number of AcquireLicense() requests that are invoked but failed persecond. The value format is a 4-byte float.

Failed AcquirePreLicense()/sec The number of AcquirePreLicense() requests that are invoked but failedper second. The value format is a 4-byte float.

Failed AcquireTemplates()/sec The number of AcquireTemplates() requests that are invoked but failedper second. The value format is a 4-byte float.


Failed Certify()/sec The number of Certify() requests that are invoked but failed per second. The valueformat is a 4-byte float.

Failed External AcquireLicense() Requests/sec The total number of failed AcquireLicense() requests thatare made to external RMS servers per second. The value format is a 4-byte float.

Failed External Certification Requests/sec The total number of failed certification requests that are madefor external RMS servers per second. The value format is a 4-byte float.

Failed FindServiceLocations()/sec The number of FindServiceLocations() requests that are invoked butfailed per second. The value format is a 4-byte float.

Failed GetClientLicensorCert()/sec The number of GetClientLicensorCert() requests that are invoked butfailed per second. The value format is a 4-byte float.

Successful AcquireLicense()/sec The number of AcquireLicense() requests that are invoked and processedsuccessfully per second. The value format is a 4-byte float.

Successful AcquirePreLicense()/sec The number of AcquirePreLicense() requests that are invoked andprocessed successfully per second. The value format is a 4-byte float.

Successful AcquireTemplates()/sec The number of AcquireTemplates() requests that are invoked andprocessed successfully per second. The value format is a 4-byte float.

Successful Certify()/sec The number of Certify() requests that are invoked and processed successfully persecond. The value format is a 4-byte float.

Successful External AcquireLicense() Requests/sec The total number of successful AcquireLicense()requests that are made for external RMS servers per second. The value format is a 4-byte float.

Successful External Certification Requests/sec The total number of successful certification requests thatare made for external RMS servers per second. The value format is a 4-byte float.

Successful FindServiceLocations()/sec The number of FindServiceLocations() requests that are invokedand processed successfully per second. The value format is a 4-byte float.

Successful GetClientLicensorCert()/sec The number of GetClientLicensorCert() requests that are invokedand processed successfully per second. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


Total cache hit of RMS Server Info The total number of cache-hits of RMS server information. The valueformat is a 4-byte integer.

Total cache miss of RMS Server Info The total number of cache-misses of RMS server information. Thevalue format is a 4-byte integer.

MS Exchange Role Based Services attributesThis report provides the status of the MS Exchange system service on the server.


Roles The MS Exchange Server roles.

Service Name (superseded) The name of the MS Exchange system service.

Service Name The name of the MS Exchange server service.

Status The status of MS Exchange system service.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Role Topology attributesThis group of data provides details about the Topology of Exchange Server.

Note: The following attributes are available in Microsoft Exchange Server 2007 and 2010. No data will bereturned for all other Microsoft Exchange Servers. The name of the Microsoft Exchange 2007 and 2010Server role to be used with each attribute group is in the "Attribute groups and Microsoft Exchange 2007and 2010 Server roles" table in the User's Guide for this monitoring agent.

Domain Name The fully qualified domain name.

Exchange Server Name The name of the machine part of the organizational Exchange setup.

Roles The list of roles installed on the machine.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange RPC Client Access attributesThis attribute group monitors the activities of the RPC Client Access service on the Microsoft ExchangeServer. By using the RPC Client Access service, the clients can access the Mailbox Server through theClient Access Server.


Active User Count The total number of users who have been logged on to the server and have donesome activity during the last 2 minutes since the service was started. The value format is a 4-byte integer.

Client Background RPCs Failed The total number of background RPC requests that have been reportedby the clients, and that have failed since the service was started. The value format is a 4-byte integer.

Client Background RPCs Succeeded The total number of background RPC requests that have beenreported by the clients, and that have been processed since the service was started. The value format is a4-byte integer.

Client Foreground RPCs Failed The total number of foreground RPC requests that have been reportedby the clients, and that have failed since the service was started. The value format is a 4-byte integer.

Client Foreground RPCs Succeeded The total number of foreground RPC requests that have beenreported by the clients, and that have been processed since the service was started. The value format is a4-byte integer.

Client RPCs Attempted The total number of RPC requests that have been attempted by the users sincethe service was started. The value format is a 4-byte integer.

Client RPCs Failed The total number of RPC requests that have been reported by the clients, and thathave failed since the service was started. The value format is a 4-byte integer.

Client RPCs Succeeded The total number of RPC requests that have been processed by the Outlookclient since the service was started. The value format is a 4-byte integer.

Connection Count The number of clients who are currently connected to the server. The value format is a4-byte integer.

RPC Average Latency The average RPC latency (in milliseconds) of the server for the last 1024 packets.The value format is a 4-byte float.

RPC Clients Bytes Read The number of bytes that are currently read from the RPC clients. The valueformat is a 4-byte integer.


RPC Clients Bytes Written The number of bytes that are currently written to the RPC clients. The valueformat is a 4-byte integer.

RPC Operations/Sec The number of RPC operations that are currently requested from the server persecond. The value format is a 4-byte integer.

RPC Packets/Sec The number of RPC packets that are currently processed per second. The value formatis a 4-byte integer.

RPC Requests The number of RPC requests that are currently being processed by the RPC Client Accessservice. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

User Count The number of users who are currently using the RPC Client Access service. The valueformat is a 4-byte integer.

MS Exchange Search Indices attributesThis attribute group monitors the activities of the Microsoft Exchange Search Indexer service.


Average Document Indexing Time The average time (in milliseconds) that is taken to index documents.The value format is a 4-byte float.

Average Latency of RPCs to Obtain Content The average latency (in milliseconds) of the current RPCrequests that retrieve the content from the specified database for the filter daemon. The value format is a4-byte float.


Average Size of Indexed Attachments The average size of the attachments that have been indexed sincethe filter daemon process was started. The value format is a 4-byte float.

Average Size of Indexed Attachments for Protected Messages The average size of the indexedattachments in the messages with Information Rights Management (IRM) protection. The value format isa 4-byte float.



Number of Failed Retries The total number of indexing attempts that have failed again for thedocuments for which indexing had initially failed since the service was started. The value format is a4-byte integer.

Full Crawl Mode Status A numeric value that indicates whether a full-text crawl has occurred on adatabase. The value format is a 4-byte integer. The following table provides the enumeration values of theattribute:

Enum value Value

0 No

1 Yes

Number of Items in Notification Queue The current number of items in the notification queue that arewaiting to be indexed. The value format is a 4-byte integer.

Number of Outstanding Batches The number of batches that are currently sent to the Microsoft SearchIndexer service, and that are being processed. The value format is a 4-byte integer.

Search Indices Instance Name The name of the Search Indices instance. The value format is analphanumeric string with a maximum of 600 characters.

Number of Successful Retries The total number of indexing attempts that have been processed for thedocuments for which indexing had initially failed since the service was started. The value format is a4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Throttling Delay Value The total time (in milliseconds) for which a worker thread waits before retrievinga document from the Microsoft Exchange Information Store service. The throttling delay value is set bythe throttling monitor thread. The value format is a 4-byte integer.


Total Indexing Time for Protected Messages The total time (in milliseconds) that is taken to index themessages with IRM protection. The value format is a 4-byte integer.


MS Exchange Search Mailbox OperatorsThis attribute group monitors the activities to search mailboxes on the Exchange Server.



Items Processed in 0 - 50 ms The total number of items that were processed in the range 0 - 50milliseconds since the search process was started. The value format is a 4-byte integer.



Items Processed in Greater than 2000 ms The total number of items that were processed in the durationgreater than 2000 milliseconds since the search process was started. The value format is a 4-byte integer.

Items with Rights Management Attempted for Processing The total number of Information RightsManagement (IRM) - protected items that were attempted for processing since the process was started.The value format is a 4-byte integer.

Items with Rights Management Partially Processed The total number of IRM-protected items that werepartially processed since the process was started. The value format is a 4-byte integer.

Items with Rights Management Skipped The total number of IRM-protected messages that were notprocessed since the process was started. The value format is a 4-byte integer.

Items with Valid Annotation Token The number of items with a valid annotation token. The valueformat is a 4-byte integer.

Items without Annotation Token The number of items without an annotation token. The value format isa 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Search Mailbox Session CacheThis attribute group monitors the cache activities that occur when you search content on the ExchangeServer.



Cache Hit Ratio The percentage of cache access attempts out of total cache access attempts when therequired data was available in the cache. The value format is a 4-byte float.

Cache Hits The total number of cache access attempts when the required data was available in the cachesince the service was started. The value format is a 4-byte integer.

Cache Instance Name The name of the cache instance. The value format is an alphanumeric string with amaximum of 600 characters.

Cache Miss Ratio The percentage of cache access attempts out of the total cache access attempts whenthe required data was not available in the cache. The value format is a 4-byte float.

Cache Misses The total number of cache access attempts when the required data was not available in thecache since the service was started. The value format is a 4-byte integer.

Cache Requests The total number of cache requests that were processed since the service was started.The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Sender Filter Agent attributesThis group of data provides details about MS Exchange Sender Filter statistics activity.


Messaged Evaluated by Sender Filter The total number of messages evaluated by the Sender Filteragent.

Messaged Evaluated by Sender Filter/Sec The total number of messages evaluated by the Sender Filteragent per second.

Messaged Filtered by Sender Filter The total number of messages filtered by the Sender Filter agent.

Messaged Filtered by Sender Filter/Sec The total number of messages filtered by the Sender Filter agentper second.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Sender ID Agent attributesThis group of data provides details about the MS Exchange Sender ID Agent.


DNS Queries The total number of DNS Queries performed by Sender ID Agent since the server wasstarted. The value format is a 4-byte integer.

DNS Queries/Sec The total of DNS Queries per second performed by Sender ID Agent since the serverwas started. The value format is a 4-byte integer.

DNS Queries/Sec (Superseded) The total of DNS Queries per second performed by Sender ID Agentsince the server was started. The value format is a 4-byte integer.

Messages That Bypassed Validation The total number of messages that bypass validation by the SenderId agent. The value format is a 4-byte integer.

Messages That Bypassed Validation/Sec The number of messages that bypass validation per second. Thevalue format is a 4-byte float.

Messages Validated The total number of messages that are validated by the Sender Id agent. The valueformat is a 4-byte integer.

Messages Validated/Sec The number of messages that are validated per second. The value format is a4-byte float.



MM Month

DD Day

YY Year

HH Hour


mm Minute

SS Second

MS Exchange Server attributesThe MS Exchange Server attribute group describes the status of the server.

Application Percent Free Space The percent of free space available on the logical drive where theExchange Server application is installed. The agent will use the Exchange Home directory to determinethe root directory for the Exchange Application. The agent will then determine the size of the disk andamount of free space from performance objects to determine the free space available to the ExchangeApplication. The value format is a decimal.

Client Access Role This server is configured to processes client access. The Client Access server rolesupports Outlook 2007 and earlier versions, Outlook Web Access, and Exchange ActiveSync in addition tothe Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4 rev1 (IMAP4)protocols.

The Client Access server role also makes it possible to use Exchange 2007 features such as the offlineaddress book, the Autodiscover service, and the Availability service. You must have the Client Accessserver role installed in every Exchange 2007 organization. The Client Access server role handlescommunications between clients and Microsoft Exchange. Although Outlook communicates directly withthe Mailbox server, it uses the Client Access server role to connect to Exchange mailboxes when you areusing Outlook Anywhere (formerly known as RPC over HTTP) and for services such as the Autodiscoverservice and the Availability service. The Client Access server role also enables users to use such UnifiedMessaging features as Play on Phone.

The value format is an alphanumeric string with a maximum of 3 characters. This attribute is notavailable for Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003, and will return a valueof No for these servers. The following values are possible:


Yes Y

No N

Exchange Server FQDN The fully qualified domain name (FQDN) of the Exchange Server. The valueformat is an alphanumeric string with a maximum of 600 characters.

Edge Transport Role This is an Edge Transport Server. Edge Transport servers are deployed in yourorganization's perimeter network and handle all Internet-facing mail flow, provide protection againstspam, and provide secure message paths between business partners. The value format is an alphanumericstring with a maximum of 3 characters. This attribute is not available for Microsoft Exchange Server 2000or Microsoft Exchange Server 2003, and will return a value of No for these servers. The following valuesare possible:


Yes Y

No N

Hub Transport Role The Hub Transport role is responsible for all internal mail flow. This attribute is notavailable for Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003, and will return a valueof No for these servers. The value format is an alphanumeric string with a maximum of 3 characters. Thefollowing values are possible:



Yes Y

No N

Information Store Status The Status of Exchange Information Store service. The value format is a 4-byteinteger. The following values are possible:


Unknown 0

Stopped 1

Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7

Log Percent Free Space Reports the percent free space of log data space between the current sample andprevious sample. The agent will obtain the names and location of the Exchange Server Log files. Theagent will then determine the free space available to each Log file. The information returned will then beaggregated by Exchange Server Storage Group name in order to determine the total size of all log fileswithin the Storage Group and the Total free space available to that Storage Group. The Total Free Spacemust then be divided by the Total Logical Disk Size and that result multiplied by 100 to arrive at theTotal Percent Free Space available. The value format is a decimal.

Note: Configure mailbox role to display Log Percent Free Space values. If mailbox role is not available onExchange Server 2007 or if the agent is configured on Exchange Server 2003 or 2000, the value is 0 orundefined.

Mailbox Server Role This is a Mailbox Server. The Exchange Server 2007 Mailbox server role hosts bothmailbox and public folder databases, and provides calendar access for users and messaging recordsmanagement (MRM). The Mailbox server role is required if you plan to host user mailboxes, publicfolders, or both, on an Exchange 2007 server. However, if you want to implement all the features andfunctionality found in Exchange 2007, you will also have to install each of the other server roles. Thisattribute is not available for Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003, and willreturn a value of No for these servers. The value format is an alphanumeric string with a maximum of 3characters. The following values are possible:


Yes Y

No N

MTA Status The Status of Exchange Mail Transfer Agent service. The value format is a 4-byte integer.This attribute is not available for Microsoft Exchange Server 2007, and will return a value of 0 for thisserver. The following values are possible:


Unknown 0

Stopped 1



Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7

Routing Engine Status The Status of Exchange Routing Engine service. The value format is a 4-byteinteger. This attribute is not available for Microsoft Exchange Server 2007, and will return a value of 0 forthis server. The following values are possible:


Unknown 0

Stopped 1

Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7

Server Status The status of the MS Exchange server. The value format is a 4-byte integer. The followingvalues are possible:


Up 1

Down 0

The tables below identify the default Windows services that must be running for the Server Statusattribute to return an Up or Down state. These are the default Windows services unless they areconfigured through the agent configuration.

Note: The default Windows services for Exchange Server 2007 and 2010 are same.

Services in Microsoft Exchange Server 2003

Service name Description

MSExchangeIS Exchange Information Store service

MSExchangeMTA Message Transfer Agent service

RESvc Exchange Routing Engine service

MSExchangeSA Exchange System Attendant service

SMTPSVC Simple Mail Transfer Protocol service

W3SVC World Wide Web Publishing service


Services in Microsoft Exchange Server 2007 for the Client Access role


MSExchangeADTopology Active Directory Topology service

MSExchangeFDS Exchange File Distribution service

MSExchangeServiceHost Exchange Service Host service

Services in Microsoft Exchange Server 2007 for the Edge Transport role


MSExchangeTransport Exchange Transport service

MSExchangeAntispamUpdate Exchange Anti-spam Update service

ADAM MSExchange Exchange ADAM service

EdgeCredentialSvc Exchange Credential service

Services in Microsoft Exchange Server 2007 for the Mailbox Server role



MSExchangeMailboxAssistants Exchange Mailbox Assistants service

MSExchangeMailSubmission Exchange Mail Submission service

MSExchangeRepl Exchange Replication service

MSExchangeSearch Exchange Search Indexer service


W3Svc World Wide Web Publishing service

Services in Microsoft Exchange Server 2007 for the Unified Messaging role



MSSpeechService Exchange Speech Engine service

MSExchangeUM Exchange Unified Messaging service


Services in Microsoft Exchange Server 2007 for the Hub Transport role




MSExchangeEdgeSync Exchange EdgeSync service


MSExchangeTransportLogSearch Exchange Transport Log Search service

Services in Microsoft Exchange Server 2007 installed on single server





Services in Microsoft Exchange Server 2007 installed on single server







MSExchangeMailSubmission Exchange Mail Submission service


MSExchangeSearch Exchange Search Indexer service



W3Svc World Wide Web Publishing service

Services in Microsoft Exchange Server 2013 for the Mailbox role


MSExchangeADTopology Exchange Active Directory Topology service





MSExchangeMonitoring Exchange monitoring service


FMS Filtering Management service

SearchExchangeTracing Exchange Tracing service for Search

Wsbexchange Exchange Server Extension for Windows Server Backupservice

HostControllerService Exchange Search Host Controller service

MSExchangeFastSearch Exchange Fast Search service

MSExchangePOP3BE Exchange POP3 Backend service

MSExchangeSubmission Exchange Mailbox Transport Submission service

MSExchangeDelivery Exchange Mailbox Transport Delivery service

MSExchangeIMAP4BE Exchange IMAP4 Backend service

MSExchangeHM Exchange Health Manager service

MSExchangeDiagnostics Exchange Diagnostic service

MSExchangeThrottling Exchange Throttling service

MSExchangeRPC Exchange RPC Client Access service

MSExchangeMailboxReplication Exchange Mailbox Replication service







MSExchangeIMAP4 Exchange IMAP4 service


MSExchangePOP3 Exchange POP3 service


MSExchangeUMCR Exchange Unified Messaging Call Router service

MSExchangeHM Exchange Health Manager service

MSExchangeFrontEndTransport Exchange Front End Transport service

MSExchangeDiagnostics Exchange Diagnostic service

MSExchangeRPC Exchange RPC Client Access service

Services in Microsoft Exchange Server 2013 for the Unified Messaging role



MSExchangeUM Exchange Unified Messaging service



Services in Microsoft Exchange Server 2013 for the Hub Transport role









Server Version The version of the Exchange Server. The value format is a 4-byte integer. The followingvalues are possible:


Unknown -1

2000 0

2003 1

2007 2

2010 3

2013 4

SMTP Status The Status of SMTP service. This attribute is not available for Microsoft Exchange Server2007, and will return a value of 0 for this server. The value format is a 4-byte integer. The followingvalues are possible:



Unknown 0

Stopped 1

Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7

Sys Attendant Svc Status The Status of Exchange System Attendant service. This attribute is notavailable for Microsoft Exchange Server 2007, and will return a value of 0 for this server. The valueformat is a 4-byte integer. The following values are possible:


Unknown 0

Stopped 1

Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Unified Messaging Role This server is configured in a unified messaging role. The Unified Messagingserver role enables voice mail, email, and fax messages to be stored in a user's mailbox. Users can thenaccess their Exchange 2007 mailbox from a telephone or from a computer. This attribute is not availablefor Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003, and will return a value of No forthese servers. The value format is an alphanumeric string with a maximum of 3 characters. The followingvalues are possible:



Yes Y

No N

WWW Service Status The Status of WWW publishing service. The value format is a 4-byte integer. Thefollowing values are possible:


Unknown 0

Stopped 1

Start Pending 2

Stop Pending 3

Running 4

Continue Pending 5

Paused Pending 6

Paused 7

MS Exchange Services Detail attributesThis group of data provides details about the services that make up the Exchange Server.

Service Name Microsoft Exchange Server service name. The value format is an alphanumeric string witha maximum of 384 characters.

Service State Current service state. The value format is a 4-byte integer. The following values arepossible:


Stopped 0

Start Pending 1

Stop Pending 2

Running 3

Continue Pending 4

Pause Pending 5

Paused 6

Unknown 7

Service Status Current service status. The value format is a 4-byte integer. The following values arepossible:


OK 0

Error 1

Degraded 2

Unknown 3

Pred Fail 4



Starting 5

Stopping 6

Service 7

Service Start Mode Defined start mode for the service. The value format is a 4-byte integer. Thefollowing values are possible:


Automatic 1

Manual 2

Disabled 3

Unknown -1

Delayed 4



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Storage Group Detail attributesThis group of data provides details about the storage groups that make up the Exchange Server.

Note: The attribute group is not available in Microsoft Exchange Server 2010. This attribute group is amulti-instance attribute group.

Storage Group Distinguished Name The distinguished name of the storage group. The value format isan alphanumeric string with a maximum of 3072 characters.

Number of Mailboxes in Storage Group The number of mailboxes in a particular storage group.

Storage Group Name The name assigned to Exchange storage group by system or selected at installation.The value format is an alphanumeric string with a maximum of 384 characters.

Storage Group Percent Free Space The percent of free space available on the logical drive where theExchange Server application is installed. The agent will use the Exchange Home directory to determinethe root directory for the Exchange Application. The agent will then determine the size of the disk andamount of free space from performance objects to determine the free space available to the Exchangestorage group. The value format is a 4-byte integer.


Storage Group Percent Growth Reports the percent growth of the storage group between the currentsample and previous sample. The value format is a decimal.

Storage Group Size The size in megabytes of storage group. The value format is a decimal.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Store Driver attributesThis attribute group places messages from the transport pipeline into the appropriate mailbox.

Note: The following attributes are available only in Exchange Server 2007 and 2010. This attribute groupis a multi-instance attribute group.

Inbound Bytes Delivered The number of bytes delivered.

Inbound Failed Recipients The number of failed deliveries.

Inbound Local Delivery Calls The number of local delivery calls.

Inbound Local Delivery Calls Per Second The local delivery calls per second.

Inbound Message Delivery Attempts The number of attempts for delivering transport mail item.

Inbound Message Delivery Attempts Per Second The number of attempts for delivering transport mailitem per second.

Inbound Number of Delivering Threads The number of threads in delivery.

Inbound Recipients Delivered Recipients delivered.

Inbound Recipients Delivered Per Second The number of inbound recipients delivered per second.

Inbound Rerouted Recipients The number of deliveries rerouted.

Inbound Retried Recipients The number of deliveries retried.

Inbound Succeeded Recipients The number of successful deliveries.

Inbound Total Meeting Failures The number of errors seen when processing meeting messages.

Inbound Total Meeting Messages The total number of meeting messages processed.


Outbound Mapi Events Without Message The number of submitted MAPI events without message item.


Outbound Submitted Mail Items The number of submitted mail items.

Outbound Submitted Mail Items Per Second The number of mail items that are submitted per second.

Outbound Total Recipients The total number of recipients handled.

Store Driver Name The name of the store driver.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Store Driver Database attributesThis attribute group contains attributes that are related to the Exchange store driver database.

Note: This attribute group is available only in Exchange Server 2010 Service Pack 1. This attribute groupis a multi-instance attribute group.

Store Driver Database Instance Name The name of the Microsoft Exchange Store Driver Databaseinstance. The value format is an alphanumeric string with a maximum length of 600 characters.

Delivery Attempts Per Minute Over The Last Five Minutes The average number of attempts to deliverinbound messages by the store driver to Exchange stores in the last 5 minutes. The value format is a4-byte float.

Delivery Failures Per Minute Over The Last Five Minutes The average number of message deliveries bythe store driver that have failed in the last 5 minutes. The value format is a 4-byte float.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric string with a maximumlength of 64 characters.


MM Month


DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Store Driver Server attributesThis attribute group contains attributes that display data for the Exchange store driver in each mailboxserver.

Note: The attribute group is available only in Exchange Server 2010 Service Pack 1. This attribute groupis a multi-instance attribute group.

Store Driver Server Instance Name The name of the Microsoft Exchange Store Driver instance. The valueformat is an alphanumeric string with a maximum length of 600 characters.

Delivery Attempts Per Minute Over The Last Five Minutes The average number of attempts to deliverinbound messages by the store driver to Exchange stores in the last five minutes. The value format is a4-byte float.

Delivery Failures Per Minute Over The Last Five Minutes The average number of message deliveries bythe store driver that have failed in the last five minutes. The value format is a 4-byte float.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Store Interface attributesThis attribute group monitors the interface between the Exchange Information Store service on theMailbox Server and the Hub Transport servers.


Average Latency of RPC Requests The average latency (in milliseconds) of RPC requests that areprocessed by using RPC context handle pools since the exrpc32.dll process was loaded. The value formatis a 4-byte float.



Average Latency of Slow RPC Requests The average latency (in milliseconds) of the RPC requests with aprocessing time of more than 500 ms. The value format is a 4-byte float.

ExRpcConnection Creation Events The number of ExRpcConnection object creation events that haveoccurred since the service was started. The value format is a 4-byte integer.

ExRpcConnection Disposal Events The number of ExRpcConnection object disposal events that haveoccurred since the service was started. The value format is a 4-byte integer.

Open RPC Context Handles The number of RPC context handles that are currently open in all the RPCcontext handle pools. The value format is a 4-byte integer.


Percent of RPC Requests Failed The percentage of RPC requests that have failed. The failed RPCrequests are the requests with error codes and exceptions. The value format is a 4-byte float.

Percent of Slow RPC Requests The percentage of RPC requests with a processing time of more than 500ms. The value format is a 4-byte float.

ROP Requests Outstanding The number of remote operation (ROP) requests that are currently pendingto be processed. The value format is a 4-byte integer.

RPC Bytes Received The total amount of data (in bytes) that has been received from the server since theexrpc32.dll process was loaded. The value format is a 4-byte integer. The "Value_Exceed_Maximum"enumeration value is displayed on the Tivoli Enterprise Portal when the amount of received data isgreater than 2147483647 bytes.

RPC Latency Average The average latency (in milliseconds) of RPC requests since the exrpc32.dll processwas loaded. The value format is a 4-byte float.

RPC Latency Total The total time (in seconds) that has been spent to process RPC calls since theexrpc32.dll process was loaded. The value format is a 4-byte integer.

RPC Requests Failed with Exception The total number of RPC requests that have failed because ofexceptions since the exrpc32.dll process was loaded. The value format is a 4-byte integer.

RPC Requests Outstanding The number of RPC requests that are currently pending to be processed. Thevalue format is a 4-byte integer.

RPC Requests Sent The total number of RPC requests that have been initiated for processing since theexrpc32.dll process was loaded. The value format is a 4-byte integer.

RPC Requests Sent/Sec The number of RPC requests that are currently initiated for processing persecond. The value format is a 4-byte float.

RPC Requests Succeeded The number of RPC requests that have succeeded since the exrpc32.dll processwas loaded. The value format is a 4-byte integer.

RPC Slow Requests The total number of RPC requests that have taken more than 500 ms for processingsince the exrpc32.dll process was loaded. The value format is a 4-byte integer.



Store Interface Instance Name The name of the store interface instance. The value format is analphanumeric string with a maximum of 600 characters.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Latency of RPC Slow Requests The total processing time (in seconds) for the RPC calls with morethan 500 ms processing time. The value format is a 4-byte integer.

MS Exchange SubmissionThis attribute group monitors the activity of message submissions from the Mailbox server to the HubTransport server.

Note: This attribute group is available in Exchange Server 2013. This attribute group is a single instanceattribute group.

Failed Submissions The total number of message submissions that were failed since the service wasstarted. The value format is a 4-byte integer.

Failed Submissions/Sec The number of message submissions that failed per second. The value format isa 4-byte integer.

Pending Submissions The number of messages that are waiting for submission. The value format is a4-byte integer.

Percent of Permanent Failed Submissions in Last 5 Minutes The percentage of message submissionsthat permanently failed in the last 5 minutes. The value format is a 4-byte float.

Successful Submissions The total number of messages that were submitted since the service was started.The value format is a 4-byte integer.

Successful Submissions/Sec The number of messages that are submitted per second. The value format isa 4-byte integer.


Temporary Submission Failures The number of message submissions that temporarily failed. The valueformat is a 4-byte integer.

Temporary Submission Failures/Sec The number of message submissions per second that temporarilyfailed. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Submission DSN

This attribute group monitors the delivery status notifications (DSN) for messages that are sent to theMailbox Transport Submission service on the Exchange Server. DSN messages provide non-deliveryreports and other status messages to message senders.


Delay DSNs The total number of delay DSN messages that were generated since the service was started.A delay DSN message is generated after each message delivery failure. The value format is a 4-byteinteger.

Delivered DSNs The total number of DSN messages that were generated for the completed messagedeliveries since the service was started. The value format is a 4-byte integer.

DSN Type The type of DSN. The value format is an alphanumeric string with a maximum of 600characters.

Expanded DSNs The total number of expanded DSN messages that were generated since the service wasstarted. The value format is a 4-byte integer.

Failure DSNs in Last Hour that can be Alerted The number of failure DSN messages that can be alertedwithin the last hour because of message delivery failures. The value format is a 4-byte integer.

Failure DSNs Total The total number of failure DSN messages that were generated because of messagedelivery failures since the service was started. The value format is a 4-byte integer.

Last Hour Delayed DSNs The number of delay DSN messages that are generated within the last hour.The value format is a 4-byte integer.

Last Hour Failure DSNs The number of failure DSN messages that are generated within the last hourbecause of message delivery failures. The value format is a 4-byte integer.

NDRs Generated for Catch-All Recipients The total number of non-delivery reports that were generatedbecause of non-delivery of messages to the catch-all mailbox recipients since the service was started. Thevalue format is a 4-byte integer.

Relay DSNs The total number of relay DSN messages that were generated since the service was started.The value format is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Text Messaging attributesThis attribute group monitors the text messaging activity of the Exchange Server.


Average Text Message Delivery Latency (milliseconds) The average time (in milliseconds) to send therecent 1024 text messages that have been processed by the Text Messaging Transport agent. The valueformat is a 4-byte integer.


Text Messages Pending Delivery The total number of text messages that are currently being processedby the Text Messaging Transport agent. The value format is a 4-byte integer.

Text messages Sent via SMTP/sec The number of text messages that have been sent by the HubTransport Server per second via SMTP. The value format is a 4-byte integer.

Text Messages Sent/sec The number of text messages that have been sent by the Hub Transport Serverper second. The value format is a 4-byte integer.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Messages Sent via SMTP The total number of text messages that have been sent via SMTP sincethe service was started. The value format is a 4-byte integer.

Total Text Messages Sent The total number of text messages that have been sent since the service wasstarted. The value format is a 4-byte integer.

MS Exchange Throttling attributesThis attribute group contains attributes that are related to the client throttling policies.



Throttling Instance Name The name of the Microsoft Exchange Throttling instance. The value format isan alphanumeric string with a maximum length of 600 characters.

Active PowerShell Runspaces The number of currently active Windows PowerShell runspaces that havebeen hosted by the Exchange Server. The value format is a 4-byte integer.

Active PowerShell Runspaces/Sec The number of currently active Windows PowerShell runspaces thatare hosted by the Exchange Server per second. The value format is a 4-byte float.

Average Task Wait Time The average amount of time (in milliseconds) that was spent between addingand removing a task from the task queue. The value format is a 4-byte integer.

Note: This attribute is available only in Exchange Server 2010 Service Pack 1.

Average Thread Sleep Time The average amount of time (in milliseconds) for which the threads are idle.The value format is a 4-byte integer.

Current Delayed Tasks The number of tasks that are currently delayed because of throttling. The valueformat is a 4-byte integer.


Delay Time Threshold The amount of time (in milliseconds) a single operation must be delayed in 1minute before the value in the Users Delayed X Milliseconds attribute is incremented. The value format isa 4-byte integer.


Exchange Executing Cmdlets The number of Exchange cmdlets that are currently processed. The valueformat is a 4-byte integer.

Exchange Executing Cmdlets/Sec The number of Exchange cmdlets that are currently processed persecond. The value format is a 4-byte float.

Max Delay Per Minute The maximum amount of time for which a caller was delayed in the current1-minute window because of throttling. The value format is a 4-byte float.


Max Delayed Tasks The maximum number of tasks that have been delayed since the service was started.The value format is a 4-byte integer.


Max Effective Time In Active Directory Per Minute The maximum percentage of time that is spent onprocessing LDAP requests in the current 1-minute window. The value format is a 4-byte float.


Max Effective Time In Address Book Per Minute The maximum percentage of time that is spent onprocessing AddressBook requests in the current 1-minute window. The value format is a 4-byte float.



Max Effective Time In CAS Per Minute The maximum percentage of time that was spent to process theClient Access server code in the last 1 minute. The value format is a 4-byte float.


Max Effective Time In MailboxRPC Per Minute The maximum percentage of time that is spent onprocessing MailboxRPC requests in the current 1-minute window. The value format is a 4-byte float.


Max Task Queue Length The maximum length of the task queue. The value format is a 4-byte integer.


Max Worker Thread Count The maximum number of worker threads to which work items are assigned.The value format is a 4-byte integer.


New Task Rejections The total number of new tasks that are rejected. The value format is a 4-byteinteger.


New Task Rejections/Sec The current number of new tasks that are rejected per second. The valueformat is a 4-byte float.


New Tasks Submitted/Sec The number of new tasks that are submitted per second. The value format is a4-byte float.


Noninteractive Cutoff Percent The cut-off percentage at which noninteractive client connections to themailbox server are interrupted. The value format is a 4-byte float.


OverBudget Threshold The number of times a user must go over budget in 1 minute to increment theUsers X Times OverBudget attribute. The value format is a 4-byte integer.


Task Failures/Sec The total number of tasks that have failed per second. The value format is a 4-bytefloat.


Task Queue Length The total length of the task queue. The value format is a 4-byte integer.



Task Timeouts Per Minute The total number of tasks that have timed out in the current 1-minutewindow. The value format is a 4-byte float.


Total New Tasks The total number of new tasks that are submitted for processing. The value format is a4-byte integer.


Total Task Failures The total number of tasks that have failed. The value format is a 4-byte integer.


Total Unique Budgets The total number of unique budgets that are processed in the current 1-minutewindow. The value format is a 4-byte integer.


Unique Budgets OverBudget The number of unique budgets that have exceeded the OverBudgetthreshold in the current 1-minute window. The value format is a 4-byte integer.


Users Delayed X Milliseconds The number of users that have to wait for X or more milliseconds in 1minute. The value format is a 4-byte integer.


Users X Times OverBudget The total number of users for which the requests are rejected more than Xtimes in the current 1-minute window. The value format is a 4-byte integer.


Worker Thread Count The total number of worker threads to which work items are assigned. The valueformat is a 4-byte integer.




MM Month

DD Day

YY Year


HH Hour

mm Minute

SS Second

MS Exchange Transport Database attributesThis group of data monitors the activity of the MS Exchange Transport Database.


Transport Database Instance Name The name of the Microsoft Exchange Transport Database instance.The format of the value is an alphanumeric string with a maximum length of 600 characters.

Column cache load total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Column cache loaded bytes/sec The counter that is used to troubleshoot a complex issue that is relatedto the Exchange Server Extension (ESE). This information is required by the Microsoft Product SupportServices.

Column cache loaded columns total The counter that is used to troubleshoot a complex issue that isrelated to the Exchange Server Extension (ESE). This information is required by the Microsoft ProductSupport Services.

Column cache loaded columns/sec The counter that is used to troubleshoot a complex issue that isrelated to the Exchange Server Extension (ESE). This information is required by the Microsoft ProductSupport Services.

Column cache loaded bytes total The counter that is used to troubleshoot a complex issue that is relatedto the Exchange Server Extension (ESE). This information is required by the Microsoft Product SupportServices.

Column cache save total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Column cache save/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Column cache saved columns total The counter that is used to troubleshoot a complex issue that isrelated to the Exchange Server Extension (ESE). This information is required by the Microsoft ProductSupport Services.

Column cache saved columns/sec The counter that is used to troubleshoot a complex issue that is relatedto the Exchange Server Extension (ESE). This information is required by the Microsoft Product SupportServices.

DataRow deletes total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow deletes/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow loads total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.


DataRow loads/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow moves total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow moves/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow seeks total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow seeks/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow updates total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

DataRow updates/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

MailItem load/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

MailItem load total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

MailItem new total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

MailItem new/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream bytes read total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream bytes read/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream bytes written total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream bytes written/sec The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream read total The counter that is used to troubleshoot a complex issue that is related to the ExchangeServer Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream read/sec The counter that is used to troubleshoot a complex issue that is related to the ExchangeServer Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream writes total The counter that is used to troubleshoot a complex issue that is related to theExchange Server Extension (ESE). This information is required by the Microsoft Product Support Services.

Stream writes/sec The counter that is used to troubleshoot a complex issue that is related to the ExchangeServer Extension (ESE). This information is required by the Microsoft Product Support Services.


System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric with a maximum lengthof 64 characters.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Transport Dumpster attributesThis group of data represents Exchange data about the transport dumpster.

Note: The attribute group is available only in Exchange Server 2007 and 2010. This attribute group is asingle instance attribute group.

Dumpster Deletes/sec The rate at which items are deleted from the transport dumpster. The format ofthe value is a 4-byte float.

Dumpster Deletes Quota The total number of messages that the transport dumpster deletes when thequota exceeds the specified limit. The format of the value is a 4-byte integer.

Note: This attribute is not available on Microsoft Exchange Server 2007.

Dumpster Inserts/sec The rate at which items are inserted into the transport dumpster. The format of thevalue is a 4-byte float.

Dumpster Item Count The total number of mail items that are currently in the transport dumpster. Theformat of the value is a 4-byte integer.

Dumpster Mailbox Database Count The current number of associated mailbox databases for messagesthat are stored in the transport dumpster. The format of the value is a 4-byte integer.

Note: This attribute is not available on Microsoft Exchange Server 2007.

Dumpster Size The total size (in bytes) of mail items that are currently in the transport dumpster on theserver. The format of the value is a 4-byte integer.

Redelivery Count The number of mail items that were re-delivered from the transport dumpster on theserver. The format of the value is a 4-byte integer.



MM Month


DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Transport Queues attributesThis group of data provides details about Exchange Server Transport Queues.


Active Remote Delivery Queue Length The number of messages queued for remote delivery. The valueformat is a 4-byte integer.


Active Mailbox Delivery Queue Length The number of messages queued for delivery to an activemailbox. The value format is a 4-byte integer.

Active Non-SMTP Delivery Queue Length The number of messages queued for delivery to a Non-SMTPtransport. The value format is a 4-byte integer.

Aggregate Delivery Queue Length The number of messages queued for aggregate delivery. The valueformat is a 4-byte integer.


Items Completed Delivery/Sec The number of times that messages completed delivery since the serverwas started per second. The value format is a decimal.

Items Completed Delivery Total The total number of messages that completed delivery since the serverwas started. The value format is a 4-byte integer.

Items Deleted by Admin Total The total number of items deleted by Admin since the server was started.The value format is a 4-byte integer.

Items Queued For Delivery/Sec The number of times that messages are queued for delivery since theserver was started per second. The value format is a decimal.

Items Queued For Delivery Expired Total The total number of items queued for delivery that haveexpired since the server was started. The value format is a 4-byte integer.

Items Queued For Delivery Total The total number of messages queued for delivery since the server wasstarted. The value format is a 4-byte integer.

Items Resubmitted Total The total number of items resubmitted since the server was started. The valueformat is a 4-byte integer.

Largest Delivery Queue Length The number of items in the largest delivery queue. The value format is a4-byte integer.


Messages Completed Delivery/Sec The number of times that messages completed delivery since theserver was started per second. The value format is a decimal.

Messages Completed Delivery Total The total number of messages that completed delivery since theserver was started. The value format is a 4-byte integer.

Messages Queued For Delivery The number of messages queued to be delivered when sample wastaken. The value format is a 4-byte integer.

Messages Queued For Delivery/Sec The number of times that messages are queued for delivery since theserver was started per second. The value format is a decimal.

Messages Queued For Delivery Total The total number of messages that were queued for delivery sinceserver started. The value format is a 4-byte integer.

Messages Submitted/Sec The number of times that messages are being submitted per second since theserver was started. The value format is a decimal.

Messages Submitted Total The total number of messages submitted since the server was started. Thevalue format is a 4-byte integer.

Poison Queue Length The number of messages in the poison message queue. The value format is a4-byte integer.

Retry Mailbox Delivery Queue Length The number of messages queued for retry delivery to activemailbox since the server was started. The value format is a 4-byte integer.

Retry Non-SMTP Delivery Queue Length The number of messages queued for delivery retry to aNon-SMTP transport since the server was started. The value format is a 4-byte integer.

Retry Remote Delivery Queue Length The number of messages queued for delivery retry since theserver was started. The value format is a 4-byte integer.


Submission Queue Items Expired Total The total number of items in submission queue that haveexpired since the server was started. The value format is a 4-byte integer.

Submission Queue Length The number of items in the submission queue when sample was taken. Thevalue format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute


SS Second

Transport Queue Instance Name The Exchange Server Instance name where Transport Queue activity isreported from. The value format is an alphanumeric string with a maximum of 384 characters.

Unreachable Queue Length The number of messages in Unreachable Queue when sample was taken.The value format is a 4-byte integer.

MS Exchange Transport Rules attributesThis attribute group reports Transport rules activity performed by the Exchange Server.


Messages Evaluated The total number of messages evaluated by Exchange Server Transport Rules sincethe server was started. The value format is a 4-byte integer.

Messages Evaluated/Sec The number of times that messages are evaluated by Exchange Server TransportRules per second since the server was started. The value format is a decimal.

Messages Processed The total number of messages passed through Exchange Server Transport Rulessince the server was started. The value format is a 4-byte integer.

Messages Processed/Sec The number of times that messages are processed by Exchange Server TransportRules per second since the server was started. The value format is a decimal.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Transport Rule Name Transport Rule Name that is confirmed by the Exchange Administrator. The valueformat is an alphanumeric string with a maximum of 384 characters.

MS Exchange Transport Shadow Redundancy attributesThis group of data monitors the activity of the Exchange Transport Shadow Redundancy.

Note: The attribute group is available in the Exchange Server 2010, or later. This attribute group is amulti-instance attribute group.

Current Messages Acknowledged before Relay Completed The current number of messages that arereceived and acknowledged before the relay is complete. The value format is a 4-byte integer.


Redundant Message Discard Events The current number of discarded messages that are in queue for allshadow servers. The value format is a 4-byte integer.

Redundant Message Discard Events Expired The total number of discarded messages that were in queueand are expired. The value format is a 4-byte integer.

Transport Shadow Redundancy Instance Name The name of the Microsoft Exchange Transport ShadowRedundancy instance. The value format is an alphanumeric string with a maximum of 332 characters.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is an alphanumeric with a maximum of64 characters.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Transport SMTP Availability attributesThis attribute group contains attributes that are related to the Exchange Transport SMTP Availability.


Transport SMTP Availability Instance Name The name of the Microsoft Exchange Transport SMTPinstance. The value format is an alphanumeric string with a maximum length of 600 characters.

% Activity The combination of % Availability and Total Connections attribute values that are used forsending alerts. The value format is a 4-byte float.

% Availability The ratio of successful connections to the total valid connections in the sliding window.The value format is a 4-byte float.

% Failures Due To Active Directory Down The current percentage of valid connections in the slidingwindow that have failed because the Active Directory is unavailable. The value format is a 4-byte float.

% Failures Due To Back Pressure The current percentage of valid connections in the sliding window thathave failed because of back pressure. The value format is a 4-byte float.

% Failures Due To I/O Exceptions The current percentage of valid connections in the sliding windowthat have failed because of input/output exceptions. The value format is a 4-byte float.

% Failures Due To Max Inbound Connection Limit The current percentage of valid connections in thesliding window that have failed because the maximum inbound connection limit was exceeded. Thevalue format is a 4-byte float.

% Failures Due To TLS Errors The current percentage of valid connections in the sliding window thathave failed because of Transport Layer Security (TLS) errors. The value format is a 4-byte float.


Failures Due To Maximum Local Loop Count The number of message deliveries that have failed becausethe maximum number of local loop count was exceeded since the service was started. The value format isa 4-byte integer.


Total Connections The total number of valid connections in the sliding window since the server wasstarted. The value format is a 4-byte integer.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric string with a maximumof 64 characters.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Transport SmtpReceive attributesThis group of data provides details about inbound message traffic.


Average bytes/connection (MB) The average number of bytes (in MB) that are received per connection.The value format is a 4-byte float.

Average bytes/message (MB) The average number of message bytes (in MB) that are received perinbound message. The value format is a 4-byte float.

Average messages/connection The average number of messages that are received per connection. Thevalue format is a 4-byte float.

Average Recipients Message The average messages received since SMTP initialization. This value reflectsthe number of messages generated for inbound and outbound recipients.

Bytes Received/Sec The number of bytes received by SMTP Receive Service per second since the serverwas started. The value format is a decimal.

Bytes Received Total Total bytes received by SMTP Receive Service since the server was started. Thevalue format is a 4-byte integer.

Connections Current The number of current connections to SMTP Receive Service since the server wasstarted. The value format is a 4-byte integer.

Connections Total The total number of connections to SMTP Receive Service since the server was started.The value format is a 4-byte integer.


Disconnections By Agents The number of inbound connections that are dropped by agent actions. Thevalue format is a 4-byte integer.

Disconnections by Agents/Sec The number of inbound connections that are dropped by agent actionsper second. The value format is a 4-byte float.

Message Bytes Received Total The number of message bytes received by SMTP Receive Service since theserver was started. The value format is a 4-byte integer.

Message Bytes Received/Sec The number of message bytes received by SMTP Receive Service per secondsince the server was started. The value format is a decimal.

Messages Received/Sec The number of messages received by SMTP Receive Service per second since theserver was started. The value format is a decimal.

Messages Received Total The total number of messages received by SMTP Receive Service since theserver was started. The value format is a 4-byte integer.

Messages Refused For Size The total number messages refused for size by SMTP Receive Service sincethe server was started. The value format is a 4-byte integer.

Recipients accepted Total The number of recipients accepted. The value format is a 4-byte integer.

SMTP Receive Instance Name The network name of the source of this information. The value format isan alphanumeric string with a maximum of 64 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange Transport SmtpSend attributesThis group of data provides details about SMTP Send Service.


Average bytes/connection The average number of bytes that are sent by the SmtpSend connector perconnection. The value format is a 4-byte float.

Average message bytes/message The average number of bytes that are sent by the SmtpSend connectorper message. The value format is a 4-byte float.


Average messages/connection The average number of messages that are sent by the SmtpSend connectorper connection. The value format is a 4-byte float.

Average Recipients Message The average messages sent since SMTP initialization. This value reflects thenumber of messages generated for inbound and outbound recipients. The value format is a 4-byte integer.

Bytes Sent/Sec The number of times that the bytes are sent by SMTP Send Service per second since theserver was started. The value format is a decimal.

Bytes Sent Total Total bytes sent by SMTP Send Service since the server was started. The value format isa 4-byte integer.

Connections Created/Sec The number of outbound connections that are established by the SmtpSendconnector per second. The value format is a 4-byte float.

Connections Current The number of current connections to SMTP Send Service since the server wasstarted. The value format is a 4-byte integer.

Connections Total The total number of connections to SMTP Send Service since server last started. Thevalue format is a 4-byte integer.

Message Bytes Sent The number of message bytes sent by SMTP Send Service since the server wasstarted. The value format is a 4-byte integer.

Message Bytes Sent/Sec The number of times that the message bytes are sent by SMTP Send Service persecond since the server was started. The value format is a decimal.

Messages Sent/Sec The number of times that the messages are sent by SMTP Send service per secondsince the server was started. The value format is a decimal.

Messages Sent Total The total number of messages sent by SMTP Send Service since the server wasstarted. The value format is a 4-byte integer.

Recipients sent The number of recipients sent by the SmtpSend connector. The value format is a 4-bytefloat.

SMTP Send Instance Name The network name of the source of this information. The value format is analphanumeric string with a maximum of 64 characters.

System Name The key for the table view in the format hostname: EX. This character string provides aunique identifier for each server across an enterprise. The value is alphanumeric with a maximum of 64characters..


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second


MS Exchange UM Auto Attendant attributesThis attribute group monitors the activities of the Unified Messaging (UM) auto attendants.


Auto Attendant Name The name of the UM auto attendant. The value format is an alphanumeric stringwith a maximum of 384 characters.

Percentage of Successful Calls The percentage of total calls that have been answered by the UM autoattendant. The value format is a 4-byte integer.

Average Call Time The average call duration with the UM auto attendant. The value format is a 4-byteinteger.

Average Recent Call Time The average time (in seconds) of the last 50 calls that have been answered bythe UM auto attendant. The value format is a 4-byte integer.

Business Hours Calls The total number of calls that have been answered by the UM auto attendantduring business hours since the service was started. The value format is a 4-byte integer.

Calls with Speech Input The total number of UM auto attendant calls for which callers have providedspeech inputs since the service was started. The value format is a 4-byte integer.

Calls with Spoken Name The total number of UM auto attendant calls for which callers have spokentheir names since the service was started. The value format is a 4-byte integer.

Directory Accessed The number of times the UM auto attendant has accessed the directory since theservice was started. The value format is a 4-byte integer.

Directory Accessed by Dial by Name The total number of times the subscriber has accessed the directoryby using the Dial by Name feature since the service was started. The value format is a 4-byte integer.

Directory Accessed by Extension The total number of times the subscriber has accessed the directory byspecifying the extension number since the service was started. The value format is a 4-byte integer.

Directory Accessed by Spoken Name The total number of times the subscriber has accessed the directoryby providing the recipient name verbally since the service was started. The value format is a 4-byteinteger.

Directory Accessed Successfully using Dial by Name The total number of times the caller has accessedthe directory by using the Dial by Name feature since the service was started. The value format is a4-byte integer. This attribute value is incremented only when the caller connects with the user who isspecified by using the Dial by Name feature after accessing the directory.

Directory Accessed Successfully by Spoken Name The total number of times the caller has accessed thedirectory by providing the recipient name verbally since the service was started. The value format is a4-byte integer. This attribute value is incremented only when the caller connects with the recipient afteraccessing the directory.

Disconnected Without Input The total number of calls that have been dropped because callers did notprovide inputs after being prompted by the UM auto attendant since the service was started. The valueformat is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Calls The total number of calls that have been answered by the UM auto attendant since the servicewas started. The value format is a 4-byte integer.

Transferred Count The total number of calls that have been transferred by the UM auto attendant sincethe service was started. The value format is a 4-byte integer. This attribute value does not include callsthat are transferred by the operator.

MS Exchange UM Availability attributesThis attribute group monitors the availability of the Unified Messaging system.


Average Hub Transport Access Failures Percentage The percentage of attempts that have failed to accessthe Hub Transport server since the service was started. The value format is a 4-byte integer.

Note: This attribute is available only in Exchange Server 2010 SP1.

Failed Mailbox Connection Attempts Percentage The percentage of attempts that failed to connect to theMailbox server. The value format is a 4-byte integer.


Directory Access Failures The total number of attempts that have failed to access the Active Directorysince the service was started. The value format is a 4-byte integer.

Hub Transport Access Completed The total number of times the Hub Transport server has been accessedsince the service was started. The value format is a 4-byte integer.

Note: This attribute is available only in Exchange Server 2007.

Hub Transport Access Failures The total number of attempts that have failed to access Hub Transportservers since the service was started. The value format is a 4-byte integer. This attribute value isincremented if all the Hub Transport servers are unavailable.


Mailbox Server Access Failures The total number of attempts that have failed to access the Mailboxserver since the service was started. The value format is a 4-byte integer.



Percentage of Messages Successfully Processed Over the Last Hour The percentage of messages thathave been processed by the Microsoft Exchange Unified Messaging service in the last hour. The valueformat is a 4-byte integer.


Retrieved System Name The total number of times the name of a user has been retrieved since theservice was started. The value format is a 4-byte integer.


Text to Speech Performed The total number of times the Text-to-Speech feature has been used togenerate the audio output of the subscriber name since the service was started. The value format is a4-byte integer.


MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Worker Process Call Count The total number of calls that have been processed by the UM workerprocess since the service was started. The value format is a 4-byte integer.

Worker Process Recycled The total number of times a new UM worker process has been recycled sincethe service was started. The value format is a 4-byte integer.

MS Exchange UM Call Answer attributesThis attribute group monitors the call answering activity of the Unified Messaging system.


Average Greeting Size The average size (in seconds) of recorded greetings that have been retrieved bythe Unified Messaging Server. The value format is a 4-byte integer.

Average Recent Voice Message Size The average size (in seconds) of the last 50 voice messages that havebeen received for subscribers. The value format is a 4-byte integer.

Average Voice Message Size The average size (in seconds) of the voice messages that have been receivedfor subscribers. The value format is a 4-byte integer.

Call Answering Calls The total number of diverted calls that have been answered on behalf ofsubscribers since the service was started. The value format is a 4-byte integer.


Call Answering Missed Calls The total number of times a diverted call was dropped without leaving amessage for the caller since the service was started. The value format is a 4-byte integer.

Call Answering Voice Messages The total number of voice messages that have been submitted fordelivery as a result of answering the calls on behalf of subscribers since the service was started. Thevalue format is a 4-byte integer.

Calls Without Personal Greetings The total number of diverted calls without greeting messages thathave been received for subscribers since the service was started. The value format is a 4-byte integer.

Diverted Extension Not Provisioned The total number of received calls for which the specified extensionto divert calls is not the Unified Messaging subscriber extension since the service was started. The valueformat is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

MS Exchange UM Enabled User Details attributesThis attribute group monitors details of users who are enabled for Unified Messaging. This attributegroup is a multi-instance attribute group.

Note: This attribute group is available in Exchange Server 2007 or later.

Dial Plan The name of the dial plan that is associated with the user. The value format is an alphanumericstring with a maximum of 384 characters.

Mailbox Name The name of the user whose mailbox is enabled for Unified Messaging. The value formatis an alphanumeric string with a maximum of 384 characters.



MM Month

DD Day

YY Year

HH Hour

mm Minute


SS Second

UM Mailbox Policy The name of the Unified Messaging mailbox policy that is associated with the user.The value format is an alphanumeric string with a maximum of 384 characters.

MS Exchange UM General attributesThis attribute group monitors the general performance of the Unified Messaging system.


Average Call Duration The average duration (in seconds) of calls since the service was started. The valueformat is a 4-byte integer.

Average MWI Latency The average time (in milliseconds) from the delivery of the voice mail to thereceipt of the confirmation by the Unified Messaging Server. The value format is a 4-byte integer. Theaverage is calculated for the last 50 messages.


Average Recent Call Duration The average duration (in seconds) of the last 50 calls. The value format isa 4-byte integer.

Call Duration Exceeded The total number of calls that have been disconnected because the calls exceededthe maximum call limit that is specified in the Unified Messaging Server since the service was started.The value format is a 4-byte integer. This attribute value contains all types of calls including fax calls.

Calls Disconnected by User Failure The total number of calls that have been disconnected because theinputs provided by users were invalid since the service was started. The value format is a 4-byte integer.

Current Auto Attendant Calls The number of UM auto attendant calls that are currently connected to theUnified Messaging Server since the service was started. The value format is a 4-byte integer.

Current Calls The number of calls that are currently connected to the Unified Messaging Server since theservice was started. The value format is a 4-byte integer.

Current Fax Calls The number of fax calls that are currently connected to the Unified Messaging Serversince the service was started. The value format is a 4-byte integer. Voice calls change to fax calls after afax tone is detected.

Current Subscriber Access Calls The number of subscribers who are currently logged on and areconnected to the Unified Messaging Server since the service was started. The value format is a 4-byteinteger.

Current Unauthenticated Pilot Number Calls The number of voice calls to the pilot number that are notauthenticated since the service was started. The value format is a 4-byte integer.

Current Voice Mail Calls The number of voice mail calls that are currently connected to the UnifiedMessaging Server since the service was started. The value format is a 4-byte integer.


Delayed Calls The total number of calls that have taken more than 2 seconds to connect since the servicewas started. The value format is a 4-byte integer.




MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Calls The total number of calls that have been answered or made since the service was started. Thevalue format is a 4-byte integer. This attribute value does not include transferred calls.

Total Calls per Second The number of calls that have been received in the last second. The value formatis a 4-byte float.

User Response Latency The average response time (in milliseconds) of the system to respond to a userrequest. The value format is a 4-byte integer. The average is calculated for the last 25 calls. This attributeis used for calls that require significant processing.

MS Exchange UM Subscriber Access attributesThis attribute group monitors the Unified Messaging-related activities of subscribers.


Average Recent Sent Voice Message Size The average size (in seconds) of the last 50 voice messages thathave been sent. The value format is a 4-byte integer.

Average Recent Subscriber Call Duration The average duration (in seconds) of the last 50 subscribercalls when subscribers were logged on to the system. The value format is a 4-byte integer.

Average Sent Voice Message Size The average size (in seconds) of the voice messages that have beensent. The value format is a 4-byte integer. This attribute value does not include the size of an attachment.

Average Subscriber Call Duration The average duration (in seconds) for which subscribers have beenlogged on to the system during the call. The call duration is calculated after subscribers log off from thesystem. The value format is a 4-byte integer.

Calendar Accessed The total number of times the subscribers have accessed their calendars by using thetelephone user interface since the service was started. The value format is a 4-byte integer.

Calendar Items Details Requested The total number of times a subscriber has requested additionaldetails for a calendar item since the service was started. The value format is a 4-byte integer.

Calendar Items Heard The total number of calendar items that have been heard by subscribers since theservice was started. The value format is a 4-byte integer.


Calendar Late Attendance The total number of messages that have been sent to inform the meetingorganizer about the late joining of the subscriber since the service was started. The value format is a4-byte integer.

Called Meeting Organizer The total number of times the subscribers have called the meeting organizersince the service was started. The value format is a 4-byte integer.

Contact Items Heard The total number of times the subscribers have listened to the directory detailssince the service was started. The value format is a 4-byte integer.

Contacts Accessed The total number of times the subscribers have accessed the Main Menu Contactsoption by using the telephone user interface since the service was started. The value format is a 4-byteinteger.

Directory Accessed The total number of times the subscribers have accessed the Main Menu Directoryoption by using the telephone user interface since the service was started. The value format is a 4-byteinteger.

Directory Accessed by Dial by Name The total number of times the subscribers have accessed thedirectory by using the Dial by Name feature since the service was started. The value format is a 4-byteinteger.

Directory Accessed by Extension The total number of times the subscribers have accessed the directoryby specifying the extension number since the service was started. The value format is a 4-byte integer.

Email Message Queue Accessed The total number of times the subscribers have accessed their emailmessage queue by using the telephone user interface since the service was started. The value format is a4-byte integer.

Email Messages Deleted The total number of email messages that have been deleted by subscribers sincethe service was started. The value format is a 4-byte integer.

Email Messages Heard The total number of email messages containing audio file attachments that havebeen heard by subscribers since the service was started. The value format is a 4-byte integer.

Forward Messages Sent The total number of messages that have been forwarded by subscribers since theservice was started. The value format is a 4-byte integer.

Launched Calls The total number of subscriber calls that result in outbound calls being placed on holdsince the service was started. The value format is a 4-byte integer.

Meetings Accepted The total number of meeting acceptance messages that have been sent by subscriberssince the service was started. The value format is a 4-byte integer.

Meetings Declined The total number of meeting declined messages that have been sent by subscriberssince the service was started. The value format is a 4-byte integer.

Replied to Organizer The total number of reply messages that have been sent by subscribers to meetingorganizers since the service was started. The value format is a 4-byte integer.

Reply Messages Sent The total number of reply messages that have been sent by subscribers since theservice was started. The value format is a 4-byte integer.

Subscriber Authentication Failures The total number of subscriber authentications that have failed sincethe service was started. The value format is a 4-byte integer. The value of this attribute increments witheach failed authentication. Multiple authentication failures are possible for a single phone call.


Subscriber Logon Failures The total number of subscriber logon attempts that have failed since theservice was started. The value format is a 4-byte integer.

Subscriber Logons The total number of subscribers that have been authenticated since the service wasstarted. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Voice Message Queue Accessed The total number of times the subscribers have accessed their voicemessage queue by using the telephone user interface since the service was started. The value format is a4-byte integer.

Voice Messages Deleted The total number of voice messages that have been deleted by subscribers sincethe service was started. The value format is a 4-byte integer.

Voice Messages Played The total number of voice messages that have been played for subscribers sincethe service was started. The value format is a 4-byte integer. The value of this attribute increments whenthe voice playback starts. The subscriber might not listen to the entire message.

Voice Messages Sent The total number of voice messages that have been sent by subscribers since theservice was started. The value format is a 4-byte integer.

MS Exchange Web Services attributesThis attribute group monitors the activities of the Exchange Web Services (EWS) on the MicrosoftExchange Server.


Average Response Time The average time (in milliseconds) that has elapsed between the beginning andthe end of requests that are sent through the proxy Client Access server. The value format is a 4-bytefloat.

Total Number of IDs Converted The total number of identifiers that have been converted to otheridentifier formats since the service was started. The value format is a 4-byte integer.

IDs Converted/Sec The number of identifiers that are currently converted per second to other identifierformats. The value format is a 4-byte integer.

Number of Current Proxy Calls The number of requests that are currently sent through the proxy ClientAccess server to the other Client Access servers. The value format is a 4-byte integer.


Number of EWS Failovers The total number of times the EWS has failed over to an alternate proxyClient Access server while processing proxy requests since the service was started. The value format is a4-byte integer.

Total Number of Proxy Request Bytes The total number of bytes in requests that have been sent throughthe proxy Client Access server to the other Client Access servers since the service was started. The valueformat is a 4-byte integer.

Total Number of Proxy Response Bytes The total number of bytes in responses that have been generatedfor the requests sent through the proxy Client Access server since the service was started. The valueformat is a 4-byte integer.

Proxy Average Response Time The average time (in milliseconds) that has elapsed between thebeginning and the end of a request that is sent through the proxy Client Access server. The value formatis a 4-byte float.

Number of Proxy Failovers/Sec The average number of proxy failovers that occurred per second. Thevalue format is a 4-byte float.

Number of Proxy Requests/Sec The number of requests that are currently sent per second through theproxy Client Access server. The value format is a 4-byte integer.

Requests/Sec The number of requests that are currently processed per second. The value format is a4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Client Disconnects The total number of times the clients have been disconnected before completionof request processing since the service was started. The value format is a 4-byte integer.


Total Number of Proxy Requests The total number of requests that have been sent through the proxyClient Access server to the other Client Access servers since the service was started. The value format is a4-byte integer.


RPC/HTTP Proxy attributesThis attribute group monitors the activities of the RPC/HTTP Proxy on the Microsoft Exchange Server.



Back-End Connection Attempts/Sec The number of attempts that are made per second by the RPC proxyserver to connect to the back-end server. The value format is a 4-byte integer.

Number of Incoming RPC/HTTP Connections The number of users that are currently connected to thefront-end server by using the RPC/HTTP protocol. The value format is a 4-byte integer.

Current Number of Unique Users The number of unique users that are currently connected to theback-end server by using the RPC over HTTP protocol. The value format is a 4-byte integer.

Failed Back-End Connection Attempts/Sec The number of RPC proxy server attempts per second thatcurrently failed to connect to the back-end server. The value format is a 4-byte integer.

RPC/HTTP Requests/Sec The number of RPC over HTTP requests that are sent per second to theback-end servers. The value format is a 4-byte integer.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Incoming Bandwidth From Back-End Servers The number of bytes that are received per second bythe back-end servers from the RPC proxy server. The value format is a 4-byte float.

Total Outgoing Bandwidth to Back-End Servers The number of bytes that are sent per second by theback-end servers to the RPC proxy server. The value format is a 4-byte float.

SMTP attributesThis group of data represents MS Exchange SMTP activity. Use SMTP attributes to create situations tomonitor a wide range of activities associated with the hosting of an electronic mail server.

Note: The attribute group is available only in Exchange Server 2003. This attribute group is amultiple-instance attribute group.

% Recipients Local The percentage of recipients to be delivered locally since the server was started. Thevalue format is a decimal.

% Recipients Remote The percentage of recipients to be delivered remotely since the server was started.The value format is a decimal.

Avg Recipients/msg Received The average number of recipients per inbound message received since theserver was started. The value format is a decimal.


Avg Recipients/msg Sent The average number of recipients per outbound messages sent since the serverwas started. The value format is a decimal.

Avg Retries/msg Delivered The average number of retries per local delivery since the server was started.The value format is a decimal.

Avg Retries/msg Sent The average number of retries per outbound message sent since the server wasstarted. The value format is a decimal.

Badmailed Messages (Bad Pickup File) The number of malformed pickup messages that are sent to thebadmail folder. The value format is a 4-byte integer.

Badmailed Messages (General Failure) The number of messages that are sent to the badmail folder forreasons not associated with a specific counter. The value format is a 4-byte integer.

Badmailed Messages (Hop Count Exceeded) The number of messages that are sent to the badmail folderbecause it exceeds the maximum hop count. The value format is a 4-byte integer.

Badmailed Messages (NDR of DSN) The number of Delivery Status Notifications sent to the badmailfolder because messages are not delivered. The value format is a 4-byte integer.

Badmailed Messages (No Recipients) The number of messages that are sent to the badmail folderbecause they had no recipients. The value format is a 4-byte integer.

Badmailed Messages (Triggered via Event) The number of messages that are sent to the badmail folderon the request of a server event sink. The value format is a 4-byte integer.

Bytes Received/Sec The number of times that bytes are received per second since the server was started.The value format is a decimal.

Bytes Sent/Sec The number of times that bytes are sent per second since the server was started. Thevalue format is a decimal.

Bytes Total/Sec The number of times that bytes are sent and received per second since the server wasstarted. The value format is a decimal.

Categorizer Queue Length The number of messages on categorizer queue since the server was started.The value format is a 4-byte integer.

Connection Errors/Sec The number of connection errors per second since the server was started. Thevalue format is a decimal.

Current Messages in Local Delivery The number of messages that are being processed by a server eventsink for local delivery. The value format is a 4-byte integer.

Directory Drops/Sec The number of messages placed in a drop directory per second since the server wasstarted. The value format is a decimal.

Directory Drops Total The total number of messages placed in a drop directory since the server wasstarted. The value format is a 4-byte integer.

Directory Pickup Queue Length The number of messages in the directory pickup queue since the serverwas started. The value format is a 4-byte integer. For all versions of Microsoft Exchange environments thefollowing value is returned:



Undefined -1

DNS Queries/Sec The number of DNS lookups per second since the server was started. The value formatis a decimal.

DNS Queries Total The total number of DNS lookups since the server was started. The value format is a4-byte integer.

ETRN Messages/Sec The number of ETRN messages per second since the server was started. The valueformat is a decimal.

ETRN Messages Total The total number of ETRN messages received by the server since the server wasstarted. The value format is a 4-byte integer.

Inbound Connections Current The total number of connections currently inbound since the server wasstarted. The value format is a 4-byte integer.

Inbound Connections Total The total number of inbound connections received since the server wasstarted. The value format is a 4-byte integer.

kBytes Received Total The total number of kilobytes received since the server was started. The valueformat is a 4-byte integer.

kBytes Sent Total The total number of kilobytes sent since the server was started. The value format is a4-byte integer.

kBytes Total The total number of kilobytes sent and received since the server was started. The valueformat is a 4-byte integer.

Local Queue Length The number of messages in the local queue since the server was started. The valueformat is a 4-byte integer.

Local Retry Queue Length The number of messages in the local retry queue since the server was started.The value format is a 4-byte integer.

Message Bytes Received/Sec The number of times that bytes are received in messages per second sincethe server was started. The value format is a decimal.

Message Bytes Sent/Sec The number of times that bytes are sent in messages per second since the serverwas started. The value format is a decimal.

Message Bytes Total/Sec The number of times that bytes are sent and received in messages per secondsince the server was started. The value format is a decimal.

Messages Currently Undeliverable The number of messages that are reported as undeliverable byrouting. The value format is a 4-byte integer.

Messages Received Total The total number of inbound messages accepted since the server was started.The value format is a 4-byte integer.

Messages Delivered/Sec The number of times that messages are delivered to local mailboxes per secondsince the server was started. The value format is a decimal.


Messages Delivered Total The total number of messages delivered to local mailboxes since the serverwas started. The value format is a 4-byte integer.

Message Delivery Retries The total number of local deliveries that were retried since the server wasstarted. The value format is a 4-byte integer.

Message kBytes Received Total The total number of kilobytes received in messages since the server wasstarted. The value format is a 4-byte integer.

Message kBytes Sent Total The total number of kilobytes sent in messages since the server was started.The value format is a 4-byte integer.

Message kBytes Total The total number of kilobytes sent and received in messages since the server wasstarted. The value format is a 4-byte integer.

Messages Pending Routing The total number of messages to be routed that are pending since the serverwas started. The value format is a 4-byte integer.

Messages Received/Sec The number of times that inbound messages are received per second since theserver was started. The value format is a decimal.

Messages Refused for Address Objects The total number of messages refused due to lack of addressobjects since the server was started. The value format is a 4-byte integer.

Messages Refused for Mail Objects The total number of messages refused due to lack of mail objectssince the server was started. The value format is a 4-byte integer.

Messages Refused for Size The total number of messages rejected because they were too big since theserver was started. The value format is a 4-byte integer.

Message Send Retries The total number of outbound message sends that were retried since the serverwas started. The value format is a 4-byte integer.

Messages Sent/Sec The number of times that outbound messages are sent per second since the serverwas started. The value format is a decimal.

Messages Sent Total The total number of outbound messages sent since the server was started. The valueformat is a 4-byte integer.

NDRs Generated The number of non-delivery reports that were generated since the server was started.The value format is a 4-byte integer.

Number of MailFiles Open Number of handles to open mail files since the server was started. The valueformat is a 4-byte integer.

Number of QueueFiles Open Number of handles to open queue files since the server was started. Thevalue format is a 4-byte integer.

Outbound Connections Current The number of connections currently outbound since the server wasstarted. The value format is a 4-byte integer.

Outbound Connections Refused The number of outbound connection attempts refused by remote sitessince the server was started. The value format is a 4-byte integer.

Outbound Connections Total The total number of outbound connections attempted since the server wasstarted. The value format is a 4-byte integer.


Pickup Directory Messages Retrieved/sec The rate at which the messages are retrieved from the mailpickup directory. The value format is a 4-byte float.

Pickup Directory Messages Retrieved Total The total number of messages that are retrieved from themail pickup directory. The value format is a 4-byte integer.

Remote Queue Length The number of messages in the remote queue since the server was started. Thevalue format is a 4-byte integer.

Remote Retry Queue Length The number of messages in the retry queue for remote delivery since theserver was started. The value format is a 4-byte integer.

Routing Table Lookups/Sec The number of routing table lookups per second since the server wasstarted. The value format is a decimal.

Routing Table Lookups Total The total number of routing table lookups since the server was started. Thevalue format is a 4-byte integer.

SMTP Server The instance name (SMTP Server). The value format is a 64 character string.



MM Month

DD Day

YY Year

HH Hour

mm Minute

SS Second

Total Connection Errors The total number of connection errors since the server was started. The valueformat is a 4-byte integer.

Total DSN Failures The total number of DSN generation attempts that are failed. The value format is a4-byte integer.

Total Messages Submitted The total number of messages submitted from SMTP Server since the serverwas started. The value format is a 4-byte integer.

Disk capacity planning for historical dataDisk capacity planning for a monitoring agent is a prediction of the amount of disk space to beconsumed by the historical data in each attribute group that is collecting historical data. Required diskstorage is an important factor when you are defining data collection rules and your strategy for historicaldata collection.

The Capacity planning for historical data table provides the following information, which is required tocalculate disk space for this monitoring agent:


Table Table name as it is displayed in the warehouse database, if the attribute group is configured to bewritten to the warehouse.

Attribute groupName of the attribute group that is used to create the table in the warehouse database if it isshort enough to fit in the table naming constraints of the database that is being used for thewarehouse.

Bytes per row (agent)Estimate of the record length for each row or instance that is written to the agent disk forhistorical data collection. This estimate can be used for agent disk space planning purposes.

Database bytes per row (warehouse)Estimate of the record length for detailed records that are written to the warehouse database, ifthe attribute group is configured to be written to the warehouse. Detailed records are records thatwere uploaded from the agent for long-term historical data collection. This estimate can be usedfor warehouse disk-space planning purposes.

Aggregate bytes per row (warehouse)Estimate of the record length for aggregate records that are written to the warehouse database, ifthe attribute group is configured to be written to the warehouse. Aggregate records are created bythe Summarization agent for attribute groups that were configured for summarization. Thisestimate can be used for warehouse disk-space planning purposes.

In addition to the information in the tables, you must know the number of rows of data that you plan tocollect. An attribute group can have single or multiple rows of data, depending on the applicationenvironment that is being monitored. For example, if your attribute group monitors each processor inyour computer and you have a dual processor computer, the number of rows is two.

Table 14. Capacity planning for historical data logged by the Microsoft Exchange Server agent

Table Attribute group

Bytes perrow(agent)

Databasebytes perrow(warehouse)

Aggregatebytes perrow(warehouse)

FFEXODS Forefront_Exchange_On_Demand_Scanner

768 798 1102

FFEXRTS Forefront_Exchange_Realtime_Scanner

768 798 1102

FFEXSCHS Forefront_Exchange_Scheduled_Scanner

768 798 1102

FFEXTRNSS Forefront_Exchange_Transport_Scanner

768 798 1102

MSEABK MS_Exchange_AB 176 215 777

MSEADCAH MS_Exchange_ADAccess_Caches 608 748 1838

MSEADDC MS_Exchange_ADAccess_Domain_Controllers

752 790 1190

MSEADFD MS_Exchange_ADAccess_Forest_Discovery

756 819 1186

MSEADACP MS_Exchange_ADAccess_Processes 780 933 1699

MSEAM MS_Exchange_Active_Manager 724 719 756

MSEAMC MS_Exchange_Active_Manager_Client 764 781 1034

MSEAMS MS_Exchange_Active_Manager_Server 136 153 361

MSEASYNC MS_Exchange_Active_Sync 372 844 3254

MSEASSIT MS_Exchange_Assistants 788 895 1634


Table 14. Capacity planning for historical data logged by the Microsoft Exchange Server agent (continued)


Bytes perrow(agent)



MSEASSTDB MS_Exchange_Assistants_Per_Database

760 836 1326

MSEAF MS_Exchange_Attachment_Filtering 128 131 273

MSEAUTH MS_Exchange_Authentication 736 746 918

MSEATDCVR MS_Exchange_Autodiscover 132 124 269

MSEAVSERV MS_Exchange_Availability_Service 164 188 573

MSECALATD MS_Exchange_Calendar_Attendant 144 151 329

MSECFA MS_Exchange_Connection_Filtering_Agent

152 233 657

MSECONFA MS_Exchange_Content_Filter_Agent 200 221 657

MSERBAC MS_Exchange_Control_Panel_RBAC 244 372 1597

MSEDB MS_Exchange_DB 620 894 2173

MSEDBINS MS_Exchange_DB_Instance 580 749 1698

MSEDS MS_Exchange_DS 188 326 1197

MSEDAG MS_Exchange_Database_Availability_Group

1028 1033 1130

MSEDDSN MS_Exchange_Delivery_DSN 752 754 998

MSEEVNTD MS_Exchange_Event_Details 3676 3688 3740

MSEXTAGT MS_Exchange_Extensibility_Agents 724 731 834

MSEFOAB MS_Exchange_FDS_OAB 732 729 922

MSEIS MS_Exchange_IS 412 798 3313

MSEISCLI MS_Exchange_IS_Client 212 306 790

MSEISHAD MS_Exchange_IS_HA_Active_Database 760 836 1326

MSEISPRI MS_Exchange_IS_Private 2868 3144 4672

MSEISPUB MS_Exchange_IS_Public 2864 3091 4436

MSEISPUR MS_Exchange_IS_Public_Replication 780 789 1066

MSEISSTR MS_Exchange_IS_Store 2948 3040 5336

MSELOTUS MS_Exchange_Lotus_Notes_Connector_Summary

172 174 661

MSEMCD MS_Exchange_MAPI_Connectivity_Details

240 231 268

MSEMTA MS_Exchange_MTA 204 334 1205

MSEMTAC MS_Exchange_MTA_Connections 520 591 1198

MSEMS MS_Exchange_Mail_Submission 760 812 1230

MSEMT MS_Exchange_Mail_Tips 212 416 1437

MSEMBXD MS_Exchange_Mailbox_Detail 1680 1716 1843

MSEMREPS MS_Exchange_Mailbox_Replication_Service

144 138 389

MSEMRSPM MS_Exchange_Mailbox_Replication_Service_per_Mdb

592 800 2362




Bytes perrow(agent)



MSEMANFA MS_Exchange_Managed_Folder_Assistant

136 129 241

MSENLBS MS_Exchange_NLB_Status 180 170 207

MSEOWA MS_Exchange_OWA 204 238 845

MSEPAA MS_Exchange_Protocol_Analysis_Agent

152 149 417

MSEPFLDD MS_Exchange_Public_Folder_Detail 1292 1310 1437

MSEREACH MS_Exchange_Reachability 908 921 1009

MSERCACH MS_Exchange_Recipient_Cache 516 513 634

MSERFA MS_Exchange_Recipient_Filter_Agent

132 148 317

MSERPSD MS_Exchange_Replica_Seeder 728 724 806

MSEREPL MS_Exchange_Replication 176 179 450

MSERS MS_Exchange_Replication_Server 124 126 229

MSEREPLI MS_Exchange_Replication_Version630

820 839 1224

MSERSCBK MS_Exchange_Resource_Booking 140 146 309

MSERH MS_Exchange_Resource_Health 776 808 1358

MSERMS MS_Exchange_Rights_Management_Service

236 518 1941

MSERBS MS_Exchange_Role_Based_Services 572 568 605

MSRTOPO MS_Exchange_Role_Topology 840 839 876

MSERPCCA MS_Exchange_Rpc_Client_Access 180 196 701

MSESRCHID MS_Exchange_Search_Indices 760 812 1239

MSESMO MS_Exchange_Search_Mailbox_Operators

752 754 974

MSESMSC MS_Exchange_Search_Mailbox_Session_Cache

736 758 942

MSESFA MS_Exchange_Sender_Filter_Agent 132 148 317

MSESIDAG MS_Exchange_Sender_Id_Agent 144 175 425

MSESERVR MS_Exchange_Server 771 803 942

MSESRVCD MS_Exchange_Services_Detail 512 508 545

MSESGRPD MS_Exchange_Storage_Group_Detail 2516 2554 2759

MSESTRDR MS_Exchange_Store_Driver 788 847 1322

MSESDD MS_Exchange_Store_Driver_Database 724 743 882

MSESDS MS_Exchange_Store_Driver_Server 724 743 882

MSESTOINT MS_Exchange_Store_Interface 788 871 1466

MSESUBM MS_Exchange_Submission 148 156 469

MSESDSN MS_Exchange_Submission_DSN 752 754 998

MSETXTMSG MS_Exchange_Text_Messaging 140 134 333




Bytes perrow(agent)



MSET MS_Exchange_Throttling 840 1008 2230

MSETRDB MS_Exchange_Transport_Database 844 1061 2154

MSETRDMP MS_Exchange_Transport_Dumpster 144 163 425

MSETRQUE MS_Exchange_Transport_Queues 604 683 1554

MSETRRUL MS_Exchange_Transport_Rules 516 537 706

MSETSMTPA MS_Exchange_Transport_SMTP_Availability

752 838 1262

MSETRSR MS_Exchange_Transport_Shadow_Redundancy

460 456 562

MSESMTPR MS_Exchange_Transport_SmtpReceive 564 657 1282

MSESMTPS MS_Exchange_Transport_SmtpSend 556 647 1218

MSEUMAATTD MS_Exchange_UM_Auto_Attendant 560 568 902

MSEUMAVLBT MS_Exchange_UM_Availability 160 159 433

MSEUMCANS MS_Exchange_UM_Call_Answer 148 144 373

MSEUMEUDTS MS_Exchange_UM_Enabled_User_Details

1268 1271 1308

MSEUMGEN MS_Exchange_UM_General 176 191 585

MSEUMSA MS_Exchange_UM_Subscriber_Access 236 254 837

MSEWS MS_Exchange_WS 168 217 665

MSMBSCS Mailbox_Server_Cluster_State 840 839 876

MSFSSS Microsoft_Forefront_Server_Security_Scan

224 273 634

MSEPRXY RPC_HTTP_Proxy 144 163 497

KEXSMTP SMTP 444 751 2918

For more information about historical data collection, see the IBM Tivoli Monitoring Administrator's Guide.


Chapter 5. Situations reference

A situation is a logical expression involving one or more system conditions. Situations are used tomonitor the condition of systems in your network. You can manage enterprise situations from the TivoliEnterprise Portal by using the Situation Editor or from the command line interface using the tacmds forsituations.

About situations

The monitoring agents that you use to monitor your system environment are shipped with a set ofpredefined situations that you can use as-is. You can also create new situations to meet yourrequirements. Predefined situations contain attributes that check for system conditions common to manyenterprises.

Using predefined situations can improve the speed with which you can begin using the MicrosoftExchange Server agent. You can examine and, if necessary, change the conditions or values beingmonitored by a predefined situation to those best suited to your enterprise.

Note: The predefined situations provided with this monitoring agent are not read-only. Do not edit thesesituations and save over them. Software updates will write over any of the changes that you make tothese situations. Instead, clone the situations that you want to change to suit your enterprise.

You can display predefined situations and create your own situations using the Situation editor. The leftframe of the Situation editor initially lists the situations associated with the Navigator item that youselected. When you click a situation name or create a new situation, the right frame opens with thefollowing tabs:

FormulaCondition being tested

DistributionList of managed systems (operating systems, subsystems, or applications) to which the situationcan be distributed.

Expert AdviceComments and instructions to be read in the event workspace

ActionCommand to be sent to the system

Until Duration of the situation

Additional information about situations

The Tivoli Enterprise Portal User's Guide contains more information about predefined and customsituations and how to use them to respond to alerts.

For a list of the predefined situations for this monitoring agent and a description of each situation, referto the “Predefined situations” on page 212 section below and the information in that section for eachindividual situation.


Predefined situationsThe monitoring agent contains predefined situations, which are organized by Navigator item.

This monitoring agent contains the following predefined situations:v Main Exchange Navigator item

– EX_Server_Down– EX_ASync_Request_Queued_Crit– EX_ASync_Request_Queued_Warn– EX_RBAC_OBPrxy_Avg_RTime_Crit– EX_OWA_Avg_Search_Time_Crit– EX_RBAC_Req_Avg_Resp_Time_Crit– EX_Rsc_Book_Requests_Failed_Crit

v Database Navigator item– EX_DB_Log_Record_Stalls_Warn– EX_DB_Log_Threads_Waiting_Warn– EX_Cache_Pg_Fault_Sec_Crit– EX_Cache_Pg_Fault_Sec_Warn– EX_DB_Log_Gen_CkPt_Depth_Crit– EX_DB_Log_Gen_CkPt_Depth_Warn– EX_DB_Log_Rec_Stall_Sec_Crit– EX_DB_Log_Rec_Stall_Sec_Warn– EX_DB_Log_Write_Avg_Lat_Crit

v Events Navigator item– EX_Error_Event

v Information Store Navigator item– EX_IS_RPC_Operations_Warn– EX_IS_RPC_Requests_Warn– EX_IS_Slow_Search_Threads_Crit– EX_IS_Slow_QP_Threads_Crit– EX_IS_RPC_Requests_Crit– EX_IS_RPC_Avg_Latency_Crit– EX_IS_Cli_RPC_Fail_ServBsy_Crit– EX_IS_Cli_RPC_Avg_Lat_Crit

v IS Mailbox Navigator item– EX_IS_Pri_Avg_Delvry_Warn– EX_IS_Pri_Avg_Local_Delvry_Warn– EX_IS_Pri_Message_Delvrd_Crit– EX_IS_Pri_Message_Delvrd_Warn– EX_IS_Pri_Receive_Queue_Warn– EX_IS_Pri_Send_Queue_Warn– EX_IS_Mail_Store_State_Critical– EX_IS_Pri_Slow_FdRw_Rate_Crit– EX_IS_Pri_Search_Task_Rate_Crit– EX_IS_Pri_Msg_Queue_Sub_Crit

v IS Public Navigator item


– EX_IS_Pub_Receive_Queue_Warn– EX_IS_Pub_Send_Queue_Warn– EX_IS_Pub_Msg_Queue_Sub_Crit

v MTA Navigator item– EX_MTA_Conn_Queue_Warn– EX_MTA_Work_Queue_Warn

v Replication Navigator item– EX_Replication_Failed_Warn– EX_Replication_Suspended_Warn– EX_Rep_Copy_Queue_Length_Crit

v Roles Navigator item– Messages_Bypassed_Scan_Crit– Messages_Bypassed_Scan_Warn– Cluster_Mailbox_State_Crit– EX_NLB_Status_Crit

v SMTP Navigator item– EX_SMTP_Local_Queue_Warn– EX_SMTP_Remote_Queue_Warn– EX_SMTP_Categorizer_QLen_Warn– EX_SMTP_Dir_PickupQ_Warn– EX_SMTP_Mess_Pend_Rt_Critical– EX_SMTP_Mess_Pend_Rt_Warn– EX_SMTP_Queue_Len_Warn– EX_SMTP_Remote_RetryQ_Warn– EX_SMTP_Retry_QLen_Warn

v Server Navigator item– EX_Rep_Failed_Warn– EX_Rep_Suspended_Warn– EX_Server_App_Pct_Free_Critical– EX_Server_App_Pct_Free_Warn– EX_Server_Attendant_Stat_Crit– EX_Server_IS_Status_Critical– EX_Server_Log_Pct_Free_Critical– EX_Server_Log_Pct_Free_Warn– EX_Server_MTA_Status_Critical– EX_Server_Res_Status_Critical– EX_Server_Status_Critical– EX_Server_WWW_Status_Critical– EX_Service_Start_Critical– EX_Service_State_Critical– EX_Service_Status_Critical– EX_TQ_ActMail_Delivey_Q_Crit– EX_TQ_ActMail_Delivey_Q_Warn– EX_TQ_Act_RD_QLen_Crit– EX_TQ_Act_RD_QLen_Warn

Chapter 5. Situations reference 213

– EX_TQ_Act_nSMTP_Q_Len_Crit– EX_TQ_Act_nSMTP_Q_Len_Warn– EX_TQ_Agg_Delivery_Q_Len_Crit– EX_TQ_Agg_Delivery_Q_Len_Warn– EX_TQ_Retry_RD_QLen_Crit– EX_TQ_Retry_RD_QLen_Warn– EX_TQ_RtryMailDeliver_QLen_Crit– EX_TQ_RtryMailDeliver_QLen_Warn– EX_TQ_Rtry_nSMTP_Q_Len_Crit– EX_TQ_Rtry_nSMTP_Q_Len_Warn– EX_TQ_Unreach_Q_Len_Crit– EX_TQ_Unreach_Q_Len_Warn– EX_TQ_Sub_Queue_Len_Warn– EX_TQ_Sub_Queue_Len_Crit– EX_TQ_Poison_Q_Len_Crit– EX_TQ_Lar_Dlv_Q_Len_Warn– EX_TQ_Lar_Dlv_Q_Len_Crit– EX_Store_Int_RPC_Slow_Req_Crit– EX_Store_Int_RPC_Req_OutSt_Crit– EX_Store_Int_RPC_Req_Fail_Crit– EX_Store_Int_RPC_Avg_Lat_Crit– EX_SI_Avg_Doc_Idx_Time_Warn– EX_SI_Full_Crawl_Mod_Sta_Warn– EX_HTTP_Pxy_Fail_Bknd_Con_Crit– EX_FDS_OAB_Dwnld_Task_Que_Warn– EX_CAS_RPC_Requests_Warn– EX_CAS_RPC_Requests_Crit– EX_CAS_RPC_Avg_Latency_Warn– EX_CAS_RPC_Avg_Latency_Crit– EX_Asst_Avg_Evt_Proc_Time_Crit– EX_AVSER_Avg_Proc_Free_Bsy_Crit– EX_AB_REF_RPC_Req_Avg_Lat_Crit– EX_AB_NSPI_RPC_Req_Avg_Lat_Crit– EX_AB_NSPI_RPC_Br_Avg_Lat_Crit– EX_Rsc_Book_Requests_Failed_Crit

Situation descriptionsEach situation description provides information about the situation that you can use to monitor thecondition of systems in your network.

The situation descriptions provide the following information:

DescriptionInformation about the conditions that the situation tests.


FormulaSyntax that contains one or more logical expressions describing the conditions for the situation tomonitor. The information center topic that corresponds to this situation contains the formula forthis agent.

EX_DB_Log_Record_Stalls_WarnIndicates the Database Log Record Stalls/Sec is high. Use the following formula:Log_Record_Stalls/Sec GT 0

EX_DB_Log_Threads_Waiting_WarnIndicates the Database Log Threads waiting is high. Use the following formula:Log_Threads_Waiting GT 25

EX_IS_Pri_Avg_Delvry_WarnIndicates the IS Mailbox Average Delivery time is high. Use the following formula:Average_Delivery_Time GT 3000

EX_IS_Pri_Avg_Local_Delvry_WarnIndicates the IS Mailbox Average Local Delivery time is high. Use the following formula:Average_Local_Delivery_Time GT 1000

Note: This situation applies only to Microsoft Exchange Server 2000.

EX_IS_Pri_Message_Delvrd_CritIndicates the IS Mailbox Messages Delivered/min is very high. Use the following formula:Messages_Delivered/min GT 3000

Note: This situation applies only to Microsoft Exchange Server 2000 and Microsoft Exchange Server 2003.

EX_IS_Pri_Message_Delvrd_WarnIndicates the IS Mailbox Messages Delivered/min is high. Use the following formula:Messages_Delivered/min GT 1000


EX_IS_Pri_Receive_Queue_WarnIndicates the IS Mailbox Receive Queue size is high. Use the following formula:Receive_Queue_Size GT 50

EX_IS_Pri_Send_Queue_WarnIndicates the IS Mailbox Send Queue size is high. Use the following formula:Send_Queue_Size GT 100


EX_IS_Pub_Receive_Queue_WarnIndicates the IS Public Receive Queue size is high. Use the following formula:Receive_Queue_Size GT 250


EX_IS_Pub_Send_Queue_WarnIndicates the IS Public Send Queue size is high. Use the following formula:Send_Queue_Size GT 1000


EX_IS_RPC_Operations_WarnIndicates a high number of RPC Operations per second. Use the following formula:RPC_Operations/Sec GT 100

EX_IS_RPC_Requests_WarnIndicates a high number of RPC Request. Use the following formula:RPC_Requests GT 50

EX_MTA_Conn_Queue_WarnIndicates the MTA Connections Queue size is high. Use the following formula:Queue_Length GT 50

This situation is only applicable on Microsoft Exchange Server 2000 and Microsoft Exchange Server 2003.

EX_MTA_Work_Queue_WarnIndicates the MTA Work Queue size is high. Use the following formula:Work_Queue_Length GT 50


EX_Server_DownIndicates Microsoft Exchange Server is down or unavailable. Use the following formula:Server_Status EQ DOWN

EX_SMTP_Local_Queue_WarnIndicates the SMTP Local Queue size is high. Use the following formula:Local_Queue_Length GT 50


EX_SMTP_Remote_Queue_WarnIndicates the SMTP Remote Queue size is high. Use the following formula:Remote_Queue_Length GT 50


EX_Cache_Pg_Stall_Sec_WarnIndicates that the number of Cache Page Stalls/Sec is high. Use the following formula:MS_Exchange_DB.Cache_Page_Fault_Stalls/Sec GT 0.0

EX_Cache_Pg_Fault_Sec_WarnIndicates that the number of Cache Page Faults/Sec is high. Use the following formula:MS_Exchange_DB.Cache_Page_Faults/Sec GT 10.0


EX_Cache_Pg_Fault_Sec_CritIndicates that the number of Cache Page Faults/Sec is very high. Use the following formula:MS_Exchange_DB.Cache_Page_Faults/Sec GT 20.0

EX_DB_Log_Rec_Stall_Sec_WarnIndicates that the Database Log Record Stalls/Sec is high. Use the following formula:MS_Exchange_DB.Log_Record_Stalls/Sec GT 50.0

EX_DB_Log_Rec_Stall_Sec_CritIndicates that the Database Log Record Stalls/Sec is very high. Use the following formula:MS_Exchange_DB.Log_Record_Stalls/Sec GT 100.0

EX_Server_Status_CriticalIndicates that the Microsoft Exchange Server is down or unavailable. Use the following formula:MS_Exchange_Server.Server_Status EQ down

EX_Server_Attendant_Stat_CritIndicates that the Microsoft Exchange Server System Attendant Service is down or unavailable. Use thefollowing formula:MS_Exchange_Server.System_Attendant_Svc_Status EQ Stopped

EX_Server_MTA_Status_CriticalIndicates that the Microsoft Exchange Server MTA service is down or unavailable. Use the followingformula:MS_Exchange_Server.Exchg_MTA_Status EQ Stopped

EX_Server_IS_Status_CriticalIndicates that the Microsoft Exchange Server Information Store service is down or unavailable. Use thefollowing formula:MS_Exchange_Server.Server_Status EQ down

EX_Server_Res_Status_CriticalIndicates that the Microsoft Exchange Routing Engine service is down or unavailable. Use the followingformula:MS_Exchange_Server.Res_Status EQ Stopped

EX_Server_SMTP_Status_CirticalIndicates that the Microsoft Exchange Server SMTP service is down or unavailable. Use the followingformula:MS_Exchange_Server.SMTP_Status EQ Stopped

EX_Server_WWW_Status_CriticalIndicates that the World Wide Web service is down or unavailable. Use the following formula:MS_Exchange_Server.WWW_Status EQ Stopped

EX_Server_App_Pct_Free_WarnIndicates the disk size and the free disk space that is available on the Microsoft Exchange Application.MS_Exchange_Server.Application_Percent_Free_Space LE 20.0 AND MS_Exchange_Server.Application_Percent_Free_Space GT 10.0


EX_Server_App_Pct_Free_CriticalIndicates the disk size and the free disk space that is available on the Microsoft Exchange Application.MS_Exchange_Server.Application_Percent_Free_Space LE 10.0

EX_Server_Log_Pct_Free_WarnIndicates the name and the location of the Microsoft Exchange Server log files. The agent also providesinformation about the free space that is available for each log file.MS_Exchange_Server.Log_Percent_Free_Space GT 10.0 AND MS_Exchange_Server.Log_Percent_Free_Space LE 20.0

EX_Server_Log_Pct_Free_CriticalIndicates the name and the location of the Microsoft Exchange Server log files. The agent also providesinformation about the free space that is available for each log file.MS_Exchange_Server.Log_Percent_Free_Space GE 0 AND MS_Exchange_Server.Log_Percent_Free_Space LE 10.0

EX_SMTP_Dir_PickupQ_WarnIndicates that the Directory Pickup Queue Length is high. Use the following formula:SMTP.Directory_Pickup_Queue_Length GT 25

EX_SMTP_Queue_Len_WarnIndicates that the Local Queue Length is high. Use the following formula:SMTP.Local_Queue_Length GT 25

EX_SMTP_Retry_QLen_WarnIndicates that the Local Retry Queue Length is high. Use the following formula:SMTP.Local_Retry_Queue_Length GT 25

EX_SMTP_Remote_RetryQ_WarnIndicates that the Remote Retry Queue Length is high. Use the following formula:SMTP.Remote_Retry_Queue_Length GT 25

EX_SMTP_Categorizer_QLen_WarnIndicates that the Categorizer Queue Length is high. Use the following formula:SMTP.Categorizer_Queue_Length GT 25

EX_DB_Log_Gen_CkPt_Depth_WarnIndicates that the Log Generation Checkpoint Depth is high. Use the following formula:MS_Exchange_DB_Instance.Log_Generation_Checkpoint_Depth GT 50000

EX_DB_Log_Gen_CkPt_Depth_CritIndicates that the Log Generation Checkpoint Depth is very high. Use the following formula:MS_Exchange_DB_Instance.Log_Generation_Checkpoint_Depth GT 60000

EX_SMTP_Mess_Pend_Rt_WarnIndicates that the Messages Pending Routing is high. Use the following formula:SMTP.Messages_Pending_Routing GT 500 AND SMTP.Messages_Pending_Routing LE 750


EX_SMTP_Mess_Pend_Rt_CriticalIndicates that the Messages Pending Routing is very high. Use the following formula:SMTP.Messages_Pending_Routing GT 750

EX_TQ_Act_RD_QLen_WarnIndicates the number of messages in the Remote Delivery Queue. It also indicates that the RemoteDelivery Queue length is greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Remote_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Active_Remote_Delivery_Queue_Length LE 750

EX_TQ_Act_RD_QLen_CritIndicates the number of messages in the Remote Delivery Queue. It also indicates that the RemoteDelivery Queue length is greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Remote_Delivery_Queue_Length GT 750

EX_TQ_Retry_RD_QLen_WarnIndicates that the Retry Remote Delivery Queue is holding messages that are in the retry state. It alsoindicates that the Retry Remote Delivery Queue length is greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Retry_Remote_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Retry_Remote_Delivery_Queue_Length LE 750

EX_TQ_Retry_RD_QLen_CritIndicates that the Retry Remote Delivery Queue is holding messages that are in the retry state. It alsoindicates that the Retry Remote Delivery Queue length is greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Retry_Remote_Delivery_Queue_Length GT 750

EX_TQ_ActMail_Delivey_Q_WarnIndicates the number of messages in Mailbox Delivery Queue. It also indicates that the Mailbox DeliveryQueue length is greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Mailbox_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Active_Mailbox_Delivery_Queue_Length LE 750

EX_TQ_ActMail_Delivey_Q_CritIndicates the number of messages in Mailbox Delivery Queue. It also indicates that the Mailbox DeliveryQueue length is greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Mailbox_Delivery_Queue_Length GT 750

EX_TQ_RtryMailDeliver_QLen_WarnIndicates that the Retry Mailbox Delivery Queue is holding messages that are in the retry state. It alsoindicates that the Mailbox Delivery Queue length is greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Retry_Mailbox_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Retry_Mailbox_Delivery_Queue_Length LE 750

EX_TQ_RtryMailDeliver_QLen_CritIndicates that the Retry Mailbox Delivery Queue is holding messages that are in the retry state. It alsoindicates that the Mailbox Delivery Queue length is greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Retry_Mailbox_Delivery_Queue_Length GT 750


EX_TQ_Act_nSMTP_Q_Len_WarnIndicates the number of messages in the Non-SMTP Delivery Queue. It also indicates that the Non-SMTPDelivery Queue length is greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Non-SMTP_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Active_Non-SMTP_Delivery_Queue_Length LE 750

EX_TQ_Act_nSMTP_Q_Len_CritIndicates the number of messages in the Non-SMTP Delivery Queue. It also indicates that the Non-SMTPDelivery Queue length is greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Active_Non-SMTP_Delivery_Queue_Length GT 750

EX_TQ_Rtry_nSMTP_Q_Len_WarnIndicates that the Retry Non-SMTP Delivery Queue is holding messages that are in a retry state. It alsoindicates that the Retry Non-SMTP Delivery Queue length is greater than 500 for the last 3 sampleintervals.MS_Exchange_Transport_Queues.Retry_Non-SMTP_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Retry_Non-SMTP_Delivery_Queue_Length LE 750

EX_TQ_Rtry_nSMTP_Q_Len_CritIndicates that the Retry Non-SMTP Delivery Queue is holding messages that are in a retry state. It alsoindicates that the Retry Non-SMTP Delivery Queue length is greater than 750 for the last 3 sampleintervals.MS_Exchange_Transport_Queues.Retry_Non-SMTP_Delivery_Queue_Length GT 750

EX_TQ_Agg_Delivery_Q_Len_WarnIndicates the total number of items that are in queue for delivery in all the queues. It also indicates thatthe total number of messages in all queues are greater than 500 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Aggregate_Delivery_Queue_Length GT 500 AND MS_Exchange_Transport_Queues.Aggregate_Delivery_Queue_Length LE 750

EX_TQ_Agg_Delivery_Q_Len_CritIndicates the total number of items that are in queue for delivery in all the queues. It also indicates thatthe total number of messages in all queues are greater than 750 for the last 3 sample intervals.MS_Exchange_Transport_Queues.Aggregate_Delivery_Queue_Length GT 750

EX_Service_State_CriticalIndicates the state of the service. A service can be in one of the following states:v Stoppedv Start Pendingv Stop Pendingv Runningv Continue Pendingv Pause Pendingv Pausedv UnknownMS_Exchange_Services_Detail.Service_State NE Running


EX_Service_Status_CriticalIndicates the status of the service. A service can have one of the following status:v Okv Errorv Degradedv Unknownv Pred Failv Startingv Stoppingv ServiceMS_Exchange_Services_Detail.Service_Status NE Starting

EX_Service_Start_CriticalIndicates that the service will either be started automatically when the system starts or manually by theuser.MS_Exchange_Services_Detail.Service_Start_Mode NE Automatic

EX_IS_Mail_Store_State_CriticalIndicates the Information Mailbox Store state. You can mount or demount the Information Mailbox Store.MS_Exchange_IS_Private.Mailbox_Store_State EQ Dismounted

EX_Rep_Failed_WarnIndicates that the Replica Instance has failed.Replication_Failed EQ 1

EX_Rep_Suspended_WarnIndicates that the Replica Instance is suspended.Replication_Suspended EQ 1

Messages_Bypassed_Scan_CritIndicates the number of messages that have bypassed scanning are 50 or more.Messages_Bypassed_Scanning GE 50

Messages_Bypassed_Scan_WarnIndicates the number of messages that have bypassed scanning are 40 or more, but less than 50.Messages_Bypassed_Scanning GE 40 and LT 50

Cluster_Mailbox_State_CritIndicates that the server is offline.Mailbox_State EQ OFFLINE

EX_NLB_Status_CritIndicates that cluster operations have stopped on at least one node.NLB_Status EQ ’Stopped’


EX_Replication_Failed_WarnIndicates that replication has failed.Replication_Failed EQ Replication_Failed

EX_Replication_Suspended_WarnIndicates that replication has been suspended.Replication_Suspended EQ Replication_Suspended

EX_Error_EventIndicates that an error type event has occurred.Event_Type EQ Failure_Audit OR Error

EX_Asst_Avg_Evt_Proc_Time_CritIndicates that the average processing time of the selected events has exceeded the critical threshold.Average_Event_Processing_Time_In_seconds GE 2

EX_ASync_Request_Queued_CritIndicates that the number of HTTP requests that are received from the client through ASP.NET hasexceeded the critical threshold.Requests_Queued GE 100

EX_ASync_Request_Queued_WarnIndicates that the number of HTTP requests that are received from the client through ASP.NET hasexceeded the warning threshold.Requests_Queued GE 95 and LT 100

EX_DB_Log_Write_Avg_Lat_CritIndicates that the average latency (in milliseconds) of database log write operations has exceeded thecritical threshold.IO_Log_Writes_Average_Latency GE 10

EX_IS_Cli_RPC_Avg_Lat_CritIndicates that the average latency (in milliseconds) of RPC requests has exceeded the critical threshold.RPC_Average_Latency GE 50

EX_IS_Cli_RPC_Fail_ServBsy_CritIndicates that some RPC requests have failed because the RPC server is too busy.Client_RPCs_Failed_Server_Too_Busy GT 0

EX_IS_Pri_Msg_Queue_Sub_CritIndicates that the number of messages in the mailbox store have been queued for submission to theTransport Server and have exceeded the critical threshold.Messages_Queued_For_Submission GE 50

EX_IS_Pri_Search_Task_Rate_CritIndicates that the number of search tasks that are created per second has exceeded the critical threshold.Search_Task_Rate GE 10


EX_IS_Pri_Slow_FdRw_Rate_CritIndicates that the Slow FindRow Rate in the mailbox store has exceeded the critical threshold.Slow_Findrow_Rate GT 10

EX_IS_Pub_Msg_Queue_Sub_CritIndicates that the number of replication messages in the public store that have been queued forsubmission to the Transport Server and have exceeded the critical threshold.Messages_Queued_For_Submission GE 20

EX_IS_RPC_Avg_Latency_CritIndicates that the RPC average latency (in milliseconds) for the information store has exceeded the criticalthreshold.RPC_Averaged_Latency GT 10

EX_IS_RPC_Requests_CritIndicates that the number of client requests in the information store process has exceeded the criticalthreshold.RPC_Requests GE 70

EX_IS_Slow_QP_Threads_CritIndicates that the number of query processor threads, which contain queries that are not optimized, hasexceeded the critical threshold.Slow_QP_Threads GE 10

EX_IS_Slow_Search_Threads_CritIndicates that the number of search threads, which contain queries that are not optimized, has exceededthe critical threshold.Slow_Search_Threads GE 10

EX_RBAC_OBPrxy_Avg_RTime_CritIndicates that the average completion time (in milliseconds) for the requests that are sent to thesecondary Client Access Server during the sampling period has exceeded the critical threshold.Average_Response_Time_of_Outbound_Proxy_Requests GE 6000

EX_OWA_Avg_Search_Time_CritIndicates that the average search time (in milliseconds) has exceeded the critical threshold.Average_Search_Time GE 5000

EX_Rep_Copy_Queue_Length_CritIndicates that the copy queue length has exceeded the critical threshold.Copy_Queue_Length GE 1

EX_RBAC_Req_Avg_Resp_Time_CritIndicates that the average time (in milliseconds) for the Exchange Control Panel to respond to a requestduring the sampling period has exceeded the critical threshold.Average_Request_Response_Time GE 6000


EX_Rsc_Book_Requests_Failed_CritIndicates that the Resource Booking Attendant has failed to process meeting requests.Meetings_Requests_Failed GT 0

EX_Store_Int_RPC_Avg_Lat_CritIndicates that the average latency of RPC requests (in milliseconds) has exceeded the critical threshold.The average is calculated for all the RPC requests since the exrpc32.dll process has been loaded.RPC_Latency_Average GE 100

EX_Store_Int_RPC_Req_OutSt_CritIndicates that some RPC requests are outstanding. The number of outstanding RPC requests must alwaysbe 0.RPC_Requests_outstanding GT 0

EX_Store_Int_RPC_Req_Fail_CritIndicates the percentage of RPC requests that have failed. The failed RPC requests are the requests witherror codes and exceptions.Percent_of_RPC_Requests_Failed GT 0

EX_Store_Int_RPC_Slow_Req_CritIndicates that the processing time for some RPC requests has exceeded the specified threshold. An RPCrequest with a processing time of more than 500 ms is called a slow RPC request.Percent_of_Slow_RPC_Requests GE 1

EX_TQ_Lar_Dlv_Q_Len_CritIndicates that the number of messages in the largest delivery queue has exceeded the critical threshold.Largest_Delivery_Queue_Length GE 200

EX_TQ_Lar_Dlv_Q_Len_WarnIndicates that the number of messages in the largest delivery queue has exceeded the warning threshold.Largest_Delivery_Queue_Length GE 190 and LT 200

EX_TQ_Poison_Q_Len_CritIndicates that the poison message queue contains some messages. The poison message queue mustalways be empty.Poison_Queue_Length GT 0

EX_TQ_Sub_Queue_Len_CritIndicates that the number of messages in the Submission queue has exceeded the critical threshold.Submission_Queue_Length GE 100

EX_TQ_Sub_Queue_Len_WarnIndicates that the number of messages in the Submission queue has exceeded the warning threshold.Submission_Queue_Length GE 95 and LT 100

EX_TQ_Unreach_Q_Len_CritIndicates that the number of messages in the Unreachable queue has exceeded the critical threshold.Unreachable_Queue_Length GE 100


EX_TQ_Unreach_Q_Len_WarnIndicates that the number of messages in the Unreachable queue has exceeded the warning threshold.Unreachable_Queue_Length GE 95 and LT 100

EX_CAS_RPC_Avg_Latency_CritIndicates that the RPC average latency for the last 1024 packets has exceeded the critical threshold.RPC_Averaged_Latency GE 250

EX_CAS_RPC_Avg_Latency_WarnIndicates that the RPC average latency for the last 1024 packets has exceeded the warning threshold.RPC_Averaged_Latency GE 225 AND RPC_Averaged_Latency LT 250

EX_CAS_RPC_Requests_CritIndicates that the number of RPC requests that are processed by the RPC Client Access service hasexceeded the critical threshold.RPC_Requests GE 40

EX_CAS_RPC_Requests_WarnIndicates that the number of RPC requests that are processed by the RPC Client Access service hasexceeded the warning threshold.RPC_Requests GE 35 AND RPC_Requests LT 40

EX_AB_NSPI_RPC_Br_Avg_Lat_CritIndicates that the average latency of the NSPI RPC browse requests has exceeded the critical threshold.NSPI_RPC_Browse_Requests_Average_Latency GE 1000

EX_AB_NSPI_RPC_Req_Avg_Lat_CritIndicates that the average latency of the NSPI RPC requests has exceeded the critical threshold.NSPI_RPC_Requests_Average_Latency GE 1000

EX_AB_REF_RPC_Req_Avg_Lat_CritIndicates that the average latency of the referral RPC requests has exceeded the critical threshold.Referral_RPC_Requests_Average_Latency GE 1000

EX_FDS_OAB_Dwnld_Task_Que_WarnIndicates that the number of OAB download tasks that are queued for execution has exceeded thewarning threshold.Download_Task_Queued GT 0

EX_AVSER_Avg_Proc_Free_Bsy_CritIndicates that the average time to process a free or a busy request has exceeded the critical threshold.Average_Time_to_Process_Free_Busy_Request GE 5

EX_HTTP_Pxy_Fail_Bknd_Con_CritIndicates that the number of attempts that failed to connect to the back-end server has exceeded thecritical threshold.Number_of_Failed_Back_End_Connection_Attempts_per_Second GT 0


EX_SI_Avg_Doc_Idx_Time_WarnIndicates that the average document indexing time has exceeded the warning threshold.Average_Document_Indexing_Time GE 30

EX_SI_Full_Crawl_Mod_Sta_WarnIndicates that the utilization of server resources has increased because the full-text crawl is currentlyrunning on the database.Full_Crawl_Mode_Status EQ 1

EX_IS_Mailbox_Store_State_CritIndicates that the mailbox store has been dismounted.Mailbox_Store_State EQ Dismounted


Chapter 6. Take Action commands reference

Take Action commands can be run from the desktop or included in a situation or a policy.

About Take Action commands

When included in a situation, the command executes when the situation becomes true. A Take Actioncommand in a situation is also referred to as reflex automation. When you enable a Take Actioncommand in a situation, you automate a response to system conditions. For example, you can use a TakeAction command to send a command to restart a process on the managed system or to send a textmessage to a cell phone.

Advanced automation uses policies to perform actions, schedule work, and automate manual tasks. Apolicy comprises a series of automated steps called activities that are connected to create a workflow.After an activity is completed, Tivoli Enterprise Portal receives return code feedback, and advancedautomation logic responds with subsequent activities prescribed by the feedback.

A basic Take Action command shows the return code of the operation in a message box that is displayedafter the action is completed or in a log file. After you close this window, no further information isavailable for this action.

More information about Take Action commands

For more information about working with Take Action commands, see the Tivoli Enterprise Portal User'sGuide.

For a list of the Take Action commands for this monitoring agent and a description of each command, seethe Predefined Take Action commands and the information for each individual command.

Predefined Take Action commandsNot all agents have predefined Take Action commands. You can create Take Action commands for themonitoring agent.

This monitoring agent contains the following Take Action commands:v Start Exchange Servicesv Stop Exchange Servicesv Mount Mailbox Databasev Mount Public Folder Database

For information about these Take Action commands, see “Take Action command descriptions” on page228.

The following information is provided about each Take Action command:

Authorization roleThe required authorization role

DescriptionWhich actions the command performs on the system to which is it sent

ArgumentsList of arguments, if any, for the Take Action with a short description and default value for eachone


Destination systemsWhere the command is to be executed: on the Managed System (monitoring agent) where theagent resides or on the Managing System (Tivoli Enterprise Monitoring Server) to which it isconnected

Usage NotesAdditional notes relevant to using the task.

Take Action command descriptionsEach Take Action command description provides information you can use to decide whether to run theTake Action command or whether to include the Take Action command in a situation or a policy.

Start Exchange Services actionThe StartExchangeServices action starts all Microsoft Exchange services that are configured to startautomatically in the Windows Services panel, but that are not currently running. Those services that aredisabled or configured to be started manually are not started by the Start Take Action. This Take Actionstarts only the following services:v Front End Transportv Filtering Managementv Host Controllerv Microsoft Exchange Active Directory Topologyv Microsoft Exchange ADAMv Microsoft Exchange Anti-spam Updatev Microsoft Exchange Credentialv Microsoft Exchange Diagnosticv Microsoft Exchange Deliveryv Microsoft Exchange EdgeSyncv Microsoft Exchange Extension for Windows Server Backupv Microsoft Exchange Fast Searchv Microsoft Exchange Health Managerv IIS Adminv Microsoft Exchange Information Storev Microsoft Exchange IMAP4v Microsoft Exchange Mailbox Assistantsv Microsoft Exchange Mail Submissionv Microsoft Exchange Mailbox Replicationv Microsoft Exchange POP3v Microsoft Exchange POP3BEv Microsoft Exchange Replicationv Microsoft Exchange RPC Client Accessv Microsoft Exchange System Attendantv Microsoft Exchange Search Indexerv Microsoft Exchange Service Hostv Microsoft Exchange Speech Enginev Microsoft Exchange Submissionv Microsoft Exchange Throttlingv Microsoft Exchange Transport Log Search


v Microsoft Search (Exchange Server)v Microsoft Exchange File Distributionv World Wide Web Publishingv Microsoft Exchange Tracing Service for Searchv Microsoft Exchange Transportv Microsoft Exchange Unified Messagingv Microsoft Exchange Unified Messaging Call Routerv Microsoft Exchange Monitoring

Authorization roleThe user must be a domain user with local administrator rights on the Microsoft ExchangeServer.

ArgumentsThere are no arguments for this Take Action command.

Destination systemsManaged system

Usage notesThis action can take a couple of minutes to complete. You receive one of the following returncodes when you run this Take Action command:

0 Successful

non-zeroNot successful. Check the RAS1 log for the Take Action command, or contact IBMSoftware Support.

Stop Exchange Services actionThe StopExchangeServices action stops all Microsoft Exchange services that are currently running. ThisTake Action stops only those services that have a name starting with Microsoft Exchange.

Note: The StopExchangeServices Take Action command stops the following dependent services:v Microsoft Exchange Address Bookv Microsoft Exchange Mailbox Replication Servicev Microsoft Exchange Protected Service Hostv Microsoft Exchange RPC Client Accessv Microsoft Exchange Throttling

However, the StartExchangeService Take Action command does not start these services automatically.


ArgumentsThere are no arguments for this Take Action command.



0 Successful

Chapter 6. Take Action commands reference 229


Mount Mailbox Database actionThe MountMailboxDatabase action mounts the selected mailbox database on the Microsoft ExchangeServer. You can access data that is stored in the database only when the database is mounted. Ensure thatthe Mailbox Server role is installed before running this Take Action command.

Note: This Take Action command is available for Exchange Server 2007, or later.


ArgumentsThe name of the mailbox database to be mounted.



0 Successful


Mount Public Folder Database actionThe MountPublicFolderDatabase action mounts the selected public folder database on the MicrosoftExchange Server. You can access data that is stored in the database only when the database is mounted.Ensure that the Mailbox Server role is installed before running this Take Action command.

Note: This Take Action command is available only for Exchange Server 2007 and 2010.


ArgumentsThe name of the public folder database to be mounted.



0 Successful

non-zeroNot successful. Check the RAS1 log for the for the Take Action command, or contact IBMSoftware Support.


Chapter 7. Policies reference

Policies are used as an advanced automation technique for implementing more complex workflowstrategies than you can create through simple automation. All agents do not provide predefined policies,but you can create policies for any agent.

A policy is a set of automated system processes that can take actions, schedule work for users, orautomate manual tasks. You use the Workflow Editor to design policies. You control the order in whichthe policy executes a series of automated steps, which are also called activities. Policies are connected tocreate a workflow. After an activity is completed, the Tivoli Enterprise Portal receives return-codefeedback, and advanced automation logic responds with subsequent activities prescribed by the feedback.

For more information about working with policies, see "Automation with policies" in the Tivoli EnterprisePortal User's Guide.

For information about using the Workflow Editor, see the IBM Tivoli Monitoring Administrator's Guide orthe Tivoli Enterprise Portal online help.

Predefined policiesNot all agents have predefined policies. But you can create policies for any agent.

The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange ServerAgent does not provide predefined policies.


Chapter 8. Tivoli Common Reporting for the monitoring agent

You can use the Tivoli Common Reporting application to generate reports for the Microsoft ExchangeServer agent. For more information about Tivoli Common Reporting, such as prerequisites, importingreports, and running reports, see the IBM Tivoli Monitoring Administrator's Guide V6.2.3.

IBM Tivoli Monitoring for Microsoft Applications reports are historical reports that include summarizeddata that is collected in the Tivoli Data Warehouse. These reports are built to run only against the IBMTivoli Monitoring for Microsoft Exchange Server agent.

The reports can be administered and run on Tivoli Common Reporting V1.3, V2.1, V2.1.1, Fix Pack 6, andV3.1.

For more information about Tivoli Common Reporting, see the developerWorks website(http://www.ibm.com/developerworks/spaces/tcr).

This version of Tivoli Common Reporting includes Cognos Business Intelligence and Reporting V8.4.

Cognos-based report packagesThe Cognos-based Tivoli Common Reporting tool is used to create, view, and manage reports for theTivoli group of products.

You can use the Cognos reports to analyze resource information such as availability, utilization,performance, and so on. With Cognos reports, you can evaluate the key metrics of the computers that areon the managed environment of your organization.

You can use the Tivoli Common Reporting tool to:v Create custom reports by using the drag-and-drop feature integrated with the web-based editor.v Schedule, share, secure, and administer reports in a single interface.v Save the report in HTML, PDF, Excel, XML, or CSV file formats.v Share reports by email or save the reports in a file system for later use.

The following databases are supported for all reports:v DB2 V9.5 and V9.7, Fix Pack 2v Oracle 10g and 11gv SQL Server 2005 and 2008

You can use Tivoli Common Reporting V1.3, V2.1, V2.1.1, Fix Pack 6, and V3.1 software that is shippedwith IBM Tivoli Monitoring V6.2.3, or later to administer, run, and edit Cognos reports. For moreinformation about Tivoli Common Reporting, see the Tivoli Common Reporting Information Center(http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ic-home.html).

PrerequisitesBefore you run the Cognos-based reports, ensure that the prerequisites that are required for installing andrunning Tivoli Common Reporting packages are met.

Procedure1. Install Tivoli Common Reporting. For more information, see the documentation in the IBM Tivoli

Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ic-home.html).


http://www.ibm.com/developerworks/spaces/tcr

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ic-home.html



To ensure that Tivoli Common Reporting is running, go to:https://machine_name:port_number/ibm/console/.

2. Obtain the reports package from the product media and extract the package.The Cognos reports are available in the following package: Product Media root/REPORTS/KEX/ITCAMMA_ExchangeServer_V710_Cognos_Reports.

3. Copy this package in a directory on any drive of the same computer where the Tivoli CommonReporting Server is installed, and extract the package in the same directory.The directory contents include:v Database scripts required to prepare the Tivoli Data Warehouse for Cognos reports.v A report installer that imports the reports into Tivoli Common Reporting and sets up the database

connection.4. Open the setup.batch file, and verify that the specified drive is the same drive where the Tivoli

Common Reporting Server is installed. If the specified drive is not correct, edit the setup.batch file tospecify the correct drive.For example, change the TCR_DEFAULT_DIR=C:\IBM\tivoli\tip to TCR_DEFAULT_DIR=F:\IBM\tivoli\tipif the Tivoli Common Reporting Server is installed on the F drive.

5. Configure historical collection for Microsoft Exchange Server agent and the IBM Tivoli WarehouseSummarization and Pruning Agent. After IBM Tivoli Monitoring V6.2.3, Fix Pack 1, or later isinstalled and the Microsoft Exchange Server agent is installed and configured, configure historicalcollection. Also, configure the Warehouse Summarization and Pruning agent with or without shiftsenabled. For more information about how to enable historical collection and configure the WarehouseSummarization and Pruning agent in IBM Tivoli Monitoring, see the following documentation:v http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/

history_manage_intro.htmv http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/

history_manage_collection.htm

Note: Historical collection and daily and hourly summarization must be enabled for all attributegroups of Microsoft Exchange Server agent.

To ensure that the required views are present, run the following query against the Tivoli DataWarehouse:v DB2: Select distinct "VIEWNAME" from SYSCAT.VIEWS where "VIEWNAME" like ’ %V’v Oracle: Select distinct "OBJECT_NAME" from OBJ where "OBJECT_TYPE" like ’%V’v MS SQL Server: Select distinct "NAME" from SYS.OBJECTS where "TYPE_DESC" like ’%V’

6. Prepare the Tivoli Data Warehouse to support Cognos dimensions.Preparing the Tivoli Data Warehouse for Tivoli Common Reporting includes creating the IBM_TRAMdimensions, which are required for running the Cognos reports and using the data models.See "Creating shared dimension tables and populating the time dimensions table" in the IBM TivoliMonitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/tcr_reports_dimensionsshared.htm)

7. Connect to the Tivoli Data Warehouse by using the database client over Open Database Connectivity(ODBC).Cognos uses ODBC to connect to the database. Install a database client on the Tivoli CommonReporting Server and connect it to the Tivoli Data Warehouse.See "Connecting to the Tivoli Data Warehouse using the database client over ODBC" in the IBM TivoliMonitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/tcr_tdwconnect.htm).

Important: All prerequisites described here must be met or the reports cannot run.


http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/history_manage_intro.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/history_manage_intro.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/history_manage_collection.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/history_manage_collection.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/tcr_reports_dimensionsshared.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/tcr_tdwconnect.htm

Importing Cognos report packagesYou must import the Cognos report package that contains the Microsoft Exchange Server agent datamodel and reports into Tivoli Common Reporting. Before you import the Cognos report package, ensurethat all the prerequisites have been met. Otherwise, reports cannot run.

For Tivoli Common Reporting V1.3, use one of the following options to import the Cognos reportpackage:v Importing by running the reports installer – For information about running the reports installer to

import the Cognos report package, see "Installing and running IBM Cognos reports" in the IBM TivoliMonitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.2, Fix Pack 2 Information Center(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/tcr_install_itm.htm).

v Importing manually – For information about manually importing the reports package, see “Importingreport packages” at the IBM Tivoli Systems Management Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/ttcr_cog_import.html).

For Tivoli Common Reporting V2.1, or later, see "Importing report packages" at the Tivoli CommonReporting Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html).

If you are using a schema other than ITMUSER, you must complete the following steps for the datamodel and reports to run:1. Verify that you have completed the following steps:

a. Altered the schema name in the database scripts when you prepared the Tivoli Data Warehousefor Cognos dimensions in Step 6 on page 234 of “Prerequisites” on page 233.

b. Installed the reports package by using the Reports installer as explained in "Importing reports byusing the report installer" topic in the IBM Tivoli Monitoring Administrator's Guide. To verify thatyou have installed the reports package, go to Tivoli Common Reporting and make sure you cansee "ITCAMMA ExchangeServer V710 Cognos Reports" in the Public Folders of IBM CognosConnection.

2. Install and configure the Cognos Framework Manager, which is the data modeling tool. See theinstructions at the Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_configure_frameworkmgr.html).

3. Open the Framework Manager. Select File > Open. Browse to the extracted ITCAMMAExchangeServer V710 Cognos Reports reports package. Browse to the model folder and select theITCAMMA ExchangeServer V710 Cognos Reports.cpf file.

4. If you are prompted to enter login credentials, enter your tipadmin user ID and password.5. After the IBM Tivoli Monitoring for Exchange Servers data model in the Framework Manager opens,

expand Data Sources under Tivoli Reporting and Analytics Model in the Project Viewer.6. Select TDW under Data Sources.7. When you select TDW, the Properties view is updated with information about the Tivoli Data

Warehouse data source. By default, the Properties view is located at the bottom center of the screen.If the Properties view is not visible, select View > Properties.

8. In the Properties, edit the Schema field. Change it from ITMUSER to your schema name.9. Save the project.

10. In the Project Viewer, expand Packages.11. Right-click ITCAMMA ExchangeServer V710 Cognos Reports.12. Select Publish Packages. The Publish Wizard opens.13. Keep the default selection and click Next.14. Click Next on the next screen.15. Clear the Verify the package before publishing check box.

Chapter 8. Tivoli Common Reporting for the monitoring agent 235

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/tcr_install_itm.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/ttcr_cog_import.html

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_configure_frameworkmgr.html

16. Click Publish. A window is displayed that alerts you that A package with that name alreadyexists and asks Do you want to publish this package?

17. Click Yes.18. Go back to Tivoli Common Reporting and check if the Modified field of "ITCAMMA ExchangeServer

V710 Cognos Reports" in the Public Folders of IBM Cognos Connection shows the time ofpublishing.

After completing these steps, you can run any report from the IBM Tivoli Monitoring for ITCAMMAExchangeServer V710 Cognos Reports package.

Cognos data models and reportsWhen all the prerequisites are met, you can use the Tivoli Integrated Portal interface to create, modify,and manage Cognos reports.

In Tivoli Common Reporting, the historical data that is collected by the agent is used to build ad hocreports and queries. The package that you import into Tivoli Common Reporting contains a Cognos datamodel. All the reports that you create in Tivoli Common Reporting are based on the data model.

Cognos data models are virtual star schema models that contain facts and dimensions. Facts aremeasurable quantities that can be aggregated, such as CPU utilization and number of processors.Dimensions are the main identifiers by which facts can be grouped, aggregated, and organized. Forexample, time and server are dimensions by which the fact CPU utilization can be grouped.

The facts in the data model are organized into the folders by their summarization type, such as Daily andHourly. The Daily and the Hourly folders contain attribute groups that correspond to tables or views inthe data warehouse. Each attribute group contains a group of facts and measures.

The data model is built on top of the data warehouse to organize data. The data model contains theTivoli Reporting and Analytics Model (TRAM) Shared Dimensions, which are shared across Tivoli byproducts such as Time.

To create reports in Tivoli Common Reporting tool, you can use one of the following report authoringtools:v Query Studio: A web-based product that is used mostly for ad hoc reporting. Users can create simple

queries and reports, and apply basic formatting to the reports.v Report Studio: A web-based tool that is used by technical users and professional report writers for

creating advanced reports. Users can retrieve data from multiple databases and create sophisticatedreports that have multiple pages and multiple queries.

Reports for the monitoring agent

You can verify whether the reporting functionality is installed and configured correctly by running thereports for the Microsoft Exchange Server agent. The Microsoft Exchange Server agent reporting packagethat you imported into Tivoli Common Reporting includes 10 reports. By using these reports, you canmonitor the reporting activity and see what a typical Cognos report includes. These reports are availablein the Common Reporting panel in Tivoli Common Reporting. The following tables describe thesereports.

Table 15. Exchange Server OWA Login Activity report

Name Exchange Server OWA Login Activity report

Description This report displays the total number of users who have connected to Outlook Web Access(OWA) since the process started. The report is available on Microsoft Exchange Server 2007 orlater.

Purpose This report helps you to determine the total number of users connected to OWA.


Table 15. Exchange Server OWA Login Activity report (continued)

ParametersDate Range

Report PeriodSelect the report period from a predefined date range, such as Last Week,Current Month, Last 30 Days, and so on. You can also enter a start date, anend date, and the time for the reporting period.

Start DateSelect a start date from the calendar and the start time from the time widget.You must select both date and time.

End DateSelect a start date from the calendar and the start time from the time widget.You must select both date and time.

Summarization Selection

Summarization TypeSelect the summarization type, such as Hourly, Daily, Weekly, Monthly,Quarterly, Yearly, or Default from the list. If you select the Default option, thesummarization type is calculated according to the number of days in the daterange.

Shift PeriodIf shift period is enabled, the hourly tables display the Shift Period as 1(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hoursthat are configured in the data warehouse. In the daily tables, the value 1corresponds to peak hours, the value 2 corresponds to off-peak hours, and thevalue -1 corresponds to the summarized value for that day. If shifts are notenabled, the default value is -1.

Vacation PeriodIf Vacation Period is not enabled, the default value is -1 (All Days). You canenter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period isenabled.

Tables/ViewsUsed

MS_Exchange_OWA_%V

Output The Outlook Web Access Login Activity chart displays the total number of users who areconnected to OWA for each Exchange Server.

Usage The administrator can use this report to determine the total number of users who haveconnected to Outlook Web Access (OWA) since the process started.

Table 16. Exchange Server Services Status Details report

Name Exchange Server Services Status Details report

Description This report displays the status of the monitored services for the Microsoft Exchange Server inthe current IBM Tivoli Monitoring environment.

Purpose You can use this report to observe the status (Up or Down) of the Microsoft Exchange Serverservices. You can also observe the available time for the services in the selected report period.


Table 16. Exchange Server Services Status Details report (continued)


Report PeriodSelect the report period from a predefined date range, such as Last Week,Current Month, Last 30 Days, and so on. You can also enter a start date, anend date, and the time for the reporting period.

Start DateSelect a start date from the calendar and the start time from the time widget.You must select both date and time.

End DateSelect a start date from the calendar and the start time from the time widget.You must select both date and time.


Summarization TypeSelect the summarization type, such as Hourly, Daily, Weekly, Monthly,Quarterly, Yearly, or Default from the list. If you select the Default option, thesummarization type is calculated according to the number of days in the daterange.

Shift PeriodIf shift period is enabled, the hourly tables display the Shift Period as 1(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hoursthat are configured in the data warehouse. In the daily tables, the value 1corresponds to peak hours, the value 2 corresponds to off-peak hours, and thevalue -1 corresponds to the summarized value for that day. If shifts are notenabled, the default value is -1.

Vacation PeriodIf Vacation Period is not enabled, the default value is -1 (All Days). You canenter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period isenabled.

Display Options

Server NameSelect the name of the server from the Server Name list.

Tables/ViewsUsed

MS_Exchange_Services_Detail_%V

Output The Microsoft Exchange Server Services Status Availability bar chart displays the availability ofthe Microsoft Exchange services for the Microsoft Exchange Server (as a percentage) for a periodof time. The other states for the services are:

v Stopped - 0

v Start Pending - 1

v Stop Pending - 2

v Running - 3

v Continue Pending - 4

v Pause Pending - 5

v Paused - 6

v Unknown - 7

Usage The IT administrator can use this report to observe the state of the Microsoft Exchange Serverservices as Running, Paused, Stopped, and so on. The administrator can observe the totalavailable time for service in the selected report period.


Table 17. Exchange Server IS Public and IS Private Availability report

Name Exchange Server IS Public and IS Private Availability report

Description This report displays the details of the availability of Public and Private InformationStore of the storage group that is selected for the Microsoft Exchange Servers in thecurrent IBM Tivoli Monitoring environment.

Purpose You can use this report to observe the mount or unmount details of IS Public and ISPrivate stores in the storage groups of the Microsoft Exchange Server InformationStore.


Report PeriodSelect the report period from a predefined date range, such as LastWeek, Current Month, Last 30 Days, and so on. You can also entera start date, an end date, and the time for the reporting period.

Start DateSelect a start date from the calendar and the start time from thetime widget. You must select both date and time.

End DateSelect a start date from the calendar and the start time from thetime widget. You must select both date and time.


Summarization TypeSelect the summarization type, such as Hourly, Daily, Weekly,Monthly, Quarterly, Yearly, or Default from the list. If you select theDefault option, the summarization type is calculated according tothe number of days in the date range.

Shift PeriodIf shift period is enabled, the hourly tables display the Shift Periodas 1 (off-peak hours) or 2 (peak hours), depending on the peak andoff-peak hours that are configured in the data warehouse. In thedaily tables, the value 1 corresponds to peak hours, the value 2corresponds to off-peak hours, and the value -1 corresponds to thesummarized value for that day. If shifts are not enabled, the defaultvalue is -1.

Vacation PeriodIf Vacation Period is not enabled, the default value is -1 (All Days).You can enter the value 0 (Work Days) or 1 (Vacation Days), ifVacation Period is enabled.

Display Options


Tables or views used MS_EXCHANGE_IS_PUBLIC_%VMS_EXCHANGE_IS_PRIVATE_%V

Output The IS Public Availability chart displays the mount or unmount status (in percentage)of the IS Public stores for the selected Microsoft Exchange Server.

Usage An IT administrator can use this report to observe the status of the Public andPrivate (mailbox) stores. The status displays the mount or unmount percentage of theinformation store for the selected Microsoft Exchange Server.

Table 18. Exchange Server IS Private Activity report

Name Exchange Server IS Private Activity report


Table 18. Exchange Server IS Private Activity report (continued)

Description This report displays the number of messages submitted, number of messages sent,number of messages delivered, average delivery time, and average local deliverytime in IS Private queue of the selected Microsoft Exchange Server.

Purpose You can use this report to observe the activity of messages in IS Private queue.









Display Options

Server NameSelect the name of the server from the Server Name list. You canselect a single server or all the servers (by selecting All) from thelist.

Tables or views used MS_Exchange_IS_Private_%V

Output The Message Delivery Details chart displays the average delivery time and theaverage local delivery time. The Message Activity Details chart displays themessages submitted, messages sent, and messages delivered. The Microsoft ExchangeMessage Queued for Submission Activity chart displays the number of messages thatare queued for submission.

Usage An IT administrator can use this report to observe the message trends on IS Privateof the Microsoft Exchange Server.

Table 19. Exchange Server I/O Log Details report

Name Exchange Server I/O Log Details report


Table 19. Exchange Server I/O Log Details report (continued)

Description This report displays the rate of the I/O log file read and the I/O log file writeoperations.

Purpose You can use this report to determine the rate of the log file read and writeoperations.









Display Options


Instance NameThe name of the database instance on the selected server.

Tables or views used MS_Exchange_DB_%V

Output The Input Output Log Detail chart displays the I/O log read and I/O log writeoperations over a period of time.

Usage The IT administrator can observe the details of the I/O log read and the I/O logwrite operations.

Table 20. Exchange Server Database Performance report

Name Exchange Server Database Performance report

Description This report displays the activity details of Microsoft Exchange Server database. Thisreport displays the heat map for cache percentage hit and cache page fault.


Table 20. Exchange Server Database Performance report (continued)

Purpose You can use this report to identify the performance of the database of a system orinstance for a period of time using the cache percentage hit and cache page faultattributes.





Display Options


Database NameSelect the name of the database from the Database Name list.



ThresholdsEnter the threshold values that represent the status. The thresholdvalues that you specify are the default threshold values.

Tables or views used MS_Exchange_DB_HV

Output This report displays the cache percentage hit and cache page faults.

Usage An IT administrator can use this report to observe the trends in the MicrosoftExchange database performance.

Table 21. Exchange Server Resource Utilization report

Name Exchange Server Resource Utilization report

Description This report displays the basic information about resource utilization of the MicrosoftExchange Server resources. The following attributes provide details of the resourceutilization by the Microsoft Exchange Server:

v Categorization count

v Storage Group Percent Free Space

Purpose You can use this report to observe the utilization of the Microsoft Exchange Server.


Table 21. Exchange Server Resource Utilization report (continued)


Report PeriodSelect the report period from a predefined date range, such as LastWeek, Current Month, Last 30 Days, and so on. You can also enter astart date, an end date, and the time for the reporting period.







Display Options


Tables or views used MS_EXCHANGE_IS_Private_%V, MSESGRPD_%V

Output The Storage Group Percent Free Space Available chart displays the free space in thestorage group. The X and Y axes represent the following attributes:

v X-axis: System name

v Y-axis: Percentage

The Categorization Count chart displays the categorization count for each MailboxStore. You can drill down to the Microsoft Exchange Server Categorization Countreport. The table following each chart displays the same data for the selected serversor all servers.

Usage An IT administrator can use this report to observe the trends in the MicrosoftExchange Server resource utilization and plan extra resources, if needed. Theadministrator can use the trends to plan the resources, such as the number ofprocessors, increased cache size, and storage.

Table 22. Exchange Server Mailbox Replication Service per MDB Activity report

Name Exchange Server Mailbox Replication Service per MDB Activity report


Table 22. Exchange Server Mailbox Replication Service per MDB Activity report (continued)

Description This report displays the Microsoft Exchange mailbox replication service per MailboxDatabase (MDB) activity detail. This report is applicable to Exchange Server 2010.

Purpose You can use this report to determine the number of completed queues, in progressqueues, failed queues, queued queues, suspended queues, and remote (cross-org)queues in mailbox database queue.









Display Options


Number of Servers to DisplaySpecify the number of servers.

Tables or views used MSEMRSPM_%V

Output The Mailbox Replication Service per MDB Activity is represented as a bar chart. Eachvertical bar corresponds to MDB Queue Completed, MDB Queue Completing, QueueFailed, MDB Queue Queued, MDB Queue Remote, and MDB Queue Suspendedattributes. The X and Y axes represent the following attributes:

v X-axis: Server name

v Y-axis: Mailbox Replication Service per MDB


Table 22. Exchange Server Mailbox Replication Service per MDB Activity report (continued)

Usage The IT administrator can use this report to observe the average number of MDBqueues completed, completing, failed, queued, remote, and suspended.

Table 23. Exchange Server Database Log Activity report

Name Exchange Server Database Log Activity report

Description This report displays the activity details of a database log of the Microsoft ExchangeServer. The administrator can take action about log size by using the followingattributes: Log Record Stalls per second, Log Threads Waiting, and Log Writes persecond.

Purpose You can use this report to observe the activity details of a database log by using logrecords. The IT administrator can use this report to see the hindrances in theMicrosoft Exchange database log.









Display Options


Tables or views used MS_Exchange_DB_%V

Output This report contains three bar charts that display log threads waiting, log recordstalls per second, and log writes per second.


Table 23. Exchange Server Database Log Activity report (continued)

Usage The IT administrator can use this report to observe the trends in the MicrosoftExchange database log activity and arrange physical resources.

Table 24. Exchange Server Categorization Count report

Name Exchange Server Categorization Count report

Description This report displays the categorization count information of the Microsoft ExchangeServer.

Purpose You can use this report to observe the categorization count of the Microsoft ExchangeServer.





Display Options


Instance NameSelect the name of the mailbox database from the Instance Namelist.



ThresholdsEnter the threshold values that represent status. The followingthreshold values are the default threshold values:

v Good: <= 20

v Fair: Between 20 and 30

v Warning: Between 30 and 50

v Bad: Between 50 and 80

v Critical: Above 80

Tables or views used MS_Exchange_IS_Private_HV


Table 24. Exchange Server Categorization Count report (continued)

Output This report displays Categorization Count heat map. The first column of the heatmap displays the dates during the selected time period and the other columnsrepresent 24 hours in the day starting with 0. The last column represents the averagevalue for the day.

Usage An IT administrator can use this report to observe the categorization count of theMicrosoft Exchange database performance.


Chapter 9. Troubleshooting

Problems can be related to IBM Tivoli Monitoring or the specific agent that you are using.

This chapter contains information about how to troubleshoot the Microsoft Exchange Server agent.Troubleshooting is the process of determining why a certain product is malfunctioning.

Note: You can resolve some problems by ensuring that your system matches the system requirementslisted in the Prerequisites topic for the agent in the information center.

This chapter provides agent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information. Also see “Support information” on page269 for other problem-solving options.

Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing with this product, gatherthe following information that relates to the problem:

Table 25. Information to gather before contacting IBM Software Support

Information type Description

Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectoryon the host computer. See “Trace logging” on page 250 for lists of all trace log files andtheir locations. See the Tivoli Enterprise Portal User's Guide for general information aboutthe IBM Tivoli Monitoring environment.

Microsoft ExchangeServer information

Version number and patch level (Select the About item in the Help menu to see thisinformation.)

Operating system Operating system version number and patch level (For example, you can right-click theMy Computer icon and select Properties to obtain this information.)

Messages Messages and other information displayed on the screen

Version numbers forIBM Tivoli Monitoring

Version number and patch level of the members of the monitoring environment.

Screen captures Screen captures of incorrect output, if any.

(UNIX only) Core dumpfiles

If the system stops on UNIX systems, collect core dump file from install_dir/bin directory,where install_dir is the directory path where you installed the monitoring agent.

You can use the pdcollect tool to collect the most commonly used information from a system. This toolgathers log files, configuration information, version information, and other data. For more informationabout using this tool, see the "pdcollect tool" in the IBM Tivoli Monitoring Troubleshooting Guide.

For information about working with IBM Software Support, see IBM Support Portal Service Requests andPMRs (http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)).

Built-in troubleshooting features

The primary troubleshooting feature in the Microsoft Exchange Server agent is logging. Logging refers tothe text messages and trace data generated by the Microsoft Exchange Server agent. Messages and tracedata are sent to a file.


http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

Trace data captures transient information about the current operating environment when a component orapplication fails to operate as designed. IBM Software Support personnel use the captured traceinformation to determine the source of an error or unexpected condition. See “Trace logging” for moreinformation.

Problem classification

The following types of problems might occur with the IBM Tivoli Composite Application Manager forMicrosoft Applications: Microsoft Exchange Server Agent:v Installation and configurationv General usage and operationv Display of monitoring datav Take Action commands

Information about symptoms and detailed workarounds for these types of problems is located in“Problems and workarounds” on page 256. For general troubleshooting information, see the IBM TivoliMonitoring Troubleshooting Guide.

Trace loggingTrace logs capture information about the operating environment when component software fails tooperate as intended. The principal log type is the RAS (Reliability, Availability, and Serviceability) tracelog. These logs are in the English language only.

The RAS trace log mechanism is available for all components of IBM Tivoli Monitoring. Most logs arelocated in a logs subdirectory. See the following sections to learn how to configure and use trace logging:v “Principal trace log files” on page 251v “Viewing trace logs” on page 252v “Setting RAS trace parameters” on page 254

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as "RAS1".

IBM Software Support uses the information captured by trace logging to trace a problem to its source orto determine why an error occurred. The default configuration for trace logging, such as whether tracelogging is enabled or disabled and trace level, depends on the source of the trace logging. Trace loggingis always enabled.

Overview of log file managementLog files have naming conventions.

“Principal trace log files” on page 251 provides the names, locations, and descriptions of RAS1 log files.The log file names adhere to the following naming convention:

hostname_product_program_timestamp-nn.log

where:v hostname is the host name of the machine on which the monitoring component is running.v product is the two-character product code. For Microsoft Exchange Server agent, the product code is ex.v program is the name of the program being run.v timestamp is an 8-character hexadecimal timestamp representing the time at which the program started.v nn is a rolling log suffix. See “Examples of trace logging” on page 253 for details of log rolling.


Principal trace log filesTrace log files are located on various systems.

Table 26 contains locations, file names, and descriptions of trace logs that can help determine the sourceof problems with agents.

Table 26. Trace log files for troubleshooting agents

System where logis located

File name and path Description

On the computerthat hosts themonitoring agent

See Definitions ofvariables fordescriptions of thevariables in thefile names incolumn two.

The RAS1 log files are named ashostname_ex_program_timestamp-nn.log The logsare available in the following directories:

v For the 32-bit agent: install_dir\TMAITM6\logs

v For the 64-bit agent: install_dir\TMAITM6_x64\logs

Note: File names for RAS1 logs include ahexadecimal time stamp.

Traces activity of the monitoring agent.Note: Other logs, such as logs for collectorprocesses and Take Action commands (ifavailable), have a similar syntax and arelocated in this directory path.

The *.LG0 file is located in theinstall_dir\tmaitm6\logs path.

A new version of this file is generatedevery time the agent is restarted. IBM TivoliMonitoring generates one backup copy ofthe *.LG0 file with the tag .LG1. View .LG0to learn the following details regarding thecurrent monitoring session:v Status of connectivity with the

monitoring server.v Situations that were running.v The success or failure status of Take

Action commands.

On the TivoliEnterpriseMonitoring Server


On UNIX: The candle_installation.log file inthe install_dir/logs path.

On Windows: The IBM Tivoli Monitoringtimestamp.log file in the install_dir\InstallITMpath. Unlike RAS1 log files, the name of the filedisplays a decimal time stamp. *

Provides details about products that areinstalled.Note: Trace logging is enabled by default.A configuration step is not required toenable this tracing.

The configuration log file for the Warehouse Proxyagent is located in the following path dependingon the operating system that you are using:

v Windows: install_dir\InstallITM\Warehouse_Configuration.log

v UNIX: install_dir\logs\KHDCFG.log

Provides details about the configuration ofdata warehousing for historical reporting.

The RAS1 log file is namedhostname_ms_timestamp-nn.log and is located inthe following path:

v On Windows: install_dir\logs

Note: File names for RAS1 logs include ahexadecimal time stamp

Also on UNIX, a log with a decimal time stampis provided: hostname_ms_timestamp.log andhostname_ms_timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn is theprocess ID.

Traces activity on the monitoring server.

Chapter 9. Troubleshooting 251

Table 26. Trace log files for troubleshooting agents (continued)

System where logis located

File name and path Description

On the TivoliEnterprise PortalServer


The RAS1 log file is namedhostname_cq_timestamp-nn.log and is located inthe following path:

v On Windows: install_dir\logs

v On UNIX: install_dir/logs

Note: File names for RAS1 logs include ahexadecimal time stamp

Also on UNIX, a log with a decimal time stampis provided: hostname_cq_timestamp.log andhostname_cq_timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn is the process ID.

Traces activity on the portal server.

The TEPS_ODBC.log file is located in the followingpath on Windows: install_dir\InstallITM.

When you enable historical reporting, thislog file traces the status of the warehouseproxy agent.

Definitions of variables:

v timestamp is a time stamp with a format that includes year (y), month (m), day (d), hour (h), and minute (m), asfollows: yyyymmdd hhmm

v HEXtimestamp is a hexadecimal representation of the time at which the process was started.

v install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir canrepresent a path on the computer that hosts the monitoring system, the monitoring agent, or the portal.

v instance refers to the name of the database instance that you are monitoring.

v instance_name refers to the name of the agent instance.

v hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs.

v nn represents the circular sequence in which logs are rotated. this value includes a range from 1 - 5, by default.The first is always retained because it includes configuration parameters.

v productcode specifies the product code, for example, um for Universal Agent or nt for Windows systems.

See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the complete set oftrace logs that are maintained on the monitoring server.

Viewing trace logsTypically IBM Software Support applies specialized knowledge to analyze trace logs to determine thesource of problems. However, you can open trace logs in a text editor such as vi to learn some basic factsabout your IBM Tivoli Monitoring environment. You can use the ls -ltr command to list the log files inthe install_dir/logs directories, sorted by time they were last updated.

About this task

This task provides information about viewing trace logs.

Procedure

On Windows, you can use the following method to view trace logs:1. In the WindowsStart menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli

Monitoring Service. The Manage Tivoli Enterprise Monitoring Services window is displayed.2. Right-click a component and select Advanced > View Trace Log in the pop-up menu. The program

displays the Select Log File window that lists the RAS1 logs for the monitoring agent.3. Select a log file from the list and click OK. You can also use this viewer to access remote logs.


Note: The viewer converts time stamps in the logs to a readable format.

Examples of trace loggingFor example, if a Microsoft Exchange Server monitoring agent is running on a server "server01", the RASlog file for the Microsoft Exchange Server agent might be named as follows:server01_ex_kexcma_437fc59-01.log

For long-running programs, the nn suffix is used to maintain a short history of log files for that startup ofthe program. For example, the kexcma program might have a series of log files as follows:server01_ex_kexcma_437fc59-01.logserver01_ex_kexcma_437fc59-02.logserver01_ex_kexcma_437fc59-03.log

As the program runs, the first log (nn=01) is preserved because it contains program startup information.The remaining logs "roll." In other words, when the set of numbered logs reach a maximum size, theremaining logs are overwritten in sequence.

Each time a program is started, a new timestamp is assigned to maintain a short program history. Forexample, if the Microsoft Exchange Server agent is started twice, it might have log files as follows:server01_ex_kexcma_437fc59-01.logserver01_ex_kexcma_437fc59-02.logserver01_ex_kexcma_437fc59-03.log

server01_ex_kexcma_537fc59-01.logserver01_ex_kexcma_537fc59-02.logserver01_ex_kexcma_537fc59-03.log

Each program that is started has its own log file. For example, the Microsoft Exchange Server agentwould have agent logs in this format:server01_ex_kexcma_437fc59-01.log

Other logs, such as logs for agent configuration window and Take Action commands, have a similarsyntax as in the following example:server01_ex_stopexchangeservices_447fc59-01.log

where stopexchangeservices is the program name.When the agent sends mail to the Exchange users to check their reachability, the following log file isgenerated:PS0313_ex_kexsendemail_4c0e42bd-01.log

Note: The log file is generated only in Exchange Server 2003 and 2007.

Note: When you communicate with IBM Software Support, you must capture and send the RAS1 logthat matches any problem occurrence that you report.

Microsoft Exchange Server agent stores data for the attribute groups in a log file. This log file is used todisplay the data on the Tivoli Enterprise Portal. The log files for the attribute groups are listed in thefollowing table.

Table 27. Log files for the attribute groups

Attribute group Log file

MS Exchange Reachability attribute group MailBox_Reachability_Results.log


Table 27. Log files for the attribute groups (continued)

Attribute group Log file

MS Exchange Mailbox Detail attribute group MailBox_Details.log

Note: This log file is generated by thembxsdetails2010.ps1 script only on Microsoft ExchangeServer 2010.

MS Exchange IS Private attribute group Mseispri_history.log

mbxstorestate2007.lo

mbxstorestate2003.log

mbxstorestate2010.log

MS Exchange IS Public attribute group Mseispub_history.log

MS Exchange Role Topology attribute group topology_details.log

MS Exchange Mailbox Server Cluster State attributegroup

clustermailboxserverstate.log

MS Exchange NLB Status attribute group nlbstatus.log

MS Exchange Public Folder Detail attribute group PublicFolderDetails2010.logNote: This log file is generated by thePublicFolderDetails2010.ps1 script only on MicrosoftExchange Server 2010.

MS Exchange Replication StorageGroupCopyStatus.logNote: This log file is generated by theStorageGroupCopyStatus.ps1 script only on MicrosoftExchange Server 2007.

MailboxDatabaseCopyStatus.logNote: This log file is generated by theMailboxDatabaseCopyStatus.ps1 script only on MicrosoftExchange Server 2010.

Setting RAS trace parametersPinpoint a problem by setting detailed tracing of individual components of the monitoring agent andmodules.

Before you begin

See “Overview of log file management” on page 250 to ensure that you understand log rolling and canreference the correct log files when you managing log file generation.

About this task

Microsoft Exchange Server agent uses RAS1 tracing and generates the logs described in Table 26 on page251. The default RAS1 trace level is ERROR.

RAS1 tracing has control parameters to manage the size and number of RAS1 logs. Use the proceduredescribed in this section to set the parameters.

Note: The KBB_RAS1_LOG parameter also provides the specification of the log file directory, log file name,and the inventory control file directory and name. Do not modify these values or log information can belost.


Specify RAS1 trace options in the KEXENV file. You can manually edit the configuration file to set tracelogging:1. Open the trace options file:install_dir\tmaitm6\KEXENV.2. Edit the line that begins with KBB_RAS1= to set trace logging preferences.

For example, if you want detailed trace logging, set the Maximum Tracing option:KBB_RAS1=ERROR (UNIT:kex ALL) (UNIT:kra ALL) (UNIT:knz ALL)

3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:v Edit the following parameters to adjust the number of rolling log files and their size.

– MAXFILES: the total number of files that are to be kept for all startups of a given program. Oncethis value is exceeded, the oldest log files are discarded. Default value is 9.

– LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5.v IBM Software Support might guide you to modify the following parameters:

– COUNT: the number of log files to keep in the rolling cycle of one program startup. Default valueis 3.

– PRESERVE: the number of files that are not to be reused in the rolling cycle of one programstartup. Default value is 1.

Note: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log filename, and the inventory control file directory and name. Do not modify these values or loginformation can be lost.

4. Restart the monitoring agent so that your changes take effect.

Procedure

(Windows only) Alternate method to edit trace logging parameters:

1. Open the Manage Tivoli Enterprise Monitoring Services window.2. Right-click the icon of the monitoring agent whose logging you want to modify.3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters

window is displayed.4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid

string.The selections are as follows:v No error tracing. KBB_RAS1=-none-v General error tracing. KBB_RAS1=ERRORv Intensive error tracing. KBB_RAS1=ERROR (UNIT:kex ALL)

v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kex ALL) (UNIT:kra ALL) (UNIT:knz ALL)

Note: As this example shows, you can set multiple RAS tracing options in a single statement.5. Modify the value for Maximum Log Size Per File (MB) field to change the log file size (changes

LIMIT value).6. Modify the value for Maximum Number of Log Files Per Session field to change the number of logs

files per startup of a program (changes COUNT value).7. Modify the value for Maximum Number of Log Files Total field to change the number of logs files

for all startups of a program (changes MAXFILES value).8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you

diagnose communications and connectivity problems between the monitoring agent and themonitoring server.


Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amountof trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, thelogs can occupy excessive amounts of hard disk space.

9. Click OK. You see a message reporting a restart of the monitoring agent so that your changes takeeffect.

What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 to 60 MB for each agentthat is running on a computer. For example, each Exchange Server that you monitor could generate 45 to60 MB of log data. See the "Procedure" section to learn how to adjust file size and numbers of log files toprevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log fileswhich are pruned automatically, other log types can grow indefinitely, for example, the logs in Table 26on page 251 that include a process ID (PID).

Consider using collector trace logs (described in Table 26 on page 251) as an additional source oftroubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount oftrace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logscan occupy excessive amounts of hard disk space.

Problems and workaroundsThe known problems and workarounds are organized into types of problems that might occur with theMicrosoft Exchange Server agent, for example installation and configuration problems and workspaceproblems.

Note: You can resolve some problems by ensuring that your system matches the system requirementslisted in the Prerequisites topic for the agent in the information center.For general troubleshooting information, see the IBM Tivoli Monitoring Troubleshooting Guide.

Installation and configuration troubleshootingProblems can occur during installation, configuration, and uninstallation of the agent.

The problems and solutions in Table 28 can occur during installation, configuration, and uninstallation ofthe agent.

Table 28. Problems and solutions for installation and configuration

Problem Solution

(UNIX only) During a command-line installation,you choose to install a component that is currentlyinstalled, and you see the following warning:WARNING - you are about to install the SAMEversion of "component_name" wherecomponent_name is the name of the component thatyou are attempting to install.Note: This problem affects UNIX command-lineinstallations. If you monitor only Windowsenvironments, you see this problem if you chooseto install a product component (for example, amonitoring server) on a UNIX system.

You must exit and restart the installation process. You cannotreturn to the list where you selected components to install.When you run the installer again, do not attempt to install anycomponent that is currently installed.


Table 28. Problems and solutions for installation and configuration (continued)

Problem Solution

A problem can arise when you install andconfigure a new monitoring agent to a computerwhere other agents are running as described inthis example:

v Agents are running on the computer andcommunicating with a Tivoli EnterpriseMonitoring Server, called TEMS1.

v You install a new agent on the same computerand you want this agent to communicate with adifferent monitoring server, called TEMS2.

v When you configure the new agent tocommunicate with TEMS2, all the existingagents are re-configured to communicate withTEMS2.

You must reconfigure the previously existing agents to restoretheir communication connection with TEMS1. For example, youcan right-click the row for a specific agent in the Manage TivoliEnterprise Monitoring Services, and select Reconfigure. See theIBM Tivoli Monitoring Installation and Setup Guide for moreinformation on reconfiguration.

Diagnosing problems with product browsesettings.

When you have problems with browse settings, perform thefollowing steps:

1. Click Start > Programs > IBM Tivoli Monitoring > ManageTivoli Enterprise Monitoring Services. The Manage TivoliEnterprise Monitoring Services is displayed.

2. Right-click the Windows agent and select Browse Settings.A text window is displayed.

3. Click Save As and save the information in the text file. Ifrequested, you can forward this file to IBM SoftwareSupport for analysis.

A message similar to Unable to find running CMSon CT_CMSLIST in the log file is displayed.

If a message similar to Unable to find running CMS onCT_CMSLIST is displayed in the Log file, the agent cannotconnect to the monitoring server. Confirm the following points:

v Do multiple network interface cards (NICs) exist on thesystem?

v If multiple NICs exist on the system, find out which one isconfigured for the monitoring server. Ensure that you specifythe correct host name and port settings for communication inthe IBM Tivoli Monitoring environment.

The system is experiencing high CPU usage. Agent process: View the memory usage of the KEXCMAprocess. If CPU usage seems to be excessive, recycle themonitoring agent.

Network Cards: The network card configurations can decreasethe performance of a system. Each of the stream of packets thata network card receives (assuming it is a broadcast or destinedfor the under-performing system) must generate a CPUinterrupt and transfer the data through the I/O bus. If thenetwork card in question is a bus-mastering card, work can beoff-loaded and a data transfer between memory and thenetwork card can continue without using CPU processingpower. Bus-mastering cards are generally 32-bit and are basedon PCI or EISA bus architectures.


Table 28. Problems and solutions for installation and configuration (continued)

Problem Solution

You have installed an agent of ITCAM forMicrosoft Applications remotely from the TivoliEnterprise Portal Client. On the Agent tab of theManaged System Configuration window, youselected the Use this account option, and typedthe account information in the "[email protected]"format (for example,[email protected]). The DeploymentStatus Detail view shows the agent deploymentstatus as failed; however, the agent is configuredand installed with the LocalSystem accountinstead of the specified user account.

Specify the account information in the domain\user format.

When you use the Installation Launch Pad toinstall a 32-bit agent on a 32-bit computer, thefollowing message is displayed: The followingcomponents cannot be installed because theinstallation action failed. IBM TivoliComposite Application Manager for MicrosoftApplications V6.2.3 for Windows on 64-bit AMDand Intel systems (x64)

No action is required. You can ignore this message and continuewith the installation.

Table 29. General problems and solutions for uninstallation

Problem Solution

On Windows, uninstallation of IBM TivoliMonitoring fails to uninstall the entireenvironment.

Confirm that the following problems do not exist:

v Ensure that you are the only user who is logging into thecomputer where you are performing an uninstallationoperation. If another user is performing operations during anuninstall process, the uninstall process fails.

v Be sure that you follow the general uninstallation processdescribed in the IBM Tivoli Monitoring Installation and SetupGuide:

1. Uninstall monitoring agents first, as in the followingexamples:

– Uninstall a single monitoring agent for a specificdatabase.

—OR—

– Uninstall all instances of a monitoring product, such asIBM Tivoli Monitoring for Databases.

2. Uninstall IBM Tivoli Monitoring.

The way to remove inactive managed systems(systems whose status is OFFLINE) from theEnterprise Navigation tree in the portal is notobvious.

Use the following steps to remove, but not uninstall, an offlinemanaged system from the Navigation tree:

1. Click the Enterprise icon in the Navigator tree.

2. Right-click, then click Workspace > Managed System Status.

3. Right-click Offline managed system, and select Clearoffline entry.

If you also want to uninstall the monitoring agent, use theprocedure described in the IBM Tivoli Monitoring Installation andSetup Guide.


Table 29. General problems and solutions for uninstallation (continued)

Problem Solution

When starting the Microsoft Exchange Agent twopopup windows are displayed. The first windowdisplays a message similar to Service did notrespond to the start or control request in atimely fashion. The second window displays amessage similar to Unable to start service, seeEvent Log for information.

This can happen on Microsoft Exchange Server 2007 when theservice has failed to start because MAPI32.dll was not found.

Install the MSExchangeMAPIcdo, MAPI, and CDO support forMicrosoft Exchange Server 2007 from the Microsoft Supportwebsite (http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en).

Unique names for monitoring componentsIBM Tivoli Monitoring automatically creates a name for each monitoring component by concatenating thehost name and product code separated by a colon (hostname:EX). When you monitor a multinode system,such as a database, IBM Tivoli Monitoring adds a subsystem name to the concatenated name, typically adatabase instance name. The length of the name that IBM Tivoli Monitoring generates is limited to 32characters. IBM Tivoli Monitoring might not be able to generate a unique name for monitoringcomponents due to the truncation of names that the product automatically generates. Truncation canresult in multiple components having the same 32-character name.

About this task

This task provides information about resolving the problem of generating the unique names for themonitoring components.

Procedure

To resolve this problem, shorten the hostname portion of the name as follows:1. Open the configuration file for the monitoring agent: install_dir\tmaitm6\KEXCMA.INI2. Find the line the begins with CTIRA_HOSTNAME=

3. Replace the existing string (which includes a variable and type parameter) with a unique, shortername for the host computer. The final concatenated name including the new host name and EX,cannot be longer than 32 characters.

Note: You must ensure that the resulting name is unique with respect to any existing monitoringcomponent that was previously registered with the Tivoli Enterprise Monitoring Server.

4. Save the file.5. Restart the agent.

Remote deployment troubleshootingProblems can occur with remote deployment and removal of agent software using the Agent RemoteDeploy process.

Table 30 on page 260 contains problems and solutions related to remote deployment.




Table 30. Remote deployment problems and solutions

Problem Solution

While you are using the remote deployment featureto install Microsoft Exchange Server agent, an emptycommand window is displayed on the targetcomputer. This problem occurs when the target ofremote deployment is a Windows computer. (See theIBM Tivoli Monitoring Installation and Setup Guide formore information on the remote deploymentfeature.)

Do not close or modify this window because is part of theinstallation process and is dismissed automatically.

The removal of a monitoring agent fails when youuse the remote removal process in the TivoliEnterprise Portal desktop or browser.

This problem might happen when you attempt the remoteremoval process immediately after you have restarted theTivoli Enterprise Monitoring Server. You must allow time forthe monitoring agent to refresh its connection with the TivoliEnterprise Monitoring Server before you begin the remoteremoval process.

When you remotely deploy the Exchange Serveragent V6.3 from the Tivoli Enterprise Portal, theagent does not display data for the MS Exchange IsPrivate attribute group and the MS Exchange ISPublic attribute group.

Restart the agent after remote deployment completes.

Agent troubleshootingA problem can occur with the agent after it has been installed.

Table 31 contains problems and solutions that can occur with the agent after it has been installed.

Table 31. Agent problems and solutions

Problem Solution

Log data accumulates toorapidly.

Check the RAS trace option settings, which are described in “Setting RAS traceparameters” on page 254. For example, trace logs grow rapidly when you applythe ALL logging option.

Performance Data is notretrieved for someWindows-based agents.

The Microsoft Exchange Server agent collects data from Windows PerformanceMonitor (Perfmon), Active Directory, and Exchange Server interfaces.

Under certain circumstances the monitoring agent is unable to retrieve data fromone or all of these sources resulting in no data available for situations, workspaceviews, or historical logging.

If you suspect Perfmon problems the Windows operating system detects aproblem in one of its extensible performance monitoring DLLs, it marks the DLLas "disabled." Any DLL that is disabled can no longer provide performance datathrough the Windows Performance Monitor interfaces (Perfmon, or PerformanceMonitor APIs). This prevents IBM Tivoli Monitoring agents from gathering datasupplied by the disabled DLL. For more information, see Microsoft SupportKnowledge Base article 248993 (http://support.microsoft.com/kb/248993).

Follow the Resolution instructions provided in article 248993 to re-enable anyperformance monitoring extension DLLs disabled by Windows. Then restart themonitoring agents.

If you suspect Active Directory or Exchange Server access problems review thepermissions setting for the user ID the monitoring agent is running as.


http://support.microsoft.com/kb/248993


Table 31. Agent problems and solutions (continued)

Problem Solution

The values of certain counteritems under the MicrosoftExchange MTA attribute groupdo not change and are largerthan expected in PerformanceMonitor in Exchange Server2003.

In Performance Monitor, you may notice that the values of the following counteritems under the Microsoft Exchange MTA attribute group do not change:

v Work Queue Bytes

v Inbound KB Total

v Outbound KB Total

Install a patch from the Microsoft support website (http://support.microsoft.com/kb/926869).

The mailbox space is low. Themailbox is accumulating largeamount of data because itreceives emails that the Exchangeagent sends to verify reachability.

The Exchange Server agent sends emails to remote Exchange Servers to verifyreachability. The agent receives automated email responses from the remoteExchange Servers. Depending on the reachability interval, the number of emailresponses in the inbox might become quite large. To keep the agent processingtime low, clean out the inbox periodically. You can do this manually with a toolsuch as MapiEdit from Microsoft, by scheduling a Windows Script to clear outthe inbox.

The Monitoring Agent for Microsoft Exchange Server has a built-in option todelete each automated response after it is analyzed for the response time. Thisoption keeps the mailbox cleared when the agent is running. To enable thisoption, you must create the KEX_DELETE_EMAILSenvironment variable, and set thevalue of the variable to YES. To activate this option, you must restart theExchange Server agent.

If a new mailbox database or astorage group is created whenthe agent is running, the agentdoes not collect data for the newmailbox database or the storagegroup from the MS ExchangeReplication Perfmon object.

Restart the agent.

Remote agent configuration byusing the Tivoli Enterprise Portalor the command line fails for anon-English user.

There is no solution to this problem.

On the Tivoli Enterprise Portal,data is not displayed correctlyfor the Last Scan Time (UTC)attribute.


When the agent is configured inthe Continuous ClusterReplication (CCR) environment,the Tivoli Enterprise Portal doesnot display the complete name ofthe ADAccess Process instance.The instance name is truncatedwhen it contains a specialcharacter in the name, such asthe number sign (#).




Table 31. Agent problems and solutions (continued)

Problem Solution

Data is not displayed on theTivoli Enterprise Portal for theStorage Group Name attribute ifthe following conditions are true:

v The storage group name is asubstring of any other storagegroup name.

v The storage group does nothave a mailbox database.

Create a storage group that has a mailbox database or a public folder database,and ensure that the storage group name is not a substring of any other storagegroup name.

You have configured themonitoring agent version 6.3 onthe Tivoli Enterprise MonitoringServer by using theself-describing agent feature. Youare using IBM Tivoli Monitoringversion 6.2.3 or version 6.2.3 FixPack 1. On the Tivoli EnterprisePortal, if you open a situation byusing the Situation Editor andview the advance options for thesituation, you can see <noneselected> in the Display Itemwindow.

Recycle the Tivoli Enterprise Portal Server.

Complete the following steps to recycle the Tivoli Enterprise Portal Server onWindows systems:

1. On the computer where the Tivoli Enterprise Portal Server is installed, clickStart > Programs > Manage Tivoli Enterprise Monitoring Services.

2. Right-click the Tivoli Enterprise Portal Server service and click Recycle.

To recycle the Tivoli Enterprise Portal Server on UNIX systems, use the followingcommands from the bin directory of /opt/IBM/ITM (or where you have installedIBM Tivoli Monitoring) in the order shown below:

v ./itmcmd agent stop cq

v ./itmcmd agent start cq

Workspace troubleshootingProblems can occur with general workspaces and agent-specific workspaces.

Table 32 contains problems and solutions related to workspaces.

Table 32. Workspace problems and solutions

Problem Solution

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute's name.

At the bottom of each view, you see thefollowing Historical workspace KFWITM220Eerror: Request failed during execution.

Ensure that you configure all groups that supply data to theview. In the Historical Configuration view, ensure that datacollection is configured and started for all groups that supplydata to the view.


Table 32. Workspace problems and solutions (continued)

Problem Solution

The process application components areavailable, but the Availability status showsPROCESS_DATA_NOT_ AVAILABLE.

This problem occurs because the PerfProc performance object isdisabled. When this condition exists, IBM Tivoli Monitoringcannot collect performance data for this process. Use thefollowing steps to confirm that this problem exists and to resolveit:

1. In the Windows Start menu, click Run.

2. Type perfmon.exe in the Open field of the Run window. ThePerformance window is displayed.

3. Click the plus sign (+) in the toolbar located above the rightpane. The Add Counters window is displayed.

4. Look for Process in the Performance object menu.

5. Complete one of the following actions:

v If you see Process in the menu, the PerfProc performanceobject is enabled and the problem is coming from adifferent source. You might need to contact IBM SoftwareSupport.

v If you do not see Process in the menu, use the Microsoftutility from the Microsoft.com Operations website toenable the PerfProc performance object.

The Process performance object becomes visible in thePerformance object menu of the Add Counters windows,and IBM Tivoli Monitoring is able to detect Availabilitydata.

6. Restart the monitoring agent.

When you use a long process name in thesituation, the process name is truncated.

Truncation of process or service names for situations in theAvailability table in the portal display is the expected behavior.The maximum name length is 100 bytes.

Regular (non-historical) monitoring data fails tobe displayed.

Check the formation of the queries you use to gather data. Forexample, look for invalid SQL statements.

Navigator items and workspace titles are labeledwith internal names such as Kxx:KXX0000 insteadof the correct names (such as Disk), where XXand xx represent the two-character agent code.

Ensure that application support has been added on themonitoring server, portal server, and portal client.

For more information about installing application support, seeInstalling and enabling application support in the IBM TivoliMonitoring Installation and Setup Guide.

You start collection of historical data but the datacannot be seen.

Managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See Chapter 2, “Agent installation and configuration,” on page9 for information on managing this feature including how toset the interval at which data is collected. By setting a morefrequent interval for data collection you reduce the load on thesystem incurred every time data is uploaded.

v You use the Summarization and Pruning monitoring agent tocollect specific amounts and types of historical data. Be awarethat historical data is not displayed until the Summarizationand Pruning monitoring agent begins collecting the data. Bydefault, this agent begins collection at 2 AM daily. At thatpoint, data is visible in the workspace view. See the IBM TivoliMonitoring Administrator's Guide to learn how to modify thedefault collection settings.


http://blogs.technet.com/b/mscom/archive/2008/12/18/the-mystery-of-the-missing-process-performance-counter-in-perfmon.aspx

Table 32. Workspace problems and solutions (continued)

Problem Solution

You have installed the ITCAM for MicrosoftApplications agent and the Windows OS agent inthe IPV6 environment. In the AgentManagement Services navigator, the IP addressin the Agents’ Runtime Status view is displayedin the IPV4 format instead of the IPV6 format.


You have installed the Tivoli EnterpriseMonitoring Server on z/OS®. In theConfiguration panel of the History CollectionConfiguration window, if you have selectedTEMS from the Collection Location list, then theTivoli Enterprise Portal does not displayhistorical data for all the attribute groups.

Reconfigure the history collection and set the collection locationas TEMA for these attribute groups.

When you create a query from a compositeworkspace, some attribute groups are notavailable for selection in the list of attributegroups.


Situation troubleshootingProblems can occur with situations and situation configuration.

Table 33 contains problems and solutions for situations.

Table 33. Situation problems and solutions

Problem Solution

You want to change the appearance ofsituations when they are displayed in aWorkspace view.

1. Right-click an item in the Navigation tree.

2. Select Situations in the pop-up menu. The Situation Editor window isdisplayed.

3. Select the situation that you want to modify.

4. Use the Status pull-down menu in the lower right of the window toset the status and appearance of the Situation when it triggers.Note: This status setting is not related to severity settings in IBMTivoli Enterprise Console.

Monitoring activity requires too muchdisk space.

Check the RAS trace logging settings that are described in “Setting RAStrace parameters” on page 254. For example, trace logs grow rapidlywhen you apply the ALL logging option.

Monitoring activity requires too manysystem resources.

“Disk capacity planning for historical data” on page 206 describes theperformance impact of specific attribute groups. If possible, decrease youruse of the attribute groups that require greater system resources.

A formula that uses mathematicaloperators appears to be incorrect. Forexample, if you were monitoring Linux,a formula that calculates when FreeMemory falls under 10 percent of TotalMemory does not work: LT#’Linux_VM_Stats.Total_Memory’ / 10

This formula is incorrect because situation predicates support only logicaloperators. Your formulas cannot have mathematical operators.Note: The Situation Editor provides alternatives to math operators.Regarding the example, you can select % Memory Free attribute andavoid the need for math operators.


Table 33. Situation problems and solutions (continued)

Problem Solution

You see the Unable to get attributename error in the Tivoli EnterpriseMonitoring Server log after creating asituation.

Ensure that the agent attribute files are installed on the Tivoli EnterpriseMonitoring Server.

The following example shows a typical log entry when you have thisproblem:

(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \Unable to get attribute name for tablename/column \<UAG524400.UA4>. Ignored.

The situation for a specific agent is notvisible in the Tivoli Enterprise Portal.

v Open the Situation Editor. Access the All managed servers view. If thesituation is absent, confirm that application support for MicrosoftExchange Server agent has been added to the monitoring server. If not,add application support to the server, as described in the IBM TivoliMonitoring Troubleshooting Guide.

v Click the Action tab and check whether the situation has an automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event orthe update in the graphical user interface.

The monitoring interval is too long. Access the Situation Editor view for the situation that you want tomodify. Check the Sampling interval area in the Formula tab. Adjust thetime interval as needed.

The situation did not activate at startup. Manually recycle the situation as follows:

1. Right-click the situation and choose Stop Situation.

2. Right-click the situation and choose Start Situation.

Note: You can permanently avoid this problem by placing a check markin the Run at Startup option of the Situation Editor view for a specificsituation.

The situation is not displayed. Click the Action tab and check whether the situation has an automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event orthe update in the graphical user interface.

An Alert event has not occurred eventhough the predicate has been properlyspecified.

Check the logs, reports, and workspaces.

A situation fires on an unexpectedmanaged object.

Confirm that you distributed and started the situation on the correctmanaged system.

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for thesituation.

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for thesituation.



Problem Solution

The situation does not fire.

Incorrect predicates are present in theformula that defines the situation. Forexample, the managed object shows astate that normally triggers a monitoringevent, but the situation is not truebecause the wrong attribute is specifiedin the formula.

In the Formula tab, analyze predicates as follows:

1. Click the fx icon in the upper-right corner of the Formula area. TheShow formula window is displayed.

a. Confirm the following details in the Formula area at the top of thewindow:v The attributes that you intend to monitor are specified in the

formula.v The situations that you intend to monitor are specified in the

formula.v The logical operators in the formula match your monitoring

goal.v The numerical values in the formula match your monitoring

goal.

b. (Optional) Click the Show detailed formula check box in the lowerleft of the window to see the original names of attributes in theapplication or operating system that you are monitoring.

c. Click OK to dismiss the Show formula window.

2. (Optional) In the Formula area of the Formula tab, temporarily assignnumerical values that will immediately trigger a monitoring event.The triggering of the event confirms that other predicates in theformula are valid.Note: After you complete this test, you must restore the numericalvalues to valid levels so that you do not generate excessive monitoringdata based on your temporary settings.

Situation events are not displayed in theEvents Console view of the workspace.

Associate the situation with a workspace.Note: The situation does not need to be displayed in the workspace. It issufficient that the situation be associated with any workspace.

You do not have access to a situation. Note: You must have administrator privileges to perform these steps.

1. Select Edit > Administer Users to access the Administer Userswindow.

2. In the Users area, select the user whose privileges you want tomodify.

3. In the Permissions tab, Applications tab, and Navigator Views tab,select the permissions or privileges that correspond to the user's role.

4. Click OK.

A managed system seems to be offline. 1. Allow several minutes to pass whenever you restart the TivoliEnterprise Portal Server. A managed system will seem to be downwhile the portal server is restarting.

2. Select Physical View and highlight the Enterprise Level of thenavigator tree.

3. Select View > Workspace > Managed System Status to see a list ofmanaged systems and their status.

4. If a system is offline, check network connectivity and status of thespecific system or application.



Problem Solution

When a situation is triggered in theEvent Log attribute group, it remains inthe Situation Event Console as long asthe event ID entry is present in theEvent Log workspace. When this eventID entry is removed from the Event Logworkspace on the Tivoli EnterprisePortal, the situation is also cleared evenif the actual problem that caused theevent is not resolved, and the event IDentry is also present in the WindowsEvent Viewer.

A timeout occurs on the cache of events for the NT Event Log group.Increase the cache time of Event Log collection to meet your requirementsby adding the following variable and timeout value to the KpcENV file forthe agent (where pc is the two-letter product code):CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600

This variable determines how long events from the NT Event Log arekept.

Associations of custom situations withnavigator items break after upgradingthe agent support.

Create the associations again by completing the following steps:

1. Right-click the navigator item, and then click Situations. A list ofsituations that are associated with the navigator item is displayed.Note: If the custom situation that you want to associate is available inthe list, ignore remaining steps.

2. Click the Set Situation filter criteria icon.

3. Select the Eligible for Association check box, and then click OK. Alist of situations is displayed.

4. Right-click the situation that you want to associate with the navigatoritem, and then click Associate.

The situation is associated with the navigator item.

When you create a custom situation,some attribute groups are not availablefor selection in the list of attributegroups.


Take Action commands troubleshootingProblems can occur with Take Action commands.

Table 34 lists general problems that might occur with Take Action commands. When each Take Actioncommand runs, it generates a log file listed in Table 26 on page 251.

Table 34. Take Action commands problems and solutions

Problem Solution

Take Action commands often require severalminutes to complete.

Allow several minutes. If you do not see a pop-up messageadvising you of completion, try to run the command manually.If you are unable to run the Take Action command manually, seethe IBM Tivoli Monitoring Troubleshooting Guide for generalinformation on troubleshooting the Take Action command.

Situations fail to trigger Take Action commands. Manually run the Take Action commands in the Tivoli EnterprisePortal. If the Take Action command works, look forconfiguration problems in the situation. See Situationstroubleshooting. If the Take Action command fails, see IBM TivoliMonitoring Troubleshooting Guide for general information ontroubleshooting Take Action commands.


Table 34. Take Action commands problems and solutions (continued)

Problem Solution

Take Action commands fail and other metrics arenot collected.

The Microsoft Exchange Server agent collects data fromWindows Performance Monitor (Perfmon), Active Directory, andExchange Server interfaces.

Under certain circumstances the monitoring agent will be unableto retrieve data from one or all of these sources resulting in nodata available for situations, workspace views or historicallogging.

If you suspect Perfmon problems, the Windows operatingsystem detects a problem in one of its extensible performancemonitoring DLLs, it will mark the DLL as "disabled." Any DLLthat is disabled can no longer provide performance data throughthe Windows Performance Monitor interfaces (Perfmon, orPerformance Monitor APIs). This prevents IBM TivoliMonitoring agents from gathering data supplied by the disabledDLL. For more information, see Microsoft Support KnowledgeBase article 248993.

Follow the Resolution instructions provided in article 248993 tore-enable any performance monitoring extension DLLs disabledby Windows. Then restart the monitoring agents.

If you suspect Active Directory or Exchange Server accessproblems review the permissions setting for the user ID themonitoring agent is running as.

Tivoli Common Reporting troubleshootingProblems can occur with the Tivoli Common Reporting predefined reports for the Microsoft ExchangeServer agent.

Table 35 contains problems and solutions that can occur with the Tivoli Common Reporting predefinedreports for IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft ExchangeServer Agent. See the Tivoli Common Reporting Information Center for more information abouttroubleshooting for the Tivoli Common Reporting tool.

Table 35. Tivoli Common Reporting for Microsoft Exchange Server agent problems and solutions

Problem Solution

When you simultaneously query two tables in the QueryStudio interface, no data is displayed. However, whenyou query the two tables separately, data is displayed.

This problem occurs when a relationship between thetables is not defined. To resolve this problem, ensure thatall the ad hoc queries have at least one identifier.

When you create an ad hoc query by dragging somecolumns in the Query Studio interface, the followingerror message is displayed:

RQP-DEF-0177 An error occurred while performingoperation ’sqlPrepareWithOptions’

status=’-232’.

This is an SQL error related to arithmetic flow. This erroris generated because the average or the sum for certaincolumns is more than the threshold size that is definedin the database. To resolve this error, use the limitedcolumns and add a standard timestamp while creatingan ad hoc query.

If a view or a table for the selected summarization typedoes not exist in the database for a report, the reportdoes not open and the following error message isdisplayed:

RQP-DEF-0177 An error occurred while performingoperation ’sqlPrepareWithOptions’

status=’-56’.

To resolve this problem, complete the following tasks:

v Verify that the summarization and pruning agent isworking correctly.

v Generate data for all the summarization types.

v Verify that the warehouse is collecting historical data.


http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b248993

http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b248993

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html

Table 35. Tivoli Common Reporting for Microsoft Exchange Server agent problems and solutions (continued)

Problem Solution

When you run a report, the report is not displayed in thecorrect format and the following error message isdisplayed:

RQP-DEF-0177 An error occurred while performingoperation ’sqlPrepareWithOptions’status=’-16’.

This problem occurs due to incorrect data source. Toresolve this problem, complete the following tasks:

v Verify that the datasource configuration parameters areconfigured correctly.

v Verify that the specified values for the parameters ofthe summarization and pruning agent such asdatabase URL, driver user, and password match withthe values of these parameters on the database.

If data is not available in the database for the selectedparameters, the following error message is displayedafter querying these parameters:

Empty data set No data returned by query.Try another set of parameters.

To resolve this error, complete the following tasks:

v Configure the summarization and pruning agent andverify that it is working correctly.

v Generate data for all the summarization types in thedatabase.

Reports are not generated correctly in the Microsoft Excelformat.

There are some limitations to generate reports in theMicrosoft Excel format. To view these limitations, see theIBM Cognos Business Intelligence Information Center(http://publib.boulder.ibm.com/infocenter/cbi/v10r1m0/topic/com.ibm.swg.im.cognos.ug_cr_rptstd.10.1.0.doc/ug_cr_rptstd_id32474excel_limitations.html).

When you view a report spanning multiple pages in thePDF format, the report parameters section is displayed atthe top of each page.

No solution is available for this problem at this time.

Charts are not displayed correctly in Microsoft Excel2007.

No solution is available for this problem at this time.

Labels for some charts are displayed in the HTMLoutput, but are not displayed in the PDF output.

The font size is rendered differently in the HTML andthe PDF output. In the PDF output, some fonts are notdisplayed because of the large font size. To resolve thisissue, reduce the font size by completing the followingsteps:

1. Open the report in Report Studio.

2. Click the chart.

3. In the chart properties, select Font.

4. Modify the font properties, such as family, size,weight, and style.

5. Save the settings, and run the report in the PDFformat.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly.

IBM provides the following ways for you to obtain the support you need:

OnlineThe following websites contain troubleshooting information:v Go to the IBM Software Support website (http://www.ibm.com/support/entry/portal/

software) and follow the instructions.v Go to the Application Performance Management Wiki (http://www.ibm.com/developerworks/

servicemanagement/apm/index.html). Feel free to contribute to this wiki.


http://publib.boulder.ibm.com/infocenter/cbi/v10r1m0/topic/com.ibm.swg.im.cognos.ug_cr_rptstd.10.1.0.doc/ug_cr_rptstd_id32474excel_limitations.html

http://www.ibm.com/support/entry/portal/software

http://www.ibm.com/developerworks/servicemanagement/apm/index.html

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to the IBM Support Assistant website (http://www.ibm.com/software/support/isa).


http://www.ibm.com/software/support/isa

Appendix A. Upgrading for warehouse summarization

The Microsoft Exchange Server made changes to the warehouse information collected. These changesextend the warehouse data through additional attributes and attribute groups, allowing for moremeaningful historical reports. This appendix explains those changes and the implications to yourwarehouse collection and reporting.

Refer to appendix A only when you are upgrading the agent from V6.1 to V6.2.0.1 This appendix doesnot apply when you are upgrading the agent from V6.2 to V6.2.0.1

Warehouse summarization is controlled on a per-table basis. How the rows in each table are summarizedis determined by a set of attributes in each table that are designated as primary keys. There is always oneprimary key representing the monitored resource, and data is minimally summarized based on this value.For all agents, this primary key is represented internally by the column name, ORIGINNODE; however,the external attribute name varies with each monitoring agent.

One or more additional primary keys are provided for each attribute group to further refine the level ofsummarization for that attribute group. For example, in an OS agent disk attribute group, a primary keymight be specified for the logical disk name that allows historical information to be reported for eachlogical disk in a computer.

Tables in the warehouseFor a monitoring agent, there are two main types of warehouse tables:v Raw tables:

These tables contain the raw information reported by a monitoring agent and written to the warehouseby the Warehouse Proxy agent. Raw tables are named for the attribute group that they represent, forexample, KEXMSESMTPS00.

v Summary tables:These tables contain summarized information based on the raw tables and written to the warehouse bythe Summarization and Pruning agent. Summarization provides aggregation results over variousreporting intervals, for example, hours, days, and so on. Summary table names are based on the rawtable name with an appended suffix, for example, KEXMSESMTPS00_H, KEXMSESMTPS00_D, and soon.

Effects on summarized attributesWhen tables are summarized in the warehouse, the summary tables and summary views are created toinclude additional columns to report summarization information.

Table 36 contains a list of the time periods and the suffixes for the summary tables and views.

Table 36. Time periods and suffixes for summary tables and views

Data collection time period Summary table suffixes Summary view suffixes

Hourly _H _HV

Daily _D _DV

Weekly _W _WV

Monthly _M _MV

Quarterly _Q _QV


Table 36. Time periods and suffixes for summary tables and views (continued)

Data collection time period Summary table suffixes Summary view suffixes

Yearly _Y _YV

Table 37 shows the expansion to summary columns of some of the most commonly used attribute types.

Table 37. Additional columns to report summarization information

Attribute name Aggregation type Additional summarization columns

MyGauge GAUGE MIN_MyGaugeMAX_MyGaugeSUM_MyGaugeAVG_MyGauge

MyCounter COUNTER TOT_MyCounterHI_MyCounterLO_MyCounterLAT_MyCounter

MyProperty PROPERTY LAT_Property

These additional columns are provided only for attributes that are not primary keys. In the cases whenan existing attribute is changed to be a primary key, the Summarization and Pruning agent no longercreates summarization values for the attributes, but the previously created column names remain in thetable with any values already provided for those columns. These columns cannot be deleted from thewarehouse database, but as new data is collected, these columns will not contain values. Similarly, whenthe primary key for an existing attribute has its designation removed, that attribute has newsummarization columns automatically added. As new data is collected, it is used to populate these newcolumn values, but any existing summarization records do not have values for these new columns.

Upgrading your warehouse with limited user permissionsThe IBM Tivoli Monitoring warehouse agents (Warehouse Proxy and Summarization and Pruning agents)can dynamically adjust warehouse table definitions based on attribute group and attribute informationbeing loaded into the warehouse.

These types of table changes must be done for this monitoring agent for one or both of the followingconditions:v The monitoring agent has added new attributes to an existing attribute group and that attribute group

is included in the warehouse.v The monitoring agent has added a new attribute group and that attribute group is included in the

warehouse.

For the warehouse agents to automatically modify the warehouse table definitions, they must havepermission to alter warehouse tables. You might not have granted these agents these permissions,choosing instead to manually define the raw tables and summary tables needed for the monitoringagents. Or, you might have granted these permissions initially, and then revoked them after the tableswere created.

You have two options to effect the required warehouse table changes during the upgrade process:v Grant the warehouse agents temporary permission to alter tables

If using this option, grant the permissions, start historical collection for all the desired tables, allow theWarehouse Proxy agent to add the new data to the raw tables, and allow the Summarization andPruning agent to summarize data for all affected tables. Then, remove the permission to alter tables

v Make the warehouse table updates manually


If using this option, you must determine the table structures for the raw and summary tables. If youmanually created the tables in the earlier warehouse definition, you already have a methodology andtools to assist you in this effort. You can use a similar technique to update and add new tables for thiswarehouse migration.For a method of obtaining raw table schema, refer to the IBM Redbook,Tivoli Management ServicesWarehouse and Reporting, January 2007, SG24-7290. The chapter that explains warehouse tuning includesa section on creating data tables manually.

Table summaryTable 38 provides information to help you determine the effects of primary key and warehouse changesfor this monitoring agent. The table shows each attribute group, the current primary keys (in addition toORIGINNODE) for the attribute group, primary keys that were removed, and whether this table is beingincluded in warehouse reporting.

Table 38. Primary key and warehouse changes for the Microsoft Exchange Server agent

Attribute group Current primary key attributes

Removedprimary keyattributes Warehoused

MS_Exchange_ADAcess_Caches ADAccess_Caches_Instance_Name None Yes

MS_Exchange_DB_Instance Database_Instance_Name None Yes

MS_Exchange_DB Database_Name_U None Yes

MS_Exchange_DS None None Yes

MS_Exchange_IS_Private Mailbox_Name_U None Yes

MS_Exchange_IS_Public_Replication Name_U None Yes

MS_Exchange_IS_Public Name_U None Yes

MS_Exchange_IS None None Yes

MS_Exchange_Lotus_Notes_Connector_Summary

None None Yes

MS_Exchange_MTA_Connections Name_U None Yes

MS_Exchange_MTA None None Yes

MS_Exchange_Mailbox_Detail Mailbox_Name None Yes

MS_Exchange_Public_Folder_Detail Public_Folder_Name None Yes

MS_Exchange_Reachability Target_Server None Yes

MS_Exchange_Recipient_Cache Recipient_Cache_Instance_Name None Yes

MS_Exchange_Sender_Id_Agent None None Yes

MS_Exchange_Server None None Yes

MS_Exchange_Services_Detail Service_Name None Yes

MS_Exchange_Storage_Group_Detail Storage_Group_Name None Yes

MS_Exchange_Transport_Queues Transport_Queue_Instance_Name None Yes

MS_Exchange_Transport_Rules Transport_Rule_Name None Yes

MS_Exchange_Transport_SmtpReceive SMTP_Receive_Instance_Name None Yes

MS_Exchange_Transport_SmtpSend SMTP_Send_Instance_Name None Yes

SMTP SMTP_Server None None Yes

Appendix A. Upgrading for warehouse summarization 273

Appendix B. Event mapping

The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to TivoliNetcool/OMNIbus or Tivoli Enterprise Console.

EIF events specify an event class, and the event data is specified as name-value pairs that identify thename of an event slot and the value for the slot. An event class can have subclasses. IBM TivoliMonitoring provides the base event class definitions and a set of base slots that are included in allmonitoring events. Agents extend the base event classes to define subclasses that include agent-specificslots. For Microsoft Exchange Server agent events, the event classes correspond to the agent attributegroups, and the agent-specific slots correspond to the attributes in the attribute group.

The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIFslots instead of using the default mapping described in this topic. For more information about EIF slotcustomization, see the Tivoli Enterprise Portal User's Guide.

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorderof Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agentand is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems) whenapplication support for the agent is installed. The BAROC file for the agent and the base BAROC filesprovided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see"Setting up event forwarding to Tivoli Enterprise Console" in the IBM Tivoli Monitoring Installation andSetup Guide.

For a description of the event slots for each event class, see Table 39 on page 276. For more informationabout mapping attribute groups to event classes, see the IBM Tivoli Monitoring Administrator's Guide.

Each of the event classes is a child of KEX_Base. The KEX_Base event class can be used for generic rulesprocessing for any event from the Microsoft Exchange Server agent.


Table 39. Overview of event slots to event classes

IBM Tivoli Enterprise Console event class Event slots

ITM_MS_Exchange_Active_Sync MS_Exchange_Active_Sync attribute group

v system_name: STRING

v timestamp: STRING

v requests_total: INTEGER

v current_requests: INTEGER

v average_request_time: INTEGER

v requests_per_sec: REAL

v meeting_response_total: INTEGER

v meeting_response_commands_per_sec: REAL

v requests_queued: INTEGER

v sync_total: INTEGER

v sync_commands_per_sec: REAL

v get_item_estimate_commands_per_sec: REAL

v get_attachment_total: INTEGER

v get_attachment_commands_per_sec: REAL

v send_mail_total: INTEGER

v send_mail_commands_per_sec: REAL

v mailbox_search_total: INTEGER

v mailbox_searches_per_sec: REAL

v mailbox_item_fetch_total: INTEGER

v mailbox_item_fetch_commands_per_sec: REAL

v ping_total: INTEGER

v ping_commands_pending: INTEGER

v ping_dropped_total: INTEGER

v ping_commands_dropped_per_sec: REAL

v busy_threads: INTEGER

v busy_threads_enum: STRING

v empty_folder_contents_total: INTEGER

v empty_folder_contents_total_enum: STRING

v failed_item_conversion_total: INTEGER

v failed_item_conversion_total_enum: STRING

v folder_create_commands_per_sec: REAL

v folder_create_commands_per_sec_enum: STRING

v folder_create_total: INTEGER

v folder_create_total_enum: STRING

v folder_delete_commands_per_sec: REAL

v folder_delete_commands_per_sec_enum: STRING

v folder_delete_total: INTEGER

v folder_delete_total_enum: STRING

v folder_sync_commands_per_sec: REAL

v folder_sync_commands_per_sec_enum: STRING

v folder_sync_total: INTEGER

Continued on next page


Table 39. Overview of event slots to event classes (continued)


ITM_MS_Exchange_Active_Sync

Continued

v folder_sync_total_enum: STRING

v folder_update_commands_per_sec: REAL

v folder_update_commands_per_sec_enum: STRING

v folder_update_total: INTEGER

v folder_update_total_enum: STRING

v gal_search_total: INTEGER

v gal_search_total_enum: STRING

v gal_searches_per_sec: REAL

v gal_searches_per_sec_enum: STRING

v idle_threads: INTEGER

v idle_threads_enum: STRING

v mailbox_attachment_fetch_commands_per_sec: REAL

v mailbox_attachment_fetch_commands_per_sec_enum: STRING

v mailbox_attachment_fetch_total: INTEGER

v mailbox_attachment_fetch_total_enum: STRING

v move_collection_commands_per_sec: REAL

v move_collection_commands_per_sec_enum: STRING

v move_collection_total: INTEGER

v move_collection_total_enum: STRING

v move_items_commands_per_sec: REAL

v move_items_commands_per_sec_enum: STRING

v move_items_total: INTEGER

v move_items_total_enum: STRING

v pid: INTEGER

v pid_enum: STRING

v provision_commands_per_sec: REAL

v provision_commands_per_sec_enum: STRING

v search_commands_per_sec: REAL

v search_commands_per_sec_enum: STRING

v search_total: INTEGER

v search_total_enum: STRING

v client_item_adds_per_sec: REAL

v client_item_adds_per_sec_enum: STRING

v client_item_changes_per_sec: REAL

v client_item_changes_per_sec_enum: STRING

v client_item_deletes_per_sec: REAL

v client_item_deletes_per_sec_enum: STRING

v client_item_fetches_per_sec: REAL

v client_item_fetches_per_sec_enum: STRING

v client_sync_items_per_sec: REAL

v client_sync_items_per_sec_enum: STRING


Appendix B. Event mapping 277



ITM_MS_Exchange_Active_Sync

Continued

v createcollection_commands_per_sec: REAL

v createcollection_commands_per_sec_enum: STRING

v current_active_directory_requests: INTEGER

v current_active_directory_requests_enum: STRING

v exchange_mailbox_server_io_requests_per_sec: REAL

v exchange_mailbox_server_io_requests_per_sec_enum: STRING

v exchange_mailbox_server_item_adds_per_sec: REAL

v exchange_mailbox_server_item_adds_per_sec_enum: STRING

v exchange_mailbox_server_item_changes_per_sec: REAL

v exchange_mailbox_server_item_changes_per_sec_enum: STRING

v exchange_mailbox_server_item_deletes_per_sec: REAL

v exchange_mailbox_server_item_deletes_per_sec_enum: STRING

v exchange_mailbox_server_item_soft_deletes_per_sec: REAL

v exchange_mailbox_server_item_soft_deletes_per_sec_enum:STRING

v exchange_mailbox_server_sync_items_per_sec: REAL

v exchange_mailbox_server_sync_items_per_sec_enum: STRING

v gethierarchy_commands_per_sec: REAL

v gethierarchy_commands_per_sec_enum: STRING

v notify_commands_per_sec: REAL

v notify_commands_per_sec_enum: STRING

v resolverecipients_commands_per_sec: REAL

v resolverecipients_commands_per_sec_enum: STRING

v smartforward_commands_per_sec: REAL

v smartforward_commands_per_sec_enum: STRING




ITM_MS_Exchange_Active_Manager_Client MS_Exchange_Active_Manager_Client attribute group


v timestamp: STRING

v active_manager_client_instance_name: STRING

v client_side_cache_hits: INTEGER

v client_side_cache_hits_enum: STRING

v client_side_cache_misses: INTEGER

v client_side_cache_misses_enum: STRING

v client_side_calls: INTEGER

v client_side_calls_enum: STRING

v client_side_calls_read_through: INTEGER

v client_side_calls_read_through_enum: STRING

v client_side_calls_per_sec: REAL

v client_side_calls_per_sec_enum: STRING

v client_side_rpc_calls: INTEGER

v client_side_rpc_calls_enum: STRING

v location_cache_entries: INTEGER

v location_cache_entries_enum: STRING

v server_information_cache_entries: INTEGER

v server_information_cache_entries_enum: STRING

v server_information_cache_hits: INTEGER

v server_information_cache_hits_enum: STRING

v server_information_cache_misses: INTEGER

v server_information_cache_misses_enum: STRING

v unique_databases_queried: INTEGER

v unique_databases_queried_enum: STRING

v unique_servers_queried: INTEGER

v unique_servers_queried_enum: STRING

ITM_MS_Exchange_Active_Manager_Server MS_Exchange_Active_Manager_Server attribute group


v timestamp: STRING

v active_manager_database_state_writes_to_persistent_storage:INTEGER

v active_manager_database_state_writes_to_persistent_storage_enum: STRING

v active_manager_database_state_writes_to_persistent_storage_per_sec: REAL

v active_manager_database_state_writes_to_persistent_storage_per_sec_enum: STRING

v getserverfordatabase_server_side_calls: INTEGER

v getserverfordatabase_server_side_calls_enum: STRING

v server_side_calls_per_sec: REAL

v server_side_calls_per_sec_enum: STRING

v total_number_of_databases: INTEGER

v total_number_of_databases_enum: STRING




ITM_MS_Exchange_Active_Manager MS_Exchange_Active_Manager attribute group


v timestamp: STRING

v active_manager_instance_name: STRING

v database_copy_role_active: INTEGER

v database_copy_role_active_enum: STRING

v database_mounted: INTEGER

v database_mounted_enum: STRING

ITM_MS_Exchange_ADAccess_Domain_Controllers

MS_Exchange_ADAccess_Domain_Controllers attribute group


v timestamp: STRING

v domain_controller_name: STRING

v critical_data_flag: INTEGER

v critical_data_flag_enum: STRING

v dsgetdcname_elapsed_time: INTEGER

v dsgetdcname_elapsed_time_enum: STRING

v ldap_pages_per_sec: REAL

v ldap_pages_per_sec_enum: STRING

v ldap_read_calls_per_sec: REAL

v ldap_read_calls_per_sec_enum: STRING

v ldap_read_time: INTEGER

v ldap_read_time_enum: STRING

v ldap_search_calls_per_sec: REAL

v ldap_search_calls_per_sec_enum: STRING

v ldap_search_time: INTEGER

v ldap_search_time_enum: STRING

v ldap_searches_timed_out_per_min: INTEGER

v ldap_searches_timed_out_per_min_enum: STRING

v long_running_ldap_operations_per_min: INTEGER

v long_running_ldap_operations_per_min_enum: STRING




ITM_MS_Exchange_ADAccess_Forest_Discovery

MS_Exchange_ADAccess_Forest_Discovery attribute group


v timestamp: STRING

v domain_controller_name: STRING

v average_discovery_time: REAL

v average_discovery_time_enum: STRING

v discovery_failures: INTEGER

v discovery_failures_enum: STRING

v in-site_domain_controllers: INTEGER

v in-site_domain_controllers_enum: STRING

v in-site_global_catalogs: INTEGER

v in-site_global_catalogs_enum: STRING

v topology_discovery_duration: REAL

v topology_discovery_duration_enum: STRING

v max_discovery_duration: REAL

v max_discovery_duration_enum: STRING

v out-of-site_domain_controllers: INTEGER

v out-of-site_domain_controllers_enum: STRING

v out-of-site_global_catalogs: INTEGER

v out-of-site_global_catalogs_enum: STRING

v average_time_to_discover_servers_for_roles: REAL

v average_time_to_discover_servers_for_roles_enum: STRING

v maximum_time_to_discover_servers_for_roles: REAL

v maximum_time_to_discover_servers_for_roles_enum: STRING

ITM_MS_Exchange_ADAccess_Processes MS_Exchange_ADAccess_Processes attribute group


v timestamp: STRING

v process_u: STRING

v ldap_read_time: REAL

v ldap_search_time: REAL

v ldap_write_time: REAL

v ldap_read_calls_per_sec: REAL

v ldap_search_calls_per_sec: REAL

v ldap_write_calls_per_sec: REAL

v ldap_pages_per_sec: REAL

v ldap_not_found_configuration_read_calls_per_sec: REAL

v long_running_ldap_operations_per_min: REAL

v ldap_timeout_errors_per_sec: REAL

v open_connections_to_domain_controllers: INTEGER

v open_connections_to_global_catalogs: INTEGER

v number_of_outstanding_requests: INTEGER




ITM_MS_Exchange_Address_Book MS_Exchange_AB attribute group


v timestamp: STRING

v nspi_rpc_requests_average_latency: REAL

v nspi_rpc_requests_average_latency_enum: STRING

v referral_rpc_requests_average_latency: REAL

v referral_rpc_requests_average_latency_enum: STRING

v nspi_connections_current: INTEGER

v nspi_connections_current_enum: STRING

v nspi_connections_per_sec: INTEGER

v nspi_connections_per_sec_enum: STRING

v nspi_rpc_requests_per_sec: INTEGER

v nspi_rpc_requests_per_sec_enum: STRING

v referral_rpc_requests_per_sec: INTEGER

v referral_rpc_requests_per_sec_enum: STRING

v nspi_connections_total: INTEGER

v nspi_connections_total_enum: STRING

v nspi_rpc_requests: INTEGER

v nspi_rpc_requests_enum: STRING

v nspi_rpc_requests_total: INTEGER

v nspi_rpc_requests_total_enum: STRING

v nspi_rpc_browse_requests: INTEGER

v nspi_rpc_browse_requests_enum: STRING

v nspi_rpc_browse_requests_total: INTEGER

v nspi_rpc_browse_requests_total_enum: STRING

v nspi_rpc_browse_requests_average_latency: REAL

v nspi_rpc_browse_requests_average_latency_enum: STRING

v nspi_rpc_browse_requests_sec: INTEGER

v nspi_rpc_browse_requests_sec_enum: STRING

v referral_rpc_requests: INTEGER

v referral_rpc_requests_enum: STRING

v referral_rpc_requests_total: INTEGER

v referral_rpc_requests_total_enum: STRING




ITM_MS_Exchange_Assistants MS_Exchange_Assistants attribute group


v timestamp: STRING

v assistant_u: STRING

v events_in_queue: INTEGER

v events_processed: INTEGER

v number_of_events_processed_per_second: REAL

v events_polled: INTEGER

v events_polled_per_sec: REAL

v polling_delay: REAL

v average_event_queue_time_in_seconds: REAL

v average_event_processing_time_in_seconds: REAL

v average_queue_size_of_event_dispatchers: INTEGER

v number_of_event_dispatchers: INTEGER

v number_of_failed_event_dispatchers: INTEGER

v number_of_threads_used: INTEGER

v average_mailbox_processing_time_in_seconds: REAL

v number_of_handled_exceptions: INTEGER

v mailboxes_processed: INTEGER

v mailboxes_processed_per_sec: REAL

ITM_MS_Exchange_Assistants_Per_Database MS_Exchange_Assistants_Per_Database attribute group


v timestamp: STRING

v assistant_name_per_database_u: STRING

v average_event_processing_time_in_seconds: REAL

v average_mailbox_processing_time_in_seconds: REAL

v events_in_queue: INTEGER

v events_polled: INTEGER

v events_polled_per_sec: REAL

v highest_event_counter_polled: INTEGER

v mailboxes_processed: INTEGER

v mailboxes_processed_per_sec: REAL

v number_of_threads_used: INTEGER

v percentage_of_interesting_events: REAL

v polling_delay: REAL

ITM_MS_Exchange_Attachment_Filtering MS_Exchange_Attachment_Filtering attribute group

v System_Name: STRING

v Timestamp: TIMESTAMP

v Messages_Attachment_Filtered: INTEGER

v Messages_Filtered/sec: INTEGER

v Change_in_Messages_Attachment_Filtered: INTEGER




ITM_MS_Exchange_Authentication MS_Exchange_Authentication attribute group


v timestamp: STRING

v authentication_instance_name: STRING

v latency: REAL

v latency_enum: STRING

v outstanding_requests: INTEGER

v outstanding_requests_enum: STRING

v rejected_requests: INTEGER

v rejected_requests_enum: STRING

v total_requests: INTEGER

v total_requests_enum: STRING

v accepted_requests: INTEGER

v accepted_requests_enum: STRING

ITM_MS_Exchange_Autodiscover MS_Exchange_Autodiscover attribute group


v Timestamp: STRING

v total_requests: INTEGER

v total_requests_enum: STRING

v requests_per_sec: INTEGER

v requests_per_sec_enum: STRING

v error_responses: INTEGER

v error_responses_enum: STRING

v error_responses_per_sec: INTEGER

v error_responses_per_sec_enum: STRING




ITM_MS_Exchange_Availability_Service MS_Exchange_Availability_Service attribute group


v timestamp: STRING

v average_time_to_process_free_busy_request: REAL

v average_time_to_process_free_busy_request_enum: STRING

v availability_requests: INTEGER

v availability_requests_enum: STRING

v current_requests: INTEGER

v current_requests_enum: STRING

v public_folder_queries: INTEGER

v public_folder_queries_enum: STRING

v average_number_of_mailboxes_processed_per_request: REAL

v average_number_of_mailboxes_processed_per_request_enum:STRING

v public_folder_request_failures: INTEGER

v public_folder_request_failures_enum: STRING

v client_reported_failures_total: INTEGER

v client_reported_failures_total_enum: STRING

v client_reported_failures_autodiscover_failures: INTEGER

v client_reported_failures_autodiscover_failures_enum: STRING

v client_reported_failures_timeout_failures: INTEGER

v client_reported_failures_timeout_failures_enum: STRING

v client_reported_failures_connection_failures: INTEGER

v client_reported_failures_connection_failures_enum: STRING

v client_reported_failures_partial_other_failures: INTEGER

v client_reported_failures_partial_other_failures_enum: STRING

v successful_client_reported_requests_total: INTEGER

v successful_client_reported_requests_total_enum: STRING




ITM_MS_Exchange_Control_Panel_RBAC MS_Exchange_Control_Panel_RBAC attribute group


v timestamp: STRING

v explicit_signon_standard_rbac_sessions: INTEGER

v explicit_signon_standard_rbac_sessions_total: INTEGER

v rbac_sessions: INTEGER

v rbac_sessions_average_creation_time: INTEGER

v rbac_sessions_peak: INTEGER

v rbac_sessions_total: INTEGER

v rbac_sessions_per_sec: REAL

v standard_rbac_requests: INTEGER

v standard_rbac_requests_peak: INTEGER

v standard_rbac_requests_total: INTEGER

v standard_rbac_requests_per_sec: REAL

v standard_rbac_sessions: INTEGER

v standard_rbac_sessions_peak: INTEGER

v standard_rbac_sessions_total: INTEGER

v standard_rbac_sessions_per_sec: REAL

ITM_MS_Exchange_Database_Availability_Group

MS_Exchange_Database_Availability_Group attribute group


v timestamp: STRING

v dag_name: STRING

v member_count: INTEGER

v witness_server_name: STRING

v mailbox_database_copies: STRING

v database_copy_status: STRING

v database_copy_status_enum: STRING

v activation_preference: INTEGER

v replay_lag_time: INTEGER

ITM_MS_Exchange_DB MS_Exchange_DB attribute group


v timestamp: STRING

v database_name_u: STRING

v cache_pct__hit: REAL

v cache_page_fault_stalls_per_sec: REAL

v cache_page_faults_per_sec: REAL

v cache_size: INTEGER

v log_record_stalls_per_sec: REAL

v log_threads_waiting: INTEGER

v log_writes_per_sec: REAL

v table_open_cache_pct__hit: REAL

v table_open_cache_hits_per_sec: REAL

v table_open_cache_misses_per_sec: REAL

v table_opens_per_sec: REAL




ITM_MS_Exchange_DB_Instance MS_Exchange_DB_Instance attribute group


v timestamp: STRING

v database_instance_name: STRING

v log_generation_checkpoint_depth: INTEGER

ITM_MS_Exchange_Delivery_DSN MS_Exchange_Delivery_DSN attribute group


v timestamp: STRING

v dsn_type: STRING

v failure_dsns_in_last_hour_that_can_be_alerted: INTEGER

v failure_dsns_in_last_hour_that_can_be_alerted_enum: STRING

v delay_dsns: INTEGER

v delay_dsns_enum: STRING

v last_hour_delayed_dsns: INTEGER

v last_hour_delayed_dsns_enum: STRING

v delivered_dsns: INTEGER

v delivered_dsns_enum: STRING

v expanded_dsns: INTEGER

v expanded_dsns_enum: STRING

v failure_dsns_total: INTEGER

v failure_dsns_total_enum: STRING

v last_hour_failure_dsns: INTEGER

v last_hour_failure_dsns_enum: STRING

v ndrs_generated_for_catch-all_recipients: INTEGER

v ndrs_generated_for_catch-all_recipients_enum: STRING

v relay_dsns: INTEGER

v relay_dsns_enum: STRING

ITM_MS_Exchange_DS MS_Exchange_DS attribute group


v timestamp: STRING

v ab_browses_per_sec: REAL

v ab_client_sessions: INTEGER

v ldap_searches_per_sec: REAL

v threads_in_use: INTEGER




ITM_MS_Exchange_Event_Details MS_Exchange_Event_Details attribute group


v timestamp: STRING

v event_id: INTEGER

v event_timestamp: STRING

v event_age: INTEGER

v event_source: STRING

v type: INTEGER

v type_enum: STRING

v event_category: STRING

v event_description: STRING

v event_log_user: STRING

ITM_MS_Exchange_Extensibility_Agents MS_Exchange_Extensibility_Agents attribute group


v timestamp: STRING

v extensibility_agent_name: STRING

v average_agent_processing_time: REAL

v average_agent_processing_time_enum: STRING

v total_agent_invocations: INTEGER

v total_agent_invocations_enum: STRING

ITM_MS_Exchange_FDS_OAB MS_Exchange_FDS_OAB attribute group


v timestamp: STRING

v fds_oab_instance_name: STRING

v download_task_queued: INTEGER

v download_task_queued_enum: STRING

v download_tasks_completed: INTEGER

v download_tasks_completed_enum: STRING

v total_bytes_to_download: INTEGER

v total_bytes_to_download_enum: STRING

v bytes_downloaded: INTEGER

v bytes_downloaded_enum: STRING




ITM_MS_Exchange_IS MS_Exchange_IS attribute group


v timestamp: STRING

v active_anonymous_user_count: INTEGER

v active_connection_count: INTEGER

v active_user_count: INTEGER

v anonymous_user_count: INTEGER

v connection_count: INTEGER

v database_session_hit_rate: REAL

v maximum_anonymous_users: INTEGER

v maximum_connections: INTEGER

v maximum_users: INTEGER

v peak_push_notifications_cache_size: INTEGER

v push_notifications_cache_size: INTEGER

v push_notifications_generated_per_sec: REAL

v push_notifications_skipped_per_sec: REAL

v read_bytes_rpc_clients_per_sec: REAL

v rpc_operations_per_sec: REAL

v rpc_packets_per_sec: REAL

v rpc_requests: INTEGER

v rpc_requests_peak: INTEGER

v user_count: INTEGER

v write_bytes_rpc_clients_per_sec: REAL

ITM_MS_Exchange_IS_Client MS_Exchange_IS_Client attribute group



v Client_Name: STRING

v RPC_Average_Latency: INTEGER

v RPC_Bytes_Received/sec: INTEGER

v RPC_Bytes_Sent/sec: INTEGER

v RPC_Packets/sec: INTEGER




ITM_MS_Exchange_IS_HA_Active_Database MS_Exchange_IS_HA_Active_Database attribute group


v timestamp: STRING

v mailbox_database_name: STRING

v average_emit_and_send_latency: REAL

v average_emit_and_send_latency_enum: STRING

v average_emit_latency: REAL

v average_emit_latency_enum: STRING

v block_mode_replication_overflows: INTEGER

v block_mode_replication_overflows_enum: STRING

v compression_enabled: INTEGER

v compression_enabled_enum: STRING

v current_log_generation_number: INTEGER

v current_log_generation_number_enum: STRING

v emit_calls_per_second: INTEGER

v emit_calls_per_second_enum: STRING

v log_generation_rate: REAL

v log_generation_rate_enum: STRING

v total_bytes_input_to_compression: REAL

v total_bytes_input_to_compression_enum: STRING

v total_bytes_output_from_compression: REAL

v total_bytes_output_from_compression_enum: STRING

v total_emit_calls: INTEGER

v total_emit_calls_enum: STRING

v total_log_bytes_generated: REAL

v total_log_bytes_generated_enum: STRING




ITM_MS_Exchange_IS_Private MS_Exchange_IS_Private attribute group


v timestamp: STRING

v mailbox_name_u: STRING

v active_client_logons: INTEGER

v average_delivery_time: REAL

v average_local_delivery_time: REAL

v average_local_delivery_time_enum: STRING

v categorization_count: INTEGER

v client_logons: INTEGER

v folder_opens_per_sec: REAL

v local_deliveries: INTEGER

v local_delivery_rate: REAL

v message_opens_per_sec: REAL

v message_recipients_delivered: INTEGER

v message_recipients_delivered_per_min: REAL

v messages_delivered: INTEGER

v messages_delivered_per_min: REAL

v messages_sent: INTEGER

v messages_sent_per_min: REAL

v messages_submitted: INTEGER

v messages_submitted_per_min: REAL

v peak_client_logons: INTEGER

v receive_queue_size: INTEGER

v send_queue_size: INTEGER

v single_instance_ratio: REAL

v total_count_of_recoverable_items: INTEGER

v total_size_of_recoverable_items: INTEGER

v mailbox_is_size: INTEGER

v mailbox_is_percent_growth: INTEGER

v mailbox_is_database_percent_space_used: INTEGER

v mailbox_store_state: INTEGER

v mailbox_store_state_enum: STRING




ITM_MS_Exchange_IS_Public MS_Exchange_IS_Public attribute group


v timestamp: STRING

v name_u: STRING

v active_client_logons: INTEGER

v average_delivery_time: REAL

v average_local_delivery_time: REAL

v average_local_delivery_time_enum: STRING

v categorization_count: INTEGER

v client_logons: INTEGER

v folder_opens_per_sec: REAL

v message_opens_per_sec: REAL

v message_recipients_delivered: INTEGER

v message_recipients_delivered_per_min: REAL

v messages_delivered: INTEGER

v messages_delivered_per_min: REAL


v messages_sent_per_min: REAL

v messages_submitted: INTEGER

v messages_submitted_per_min: REAL

v messages_submitted_per_min_enum: STRING

v number_of_messages_expired_from_public_folders: INTEGER

v peak_client_logons: INTEGER

v receive_queue_size: INTEGER

v send_queue_size: INTEGER

v single_instance_ratio: REAL

v total_count_of_recoverable_items: INTEGER

v total_size_of_recoverable_items: INTEGER

v public_is_size: INTEGER

v public_is_percent_growth: INTEGER

v public_is_database_percent_space_used: INTEGER

v public_store_state: INTEGER

v public_store_state_enum: STRING




ITM_MS_Exchange_IS_Public_Replication MS_Exchange_IS_Public_Replication attribute group


v timestamp: STRING

v name_u: STRING

v replication_backfill_data_messages_received: INTEGER

v replication_backfill_data_messages_sent: INTEGER

v replication_backfill_requests_received: INTEGER

v replication_backfill_requests_sent: INTEGER

v replication_folder_changes_received: INTEGER

v replication_folder_changes_sent: INTEGER

v replication_folder_data_messages_received: INTEGER

v replication_folder_data_messages_sent: INTEGER

v replication_folder_tree_messages_received: INTEGER

v replication_folder_tree_messages_sent: INTEGER

v replication_message_changes_received: INTEGER

v replication_message_changes_sent: INTEGER

v replication_messages_received: INTEGER

v replication_messages_sent: INTEGER

v replication_status_messages_received: INTEGER

v replication_status_messages_sent: INTEGER

ITM_MS_Exchange_Mail_Submission MS_Exchange_Mail_Submission attribute group


v timestamp: STRING

v mail_submission_instance_name: STRING

v aggregate_shadow_queue_length: INTEGER

v aggregate_shadow_queue_length_enum: STRING

v hub_servers: INTEGER hub_servers_enum: STRING

v hub_servers_in_retry: INTEGER

v hub_servers_in_retry_enum: STRING

v hub_transport_servers_percent_active: REAL

v hub_transport_servers_percent_active_enum: STRING

v shadow_message_resubmissions_total: INTEGER

v shadow_message_resubmissions_total_enum: STRING

v shadow_queue_auto_discards_total: INTEGER

v shadow_queue_auto_discards_total_enum: STRING

v shadow_resubmission_queue_length: INTEGER

v shadow_resubmission_queue_length_enum: STRING

v successful_submissions: INTEGER

v successful_submissions_enum: STRING

v successful_submissions_per_second: REAL

v successful_submissions_per_second_enum: STRING




ITM_MS_Exchange_Mail_Tips MS_Exchange_Mail_Tips attribute group


v timestamp: STRING

v automatic_replies_one_sec: REAL

v automatic_replies_one_sec_enum: STRING

v automatic_replies_ten_sec: REAL

v automatic_replies_ten_sec_enum: STRING

v automatic_replies_three_sec: REAL

v automatic_replies_three_sec_enum: STRING

v automatic_replies_turned_on: INTEGER

v automatic_replies_turned_on_enum: STRING

v average_active_directory_response_time: REAL

v average_active_directory_response_time_enum: STRING

v count_of_group_metrics_queries: REAL

v count_of_group_metrics_queries_enum: STRING

v getmailtips_average_recipient_number: REAL

v getmailtips_average_recipient_number_enum: STRING

v getmailtips_average_response_time: REAL

v getmailtips_average_response_time_enum: STRING

v getmailtips_average_response_time_for_groupmetrics_queries:REAL

v getmailtips_average_response_time_for_groupmetrics_queries_enum: STRING

v getmailtipsconfiguration_average_response_time: REAL

v getmailtipsconfiguration_average_response_time_enum: STRING

v getserviceconfiguration_average_response_time: REAL

v getserviceconfiguration_average_response_time_enum: STRING

v intra_site_mailtips_failures_per_sec: INTEGER

v intra_site_mailtips_failures_per_sec_enum: STRING

v mailboxfull_answered_within_one_second: REAL

v mailboxfull_answered_within_one_second_enum: STRING

v mailboxfull_answered_within_ten_seconds: REAL

v mailboxfull_answered_within_ten_seconds_enum: STRING

v mailboxfull_answered_within_three_seconds: REAL

v mailboxfull_answered_within_three_seconds_enum: STRING

v mailboxfull_with_positive_responses: INTEGER

v mailboxfull_with_positive_responses_enum: STRING

v mailtips_accumulated_exception_recipients: INTEGER

v mailtips_accumulated_exception_recipients_enum: STRING

v mailtips_accumulated_mailbox_sourced_recipients: INTEGER

Continued on next page.




ITM_MS_Exchange_Mail_Tips

(Continued)

v mailtips_accumulated_mailbox_sourced_recipients_enum:STRING

v mailtips_accumulated_recipients: INTEGER

v mailtips_accumulated_recipients_enum: STRING

v mailtips_accumulated_requests: INTEGER

v mailtips_accumulated_requests_enum: STRING

v mailtips_current_requests: INTEGER

v mailtips_current_requests_enum: STRING

v mailtips_queries_answered_within_one_second: REAL

v mailtips_queries_answered_within_one_second_enum: STRING

v mailtips_queries_answered_within_ten_second: REAL

v mailtips_queries_answered_within_ten_second_enum: STRING

v mailtips_queries_answered_within_three_second: REAL

v mailtips_queries_answered_within_three_second_enum: STRING

ITM_MS_Exchange_Mailbox_Replication_Service

MS_Exchange_Mailbox_Replication_Service attribute group


v timestamp: STRING

v last_scan_duration_msec: INTEGER

v mailbox_databases_in_active_directory_site: INTEGER

v mailbox_servers_in_active_directory_site: INTEGER

v unreachable_databases: INTEGER

v unreachable_servers: INTEGER

v last_scan_timestamp_utc: REAL




MS_Exchange_Mailbox_Replication_Service_per_Mdb

MS_Exchange_Mailbox_Replication_Service_per_Mdb attributegroup


v timestamp: STRING

v mailbox_database_name_u: STRING

v active_moves_total_moves: INTEGER

v mdb_health_content_indexing_lagging: INTEGER

v mdb_health_database_replication_lagging: INTEGER

v mdb_health_scan_failure: INTEGER

v mdb_queue_auto_suspended: INTEGER

v mdb_queue_completed: INTEGER

v mdb_queue_completed_with_warnings: INTEGER

v mdb_queue_completing: INTEGER

v mdb_queue_failed: INTEGER

v mdb_queue_in_progress: INTEGER

v mdb_queue_pull: INTEGER

v mdb_queue_push: INTEGER

v mdb_queue_queued: INTEGER

v mdb_queue_remote: INTEGER

v mdb_queue_remote_legacy: INTEGER

v mdb_queue_suspended: INTEGER

v mdb_queue_total: INTEGER

v move_requests_canceled_per_hour: REAL

v move_requests_completed_with_warnings_per_hour: REAL

v move_requests_completed_per_hour: REAL

v move_requests_failed_bad_item_limit_per_hour: REAL

v move_requests_failed_network_per_hour: REAL

v move_requests_failed_other_per_hour: REAL

v move_requests_failed_stall_content_indexing_per_hour: REAL

v move_requests_failed_stall_database_replication_per_hour: REAL

v move_requests_failed_per_hour: REAL

v move_requests_move_stalls_content_indexing_per_hour: REAL

v move_requests_move_stalls_database_replication_per_hour:REAL

v move_requests_move_stalls_per_hour: REAL

v move_requests_transient_failures_network_per_hour: REAL

v move_requests_transient_failures_proxy_backoff_per_hour: REAL

v move_requests_transient_failures_per_hour: REAL

v last_scan_duration_msec: INTEGER

v last_scan_timestamp_utc: REAL

v last_scan_timestamp_utc_v623: INTEGER




ITM_MS_Exchange_Managed_Folder_Assistant MS_Exchange_Managed_Folder_Assistant attribute group


v timestamp: STRING

v items_deleted_but_recoverable: INTEGER

v items_marked_as_past_retention_date: INTEGER

v items_moved: INTEGER

v items_permanently_deleted: INTEGER

v items_subject_to_retention_policy: INTEGER

ITM_MS_Exchange_MTA MS_Exchange_MTA attribute group


v timestamp: STRING

v deferred_delivery_msgs: INTEGER

v inbound_bytes_total: INTEGER

v inbound_messages_total: INTEGER

v lan_receive_bytes_per_sec: REAL

v lan_transmit_bytes_per_sec: REAL

v messages_per_sec: REAL

v outbound_bytes_total: INTEGER

v outbound_messages_total: INTEGER

v total_recipients_inbound: INTEGER

v total_recipients_outbound: INTEGER

v total_recipients_queued: INTEGER

v work_queue_length: INTEGER

ITM_MS_Exchange_MTA_Connections MS_Exchange_MTA_Connections attribute group


v timestamp: STRING

v associations: INTEGER

v failed_outbound_associations: INTEGER

v inbound_bytes_total: INTEGER

v inbound_messages_total: INTEGER

v name_u: STRING

v outbound_bytes_total: INTEGER

v outbound_messages_total: INTEGER

v queue_length: INTEGER

v receive_messages_per_sec: REAL

v send_messages_per_sec: REAL

v total_recipients_inbound: INTEGER

v total_recipients_outbound: INTEGER




ITM_MS_Exchange_Mailbox_Detail MS_Exchange_Mailbox_Detail attribute group


v timestamp: STRING

v mailbox_name: STRING

v storage_group_name: STRING

v information_store_name: STRING

v number_of_messages: INTEGER

v mailbox_size: INTEGER

v mailbox_max_size: INTEGER

v last_logon: STRING

v email_addresses: STRING

ITM_MS_Exchange_Public_Folder_Detail MS_Exchange_Public_Folder_Detail attribute group


v timestamp: STRING

v public_folder_name: STRING


v information_store_name: STRING

v number_of_messages: INTEGER

v folder_size: INTEGER

v last_logon: STRING

ITM_MS_Exchange_Replication MS_Exchange_Replication attribute group


v timestamp: STRING

v copy_notification_generation_number: INTEGER

v copy_generation_number: INTEGER

v inspector_generation_number: INTEGER

v replay_notification_generation_number: INTEGER

v replay_generation_number: INTEGER

v replay_queue_length: INTEGER

v replay_batch_size: INTEGER

v copy_queue_length: INTEGER

v replay_generations_complete: INTEGER

v replay_generations_remaining: INTEGER

v replay_generations_per_minute: INTEGER

v replica_instance_failed: INTEGER

v replica_instance_failed_enum: STRING

v replication_initializing: INTEGER

v replication_initializing_enum: STRING

v copy_queue_exceeds_mount_threshold: INTEGER

v copy_queue_exceeds_mount_threshold_enum: STRING

v replication_suspended: INTEGER

v replication_suspended_enum: STRING




ITM_MS_Exchange_Replica_Seeder MS_Exchange_Replica_Seeder attribute group


v timestamp: STRING

v replica_seeder_instance_name: STRING

v database_seeding_bytes_read: INTEGER

v database_seeding_bytes_read_enum: STRING

v database_seeding_bytes_written: INTEGER

v database_seeding_bytes_written_enum: STRING

v database_seeding_progress_percent: INTEGER

v database_seeding_progress_percent_enum: STRING

ITM_MS_Exchange_Replication_Server MS_Exchange_Replication_Server attribute group


v timestamp: STRING

v getcopystatus_server_side_calls: INTEGER

v getcopystatus_server_side_calls_enum: STRING

v getcopystatus_server_side_calls_per_sec: REAL

v getcopystatus_server_side_calls_per_sec_enum: STRING

ITM_MS_Exchange_Resource_Booking MS_Exchange_Resource_Booking attribute group


v timestamp: STRING

v average_resource_booking_processing_time: REAL

v average_resource_booking_processing_time_enum: STRING

v cancelled_meeting_requests: INTEGER

v cancelled_meeting_requests_enum: STRING

v declined_meeting_requests: INTEGER

v declined_meeting_requests_enum: STRING

v meetings_requests_failed: INTEGER

v meetings_requests_failed_enum: STRING

v meetings_requests_processed: INTEGER

v meetings_requests_processed_enum: STRING

v meetings_requests_submitted: INTEGER

v meetings_requests_submitted_enum: STRING




ITM_MS_Exchange_Resource_Health MS_Exchange_Resource_Health attribute group


v timestamp: STRING

v resource_health_instance_name: STRING

v fair_to_unhealthy_latency_threshold: INTEGER

v fair_to_unhealthy_latency_threshold_enum: STRING

v healthy_to_fair_latency_threshold: INTEGER

v healthy_to_fair_latency_threshold_enum: STRING

v max_resource_delay_per_minute: REAL

v max_resource_delay_per_minute_enum: STRING

v overflow_queue_count: INTEGER

v overflow_queue_count_enum: STRING

v overflow_queue_count_peak: INTEGER

v overflow_queue_count_peak_enum: STRING

v overflow_wait_time_peak: INTEGER

v overflow_wait_time_peak_enum: STRING

v raw_resource_value: INTEGER

v raw_resource_value_enum: STRING

v requests_per_second: REAL

v requests_per_second_enum: STRING

v resource_health_measure: INTEGER

v resource_health_measure_enum: STRING

v semaphore_count: INTEGER

v semaphore_count_enum: STRING

v semaphore_count_peak: INTEGER

v semaphore_count_peak_enum: STRING

v total_semaphore_size: INTEGER

v total_semaphore_size_enum: STRING

v total_semaphore_size_peak: INTEGER

v total_semaphore_size_peak_enum: STRING

v total_threads_beyond_acceptable_latency: INTEGER

v total_threads_beyond_acceptable_latency_enum: STRING

v unhealthy_health_measure: INTEGER

v unhealthy_health_measure_enum: STRING




ITM_MS_Exchange_Rights_Management_Service

MS_Exchange_Rights_Management_Service attribute group


v timestamp: STRING

v average_time_for_successful_acquirelicense: INTEGER

v average_time_for_successful_acquireprelicense: INTEGER

v average_time_for_successful_acquiretemplates: INTEGER

v average_time_for_successful_certify: INTEGER

v average_time_for_successful_findservicelocations: INTEGER

v average_time_for_successful_getclientlicensorcert: INTEGER

v cache-hit_of_rms_server_info_per_sec: REAL

v cache-miss_of_rms_server_info_per_sec: REAL

v entries_added_into_rms_license_store_per_sec: REAL

v entries_added_into_rms_server_info_cache_per_sec: REAL

v entries_removed_from_rms_license_store_per_sec: REAL

v entries_removed_from_rms_server_info_cache_per_sec: REAL

v failed_acquirelicense_per_sec: REAL

v failed_acquireprelicense_per_sec: REAL

v failed_acquiretemplates_per_sec: REAL

v failed_certify_per_sec: REAL

v failed_external_acquirelicense_requests_per_sec: REAL

v failed_external_certification_requests_per_sec: REAL

v failed_findservicelocations_per_sec: REAL

v failed_getclientlicensorcert_per_sec: REAL

v successful_acquirelicense_per_sec: REAL

v successful_acquireprelicense_per_sec: REAL

v successful_acquiretemplates_per_sec: REAL

v successful_certify_per_sec: REAL

v successful_external_acquirelicense_requests_per_sec: REAL

v successful_external_certification_requests_per_sec: REAL

v successful_findservicelocations_per_sec: REAL

v successful_getclientlicensorcert_per_sec: REAL

v total_cache_hit_of_rms_server_info: INTEGER

v total_cache_miss_of_rms_server-info: INTEGER




ITM_MS_Exchange_Server MS_Exchange_Server attribute group


v timestamp: STRING

v server_status: INTEGER

v server_status_enum: STRING

v server_version: INTEGER

v server_version_enum: STRING

v system_attendant_svc_status: INTEGER

v system_attendant_svc_status_enum: STRING

v exchg_mta_status: INTEGER

v exchg_mta_status_enum: STRING

v exchg_is_status: INTEGER

v exchg_is_status_enum: STRING

v res_status: INTEGER

v res_status_enum: STRING

v smtp_status: INTEGER

v smtp_status_enum: STRING

v www_status: INTEGER

v www_status_enum: STRING

v application_percent_free_space: REAL

v log_percent_free_space: REAL

v edge_transport_role: STRING

v edge_transport_role_enum: STRING

v mailbox_server_role: STRING

v mailbox_server_role_enum: STRING

v client_access_role: STRING

v client_access_role_enum: STRING

v unified_messaging_role: STRING

v unified_messaging_role_enum: STRING

v hub_transport_role: STRING

v hub_transport_role_enum: STRING




ITM_SMTP SMTP attribute group


v timestamp: STRING

v smtp_server: STRING

v pct__recipients_local: REAL

v pct__recipients_remote: REAL

v avg_recipients_per_msg_received: REAL

v avg_recipients_per_msg_sent: REAL

v avg_retries_per_msg_delivered: REAL

v avg_retries_per_msg_sent: REAL

v kbytes_received_total: INTEGER

v bytes_received_per_sec: REAL

v kbytes_sent_total: INTEGER

v bytes_sent_per_sec: REAL

v kbytes_total: INTEGER

v bytes_total_per_sec: REAL

v connection_errors_per_sec: REAL

v directory_drops_total: INTEGER

v directory_drops_per_sec: REAL

v directory_pickup_queue_length: INTEGER

v directory_pickup_queue_length_enum: STRING

v dns_queries_total: INTEGER

v dns_queries_per_sec: REAL

v etrn_messages_total: INTEGER

v etrn_messages_per_sec: REAL

v inbound_connections_current: INTEGER

v inbound_connections_total: INTEGER

v local_queue_length: INTEGER

v local_retry_queue_length: INTEGER

v message_kbytes_received_total: INTEGER

v message_bytes_received_per_sec: REAL

v message_kbytes_sent_total: INTEGER

v message_bytes_sent_per_sec: REAL

v message_kbytes_total: INTEGER

v message_bytes_total_per_sec: REAL

v message_delivery_retries: INTEGER

v messages_received_per_sec: REAL

v message_send_retries: INTEGER

v messages_delivered_total: INTEGER

v messages_delivered_per_sec: REAL

v messages_received_total: INTEGER

v messages_refused_for_address_objects: INTEGER





ITM_SMTP(Continued)

v messages_refused_for_mail_objects: INTEGER

v messages_refused_for_size: INTEGER

v messages_sent_total: INTEGER

v messages_sent_per_sec: REAL

v ndrs_generated: INTEGER

v number_of_mailfiles_open: INTEGER

v number_of_queuefiles_open: INTEGER

v outbound_connections_current: INTEGER

v outbound_connections_refused: INTEGER

v outbound_connections_total: INTEGER

v remote_queue_length: INTEGER

v remote_retry_queue_length: INTEGER

v routing_table_lookups_total: INTEGER

v routing_table_lookups_per_sec: REAL

v total_connection_errors: INTEGER

v total_messages_submitted: INTEGER

v categorizer_queue_length: INTEGER

v messages_pending_routing: INTEGER

ITM_MS_Exchange_Services_Detail MS_Exchange_Services_Detail attribute group


v timestamp: STRING

v service_name: STRING

v service_state: INTEGER

v service_state_enum: STRING

v service_status: INTEGER

v service_status_enum: STRING

v service_start_mode: INTEGER

v service_start_mode_enum: STRING

ITM_MS_Exchange_Storage_Group_Detail MS_Exchange_Storage_Group_Detail attribute group


v timestamp: STRING


v storage_group_size: REAL

v storage_group_percent_free_space: REAL

v storage_group_percent_growth: REAL




ITM_MS_Exchange_Store_Driver MS_Exchange_Store_Driver attribute group


v timestamp: STRING

v store_driver_u: STRING

v inbound_local_delivery_calls: INTEGER

v inbound_local_delivery_calls_per_second: REAL

v inbound_message_delivery_attempts: INTEGER

v inbound_message_delivery_attempts_per_second: REAL

v inbound_recipients_delivered: INTEGER

v inbound_recipients_delivered_per_second: REAL

v inbound_bytes_delivered: INTEGER

v inbound_number_of_delivering_threads: INTEGER

v inbound_succeeded_recipients: INTEGER

v inbound_failed_recipients: INTEGER

v inbound_retried_recipients: INTEGER

v inbound_rerouted_recipients: INTEGER

v outbound_submitted_mail_items: INTEGER

v outbound_submitted_mail_items_per_second: REAL

v outbound_mapi_events_without_message: INTEGER

v outbound_total_recipients: INTEGER

v inbound_total_meeting_messages: INTEGER

v inbound_total_meeting_failures: INTEGER

ITM_MS_Exchange_Text_Messaging MS_Exchange_Text_Messaging attribute group


v timestamp: STRING

v average_text_message_delivery_latency_in_milliseconds:INTEGER

v text_messages_pending_delivery: INTEGER

v text_messages_sent_via_smtp_per_sec: INTEGER

v text_messages_sent_per_sec: INTEGER

v total_messages_sent_via_smtp: INTEGER

v total_text_messages_sent: INTEGER

ITM_MS_Exchange_Store_Driver_Database MS_Exchange_Store_Driver_Database attribute group


v timestamp: STRING

v store_driver_database_instance_name: STRING

v delivery_attempts_per_minute_over_the_last_five_minutes: REAL

v delivery_attempts_per_minute_over_the_last_five_minutes_enum:STRING

v delivery_failures_per_minute_over_the_last_five_minutes: REAL

v delivery_failures_per_minute_over_the_last_five_minutes_enum:STRING




ITM_MS_Exchange_Store_Driver_Server MS_Exchange_Store_Driver_Server attribute group


v timestamp: STRING

v store_driver_server_instance_name: STRING

v delivery_attempts_per_minute_over_the_last_five_minutes_server: REAL

v delivery_attempts_per_minute_over_the_last_five_minutes_server_enum: STRING

v delivery_failures_per_minute_over_the_last_five_minutes_server: REAL

v delivery_failures_per_minute_over_the_last_five_minutes_server_enum: STRING




ITM_MS_Exchange_Store_Interface MS_Exchange_Store_Interface attribute group


v timestamp: STRING

v store_interface_instance_name: STRING

v exrpcconnection_creation_events: INTEGER

v exrpcconnection_creation_events_enum: STRING

v exrpcconnection_disposal_events: INTEGER

v exrpcconnection_disposal_events_enum: STRING

v rpc_bytes_received: INTEGER

v rpc_bytes_received_enum: STRING

v rpc_latency_average_msec: REAL

v rpc_latency_average_msec_enum: STRING

v rpc_latency_total_sec: INTEGER

v rpc_latency_total_sec_enum: STRING

v average_latency_of_rpc_requests: REAL

v average_latency_of_rpc_requests_enum: STRING

v open_rpc_context_handles: INTEGER

v open_rpc_context_handles_enum: STRING

v rpc_requests_failed_pct: REAL

v rpc_requests_failed_pct__enum: STRING

v rpc_requests_failed_with_exception: INTEGER

v rpc_requests_failed_with_exception_enum: STRING

v rpc_requests_outstanding: INTEGER

v rpc_requests_outstanding_enum: STRING

v rpc_requests_sent: INTEGER

v rpc_requests_sent_enum: STRING

v rpc_requests_sent_per_sec: REAL

v rpc_requests_sent_per_sec_enum: STRING

v rpc_requests_succeeded: INTEGER

v rpc_requests_succeeded_enum: STRING

v rpc_slow_requests: INTEGER

v rpc_slow_requests_enum: STRING

v rpc_slow_requests_pct: REAL

v rpc_slow_requests_pct__enum: STRING

v total_latency_of_rpc_slow_requests: INTEGER

v total_latency_of_rpc_slow_requests_enum: STRING




ITM_MS_Exchange_Submission MS_Exchange_Submission attribute group


v timestamp: STRING

v failed_submissions: INTEGER

v failed_submissions_enum: STRING

v failed_submissions_per_sec: INTEGER

v failed_submissions_per_sec_enum: STRING

v pending_submissions: INTEGER

v pending_submissions_enum: STRING

v percent_of_permanent_failed_submissions_in_last_5_minutes: REAL

v percent_of_permanent_failed_submissions_in_last_5_minutes_enum: STRING

v successful_submissions: INTEGER

v successful_submissions_enum: STRING

v successful_submissions_per_sec: INTEGER

v successful_submissions_per_sec_enum: STRING

v temporary_submission_failures: INTEGER

v temporary_submission_failures_enum: STRING

v temporary_submission_failures_per_sec: INTEGER

v temporary_submission_failures_per_sec_enum: STRING

ITM_MS_Exchange_Submission_DSN MS_Exchange_Submission_DSN attribute group


v timestamp: STRING

v dsn_type: STRING

v failure_dsns_in_last_hour_that_can_be_alerted: INTEGER

v failure_dsns_in_last_hour_that_can_be_alerted_enum: STRING

v delay_dsns: INTEGER

v delay_dsns_enum: STRING

v last_hour_delayed_dsns: INTEGER

v last_hour_delayed_dsns_enum: STRING

v delivered_dsns: INTEGER

v delivered_dsns_enum: STRING

v expanded_dsns: INTEGER

v expanded_dsns_enum: STRING

v failure_dsns_total: INTEGER

v failure_dsns_total_enum: STRING

v last_hour_failure_dsns: INTEGER

v last_hour_failure_dsns_enum: STRING

v ndrs_generated_for_catch-all_recipients: INTEGER

v ndrs_generated_for_catch-all_recipients_enum: STRING

v relay_dsns: INTEGER

v relay_dsns_enum: STRING




ITM_MS_Exchange_Reachability MS_Exchange_Reachability attribute group


v timestamp: STRING

v target_server: STRING

v target_email_address: STRING

v reachable: INTEGER

v reachable_enum: STRING

v round_trip_response_time: REAL

v reachability_test_run_time: STRING

ITM_MS_Exchange_Lotus_Notes_Connector_Summary

MS_Exchange_Lotus_Notes_Connector_Summary attribute group


v timestamp: STRING

v messages_received: INTEGER

v messages_rejected_from_notes: INTEGER


v messages_rejected_from_exchange: INTEGER

v volume_received: INTEGER

v volume_sent: INTEGER

v message_queued_inbound: INTEGER

v message_queued_outbound: INTEGER

v volume_queued_inbound: INTEGER

v volume_queued_outbound: INTEGER

v rate_of_messages_sent: INTEGER

v rate_of_messages_received: INTEGER

v rate_of_volume_sent: INTEGER

v rate_of_volume_received: INTEGER

ITM_MS_Exchange_Recipient_Cache MS_Exchange_Recipient_Cache attribute group


v timestamp: STRING

v recipient_cache_instance_name: STRING

v recipient_cache_instance_name_enum: STRING

v address_lookups_pending: INTEGER

v address_lookups_pending_enum: STRING

v batched_address_lookups: INTEGER

v batched_address_lookups_enum: STRING

v expand_group_requests: INTEGER

v expand_group_requests_enum: STRING

v individual_address_lookups: INTEGER

v individual_address_lookups_enum: STRING




ITM_MS_Exchange_ADAcess_Caches MS_Exchange_ADAcess_Caches attribute group


v timestamp: STRING

v adaccess_caches_instance_name: STRING

v adaccess_caches_instance_name_enum: STRING

v ldap_searches_per_sec: INTEGER

v ldap_searches_per_sec_enum: STRING

ITM_MS_Exchange_Transport_Rules MS_Exchange_Transport_Rules attribute group


v timestamp: STRING

v transport_rule_name: STRING

v messages_processed: INTEGER

v messages_processed_enum: STRING

v messages_processed_per_sec: REAL

v messages_processed_per_sec_enum: STRING

v messages_evaluated: INTEGER

v messages_evaluated_enum: STRING

v messages_evaluated_per_sec: REAL

v messages_evaluated_per_sec_enum: STRING




ITM_MS_Exchange_Transport_Database MS_Exchange_Transport_Database attribute group


v timestamp: STRING

v transport_database_instance_name: STRING

v column_cache_load_total: INTEGER

v column_cache_load_per_sec: REAL

v column_cache_loaded_bytes_per_sec: REAL

v column_cache_loaded_columns_total: INTEGER

v column_cache_loaded_columns_per_sec: REAL

v column_cache_save_total: INTEGER

v column_cache_save_per_sec: REAL

v column_cache_saved_columns_total: INTEGER

v column_cache_saved_columns_per_sec: REAL

v datarow_deletes_total: INTEGER

v datarow_deletes_per_sec: REAL

v datarow_loads_total: INTEGER

v datarow_loads_per_sec: REAL

v datarow_moves_total: INTEGER

v datarow_moves_per_sec: REAL

v datarow_seeks_total: INTEGER

v datarow_seeks_per_sec: REAL

v datarow_updates_total: INTEGER

v datarow_updates_per_sec: REAL

v mailitem_load_per_sec: REAL

v mailitem_new_total: INTEGER

v mailitem_new_per_sec: REAL

v stream_bytes_read_total: INTEGER

v stream_bytes_read_per_sec: REAL

v stream_bytes_written_total: INTEGER

v stream_bytes_written_per_sec: REAL

v stream_read_total: INTEGER

v stream_read_per_sec: REAL

v stream_writes_total: INTEGER

v stream_writes_per_sec: REAL

v column_cache_loaded_bytes_total: INTEGER

v mailitem_load_total: INTEGER




ITM_MS_Exchange_Transport_Dumpster MS_Exchange_Transport_Dumpster attribute group


v timestamp: STRING

v dumpster_deletes_per_sec: REAL

v dumpster_inserts_per_sec: REAL

v dumpster_item_count: INTEGER

v dumpster_mailbox_database_count: INTEGER

v dumpster_mailbox_database_count_enum: STRING

v dumpster_size: INTEGER

v redelivery_count: INTEGER

v dumpster_deletes_quota: INTEGER

v dumpster_deletes_quota_enum: STRING




ITM_MS_Exchange_Transport_Queues MS_Exchange_Transport_Queues attribute group


v timestamp: STRING

v transport_queue_instance_name: STRING

v transport_queue_instance_name_enum: STRING

v active_remote_delivery_queue_length: INTEGER

v active_remote_delivery_queue_length_enum: STRING

v retry_remote_delivery_queue_length: INTEGER

v retry_remote_delivery_queue_length_enum: STRING

v active_mailbox_delivery_queue_length: INTEGER

v active_mailbox_delivery_queue_length_enum: STRING

v retry_mailbox_delivery_queue_length: INTEGER

v retry_mailbox_delivery_queue_length_enum: STRING

v active_non-smtp_delivery_queue_length: INTEGER

v active_non-smtp_delivery_queue_length_enum: STRING

v retry_non-smtp_delivery_queue_length: INTEGER

v retry_non-smtp_delivery_queue_length_enum: STRING

v aggregate_delivery_queue_length: INTEGER

v aggregate_delivery_queue_length_enum: STRING

v items_queued_for_delivery_total: INTEGER

v items_queued_for_delivery_total_enum: STRING

v items_queued_for_delivery_per_sec: REAL

v items_queued_for_delivery_per_sec_enum: STRING

v items_completed_delivery_total: INTEGER

v items_completed_delivery_total_enum: STRING

v items_completed_delivery_per_sec: REAL

v items_completed_delivery_per_sec_enum: STRING

v items_queued_for_delivery_expired_total: INTEGER

v items_queued_for_delivery_expired_total_enum: STRING

v items_deleted_by_admin_total: INTEGER

v items_deleted_by_admin_total_enum: STRING

v items_resubmitted_total: INTEGER

v items_resubmitted_total_enum: STRING

v messages_queued_for_delivery: INTEGER

v messages_queued_for_delivery_enum: STRING

v messages_queued_for_delivery_total: INTEGER

v messages_queued_for_delivery_total_enum: STRING

v messages_queued_for_delivery_per_sec: REAL

v messages_queued_for_delivery_per_sec_enum: STRING

v messages_completed_delivery_total: INTEGER

v messages_completed_delivery_total_enum: STRING

v messages_completed_delivery_per_sec: REAL





ITM_MS_Exchange_Transport_Queues(Continued)

v messages_completed_delivery_per_sec_enum: STRING

v unreachable_queue_length: INTEGER

v unreachable_queue_length_enum: STRING

v poison_queue_length: INTEGER

v poison_queue_length_enum: STRING

v submission_queue_length: INTEGER

v submission_queue_length_enum: STRING

v messages_submitted_total: INTEGER

v messages_submitted_total_enum: STRING

v messages_submitted_per_sec: REAL

v messages_submitted_per_sec_enum: STRING

v submission_queue_items_expired_total: INTEGER

v submission_queue_items_expired_total_enum: STRING

ITM_MS_Exchange_Transport_Shadow_Redundancy

MS_Exchange_Transport_Shadow_Redundancy attribute group


v timestamp: STRING

v transport_shadow_redundancy_instance_name: STRING

v current_messages_acknowledged_before_relay_completed:INTEGER

v redundant_message_discard_events: INTEGER

v redundant_message_discard_events_expired: INTEGER

ITM_MS_Exchange_Transport_SMTP_Availability

MS_Exchange_Transport_SMTP_Availability attribute group


v timestamp: STRING

v transport_smtp_availability_instance_name: STRING

v pct__activity: REAL

v pct__activity_enum: STRING

v pct__availability: REAL

v pct__availability_enum: STRING

v pct__failures_due_to_active_directory_down: REAL

v pct__failures_due_to_active_directory_down_enum: STRING

v pct__failures_due_to_back_pressure: REAL

v pct__failures_due_to_back_pressure_enum: STRING

v pct__failures_due_to_io_exceptions: REAL

v pct__failures_due_to_io_exceptions_enum: STRING

v pct__failures_due_to_max_inbound_connection_limit: REAL

v pct__failures_due_to_max_inbound_connection_limit_enum:STRING

v pct__failures_due_to_tls_errors: REAL

v pct__failures_due_to_tls_errors_enum: STRING

v failures_due_to_maximum_local_loop_count: INTEGER

v failures_due_to_maximum_local_loop_count_enum: STRING

v total_connections: INTEGER

v total_connections_enum: STRING




ITM_MS_Exchange_Transport_SmtpReceive MS_Exchange_Transport_SmtpReceive attribute group


v timestamp: STRING

v smtp_receive_instance_name: STRING

v smtp_receive_instance_name_enum: STRING

v average_recipients_message: INTEGER

v average_recipients_message_enum: STRING

v bytes_received_total: INTEGER

v bytes_received_total_enum: STRING

v bytes_received_per_sec: REAL

v bytes_received_per_sec_enum: STRING

v connections_current: INTEGER

v connections_current_enum: STRING

v connections_total: INTEGER

v connections_total_enum: STRING

v message_bytes_received: INTEGER

v message_bytes_received_enum: STRING

v message_bytes_received_per_sec: REAL

v message_bytes_received_per_sec_enum: STRING

v messages_received_total: INTEGER

v messages_received_total_enum: STRING

v messages_received_per_sec: REAL

v messages_received_per_sec_enum: STRING

v messages_refused_for_size: INTEGER

v messages_refused_for_size_enum: STRING




ITM_MS_Exchange_Transport_SmtpSend MS_Exchange_Transport_SmtpSend attribute group


v timestamp: STRING

v smtp_send_instance_name: STRING

v smtp_send_instance_name_enum: STRING

v average_recipients_message: INTEGER

v average_recipients_message_enum: STRING

v bytes_sent_total: INTEGER

v bytes_sent_total_enum: STRING

v bytes_sent_per_sec: REAL

v bytes_sent_per_sec_enum: STRING

v connections_current: INTEGER

v connections_current_enum: STRING

v connections_total: INTEGER

v connections_total_enum: STRING

v message_bytes_sent: INTEGER

v message_bytes_sent_enum: STRING

v message_bytes_sent_per_sec: REAL

v message_bytes_sent_per_sec_enum: STRING

v messages_sent_total: INTEGER

v messages_sent_total_enum: STRING

v messages_sent_per_sec: REAL

v messages_sent_per_sec_enum: STRING

ITM_MS_Exchange_UM_Auto_Attendant MS_Exchange_UM_Auto_Attendant attribute group


v timestamp: STRING

v auto_attendant_name: STRING

v pct__successful_calls: INTEGER

v average_call_time: INTEGER

v average_recent_call_time: INTEGER

v business_hours_calls: INTEGER

v calls_with_speech_input: INTEGER

v calls_with_spoken_name: INTEGER

v directory_accessed: INTEGER

v directory_accessed_by_dial_by_name: INTEGER

v directory_accessed_by_extension: INTEGER

v directory_accessed_by_spoken_name: INTEGER

v directory_accessed_successfully_by_dial_by_name: INTEGER

v directory_accessed_successfully_by_spoken_name: INTEGER

v disconnected_without_input: INTEGER

v total_calls: INTEGER

v transferred_count: INTEGER




ITM_MS_Exchange_UM_Availability MS_Exchange_UM_Availability attribute group


v timestamp: STRING

v pct__of_messages_successfully_processed_over_the_last_hour:INTEGER

v directory_access_failures: INTEGER

v name_ttsed: INTEGER

v spoken_name_accessed: INTEGER

v total_worker_process_call_count: INTEGER

v worker_process_recycled: INTEGER

v hub_transport_access_completed: INTEGER

v hub_transport_access_completed_enum: STRING

v hub_transport_access_failures: INTEGER

v hub_transport_access_failures_enum: STRING

v mailbox_server_access_failures: INTEGER

v mailbox_server_access_failures_enum: STRING

v failed_mailbox_connection_attempts_pct: INTEGER

v failed_mailbox_connection_attempts_pct_enum: STRING

v average_hub_transport_access_failures_pct: INTEGER

ITM_MS_Exchange_UM_Call_Answer MS_Exchange_UM_Call_Answer attribute group


v timestamp: STRING

v average_greeting_size: INTEGER

v average_recent_voice_message_size: INTEGER

v average_voice_message_size: INTEGER

v call_answering_calls: INTEGER

v call_answering_missed_calls: INTEGER

v call_answering_voice_messages: INTEGER

v calls_without_personal_greetings: INTEGER

v diverted_extension_not_provisioned: INTEGER




ITM_MS_Exchange_UM_General MS_Exchange_UM_General attribute group


v timestamp: STRING

v average_call_duration: INTEGER

v average_mwi_latency: INTEGER

v average_recent_call_duration: INTEGER

v call_duration_exceeded: INTEGER

v calls_disconnected_by_user_failure: INTEGER

v current_auto_attendant_calls: INTEGER

v current_calls: INTEGER

v current_fax_calls: INTEGER

v current_subscriber_access_calls: INTEGER

v current_unauthenticated_pilot_number_calls: INTEGER

v current_voice_mail_calls: INTEGER

v delayed_calls: INTEGER

v total_calls: INTEGER

v total_calls_per_second: REAL

v user_response_latency: INTEGER

ITM_MS_Exchange_UM_Enabled_User_Details MS_Exchange_UM_Enabled_User_Details attribute group


v timestamp: STRING

v mailbox_name: STRING

v dial_plan: STRING

v um_mailbox_policy: STRING




ITM_MS_Exchange_UM_Subscriber_Access MS_Exchange_UM_Subscriber_Access attribute group


v timestamp: STRING

v average_recent_sent_voice_message_size: INTEGER

v average_recent_subscriber_call_duration: INTEGER

v average_sent_voice_message_size: INTEGER

v average_subscriber_call_duration: INTEGER

v calendar_accessed: INTEGER

v calendar_items_details_requested: INTEGER

v calendar_items_heard: INTEGER

v calendar_late_attendance: INTEGER

v called_meeting_organizer: INTEGER

v contact_items_heard: INTEGER

v contacts_accessed: INTEGER

v directory_accessed: INTEGER

v directory_accessed_by_dial_by_name: INTEGER

v directory_accessed_by_extension: INTEGER

v email_message_queue_accessed: INTEGER

v email_messages_deleted: INTEGER

v email_messages_heard: INTEGER

v forward_messages_sent: INTEGER

v launched_calls: INTEGER

v meetings_accepted: INTEGER

v meetings_declined: INTEGER

v replied_to_organizer: INTEGER

v reply_messages_sent: INTEGER

v subscriber_authentication_failures: INTEGER

v subscriber_logon_failures: INTEGER

v subscriber_logons: INTEGER

v voice_message_queue_accessed: INTEGER

v voice_messages_deleted: INTEGER

v voice_messages_heard: INTEGER

v voice_messages_sent: INTEGER




ITM_MS_Exchange_Throttling MS_Exchange_Throttling attribute group


v timestamp: STRING

v throttling_instance_name: STRING

v active_powershell_runspaces: INTEGER

v active_powershell_runspaces_enum: STRING

v active_powershell_runspaces_per_sec: REAL

v active_powershell_runspaces_per_sec_enum: STRING

v average_task_wait_time: INTEGER

v average_task_wait_time_enum: STRING

v average_thread_sleep_time: INTEGER

v average_thread_sleep_time_enum: STRING

v current_delayed_tasks: INTEGER

v current_delayed_tasks_enum: STRING

v delay_time_threshold: INTEGER

v delay_time_threshold_enum: STRING

v exchange_executing_cmdlets: INTEGER

v exchange_executing_cmdlets_enum: STRING

v exchange_executing_cmdlets_per_sec: REAL

v exchange_executing_cmdlets_per_sec_enum: STRING

v max_delay_per_minute: REAL

v max_delay_per_minute_enum: STRING

v max_delayed_tasks: INTEGER

v max_delayed_tasks_enum: STRING

v max_effective_time_in_active_directory_per_minute: REAL

v max_effective_time_in_active_directory_per_minute_enum:STRING

v max_effective_time_in_address_book_per_minute: REAL

v max_effective_time_in_address_book_per_minute_enum: STRING

v max_effective_time_in_cas_per_minute: REAL

v max_effective_time_in_cas_per_minute_enum: STRING

v max_effective_time_in_mailboxrpc_per_minute: REAL

v max_effective_time_in_mailboxrpc_per_minute_enum: STRING

v max_task_queue_length: INTEGER

v max_task_queue_length_enum: STRING

v max_worker_thread_count: INTEGER

v max_worker_thread_count_enum: STRING

v new_task_rejections: INTEGER

v new_task_rejections_enum: STRING

v new_task_rejections_per_sec: REAL





ITM_MS_Exchange_Throttling

(Continued)

v new_task_rejections_per_sec_enum: STRING

v new_tasks_submitted_per_sec: REAL

v new_tasks_submitted_per_sec_enum: STRING

v non_interactive_cutoff_percent: REA

v non_interactive_cutoff_percent_enum: STRING

v over_budget_threshold: INTEGER

v over_budget_threshold_enum: STRING

v task_failures_per_sec: REAL

v task_failures_per_sec_enum: STRING

v task_queue_length: INTEGER

v task_queue_length_enum: STRING

v task_timeouts_per_minute: REAL

v task_timeouts_per_minute_enum: STRING

v total_new_tasks: INTEGER

v total_new_tasks_enum: STRING

v total_task_failures: INTEGER

v total_task_failures_enum: STRING

v total_unique_budgets: INTEGER

v total_unique_budgets_enum: STRING

v unique_budgets_overbudget: INTEGER

v unique_budgets_overbudget_enum: STRING

v users_delayed_x_milliseconds: INTEGER

v users_delayed_x_milliseconds_enum: STRING

v users_x_times_overbudget: INTEGER

v users_x_times_overbudget_enum: STRING

v worker_thread_count: INTEGER

v worker_thread_count_enum: STRING

ITM_MS_Exchange_Role_Topology MS_Exchange_Role_Topology attribute group



v Machine_Name: STRING

v Domain_Name: STRING

v Roles: STRING




ITM_MS_Exchange_Rpc_Client_Access MS_Exchange_RPC_Client_Access attribute group


v timestamp: STRING

v active_user_count: INTEGER

v active_user_count_enum: STRING

v connection_count: INTEGER

v connection_count_enum: STRING

v rpc_averaged_latency: REAL

v rpc_averaged_latency_enum: STRING

v rpc_operations: REAL

v rpc_operations_enum: STRING

v rpc_requests: INTEGER

v rpc_requests_enum: STRING

v user_count: INTEGER

v user_count_enum: STRING

v rpc_packets_sec: INTEGER

v rpc_packets_sec_enum: STRING

v rpc_clients_bytes_read: INTEGER

v rpc_clients_bytes_read_enum: STRING

v rpc_clients_bytes_written: INTEGER

v rpc_clients_bytes_written_enum: STRING

v client_rpcs_attempted: INTEGER

v client_rpcs_attempted_enum: STRING

v client_rpcs_succeeded: INTEGER

v client_rpcs_succeeded_enum: STRING

v client_background_rpcs_succeeded: INTEGE

v client_background_rpcs_succeeded_enum: STRING

v client_foreground_rpcs_succeeded: INTEGER

v client_foreground_rpcs_succeeded_enum: STRING

v client_rpcs_failed: INTEGER

v client_rpcs_failed_enum: STRING

v client_background_rpcs_failed: INTEGER

v client_background_rpcs_failed_enum: STRING

v client_foreground_rpcs_failed: INTEGER

v client_foreground_rpcs_failed_enum: STRING




ITM_MS_Exchange_RPC_HTTP_Proxy MS_Exchange_RPC_HTTP_Proxy attribute group


v timestamp: STRING

v number_of_incoming_rpc_over_http_connections: INTEGER

v number_of_incoming_rpc_over_http_connections_enum: STRING

v current_number_of_unique_users: INTEGER

v current_number_of_unique_users_enum: STRING

v number_of_failed_backend_connection_attempts_per_second:INTEGER

v number_of_failed_backend_connection_attempts_per_second_enum: STRING

v rpc_http_requests_per_second: INTEGER

v rpc_http_requests_per_second_enum: STRING

v total_outgoing_bandwidth_to_backend_servers: REAL

v total_outgoing_bandwidth_to_backend_servers_enum: STRING

v total_incoming_bandwidth_from_backend_servers: REAL

v total_incoming_bandwidth_from_backend_servers_enum:STRING

v number_of_backend_connection_attempts_per_second: REAL

v number_of_backend_connection_attempts_per_second_enum:STRING




ITM_MS_Exchange_Search_Indices MS_Exchange_Search_Indices attribute group


v timestamp: STRING

v search_indices_instance_name: STRING

v average_document_indexing_time: REAL

v average_document_indexing_time_enum: STRING

v recent_average_latency_of_rpcs_used_to_obtain_content: REAL

v recent_average_latency_of_rpcs_used_to_obtain_content_enum:STRING

v full_crawl_mode_status: INTEGER

v full_crawl_mode_status_enum: STRING

v total_time_taken_for_indexing_protected_messages: INTEGER

v total_time_taken_for_indexing_protected_messages_enum:STRING

v average_size_of_indexed_attachments_for_protected_messages:REAL

v average_size_of_indexed_attachments_for_protected_messages_enum: STRING

v throttling_delay_value: REAL

v throttling_delay_value_enum: STRING

v average_size_of_indexed_attachments: REAL

v average_size_of_indexed_attachments_enum: STRING

v number_of_successful_retries: INTEGER

v number_of_successful_retries_enum: STRING

v number_of_failed_retries: INTEGER

v number_of_failed_retries_enum: STRING

v number_of_items_in_a_notification_queue: INTEGER

v number_of_items_in_a_notification_queue_enum: STRING

v number_of_outstanding_batches: INTEGER

v number_of_outstanding_batches_enum: STRING




ITM_MS_Exchange_Search_Mailbox_Operators MS_Exchange_Search_Mailbox_Operators attribute group


v timestamp: STRING

v mailbox_database_name: STRING

v items_processed_in_0_-_50_ms: INTEGER

v items_processed_in_0_-_50_ms_enum: STRING





v items_processed_in_greater_than_2000_ms: INTEGER

v items_processed_in_greater_than_2000_ms_enum: STRING

v items_with_rights_management_attempted_for_processing:INTEGER

v items_with_rights_management_attempted_for_processing_enum:STRING

v items_with_rights_management_partially_processed: INTEGER

v items_with_rights_management_partially_processed_enum:STRING

v items_with_rights_management_skipped: INTEGER

v items_with_rights_management_skipped_enum: STRING

v items_with_valid_annotation_token: INTEGER

v items_with_valid_annotation_token_enum: STRING

v items_without_annotation_token: INTEGER

v items_without_annotation_token_enum: STRING

ITM_MS_Exchange_Search_Mailbox_Session_Cache

MS_Exchange_Search_Mailbox_Session_Cache attribute group


v timestamp: STRING

v cache_instance_name: STRING

v cache_hit_ratio: REAL

v cache_hit_ratio_enum: STRING

v cache_hits: INTEGER

v cache_hits_enum: STRING

v cache_miss_ratio: REAL

v cache_miss_ratio_enum: STRING

v cache_misses: INTEGER

v cache_misses_enum: STRING

v cache_requests: INTEGER

v cache_requests_enum: STRING

ITM_MS_Exchange_Sender_Filter_Agent MS_Exchange_Sender_Filter_Agent attribute group



v Messages_Evaluated_by_Sender_Filter: INTEGER

v Messages_Evaluated_by_Sender_Filter/sec: INTEGER

v Messages_Filtered_by_Sender_Filter: INTEGER

v Messages_Filtered_by_Sender_Filter/sec: INTEGER




ITM_MS_Exchange_Sender_Id_Agent MS_Exchange_Sender_Id_Agent attribute group


v timestamp: STRING

v dns_queries: INTEGER

v dns_queries_enum: STRING

v dns_queries_per_sec: INTEGER

v dns_queries_per_sec_enum: STRING

ITM_MS_Exchange_Connection_Filtering_Agent

MS_Exchange_Connection_Filtering_Agent attribute group



v Connections_on_IP_Allow_List/sec: INTEGER

v Connections_on_IP_Block_List/sec: INTEGER

v Messages_with_Originating_IP_on_IP_Allow_List/sec: INTEGER

v Messages_with_Originating_IP_on_IP_Block_List/sec: INTEGER

ITM_MS_Exchange_Protocol_Analysis_Agent MS_Exchange_Protocol_Analysis_Agent attribute group



v Senders_Blocked_Because_of_Local_Open_Proxy: INTEGER

v Senders_Blocked_Because_of_Local_SRL: INTEGER

v Senders_Blocked_Because_of_Remote_Open_Proxy: INTEGER

v Senders_Blocked_Because_of_Remote_SRL: INTEGER

v Change_in_Senders_Blocked_Because_of_Local_Open_Proxy:INTEGER

v Change_in_Senders_Blocked_Because_of_Local_SRL: INTEGER

v Change_in_Senders_Blocked_Because_of_Remote_Open_Proxy:INTEGER

v Change_in_Senders_Blocked_Because_of_Remote_SRL: INTEGER

ITM_MS_Exchange_Content_Filter_Agent MS_Exchange_Content_Filter_Agent attribute group



v Messages_Scanned_Per_Second: INTEGER

v Messages_Bypassed_Scanning: INTEGER

v Messages_Bypassed_Scanning_organization-wide_Safe_Sender:INTEGER

v Messages_Outlook_Postmark_not_validated: INTEGER

v Messages_Outlook_Postmark_validated_successfully: INTEGER

v Change_in_Messages_Bypassed_Scanning: INTEGER

v Change_in_Messages_Bypassed_Scanning_organization-wide_Safe_Sender: INTEGER

ITM_MS_Exchange_Recipient_Filter_Agent MS_Exchange_Recipient_Filter_Agent attribute group



v Recipients_Rejected_by_Block_List/sec: INTEGER

v Recipients_Rejected_by_Recipient_Validation/sec: INTEGER

v Recipients_Rejected_by_Block_List: INTEGER

v Recipients_Rejected_by_Recipient_Validation: INTEGER




ITM_MS_Exchange_Calendar_Attendant MS_Exchange_Calendar_Attendant attribute group


v timestamp: STRING

v average_calendar_attendant_processing_time: REAL

v average_calendar_attendant_processing_time_enum: STRING

v meeting_requests_invitations: INTEGER

v meeting_requests_invitations_enum: STRING

v meeting_cancellations: INTEGER

v meeting_cancellations_enum: STRING

v meeting_messages_deleted: INTEGER

v meeting_messages_deleted_enum: STRING

v meeting_messages_processed: INTEGER

v meeting_messages_processed_enum: STRING

v meeting_responses: INTEGER

v meeting_responses_enum: STRING

v requests_failed: INTEGER

v requests_failed_enum: STRING

ITM_MS_Exchange_OWA MS_Exchange_OWA attribute group



v Average_Response_Time: INTEGER

v Average_Search_Time: INTEGER

v Proxy_Request_Bytes: INTEGER

v Proxy_Response_Bytes: INTEGER

v Proxy_Response_Time_Average: INTEGER

v Proxy_User_Requests: INTEGER

v Proxy_User_Requests/sec: INTEGER

v Requests: INTEGER

v Request_Failed: INTEGER

v Requests/sec: INTEGER




ITM_Microsoft_Forefront_Server_Security_Scan Microsoft_Forefront_Server_Security_Scan attribute group



v Scan_Job_Name: STRING

v Attachments_Cleaned_Rate: INTEGER

v Attachments_Detected_Rate: INTEGER

v Attachments_Removed_Rate: INTEGER

v Attachments_Scanned_Rate: INTEGER

v Total_Attachments_Cleaned: INTEGER

v Total_Attachments_Detected: INTEGER

v Total_Attachments_Removed: INTEGER

v Total_Attachments_Scanned: INTEGER

v Total_Messages_Detected: INTEGER

v Total_Messages_Purged: INTEGER

v Total_Messages_Scanned: INTEGER

v Total_Messages_Tagged: INTEGER

ITM_Mailbox_Server_Cluster_State Mailbox_Server_Cluster_State attribute group



v Clustered_Mailbox_Server_Name: STRING

v Mailbox_State: STRING

v Operational_Machines: STRING

ITM_MS_Exchange_NLB_Status MS_Exchange_NLB_Status attribute group



v NLB_Status: INTEGER

v Machine_Name: STRING

ITM_MS_Exchange_MAPI_Connectivity_Details

MS_Exchange_MAPI_Connectivity_Details attribute group



v Mailbox_Server_Name: STRING

v Database_Name: STRING

v Connection_Status: INTEGER

ITM_MS_Exchange_Role_Based_Services MS_Exchange_Role_Based_Services attribute group



v Service_Name: STRING

v Service_Status: INTEGER

v Role_Name: STRING




ITM_MS_Exchange_WS MS_Exchange_WS attribute group


v timestamp: STRING

v requests_per_sec: INTEGER

v requests_per_sec_enum: STRING

v total_number_of_ids_converted: INTEGER

v total_number_of_ids_converted_enum: STRING

v ids_converted_per_sec: INTEGER

v ids_converted_per_sec_enum: STRING

v number_of_current_proxy_calls: INTEGER

v number_of_current_proxy_calls_enum: STRING

v total_number_of_proxied_requests: INTEGER

v total_number_of_proxied_requests_enum: STRING

v number_of_proxied_requests_per_second: REAL

v number_of_proxied_requests_per_second_enum: STRING

v total_number_of_bytes_proxied: INTEGER

v total_number_of_bytes_proxied_enum: STRING

v total_number_of_proxy_response_bytes: INTEGER

v total_number_of_proxy_response_bytes_enum: STRING

v total_number_of_proxy_failover: INTEGER

v total_number_of_proxy_failover_enum: STRING

v number_of_proxy_failovers_per_second: REAL

v number_of_proxy_failovers_per_second_enum: STRING

v proxy_average_response_time: REAL

v proxy_average_response_time_enum: STRING

v average_response_time: REAL

v average_response_time_enum: STRING

v totalclientdisconnects: INTEGER

v totalclientdisconnects_enum: STRING




ITM_Forefront_Exchange_On_Demand_Scanner

Forefront_Exchange_On_Demand_Scanner attribute group


v timestamp: STRING

v on_demand_scanner_job_name_u: STRING

v malware_message_parts_cleaned: INTEGER

v malware_message_parts_deleted: INTEGER

v malware_message_parts_detected: INTEGER

v malware_message_parts_quarantined: INTEGER

v message_parts_scanned: INTEGER

v message_parts_scanned_per_sec: REAL

v messages_scanned_per_sec: REAL

v sender_filter_messages_detected: INTEGER

v sender_filter_messages_quarantined: INTEGER

v sender_filter_messages_skipped: INTEGER

v subject_filter_messages_detected: INTEGER

v subject_filter_messages_quarantined: INTEGER

v subject_filter_messages_skipped: INTEGER

ITM_Forefront_Exchange_Realtime_Scanner Forefront_Exchange_Realtime_Scanner attribute group


v timestamp: STRING

v realtime_scanner_job_name_u: STRING








v sender_filter_message_parts_detected: INTEGER

v sender_filter_message_parts_quarantined: INTEGER

v sender_filter_message_parts_skipped: INTEGER

v subject_filter_message_parts_detected: INTEGER

v subject_filter_message_parts_quarantined: INTEGER

v subject_filter_message_parts_skipped: INTEGER




ITM_Forefront_Exchange_Scheduled_Scanner Forefront_Exchange_Scheduled_Scanner attribute group


v timestamp: STRING

v scheduled_scanner_job_name_u: STRING








v sender_filter_message_parts_detected: INTEGER

v sender_filter_message_parts_quarantined: INTEGER

v sender_filter_message_parts_skipped: INTEGER

v subject_filter_message_parts_detected: INTEGER

v subject_filter_message_parts_quarantined: INTEGER

v subject_filter_message_parts_skipped: INTEGER

ITM_Forefront_Exchange_Transport_Scanner Forefront_Exchange_Transport_Scanner attribute group


v timestamp: STRING

v transport_scanner_job_name_u: STRING








v sender_filter_messages_detected: INTEGER

v sender_filter_messages_quarantined: INTEGER

v sender_filter_messages_skipped: INTEGER

v subject_filter_messages_detected: INTEGER

v subject_filter_messages_quarantined: INTEGER

v subject_filter_messages_skipped: INTEGER


Appendix C. Discovery Library Adapter for the MicrosoftExchange Server agent

The Tivoli Management Services Discovery Library Adapter (DLA) discovers resources and relationships,and creates a Discovery Library Book file for the agent.

About the DLA

The Book file follows the Discovery Library IdML schema and is used to populate the ConfigurationManagement Database (CMDB) and Tivoli Business Service Manager products. The Tivoli ManagementServices DLA discovers Microsoft Exchange Server resources. For all Microsoft Exchange Server systemsthat are active and online at the Tivoli Enterprise Portal Server, information is included in the discoverybook for those resources. The Tivoli Management Services DLA discovers active resources. It is run ondemand and can be run periodically to discover resources that were not active during previousdiscoveries.

The DLA discovers Microsoft Exchange Server components.

More information about DLAs

The following sources contain additional information about using the DLA program with all monitoringagents:v The IBM Tivoli Monitoring Administrator's Guide contains information about using the Tivoli

Management Services Discovery Library Adapter.v For information about using a DLA with Tivoli Application Dependency Discovery Manager (TADDM),

see the TADDM Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.2/welcome_page/welcome.html).

DLA data model class types represented in CDMThe source application data objects map to classes in the Common Data Model (CDM) for the MicrosoftExchange Server agent.

The following information is provided for each class:

CDM class nameClass name for which the agent is providing information

RelationshipsCDM relationships (hierarchical) between currently identified model objects

CDM attributes, agent attributes, descriptions, and examplesCDM and agent attributes that are required to create an instance of a resource, descriptions of theattributes, and examples of the attributes

DLA data model classes for Microsoft Exchange Server agentEach agent that uses the Discovery Library Adapter has DLA data model classes defined for the agent.

The Microsoft Exchange Server agent has the following Discovery Library Adapter data model classes:v ExchangeServer classv ExchangeStorageGroup classv ExchangePublicFolderStore class


http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.2/welcome_page/welcome.html

v ExchangeMailBoxStore classv TMSAgent class

ExchangeServer classThe ExchangeServer class represents the instance of the Microsoft Exchange Server.

CDM class nameapp.messaging.exchange.ExchangeServer

Relationships

containsv Source: ExchangeServerv Target: ExchangeStorageGroupv Example: 10.77.69.207-ExchangeServer contains ESX3-PG3-22-Second_Storage_Group-

ExchangeStorageGroup

monitorsv Source: TMSAgentv Target: ExchangeServerv Example: EXCH14-W2K8:EX-TMSAgent monitors 10.77.70.100-ExchangeServer

runsOnv Source: ExchangeServerv Target: ComputerSystemv Example: 10.77.70.100-ExchangeServer runs on 10.77.70.100-ComputerSystem

runsOnv Source: ExchangeServerv Target: OperatingSystemv Example: 10.77.70.100-ExchangeServer runs on 10.77.70.100-OperatingSystem

CDM attributes, agent attributes, descriptions, and examples

v CDM attribute: Id (IdML)Agent attribute: INODESTS.HOSTADDRDescription: The IP address of the workstation where the Microsoft Exchange Server isrunning.Example: 10.77.89.34 - ExchangeServer

v CDM attribute: ManagedSystemNameAgent attribute: INODESTS.NODEDescription: The name of the IBM Tivoli Monitoring component that provides data for themanagement of this instance.Example: PS0313:EX

v CDM attribute: ActiveDirectoryDomainNameAgent attribute: MSESERVR.SRVRADDNDescription: The version of the Microsoft Exchange Server.Example: Exchange2000

v CDM attribute: StatusAgent attribute: MSESERVR.STATUSDescription: The status of the Microsoft Exchange Server.Example: Running

v CDM attribute: Product VersionAgent attribute: MSESERVR.VERSIONDescription: The version of the Microsoft Exchange Server.


Example: 2000

ExchangeStorageGroup classThe ExchangeStorageGroup class represents the storage group on the Microsoft Exchange Server.

CDM class nameapp.messaging.exchange.ExchangeStorageGroup

Relationships

containsv Source: ExchangeServerv Target: ExchangeStorageGroupv Example: 10.77.69.207-ExchangeServer contains ESX3-PG3-22-First Storage

Group-ExchangeStorageGroup

memberOfv Source: ExchangeMailboxStorev Target: ExchangeStorageGroupv Example: ESX3-PG3-22-First Storage Group-Mailbox Database-ExchangeMailboxStore

memberof ESX3-PG3-22-First Storage Group-ExchangeStorageGroup

memberOfv Source: ExchangePublicFolderStorev Target: ExchangeStorageGroupv Example: ESX3-PG3-22-Second_Storage_Group-Public_DB-ExchangePublicFolderStore memberof

ESX3-PG3-22-Second_Storage_Group-ExchangeStorageGroup


v CDM attribute: Id (IdML)Agent attribute: MSESGRPD.SGNAMEDescription: The ID that represents the storage group on the Microsoft Exchange Server.Example: TestStorageGroup- ExchangeStorageGroup

v CDM attribute: DistinguishedNameAgent attribute: MSESGRPD.DISTNAMEDescription: The distinguished name of the storage group on the Microsoft Exchange Server.Example: CN=StorageGp333,CN=InformationStore,CN=IBMESX4-ITM-284,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=AdministrativeGroups,CN=First Organization,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=exchangepoc,DC=com

v CDM attribute: ManagedSystemNameAgent attribute: INODESTS.NODEDescription: The name of the IBM Tivoli Monitoring component that provides data for themanagement of this instance.Example: PS0313:EX

v CDM attribute: StorageGroupNameAgent attribute: MSESGRPD.SGNAMEDescription: The name of the storage group.Example: LCRStorage

ExchangePublicFolderStore classThe ExchangePublicFolderStore class represents the public folder store on the Microsoft Exchange Server.

CDM class nameapp.messaging.exchange.ExchangePublicFolderStore

Appendix C. Discovery Library Adapter for the Microsoft Exchange Server agent 335

Relationships

memberOfv Source: ExchangePublicFolderStorev Target: ExchangeStorageGroupv Example: ESX3-PG3-22-Second_Storage_Group-Public_DB-ExchangePublicFolderStore memberof

ESX3-PG3-22-Second_Storage_Group-ExchangeStorageGroup


v CDM attribute: Id (IdML)Agent attribute: MSEISPUB.DISTNAMEDescription: The ID of the storage group.Example: ESX3-PG3-22-Second_Storage_Group-Public_DB-ExchangePublicFolderStore

v CDM attribute: DistinguishedNameAgent attribute: MSEISPUB.DISTNAMEDescription: The distinguished name of the storage group.Example: CN=Public_DB,CN=Second_Storage_Group,CN=InformationStore,CN=IBMESX4-ITM-284,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=AdministrativeGroups,CN=First Organization,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=exchangepoc,DC=com

v CDM attribute: PublicFolderStoreNameAgent attribute: MSEISPUB.DISTNAMEDescription: The distinguished name of the public folder store.Example: Public_DB

ExchangeMailBoxStore classThe ExchangeMailBoxStore class represents the instance of a mailbox store on the Microsoft ExchangeServer.

CDM class nameapp.messaging.exchange.ExchangeMailboxStore

Relationships

memberOfv Source: ExchangeMailboxStorev Target: ExchangeStorageGroupv Example: ESX3-PG3-22-First Storage Group-Mailbox Database-ExchangeMailboxStore

memberof ESX3-PG3-22-First Storage Group-ExchangeStorageGroup


v CDM attribute: Id (IdML)Agent attribute: MSEISPRI.DISTNAMEDescription: The ID of the mailbox.Example: ESX3-PG3-22-First Storage Group-Mailbox Database-ExchangeMailboxStore

v CDM attribute: DistinguishedNameAgent attribute: MSEISPRI.DISTNAMEDescription: The distinguished name of the mailbox.Example: CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=IBMESX4-ITM-284,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=exchangepoc,DC=com

TMSAgent classThe TMSAgent class represents a Tivoli Management Services agent.


CDM class nameapp.TMSAgent

Relationships

memberOfv Source: TMSAgentv Target: ExchangeServerv Example: EXCH14-W2K8:EX-TMSAgent memberof 10.77.70.100-ExchangeServer


v CDM attribute: Id (IdML)Agent attribute: INODESTS.NODEDescription: The ID of the IBM Tivoli Monitoring component that provides data for themanagement of this instance.Example: ESX3-PG3-22:EX-TMSAgent

v CDM attribute: ManagedSystemNameAgent attribute: INODESTS.NODEDescription: The name of the IBM Tivoli Monitoring component that provides data for themanagement of this instance.Example: ESX3-PG3-22:EX

v CDM attribute: ManagedObjectNameAgent attribute: INODESTS.NODEDescription: The name of the IBM Tivoli Monitoring component that provides data for themanagement of this instance.Example: p@ESX3-PG3-22:EX

v CDM attribute: SoftwareVersionAgent attribute: INODESTS.VERSIONDescription: The version of the Microsoft Exchange agent.Example: 06.30.00

v CDM attribute: Product CodeAgent attribute: INODESTS.PRODUCTDescription : The product code of the Microsoft Exchange agent.Example : EX

v CDM attribute: AffinityAgent attribute: INODESTS. AFFINITIESDescription: The affinity of the Microsoft Exchange agent.Example: 0000000080000000000000000000000004000H468f0

v CDM attribute: LabelAgent attribute: INODESTS.NODEDescription: The label of the Microsoft Exchange agent.Example: ESX3-PG3-22:EX - Exchange Server

Appendix C. Discovery Library Adapter for the Microsoft Exchange Server agent 337

Appendix D. Integration with Tivoli Business Service Manager

Microsoft Exchange Server agent provides data to create, update the status of, and view IBM TivoliBusiness Service Manager services.

The Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkitprovides data for the Tivoli Business Service Manager service models. The Tivoli Event IntegrationFacility (EIF) probe updates the status of these services, and you use the Tivoli Enterprise Portal to viewthe data for the services. To implement the integration of the agent with Tivoli Business Service Manager,perform the integration tasks.

Components for integrating with Tivoli Business Service ManagerThe data for integrating with Tivoli Business Service Manager is supplied through the followingcomponents: Tivoli Management Services Discovery Library Adapter (DLA) and Discovery LibraryToolkit, Tivoli Event Integration Facility (EIF) probe, and Tivoli Enterprise Portal.

Tivoli Management Services Discovery Library Adapter (DLA) and DiscoveryLibrary Toolkit

By using data from the Tivoli Management Services Discovery Library Adapter, you can build TivoliBusiness Service Manager service models that include resources monitored by the Microsoft ExchangeServer agent.

The DLA files can be imported directly into Tivoli Business Service Manager using the Discovery LibraryToolkit or they can be loaded into IBM Tivoli Application Dependency Discovery Manager (TADDM) andthen fed into Tivoli Business Service Manager using the Discovery Library Toolkit.

See the following sources for more information about the DLA and Discovery Library Toolkit:v Resources and relationships that are discovered by the Microsoft Exchange Server agent and included

in Tivoli Management Services DLA files: Appendix C, “Discovery Library Adapter for the MicrosoftExchange Server agent,” on page 333

v Using the Tivoli Management Services DLA: IBM Tivoli Monitoring Administrator's Guide

v Using the Discovery Library Toolkit: Tivoli Business Service Manager Customization Guide

Tivoli Event Integration Facility (EIF) probe

Situation events detected by the Microsoft Exchange Server agent can update the status of services inTivoli Business Service Manager.

The situation events are forwarded from IBM Tivoli Monitoring to the Netcool/OMNIbus Probe for theTivoli Event Integration Facility. The Microsoft Exchange Server agent provides a probe rules file thatupdates its events with information to identify the affected service in Tivoli Business Service Manager.The EIF probe then forwards the events to the Netcool/OMNIbus ObjectServer. Tivoli Business ServiceManager monitors the Netcool/OMNIbus ObjectServer for new events and updates the status of affectedservices.

See the following sources for more information about event integration:v Installation (using an existing EIF probe and Netcool/OMNIbus ObjectServer installation or using

Tivoli Business Service Manager to install these components): Netcool/OMNIbus Information Center orthe Tivoli Business Service Manager Installation Guide.


v Setting up event integration between IBM Tivoli Monitoring, the EIF probe, and the Netcool/OMNIbusObjectServer: IBM Tivoli Monitoring Installation and Setup Guide.

v Configuring the EIF probe to use the Microsoft Exchange Server agent rules file after the EIF probe hasbeen installed and configured for event integration with IBM Tivoli Monitoring: “Configuring theTivoli Event Integration Facility (EIF) probe to enrich events”

Tivoli Enterprise Portal

You can use the integration of the Tivoli Enterprise Portal with Tivoli Business Service Manager to viewthe services in the Tivoli Business Service Manager console.

For more detailed examination and analysis, you can easily link from the Tivoli Business Service Managerconsole to the Tivoli Enterprise Portal to view the data within the Microsoft Exchange Server agent.

Tasks to integrate the agent with Tivoli Business Service ManagerTo integrate the Microsoft Exchange Server agent with Tivoli Business Service Manager, you must installand configure the required components. Then, you can view the data in the Tivoli Enterprise Portal.

To integrate the Microsoft Exchange Server agent with Tivoli Business Service Manager and view thedata, complete the following tasks:v Install the Discovery Library Toolkit on theTivoli Business Service Manager server.v Configure the Tivoli Event Integration Facility (EIF) probe to enrich Microsoft Exchange Server agent

events.v Create a service in the Tivoli Business Service Manager console that you want to monitor.v Create a data source mapping for each data source that you want to access within the Tivoli Business

Service Manager.v Configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal Server.v View data in the Tivoli Enterprise Portal for the services that you have created to monitor through

Tivoli Business Service Manager.

Installing the Discovery Library Toolkit on the Tivoli Business ServiceManagerYou must install the Discovery Library Toolkit on the Tivoli Business Service Manager server.

The Discovery Library Toolkit imports data from the DLA files and TADDM, which includes informationabout the hardware and the applications that are discovered by the source.

See "Installing the Discovery Library Toolkit" in the Tivoli Business Service Manager Installation Guide.

Configuring the Tivoli Event Integration Facility (EIF) probe to enricheventsThe Netcool/OMNIbus Probe for Tivoli Event Integration Facility (EIF) forwards the Microsoft ExchangeServer agent events that are received from IBM Tivoli Monitoring to the Netcool/OMNIbus ObjectServer.Tivoli Business Service Manager monitors the Netcool/OMNIbus ObjectServer for new events, andupdates the status of affected services. The Microsoft Exchange Server agent provides a probe rulesinclude file that updates its events with information to identify the affected service in Tivoli BusinessService Manager.


Before you begin

Install and configure the Netcool/OMNIbus ObjectServer and EIF probe and set up event integrationbetween IBM Tivoli Monitoring and Netcool/OMNIbus.

About this task

To enable event enrichment, configure the EIF probe to use the rules file for the agent.

Procedure1. Locate the Microsoft Exchange Server agent rules file (kex_tbsm.rules) on a computer system where

the Microsoft Exchange Server agent, Tivoli Enterprise Monitoring Server, or Tivoli Enterprise PortalServer is installed. The file is in the following locations:v On Windows systems

The file is in the installdir\cms\TECLIB directory of the monitoring server, in theinstalldir\cnps\TECLIB directory of the portal server, or in the installdir\TMAITM6\EIFLIBdirectory of the agent, where installdir is the IBM Tivoli Monitoring or ITCAM for MicrosoftApplications installation directory.

v On Linux and UNIX systemsThe file is in the installdir/tables/ms_name/TECLIB directory of the monitoring server or in theinstalldir/platform/xx/TECLIB directory of the agent, where installdir is the IBM Tivoli Monitoringor ITCAM for Microsoft Applications directory, ms_name is the name of the monitoring server, andplatform is the architecture directory for the agent.

2. Copy the kex_tbsm.rules file to the following directory on the computer system where the EIF probeis installed:v On Windows systems

%OMNIHOME%\probes\arch

v On UNIX systems$OMNIHOME/probes/arch

Where:

OMNIHOMESystem-defined variable defining the installation location of Netcool/OMNIbus

arch Operating system directory where the probe is installed; for example, solaris2 when runningon a Solaris system, and win32 for a Windows system.

3. Edit the tivoli_eif.rules file and uncomment the include statement for kex_tbsm.rules. (Thetivoli_eif.rules file is located in the same directory as the kex_tbsm.rules file.) If you are using aversion of the tivoli_eif.rules file without an include statement for kex_tbsm.rules, add thefollowing line after the include statement for itm_event.rules:include "kex_tbsm.rules"

4. Restart the EIF probe.

Creating a service in Tivoli Business Service ManagerYou must create a service in the Tivoli Business Service Manager console for each service that you wantto monitor.

To create the services that you want to monitor in the Tivoli Business Service Manager console, see"Configuring services" in the IBM Tivoli Business Service Manager Service Configuration Guide.

Appendix D. Integration with Tivoli Business Service Manager 341

Creating a data source mapping for each data sourceYou can create a data source mapping for each data source that you want to access within Tivoli BusinessService Manager.

Also, you can create the data fetchers and use the data to create incoming status rules that are populatedin your service templates.

For more information, see "Data sources" and "Data fetchers" in the IBM Tivoli Business Service ManagerService Configuration Guide.

Configuring additional IBM Tivoli Monitoring web servicesYou can configure additional IBM Tivoli Monitoring web services for each Tivoli Enterprise Portal Server.

To configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal server, see"Configure TBSM charts" in the IBM Tivoli Business Service Manager Scenarios Guide.

Viewing data in the Tivoli Enterprise PortalFrom Tivoli Business Service Manager, you can open the Tivoli Enterprise Portal and view the MicrosoftExchange Server agent.

You can also launch Tivoli Business Service Manager from the Tivoli Enterprise Portal.

For more information about launching applications, see "Launching to and from applications" in the TivoliBusiness Service Manager Customization Guide.


Appendix E. Documentation library

A variety of publications are relevant to the use of the IBM Tivoli Composite Application Manager forMicrosoft Applications: Microsoft Exchange Server Agent.

The IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Manager products: DocumentationGuide, SC23-8816, contains information about accessing and using publications. You can find theDocumentation Guide in the following information centers:v IBM Tivoli Monitoring and OMEGAMON® XE (http://publib.boulder.ibm.com/infocenter/tivihelp/

v15r1/index.jsp)v IBM Tivoli Composite Application Manager (http://publib.boulder.ibm.com/infocenter/tivihelp/

v24r1/index.jsp)

To open the Documentation Guide in the information center, select Using the publications in theContents pane.

To find a list of new and changed publications, click What's new in the information center on theWelcome page of the IBM Tivoli Monitoring and OMEGAMON XE Information Center.

To find publications from the previous version of a product, click Previous versions under the name ofthe product in the Contents pane.

IBM Tivoli Composite Application Manager for Microsoft Applications: MicrosoftExchange Server Agent library

The documentation for this agent and other product components is located in the IBM Tivoli CompositeApplication Manager for Microsoft Applications Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html).

One document is specific to the IBM Tivoli Composite Application Manager for Microsoft Applications:Microsoft Exchange Server Agent: IBM Tivoli Composite Application Manager for Microsoft Applications:Microsoft Exchange Server Agent User’s Guide. This publication provides agent-specific information forconfiguring, using, and troubleshooting the Microsoft Exchange Server agent.

The Offering Guide also provides information about installing and configuring the component products inthe offering.

The Prerequisites topic in the information center contains information about the prerequisites for eachcomponent.

Use the information in the user's guide for the agent with the Tivoli Enterprise Portal User's Guide tomonitor Microsoft Exchange Server resources.

Prerequisite publicationsTo use the information in this publication effectively, you must have some prerequisite knowledge.

See the following publications to gain the required prerequisite knowledge:v IBM Tivoli Monitoring Readme First

v Exploring IBM Tivoli Monitoring

v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Agent Builder User's Guide


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp



v IBM Tivoli Monitoring Command Reference

v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Manager products: DocumentationGuide

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring Universal Agent User's Guide

v IBM Tivoli Universal Agent API and Command Programming Reference Guide

v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring

v IBM Tivoli Monitoring: Upgrading from V5.1.2

v IBM Tivoli Monitoring: i5/OS Agent User's Guide

v IBM Tivoli Monitoring: Linux OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX Logs OS Agent User's

v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v Tivoli Enterprise Portal User's Guide

Related publicationsThe publications in related information centers provide useful information.

See the following information centers, which you can find by accessing Tivoli Documentation Central(http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home):v IBM Tivoli Monitoringv IBM Tivoli Netcool/OMNIbusv Tivoli Application Dependency Discovery Managerv IBM Tivoli Enterprise Console

Other sources of documentationYou can obtain additional technical documentation about monitoring products from other sources.

See the following sources of technical documentation about monitoring products:v Service Management Connect (SMC)

See the introductory information about SMC (http://www.ibm.com/developerworks/servicemanagement/).For information about Tivoli products, see the Application Performance Management community onSMC (http://www.ibm.com/developerworks/servicemanagement/apm/index.html).Connect, learn, and share with Service Management professionals. Get access to developers andproduct support technical experts who provide their perspectives and expertise. You can use SMC forthese purposes:– Become involved with transparent development, an ongoing, open engagement between external

users and developers of Tivoli products where you can access early designs, sprint demos, productroadmaps, and pre-release code.

– Connect one-on-one with the experts to collaborate and network about Tivoli and Integrated ServiceManagement.

– Benefit from the expertise and experience of others using blogs.– Collaborate with the broader user community using wikis and forums.


http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home

http://www.ibm.com/developerworks/servicemanagement/



v IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/ismlibrary/) is an online catalog that contains integration documentation as well as otherdownloadable product extensions.

v IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications,Redpapers, and Redbooks technotes that provide information about products from platform andsolution perspectives.

v Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBMSoftware Support website, provide the latest information about known product limitations andworkarounds.

v Tivoli wikisTivoli Wiki Central (http://www.ibm.com/developerworks/wikis/display/tivoli/Home) is the homefor interactive wikis that offer best practices and scenarios for using Tivoli products. The wikis containwhite papers contributed by IBM employees, and content created by customers and business partners.Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki (http://www-10.lotus.com/ldd/

tivmonitorwiki.nsf) provides information about IBM Tivoli Monitoring and related distributedproducts, including IBM Tivoli Composite Application Manager products.

– Tivoli System z® Monitoring and Application Management Wiki (http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home) provides information about theOMEGAMON XE products, Tivoli NetView® for z/OS, Tivoli Monitoring Agent for z/TPF, andother System z monitoring and application management products.

Appendix E. Documentation library 345

http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/support/entry/portal/software

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www-10.lotus.com/ldd/tivmonitorwiki.nsf

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conformingto IBM‘s application programming interfaces.


Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

© IBM 2009. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.2009. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, orboth.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United Statesand other countries.

Other company, product, or service names may be trademarks or service marks of others.

Notices 349

Index

Aactivities 231additional information

attributes 59situations 211Take Action commands 227Workspaces 47

agentproblems and workarounds 260

Agent Management Services 3attribute groups

overview 59attribute groups, navigator items 49attributes

additional information 59overview 59

Ccalculate historical data disk space 206capacity planning for historical data 206commands 42

tacmd addSystem 30Take Action 227

components 2IBM Tivoli Monitoring 2

configurationagent 9problems and workarounds 256remote 30tacmd command line 30Tivoli Enterprise Portal 30

configuringcommunication for resource models 19creating a local administrator 17, 18creating a MAPI profile 18

configuring agentlocally 21

configuring the monitoring agent 9configuring the run-as user ID 20create 13

Ddata

trace logs 250data collection 4data sources 4descriptions 214developerWorks website 344Discovery Library Adapter

See DLAdisk capacity planning for historical data 206DLA 333

data model 333classes 333

documentationSee publications

Eenhancements 2environment 1event

mapping 275exchange server 2007 13, 16exchange server 2010 16

Ffeatures 1files

trace logs 250

Hhistorical data

calculate disk space 206disk capacity planning 206

IIBM Tivoli Enterprise Console

event mapping 275IBM Tivoli Monitoring 2installation 21

agent 9problems and workarounds 256remote 30silent 21

installing agentlocally 21

installing language packs 9installing the monitoring agent 9instance name 24Integrated Service Management Library documentation 344interface, user 3

Llanguage packs

installing 9limited user permissions, upgrading your warehouse

with 272local configuration 21local installation 21logging

location and configuration of logs 250trace log files 250

MMAPI profile 18Messaging Application Programming Interface profile 18Microsoft Exchange Server

configuring communication 19creating a local administrator 17, 18creating a MAPI profile 18


Microsoft Exchange Server agent 1

Nnew in this release 2new user utility 13

PPassword 24path names, for trace logs 250permissions, upgrading your warehouse with limited

user 272policies 231prerequisite checker 12prerequisite publications 343prerequisites 12problems and workarounds 256

agent-specific 260agent-specific workspaces 262configuration 256install 256remote deployment 259situations 264Take Action commands 267Tivoli Common Reporting 268workspaces 262

publications 343, 344developerWorks website 344IBM Tivoli Monitoring 343Integrated Service Management Library 344prerequisite 343Redbooks 344related 344Technotes 344wikis 344

Qqueries, using attributes 59

RReachability

configuring communication for 19Redbooks 344remote configuration 30remote deployment

problems and workarounds 259remote installation 30run-as user ID

configuring 20

SServer Name 24silent 21situations 214

additional informationpredefined, defined 211

overview 211predefined 212Situation Editor 211

situations, using attributes 59

Ttacmd addSystem command 30tacmd command line

remote configuration 30tacmd startAgent 42Take Action commands

additional information 227overview 227predefined 227, 231problems and workarounds 267

take actionsdescriptions 228

Technotes 344Tivoli Common Reporting

problems and workarounds 268Tivoli Enterprise Portal

configuring the agent remotely 30trace logs 250

directories 250troubleshooting 249, 256

agent-specific 260agent-specific workspaces 262installation 256remote deployment 259situations 264Take Action commands 267Tivoli Common Reporting 268uninstallation 256workspaces 262

Uupgrading for warehouse summarization 271upgrading your warehouse with limited user

permissions 272user

administrator rights 16user ID

configuring the run-as 20user interfaces options 3user permissions, upgrading your warehouse with

limited 272users 13

Wwarehouse summarization

upgrading foroverview 271

warehouse summarization upgradingeffects on summarized attributes 271table summary 273tables in the warehouse 271

wikis 344workarounds 256Workflow Editor 231workspaces

predefined 47problems and workarounds 262

Workspacesadditional information 47overview 47


��

Printed in USA

SC23-6593-06

store interface workspace.........57 resource scheduling details workspace ....57 availability...

Documents