Delete unreachable DC objects during forest-recovery cleanup

Treat this document as a focused evidence review: Delete unreachable DC objects during forest-recovery cleanup. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official AD Forest Recovery – Cleaning metadata of removed writable domain controllers from Microsoft supports the following bounded statements:

• Metadata cleanup removes AD data that identifies a domain controller to the replication system. The research record locates this support at Opening overview.
• The cleanup applies when a controller cannot complete normal demotion because it is no longer reachable. The research record locates this support at Opening overview.

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps only where the source and recorded environment align.

What the source does not establish

Delete only controllers the recovery plan identifies for reinstall; preserve surviving authorities. A correct source interpretation can still be inapplicable to a particular design. Confirm offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps are in and out of scope?
• Which condition in offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

Build a reproducible chain from Opening overview; Opening overview to the observed environment. Useful domain evidence includes backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings; label every item with scope, timestamp, collector, and stable identifier.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• AD Forest Recovery – Cleaning metadata of removed writable domain controllers — Microsoft