This guide walks you through restoring Active Directory from a Windows Server Backup, a process that returns your domain controllers to a previous state after accidental deletions, corruption, or other issues. You’ll need a valid backup that includes the System State (which contains AD data) and access to Directory Services Restore Mode (DSRM) credentials. The steps below apply to Windows Server 2016, 2019, and 2022.
What You’ll Need
- A Windows Server Backup (or another backup tool) that captured the System State of the domain controller.
- The DSRM password for the domain controller you’re restoring.
- Administrator credentials on the server.
- Access to the backup media (local disk, network share, or removable drive).
- A plan for restoring multiple domain controllers (if applicable) — usually restore one, then let replication handle the rest.
Step-by-Step
- Boot into Directory Services Restore Mode (DSRM). Restart the server. During boot, press F8 (or Shift+F8 on some systems) to open Advanced Boot Options. Select Directory Services Restore Mode and press Enter. Log in with the local Administrator account using the DSRM password (not the domain admin password).
- Open Windows Server Backup. Once in DSRM, open Server Manager, then click Tools > Windows Server Backup. If the snap-in isn’t installed, add it via Add Roles and Features.
- Start the Recovery Wizard. In the right pane, click Recover. The Recovery Wizard opens.
- Select the backup source. Choose This server if the backup is stored locally, or A backup stored on another location to browse to a network share or external drive. Click Next.
- Choose the backup date. Select the specific backup you want to restore from the calendar and list. Make sure it’s a System State backup. Click Next.
- Select recovery type. Choose System State and click Next.
- Specify restore options. Select Original location to restore in place. For a non-authoritative restore (the standard method), leave Restore the System State to its original location selected and Do not check the box for Perform an authoritative restore (unless you specifically need to force replication of deleted objects — see Tips). Click Next.
- Confirm and begin. Review the summary, then click Finish. The restore begins; it may take several minutes to an hour.
- Restart automatically. The server will restart automatically after the restore. If it doesn’t, restart manually. The server will boot into normal mode.
- Verify the restore. After boot, log in with a domain account. Open Event Viewer and check the Directory Service log for errors. Run
dcdiag /candrepadmin /replsumto confirm replication is healthy.
Common Mistakes
- Forgetting the DSRM password. If you don’t know it, you can’t log in to DSRM. You can reset it using
ntdsutilfrom a normal command prompt (if you have domain admin rights), but that’s a separate procedure. - Choosing the wrong backup. Restoring an older backup than necessary can cause more data loss. Always pick the most recent backup that contains the pre-incident state.
- Performing an authoritative restore unintentionally. If you check the authoritative restore box, the restored data will be replicated to all other domain controllers, potentially overwriting newer changes. Only use this when you deliberately want to roll back AD objects across the domain.
- Restoring on a server that’s not the intended one. The backup must match the server’s identity (computer name and SID). Restoring a backup from another domain controller can cause conflicts.
- Not checking replication afterward. Even after a successful restore, replication issues can arise. Always run
repadminanddcdiag.
Tips
- If you have multiple domain controllers, restore one and let replication bring the others up to date. This is the standard approach for a non-authoritative restore.
- For an authoritative restore (to undo a mass deletion), you must use
ntdsutilafter the System State restore to mark specific objects as authoritative. This is advanced and should be tested in a lab first. - Always test your backups by restoring to a lab environment periodically. This ensures you can actually restore when needed.
- If the backup is stored on a network share, ensure the server has network access in DSRM. Sometimes you need to load network drivers manually.
- Consider using Windows Server Backup scheduled backups that include System State. This is the simplest way to have a restore point.
Troubleshooting
- Cannot boot into DSRM. If F8 doesn’t work, use
msconfigto check the boot options, or use the installation media to boot and select Repair your computer > Troubleshoot > Command Prompt, then runbcdedit /set safeboot dsrepair. After restoring, runbcdedit /deletevalue safeboot. - Restore fails with “Access denied”. Ensure you’re logged in as the local Administrator in DSRM, not a domain account. Also verify the backup file permissions if using a network share.
- Backup not visible in the wizard. If the backup is on a removable drive, make sure it’s connected and recognized. For network shares, you may need to provide credentials in the wizard.
- Restore completes but AD doesn’t work. Check event logs for errors. Run
dcdiag /candrepadmin /showrepl. If replication fails, you may need to force replication or demote/promote the DC again. - System State restore is grayed out. This happens if the backup doesn’t contain System State. Use a backup that includes it, or re-run the backup with System State selected.
- Server boots normally but hangs after login. This can happen if the restore was incomplete. Restart and try again, or use
ntdsutilto check the AD database integrity.
Frequently Asked Questions
Can I restore Active Directory without DSRM?
No, DSRM is required for a System State restore on a domain controller. It stops AD services so the restore can overwrite files safely.
What is the difference between authoritative and non-authoritative restore?
Non-authoritative restore (the default) lets the restored data be updated by other domain controllers via replication. Authoritative restore marks the restored objects as the most current, so they replicate out and overwrite changes on other DCs.
How long does a System State restore take?
It varies based on hardware and data size, but typically 30 minutes to 2 hours. The server will be unavailable during this time.
Can I restore AD to a different server?
No, a System State backup is tied to the original server’s identity. You cannot restore it to a different machine without a full bare-metal recovery and even then, it’s not recommended.
Do I need to restore all domain controllers?
No, restore one DC and let replication bring the others up to date. Restoring all DCs from backups can cause conflicts and USN rollback issues.
What if I don’t have a System State backup?
You cannot restore AD from a file-level backup alone. You would need to rebuild the DC from scratch and let replication repopulate AD from other DCs.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- Fix msmpeg2vdec.dll Errors in Windows
- How to Group Text and Pictures in Word