The Forest Recovery Console provides a tool that allows you to check the health of your forest. You can use the tool to run tests to ensure that domain controllers, Active Directory® replication, domain trusts, user authentication, RID Master, and global catalog are working properly in your Active Directory® forest.
The Forest Recovery Console automatically prompts you to check the forest health after the forest recovery has succeeded, so that you could ensure the forest works exactly the way you want. If necessary, you can manually run a health check on your forest at any time before or after the forest recovery operation.
| NOTE |
Recovery Manager for Active Directory uses the domain controller access credentials to perform the forest health checks. Make sure, that the credentials are valid. For more details see the General tab section. |
What does Recovery Manager for Active Directory check?
Verifies that every domain controller in a forest is accessible and running using the LDAP bind request to the directory root (RootDSE) of a domain controller.
Checks that Forest Recovery Agents are installed on domain controllers and accessible using the RPC call to get information about agents and domain controller states.
Open your recovery project.
In the Forest Recovery Console, from the main menu, select Tools | Diagnose | Check Forest Health.
In the dialog box that opens, on the Settings tab, select the check boxes next to the items whose health you want to check.
When finished, click the Check Health button.
When the check health operation completes, use the Details tab to view information about the health of the selected items.
If you select the User authentication; RID Master and GC operation option on the Settings tab, you can specify a container for the test user account on the domain controller.
For the list of required permissions, see Recovery Manager .
Close the Forest Recovery console.
Open the project (.frproj) file that was created by the Console and edit the '<Domains>' section, as shown in the following example.
You can specify different containers for different domains.
<Domains>
<Domain DomainName="rmad.local" HealthCheckContainer="OU=test1" />
<Domain DomainName="second.rmad.local" HealthCheckContainer="OU=test2” />
</Domains>
To specify the same container for different domains, you can use the asterisk wildcard (*), for example:
<Domains>
<Domain DomainName="*" HealthCheckContainer="OU=test1" />
</Domains>
You should specify the relative container distinguished name for the HealthCheckContainer attribute. For example, if the full DN of the container is OU=test1,DC=rmad,DC=local, specify the DN name as OU=test1.
There may be a situation where technical support requests you to gather and supply diagnostic data from your computer collection. For this purpose, you can use a special tool provided in the Forest Recovery Console called Diagnostic Data Collector.
| NOTE |
From version 8.7, the diagnostic data can be collected for the Recovery Manager Console as well. |
From Forest Recovery Console machine
Collects the data saved in the current Recovery Project (.frproj) file, except for the passwords stored in that file.
Collects the Forest Recovery Console log
Collects the Recovery Manager for Active Directory event logs
.db3 database files
Recovery Manager for Active Directory
From Domain Controller
Collects Backup and Restore agent logs
Collects system event logs
Windows debug logs
Runs Microsoft Netdiag, Dcdiag, Nltest, MsInfo32 and Repadmin tools (in diagnostic mode only), and then collects the output provided by these tools. The tools are started by Collectdcdata.cmd and you can modify the list of collected logs.
To gather diagnostic data for your recovery project by using the Diagnostic Data Collector, you need to complete the following steps:
Step 1: Use Diagnostic Data Collector to automatically gather data. In this step, you use the Diagnostic Data Collector to automatically gather diagnostic data from each domain controller in your recovery project and save the data to the folder you specify. You can perform this step regardless of whether or not a recovery operation is currently running on the recovery project. If this step completes successfully for all domain controllers, Step 2 is not needed.
Step 2: Gather remaining data manually. You need to perform this step only for those domain controllers from which you could not successfully collect data in Step 1. In Step 2, you copy several files supplied with Recovery Manager for Active Directory to the target domain controller, and then run one of the copied files. As a result, diagnostic data is collected from the domain controller and saved to a new folder created in the location from which you ran the file.
There have been some changes in the way data is collected from domain controllers.
The log collector now first attempts to connect to the forest recovery agent, and if it's available, the log collector uses RPC to send a request to collect data, and then RPC pipes to retrieve the collected files from the domain controller back to the console. If a recovery agent is not available, the log collector uses the original approach of deploying a separate log collector service on a domain controller and using a network share to copy the collected files from the domain controller to the console.
By default, the log collector uses certificate-based SCHANNEL authentication, so no credentials are required to communicate with the forest recovery agent. If for any reason the SCHANNEL authentication between the console and the forest recovery agent is broken (for example, the certificate is missing), it will use NEGOTIATE authentication with the credentials provided in the Collect diagnostic data dialog. If no credentials are specified, the log collector will use the credentials from the General tab (both normal mode credentials and DSRM credentials).
The next sections provide instructions on how to complete each of these steps.
In the Forest Recovery Console, open the recovery project you want to collect diagnostic data.
Make sure you specify credentials to access each domain controller in the project. To check whether you specified access credentials for a particular domain controller, do the following:
Select that domain controller in the list of domain controllers.
Open the General tab.
Make sure you specify the correct credentials in the Domain Controller Access option.
The Forest Recovery Console will use the specified credentials to access the domain controller and gather diagnostic data from it.
From the menu bar, select Tools | Diagnose | Collect Diagnostic Data.
Use the Drop folder text box to specify the local or UNC path to the folder where you want to save the diagnostic data to be collected. The collected data is saved to a .zip, e.g. CollectedLogs_10_20_2015 07_23_25.zip
You can change credentials to access the domain controllers that were specified on the step 2.
Select the Delete collected logs from domain controllers option to delete collected RMAD\RMADFE logs from domain controllers.
Click the Collect button and wait for the operation to complete.
If you successfully collected data from all the domain controllers in this step, you can submit the .zip file to Quest® technical support. Otherwise, complete Step 2: Gather remaining data manually.
Perform the next steps for each domain controller from which you could not successfully collect data in Step 1: Use Diagnostic Data Collector to automatically gather data.
Create a temporary folder on the local disk of the target domain controller.
Copy Collectdcdata.cmd from the Recovery Manager for Active Directory installation folder to the folder you created in step 1 of this procedure.
Run the Collectdcdata.cmd file in the location you copied it to and wait for the script to complete.
The collected diagnostic data is saved to the CollectedData folder created in the location where you ran the Collectdcdata.cmd file.
Rename the CollectedData folder so that its name reflects the name of the domain controller from which you collected data.
Add the folder to the .zip file created in Step 1: Use Diagnostic Data Collector to automatically gather data.
Now you can submit the .zip file to Quest technical support.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center