# Capture domain-controller system state with two supported methods > Use AD Forest Recovery - Backing up the System State data to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/capture-dc-system-state-with-supported-methods/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:14:34+00:00 - Modified: 2026-08-27T12:58:58+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Business Continuity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use AD Forest Recovery - Backing up the System State data to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of AD Forest Recovery - Backing up the System State data ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Capture domain-controller system state with two supported methods. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [AD Forest Recovery – Backing up the System State data](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-backing-up-system-state) from Microsoft supports the following bounded statements: - The forest-recovery procedure creates domain-controller system-state backups with Windows Server Backup or wbadmin.exe. The research record locates this support at Opening overview. - Microsoft documents separate GUI and command-line procedures for the same recovery input. The research record locates this support at Sections: Windows Server Backup; Wbadmin.exe. Keep the evidence boundary at these traced claims. They support a review of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish A completed job is not sufficient evidence; verify backup integrity, retention, and restore usability. 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: Windows Server Backup; Wbadmin.exe, 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. Anchor the review in the cited section and keep observation separate from interpretation. 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. Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels. ## Verification and evidence A reviewer should be able to retrace the decision from Opening overview; Sections: Windows Server Backup; Wbadmin.exe through backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Record what was collected, where, when, by whom, and which system or role it represents. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [AD Forest Recovery – Backing up the System State data](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-backing-up-system-state) — Microsoft ## Primary reference - Name: AD Forest Recovery - Backing up the System State data - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-backing-up-system-state - Source publication date: 2025-05-12 ## Citation and use Preferred citation: “Capture domain-controller system state with two supported methods,” DSE Security, https://update.dsesecurity.com/updates/capture-dc-system-state-with-supported-methods/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.