Reestablish a global catalog after forest-root recovery

Use this document to connect an official requirement or behavior to observable evidence: Reestablish a global catalog after forest-root recovery. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official AD Forest Recovery – Adding the GC from Microsoft supports the following bounded statements:

• The forest-recovery sequence includes adding the global catalog role to a domain controller. The research record locates this support at Opening overview.
• Microsoft documents both the standard add operation and a repadmin-based method. The research record locates this support at Sections: Add the global catalog; Add the global catalog using repadmin.

The source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Confirm replication health and role placement before advertising the recovered global catalog. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections: Add the global catalog; Add the global catalog using repadmin, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and sanitize protected material before retention.

Verification and evidence

Tie each conclusion back to Opening overview; Sections: Add the global catalog; Add the global catalog using repadmin and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• AD Forest Recovery – Adding the GC — Microsoft