How to Exclude Domain Controllers from Scanning
In order to generate a report that includes non-replicated attributes, it is necessary to scan every domain controller within a specific domain to ensure accurate results.
However, there may be instances where you want to exclude certain domain controllers from the scanning process. With the help of our Active Directory Reports tool, you have the option to choose which domain controllers should be included in the scan.
When you navigate to the Forest tab and select a domain from the domain list, AD Reports will populate a list of all available domain controllers for the selected domain. By default, all domain controllers are automatically selected.

To exclude any recognized and available domain controllers from the scanning process, you can easily deselect them by removing the check mark next to their respective names in the Domain Controllers list.
A domain controller whose details AD Reports cannot read is still listed, by name, and the Output panel says so Improved in 7.6.4: one whose read timed out stays checked, so you can uncheck it to leave it out of scans; one whose read failed with an error is unchecked — excluded from scans — until you check it again. A domain controller that cannot be read during a scan — restarting for updates, say — is left out of that scan and tried again 10 minutes later. A scheduled report that could not read one records Partial in Job History and names it — “1 domain controller could not be read: DC03 (The server is not operational).” — and a report run on the AD Reports page says so in the Output panel. A domain controller you excluded never counts.