Chat now with support
Chat with Support

Archive Manager 5.9.1 - Administration Guide

Administration menu Authentication modes Data loaders Download tools Federated Search Instances Groups Index management Logins Security roles Storage location Message tags Proxy credentials Alert Service Policies Exclusion rules Mail servers Mailbox assignment Mailboxes Lync servers Lync user assignment Lync users Reports Message policies Message policy assignments Retention policies Tenants System maintenance Log Viewer Exchange Utility Administering in a hosted Exchange environment Appendix A: Moving database or attachment store Appendix B: Enabling generating publisher evidence

Modifying an Alert Policy

You can modify or delete an alert policy by clicking the Edit or Delete icon in the Alert Service Policies screen.

Sample alert message

The following is an example of how an alert message may be set up.

An administrator wants to be alerted when the attachments to index queue becomes greater than 100,000 messages. The alert is to be sent from to with the subject of “Attachments to Index Queue is Too Large”. The alert service is to check the status attachments to index every 15 minutes.

The alert policy would be defined as follows:

Name: Archive Manager Attachments to Index
When: Count Threshold: Greater Than or Equal To 100000
Subject: Attachments to Index Queue is Too Large
Message Body: Administrative action is required within 24 hours to resolve this situation.
Check Interval: 12 hours

The alert message would contain the following information:


Exclusion rules

About exclusion rules

Exclusion rules allow Archive Manager to ignore an email message based on specified attributes. This can be useful for ensuring that system-generated or administration messages are not included in the Archive Manager store. Archive Manager stores an MD5 value of excluded messages, which can be purged if required.

Archive Manager includes four Exclusion Rules by default. Exchange 2013 sends automatically generated email to monitor the health of the system. It is not necessary to archive these emails. These Exclusion Rules can be deleted if needed.

BUILTIN: E2013 Health Monitor: From inboundproxy: From
BUILTIN: E2013 Health Monitor: To inboundproxy: To

An exclusion rule cannot be deleted after an email has been excluded by that rule. Exclusion rules have the following characteristics:

The Exclusion Rule criteria may include one or more of the following parameters:

Name: The name by which you want the exclusion rule to be identified (for example, "System files").
From: The email address where the message(s) originated (example:
To: The email address to which the excluded email message(s) are sent. Important: The rule will work only where there is a single recipient in the To field of the message.
Subject: The Subject of email(s) you want to exclude. The exclusion will apply only to email(s) whose Subjects match exactly the string entered here. You may use a wildcard asterisk in this string to represent one or more characters at the beginning or end of the string, or somewhere within the string.
Header: Header information included in the email messages to be excluded (example: Content-Transfer-Encoding). The Header Value field (below) must contain a corresponding value for this Header setting to take effect.
Header Value: Header value information contained in excluded email messages (example: binary).

These field notes apply to both the Add and Edit features for exclusion rules.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating