Chat now with support
Chat with Support

Active Administrator 8.6.2 - User Guide

Active Administrator Overview User Provisioning Certificates Security & Delegation  Active Directory Health
Switching to Active Directory Health Using the Active Directory Health landing page Installing Active Directory Health Analyzer agents Using the Active Directory Health Analyzer agent configuration utility Excluding domain controllers Managing the Remediation Library Analyzing Active Directory health Analyzing Azure Active Directory Managing Active Directory Health Analyzer alerts Managing alert notifications Pushing alerts to System Center Operations Manager and SNMP managers Managing monitored domain controllers Managing data collectors Active Directory Health Templates Managing Active Directory Health Analyzer agents Using the Troubleshooter Recovering Active Directory Health data
Auditing & Alerting Group Policy Active Directory Recovery Active Directory Infrastructure DC Management DNS Management Configuration
Using the Configuration landing page Managing tasks Defining role-based access Setting email server options Configuring SCOM and SNMP Settings Setting notification options Setting Active Template options Setting agent installation options Setting recovery options Setting GPO history options Setting certificate configuration Setting service monitoring policy Managing archive databases Migrating data to another database Setting a preferred domain controller Setting up workstation logon auditing Managing configuration settings Setting user options Managing the Active Directory server
Diagnostic Console Alerts Appendix
Domain controller alerts
Active Directory Certificate Services service is not running Active Directory Domain Services is not running Active Directory Web Services service is not running Consecutive replication failures DC cache hits DC DIT disk space DC DIT log file disk space DC LDAP load DC LDAP response too slow DC Memory Usage DC properties dropped DC RID pool low DC SMB connections DC SYSVOL disk space DC time sync lost Detected NO_CLIENT_SITE record DFS Replication service not running DFS service is not running DFSR conflict area disk space DFSR conflict files generated DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted DFSRS CPU load DFSRS unresponsive DFSRS virtual memory DFSRS working set DNS Client Service is not running Domain controller CPU load Domain controller page faults Domain controller unresponsive File Replication Service is not running File replication (NTFRS) staging space free in kilobytes GC response too slow Group policy object inconsistent Hard disk drive Intersite Messaging Service is not running Invalid primary DNS domain controller address Invalid secondary DNS domain controller address KDC service is not running LSASS CPU load LSASS virtual memory LSASS working set Missing SRV DNS record for either the primary or secondary DNS server NETLOGON not shared NetLogon service is not running Orphaned group policy objects exist Physical memory Power supply Primary DNS resolver is not responding Secondary DNS resolver is not responding Security Accounts Manager Service is not running SRV record is not registered in DNS SYSVOL not shared W32Time service is not running Workstation Service is not running
Domain alerts Site alerts Forest alerts Azure Active Directory Connect alerts
Event Definitions PowerShell cmdlets

Updating audit agents

Previous Next


Auditing & Alerting > Managing audit agents > Updating audit agents

Updating audit agents

If you receive an update to the audit agent, use this option to install the update.

To update audit agents
1
Select Auditing & Alerting | Agents.
2
To update selected domain controller(s), select More | Update.

–OR-

To update all listed domain controllers, select More | Update All.

 
* 
NOTE: You may need to refresh the audit agents to correct the display. Click Refresh or select domain controllers, and click Refresh Selected.

Moving an audit agent

Previous Next


Auditing & Alerting > Managing audit agents > Moving an audit agent

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.
3
Select the account to use to move the agent. You can use the Active Administrator Foundation Service (AFS) account, or indicate a specific user account.
 
* 
NOTE: The selected account must be a full Administrator on the target server.
4
Click Next.
5
Type the target computer name or browse to locate a computer.
6
Type the user name and password of the account with domain administrative rights on the selected target computer.
* 
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®.
7
Choose options for the install process.
 

Table 67. Install options

Option

Description

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.

8
Click OK.
* 
NOTE: You can view details about the move agent process in the MoveAgentInstall*.log file, which is located in the Active Administrator\Server\Logging folder.

Automating audit agent deployment

Previous Next


Auditing & Alerting > Managing audit agents > Automating audit agent deployment

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
•
Notify users only
Deploy audit agent automatically
To deploy the audit agent automatically
1
Select Auditing & Alerting | Agents.
2
Click Auto Deployment.
3
On the General tab, select Enable automated agent deployment and notification.
4
Select whether to install the audit agent on the newly discovered domain controller or to audit the newly discovered domain controller using an agent on a different computer.
 

Table 68. Install options

Option

Description

Install on target Domain Controller(s)

By default, the audit agent is installed on the newly discovered domain controllers.

Audit from an agent on the following computer

Select to install the audit agent on a computer in the domain. Type a computer 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.
5
Type an account with domain administrative 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 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®.
6
By default, Active Administrator waits 24 hours after discovering a domain controller before installing the audit agent. Change the wait time if necessary.
* 
NOTE: During the wait time, you can cancel the pending installation. See Canceling pending automated deployments.
7
By default, Active Administrator monitors the status of the audit agent. To disable service monitoring and recovery, clear the check box.
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
On the General tab, select Enable automated agent deployment and notification.
4
Select Only notify users.
5
Use the buttons to add, edit, or remove email addresses from the list.
 
* 
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

Previous Next


Auditing & Alerting > Managing audit agents > Canceling pending automated deployments

Canceling pending automated deployments

When you set up Auto Deployment, you set a wait time between discovering domain controllers and installing the agent. During that wait time you can cancel the installation.

Topics 
•
Creating an alert
•
Managing existing alerts
•
Changing the alert notification policy
•
Setting global quiet time
•
Managing alert history
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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating