Active Administrator 8.6 - User Guide

Enable logging

Enable logging

In Active Administrator, you can view recent log entries that are stored in memory. See Managing Active Directory Health Analyzer agents. If you require a log file for troubleshooting purposes, you can enable logging in the utility, which writes the log entries to a file.

Logging for the Active Directory Health Analyzer agent is disabled by default. Enable logging only if you need a log file for troubleshooting as the process may affect performance. The maximum size for the log file is 500 MB. Once the log file reaches its maximum size, it will automatically roll over. The log file is located at C:\Windows\DAAgent\DAAgent.log.

NOTE: When you enable logging, system performance may be affected. Use the utility for troubleshooting purposes only.

•	Launch DAAgentConfig.exe, which is located at C:\Windows\DAAgent.

▪	To enable logging, click Enable, and click Yes to confirm.

▪	To view the log file, click View Log File.

▪	To delete the log file, navigate to C:\Windows\DAAgent\, and delete the DAAgent.log file.

Excluding domain controllers

Excluding domain controllers

You can exclude specified domain controllers when analyzing forests, domains, and sites, and from matching Active Directory Health Check tests. Excluded domain controllers will also be removed from the Agent Configuration wizard.

To exclude domain controllers

1	Select Active Directory Health | Agents.

2	Open the Analyzer Agents tab.

3	Select More | Excluded Domain Controllers.

1	Click Add, and browse for the domain controllers to exclude.

2

Click OK.

Use Remove to remove selected domain controllers from the list.

Managing the Remediation Library

Managing the Remediation Library

IMPORTANT: You must restart the ADS Service to load the ExcludedDomainControllers.xml file.

Remediations are actions that run when an alert reaches its critical threshold. Several built-in remediation actions are included, but you also can create custom remediations, which can be a PowerShell® script, VBS script, batch file, or .cmd file. Once you have populated the library with the remediations you need, you attach the remediations to alerts. See Setting alerts.

Topics 

•	Adding custom remediations

•	Deleting custom remediations

To manage the Remediation Library

1	Select Active Directory Health | Agents.

2	Open the Monitored Domain Controllers tab, and click Remediations.

The Remediation Library displays custom remediations in the top pane and built-in remediations in the bottom pane. You can add, edit, or delete custom remediations. See Adding custom remediations. See Deleting custom remediations.You cannot edit or delete built-in remediations.

 

Table 32. Built-in remediations

Remediation action	Description
Reboot Computer	Reboots the specified computer
Restart Windows Service	Restarts the specified Windows service
Start Windows Service	Starts the specified Windows service
Stop Windows Service	Stops the specified Windows service
Stop Process	Stops the specified process.
Start Process	Starts the specified process.
Perform Active Directory Replications	Performs Active Directory replication for all servers in the forest.
Start Conflict and Deleted Folder Cleanup	Performs DFSR SYSVOL replicated folder conflict cleanup.

Adding custom remediations

Adding custom remediations

If the built-in remediations do not provide what you need, you can create a custom remediation, which can be a PowerShell® script, VBS script, batch file, or .cmd file. After you create the custom remediation, you need to attach it to an alert. See Setting alerts.

 

NOTE: Custom remediation definitions are stored in \\AAServer\ActiveAdministrator\DACache\Remediations.xml.

To add a custom remediation

1	Select Active Directory Health | Agents.

2	Open the Monitored Domain Controllers tab, and click Remediations.

3	Click Add to create a new custom remediation.

-OR-

Click Edit to modify a selected custom remediation.

4	Enter a name for the remediation action.

5	Enter a description for the action.

6	Browse to locate the script to run.

IMPORTANT: The script must be accessible from the Active Administrator® server.

7	If arguments are required, select the check box and enter a description of the arguments to use.

NOTE: Arguments are supplied when you attach a remediation action to an alert. The description will help another user provide the necessary arguments. See Setting alerts.

8	Select the Active Directory® objects on which the script is supported.

NOTE: Built-in remediation actions can run on any Active Directory® object.

9

Click OK.