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.

AD Reports Exclude Domain Controllers

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.

The list of domain controllers is saved in AD Reports' local database, and each time you select a domain it is compared with Active Directory: new domain controllers are added (scanned unless you uncheck them), removed ones are dropped, and the Output panel says what changed; your exclusions are kept New in 7.6.4. To read the list from Active Directory again at any time, press the Reload button.
Your exclusions now persist (Fixed in 7.5.2.0): unchecking a domain controller sticks across domain reloads. Previously the exclusion could be silently lost whenever the domain was reloaded, so an excluded domain controller could quietly end up back in your scans.
Slow domain controllers are handled better (Improved in 7.5.2.0): when the domain controller list is first loaded, a single unresponsive domain controller no longer stalls the whole load far beyond its timeout — and domain controllers that are slow but healthy are kept in the list instead of being dropped as “timed out”.
If you have any questions or need assistance, please don't hesitate to contact us.

Ready to try AD Reports?

Download the free 14-day trial and start reporting on your Active Directory today.