Active Administrator 8.8.1 - Installation Guide

Table 2. Install options for the audit agent
Option	Description
Install on target Domain Controller(s)	By default, the audit agent is installed on the domain controllers you selected on the previous page.
Audit from an agent on the following computer	Select to install the audit agent on a computer in the domain. Type a computer's fully qualified domain name in the box, or browse to locate a computer. NOTE: If you choose to do remote monitoring, the Advanced Agent is not installed on the selected domain controllers.
Start collecting events immediately after installation of the agent	By default, the audit agent is activated and collection begins immediately upon completion of the installation process. Clear the check box if you want to activate the audit agents manually.
Enable agent monitoring and recovery	By default, Active Administrator monitors the status of the audit agent.

Click Next.

In the Run as box, type an account with domain administrator rights, or browse to locate an account, and enter the password.


	NOTE: The Active Administrator Agent service can also run under a domain user account provided it is either a local administrator account, which gives it the rights to log on as a service and log on locally, or these two privileges can be granted individually. This user or service account should also be a member of the AA_Admin group, which by default is located in the local groups of the server where the ActiveAdministrator database is located. If the group is not found in this location, the settings during the initially database creation were modified and it can be found under the Users container object of Active Directory®.

To verify the account, click Test Audit Agent Account.

Click Next.

Review the summary.

Click Next.

Click Finish.

The Audit Agent page lists the domain controllers you selected, the time and date of the last event collected, the status of the audit agent and the advanced audit agent, the name of the server on which Active Administrator is installed, and the version number of the audit agent installed on the domain controller.


	NOTE: By default, the audit agent is activated upon installation. To change the default setting, select Configuration \| Agent Installation Settings. You can view details about the install in the AuditAgentInstall*.log file, which is located here: C:\ProgramData\Quest\Active Administrator\Logs.

Creating alerts

A wizard guides you through creating a new Active Administrator alert. Alerts provide you the opportunity to combine different conditions into one alert that is sent to specified email recipients. You also can add a filter to the alert to further isolate audit events for the recipient.

To create a new alert

Select Auditing & Alerting | Alerts.

Click New.

On the Welcome page, click Next.

Type a name and optional description for the alert.

Select the priority of the alert: normal, low, or high.

Click Next.

Set up the email list of the recipients of the alert notification.

To manage the email list

•

To add a new email address, click Add and type the email address.

•

To edit a selected email address, click Edit.

•

To remove a selected email address from the list, click Remove.

Click Next.

Select the Event Definitions to include in the alert.

•

To filter the list, type text in the Filter box. The list changes as you type characters. The definitions displayed contain the characters you type. For example, if you type com, the definitions displayed may contain the words Completed or Computer.

•

To clear the filter and restore the list, click X.

•

To show only selected definitions, open the Show box, and choose Selected.

•

To show only unselected definitions, open the Show box, and choose Unselected.

Click Next.

Add alert filters.

Use this feature to help limit the number of emails sent to the specified email list. Alert filters are optional and applied to the details section of the event. Only the events that match the filter will be included in the notification email. For example, if the alert filter is Contains OU=Sales, only the events where OU=Sales appears in the details section are included in the notification email.

To define an alert filter

Click Add to add a new alert filter.

–OR-

Click Edit to edit a selected alert filter.

Select if the email Contains or Does not contain the condition text.

Type the text to find in the details section of the alert.

By default the filter conditions are combined using the OR operator. If you want to connect with the AND operator, select AND all conditions.

Click Next.

Define the quiet time during which no notifications are sent. Alerts that are triggered during the quiet time are still logged to the Alert History. Setting an Alert Quiet Time is optional.


	NOTE: There is also a global quiet time that you can set. The quiet times set here are in addition to any global quiet times.

To define a quiet time

Click Add to add a new quiet time.

–OR-

Click Edit to edit a selected quiet time.

Select Enabled. To disable a quiet time, clear the check box.

Select All Days or specify a specific day.

Set the start and end time.

By default, actions associated with the alert are stopped during quiet time. To run actions during quiet time, select the check box.

Click Next.

Set the alert threshold. The alert threshold sets limits that must be met before alerts are sent out.

To add a new threshold

Click Add to add a new threshold.

–OR-

Click Edit to edit a selected threshold.

Select Enabled. To disable a threshold, clear the check box.

Select the event definition from the list.

Select the number of events and minutes to define the threshold.

Click Next.

Define the action that this alert runs when the alert condition is met.

The action is run using the Notification service account. Please make sure the Notification Service account has sufficient rights to all of the resources needed by the action.

To define the action the alert runs

Select Enabled. To disable an action, clear the check box.

Type the full path to the .EXE file for the program or script or browse to locate the .EXE file.


	NOTE: The script must reside in a share on the Active Administrator server. That share must be accessible to the Active Administrator Foundation Server (AFS) service and the operator of the remote Active Administrator console. The path to the script must be entered using Uniform Naming Convention (UNC).