Moving an audit agent
You can move the audit agent from one computer to another.
To move an audit agent
1 Select Auditing & Alerting | Agents.
2 Select a domain controller, and select More | Move.
IMPORTANT: Auditing must be enabled in all domains that will be monitored. Make sure auditing is enabled on the Default Domain Controller policy. See the Quest® Active Administrator®Install Guide.
4 Click Next.
NOTE: The Active Administrator Agent service can run under a domain user account provided it is a local administrative account, which gives it the rights to log on as a service, log on locally, and manage auditing and security log, or an account with these privileges granted individually. This 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 initial database creation were modified and the group can be found under the Users container object of Active Directory®.
Table 67. Install options
Start collecting events immediately after installation of the agent
By default, Active Administrator monitors the status of the audit agent.
8 Click OK.
NOTE: You can view details about the move agent process in the MoveAgentInstall*.log file, which is located in C:\ProgramData\Quest\Active Administrator\Logs.
Automating audit agent deployment
Once you have installed an agent into a domain, Active Administrator® can monitor the domain for new domain controllers. When a new domain controller is discovered, the agent can be automatically installed on that domain controller. You also have the option to just notify users of a new domain controller so they can install the agent manually.
Deploy audit agent automatically
To deploy the audit agent automatically
1 Select Auditing & Alerting | Agents.
2 Click Auto Deployment.
3
Table 68. Install options
By default, the audit agent is installed on the newly discovered domain controllers.
NOTE: The Active Administrator Agent service can also run under a domain user account provided it is a local administrative account, which gives it the rights to log on as a service, log on locally, and manage auditing and security log, or an account with these privileges granted individually. This 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 initial database creation were modified and the group can be found under the Users container object of Active Directory®.
8 Click OK.Notify users only
To only notify users of newly discovered domain controllers
1 Select Auditing & Alerting | Agents.
2 Click Auto Deployment.
3
4 Select Only notify users.
NOTE: You also can manage the Agent Auto Deploy Configuration email list from the Settings menu. See Managing email addresses.
6 Click OK.
Canceling pending automated deployments
To cancel pending automated deployments
1 Select Auditing & Alerting | Agents.
2 Click Auto Deployment.
3 Click Pending Installations.
4 Select a pending installation, and click Cancel automated agent installation.
5 Click OK.
Managing alerts
TIP: You can configure the notification service to send emails in batches. See Setting notification options.The Alert page shows the alerts in the top pane and the alert history for a selected alert in the bottom pane. You can size the panes by dragging the horizontal split bar up or down.
To manage alerts
1 Select Auditing & Alerting | Alerts.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center