Active Directory Forest Recovery Prerequisites
Applies To: Windows Server 2016, Windows Server 2012 and 2012 R2, Windows Server 2008 and 2008 R2
The following document discuss prerequisites that you should be familiar with before devising a forest recovery plan or attempting a recovery.
Assumptions for Using This Guide
You have worked with a Microsoft Support professional and:
- Determined the cause of the forest-wide failure. This guide does not suggest a cause of the failure or recommend any procedures to prevent the failure.
- Evaluated any possible remedies.
- Concluded, in consultation with Microsoft Support, that restoring the whole forest to its state before the failure occurred is the best way to recover from the failure. In many cases, forest recovery should be the last option.
That you have followed the Microsoft best-practice recommendations for using Active Directory–integrated Domain Name System (DNS). Specifically, there should be an Active Directory–integrated DNS zone for each Active Directory domain.
- If this is not the case, you can still use the basic principles of this guide to perform forest recovery. However, you will need to take specific measures for DNS recovery based on your own environment. For more information about using Active Directory–integrated DNS, see Creating a DNS Infrastructure Design.
Although this guide is intended as a generic guide for forest recovery, not all possible scenarios are covered. For instance, beginning with Windows Server 2008, there is a Server Core version, which is a full version of Windows Server but without a full GUI. Although it is certainly possible to recover a forest consisting of just DCs that run Server Core, this guide has no detailed instructions. However, based on the guidance discussed here you will be able to design the required command-line actions yourself.
Although the objectives of this guide are to recover the forest and maintain or restore full DNS functionality, recovery can result in a DNS configuration that is changed from the configuration before the failure. After the forest is recovered, you can revert to the original DNS configuration. The recommendations in this guide do not describe how to configure DNS servers to perform name resolution of other portions of the corporate namespace where there are DNS zones that are not stored in AD DS.
Concepts for Using This Guide
Before you begin planning for recovery of an Active Directory forest, you should be familiar with the following:
- Fundamental Active Directory concepts
- The importance of operations master roles (also known as flexible single master operations or FSMO). These roles include the following:
- Schema master
- Domain naming master
- Relative ID (RID) master
- Primary domain controller (PDC) emulator master
- Infrastructure master
In addition, you should have backed up and restored AD DS and SYSVOL in a lab environment on a regular basis. For more information, see Backing up the System State data and Performing a nonauthoritative restore of Active Directory Domain Services.