This Knowledge Script is obsolete, although you can continue to use it. Its functionality is distributed among the following Knowledge Scripts introduced with AppManager for Exchange Server 2007 version 7.3.
********************************************************************************************************
Use this Knowledge Script to collect Exchange Server 2007 performance data for reporting and trend analysis. This script raises an event if the DataCollection job fails.
Before running this script, ensure that the AppManager agent service (netiqmc) is a member of the following security groups on the specified Exchange Server 2007 role:
Exchange Server 2007 Role |
Membership Group |
---|---|
Client Access server role |
The local Administrators group on the Client Access server |
Mailbox server role |
|
Hub Transport server role |
|
Edge Transport server role |
|
Exchange_ServerIcon
Exchange_ClientAccessServer
Exchange_EdgeTransportServer
Exchange_HubTransportServer
Exchange_MailboxServer
To monitor individual storage groups and mailbox databases, use the Objects tab to select the specific objects to monitor.
The default schedule is Every 30 minutes.
Set the following parameters as needed:
Parameter |
How to Set It |
---|---|
General Settings |
|
Job failure event notification |
|
Event severity when job fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the DataCollection job fails. The default is 5. |
Raise event indicating active/passive cluster state? |
Select Yes to raise an informational event indicating the current status of the cluster: active or passive. The default is No. |
Collect Exchange Server 2007 Data |
|
Client Access Server Role |
|
Collect data for Outlook Web Access activity? |
Select Yes to collect data related to Outlook Web Access (OWA) activity. When enabled, data collection returns the following data streams:
The data in these data streams is collected from the MSExchange OWA performance counter category. |
Collect data for IMAP4 activity? |
Select Yes to collect data related to IMAP4 activity. When enabled, data collection returns the following data streams:
These data streams are not available if the IMAP4 service is not running. The data in these data streams is collected from the MSExchangeImap4 performance counter category. |
Collect data for POP3 activity? |
Select Yes to collect data related to POP3 activity. When enabled, data collection returns the following data streams:
These data streams are not available if the POP3 service is not running. The data in these data streams is collected from the MSExchangePop3 performance counter category. |
Edge Transport Server Role |
|
Collect data for recipients and domains of outgoing mail? |
Select Yes to collect data related to outgoing e-mail domains and recipients. When enabled, data collection returns the following data streams:
Use the Number of top recipients and domains used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top recipient domains, based on message count and total message size. |
Number of top recipients and domains used in data |
Set the number of recipients and domains you want to include in the data streams generated by the Collect data for recipients and domains of outgoing mail? parameter. The default is 10. |
Collect data for domains sending incoming mail? |
Select Yes to collect data related to external domains that send incoming e-mail. When enabled, data collection returns the following data streams:
Use the Number of top domains used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top sending domains, based on message count and total message size. |
Number of top domains used in data |
Set the number of domains you want to include in the data streams generated by the Collect data for domains sending incoming mail? parameter. The default is 10. |
Collect data for senders of outgoing mail? |
Select Yes to collect data related to senders of e-mail to external addresses. When enabled, data collection returns the following data streams:
Use the Number of top senders used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top senders of e-mail, based on message count and total message size. |
Number of top senders used in data |
Set the number of senders you want to include in the data streams generated by the Collect data for senders of outgoing mail? parameter. The default is 10. |
Collect data for recipients of incoming mail? |
Select Yes to collect data related to recipients of e-mail from external addresses. When enabled, data collection returns the following data streams:
Use the Number of top recipients used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top recipients of e-mail, based on message count and total message size. |
Number of top recipients used in data |
Set the number of recipients you want to include in the data streams generated by the Collect data for recipients of incoming mail? parameter. The default is 10. |
Hub Transport Server Role |
|
Collect data for SMTP send and receive activity? |
Select Yes to collect data related to SMTP activity. When enabled, data collection returns the following data streams:
The data in these data streams is collected from the MSExchangeTransportSmtpReceived and MSExchangeTransportSmtpSend performance counter categories. |
Collect data for transport dumpster queue usage? |
Select Yes to collect data for transport dumpster queue activity. When enabled, data collection returns the number of e-mail in the dumpster at a given instance and also the space allocated for the transport dumpster. |
Collect data for items queued for delivery? |
Select Yes to collect data for MTA queue activity. When enabled, data collection returns the number of messages queued for delivery |
Collect data for recipients of internal mail? |
Select Yes to collect data related to recipients of internal e-mail. When enabled, data collection returns the following data streams:
Use the Number of top recipients used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top recipients of internal e-mail, based on message count and total message size. |
Number of top recipients used in data |
Set the number of internal e-mail recipients you want to include in the data streams generated by the Collect data for recipients of internal mail? parameter. The default is 10. |
Collect data for senders of internal mail? |
Select Yes to collect data related to senders of internal mails. When enabled, data collection returns the following data streams:
Use the Number of top senders used in data parameter to determine the value of n. AppManager uses the Get-MessageTrackingLog cmdlet to determine the top senders of internal e-mail, based on message count and total message size. |
Number of top senders used in data |
Set the number of internal e-mail senders you want to include in the data streams generated by the Collect data for senders of internal mail? parameter. The default is 10. |
Mailbox Server Role |
|
Collect data for mailbox size and message count? |
Select Yes to collect data related to mailbox size and message counts. When enabled, data collection returns the following data streams:
Use the Number of top mailboxes and mailbox databases used in data parameter to determine the value of n. AppManager uses Exchange cmdlets to determine the largest mailboxes and mailbox databases, based on number and size of mailboxes and messages. |
Number of top mailboxes and mailbox databases used in data |
Set the number of mailboxes and mailbox databases you want to include in the data streams generated by the Collect data for mailbox size and message count? parameter. The default is 10. |
Collect data for RPC activity of information store? |
Select Yes to collect data related to RPC (Remote Procedure Call) activity for the information store. When enabled, data collection returns the following data streams:
The data in these data streams is collected from the MSExchangeIS performance counter category. |
Collect data for message transmission activity? |
Select Yes to collect data related to message transmissions. When enabled, data collection returns the following data streams:
The data in these data streams is collected from the MSExchangeIS Mailbox performance counter category. |
Collect data for disk activity? |
Select Yes to collect data related to logical disk activity. When enabled, data collection returns the following data streams:
The data in these data streams is collected from the LogicalDisk performance counter category. |
Collect data for copy and replay queue length? |
Select Yes to collect data for copy and replay queue length. When enabled, data collection returns the following data streams:
The data in these data streams is collected per storage group. The storage group has to be enabled with Local Continuous Replication (LCR) or Cluster Continuous Replication (CCR) or both. |
Collect data for file share witness usage on two node CCR setup? |
Select Yes to collect data for file share witness usage on a two node CCR setup. When enabled, data collection returns data for the following data streams:
|