Windows 2003 and Active Directory Disaster Recovery guide (needed or not?)
Windows is, wether we like it or not, the standard in Office networking services. Active Directory is becoming a standard very fast, which makes it a crucial service in almost any medium to large sized company. Many of these do NOT have adecuate Disaster Recovery plans in place. I have written a few Disaster Recovery guides for Windows until now and the most recent ones about Windows 2003 and Active Directory. Since AD is so complex and Disaster Recovery is (or SHOULD be) a BIG part in the design and implementation process I have gathered all the needed topics that relate to this area.
I was told by a colleague that he would give gold to have a complete refence guide for Disaster recovery for windows 2003 and especially Active Directory that explains all the different options and possiblities AND the right steps.
I have the index included here as this is WAY too big to be an online article. I am thinking of getting it published since I am over 50% done with the whole thing (we are approaching quite a few pages!!) and I would like comments whether this is has areas missing or not and what the opinion of other people is, PDF download or paper print? What would you prefer? Would you even pay for such a guide? I am also inclined to make it free and just make it a big PDF and then just as for donations.
I am interested in hearing your opinions.
This is a more or less overview what will be included and does not reflect the final version but it gives you an idea.
![]()
Table of Contents
- Preface

- Who should read this book?

- Description of the Operating Environment

- How to use this book

- Disaster Types covered by this document
- Single DC Hardware Failure

- Complete site hardware failure

- Single DC AD corruption

- Restore deleted objects

- Site AD corruption

- Corporate (Global) AD corruption

- Corporate (complete) Hardware failure

- Single DC Hardware Failure
- Part 1:Design and implement a Disaster recovery plan for your organization.
- Active Directory design principles
- What we don’t need: decisions
- Lagsite design and implementation

- Better save then sorry
- Documents you need to make a proper disaster recovery plan
- How to present it to the management
- Part 2: Disaster Recovery:
- Single DC Hardware Failure (most common)
- Cleaning up the AD of old records after or before a DC re-installation
- Installation of the DC
- Promoting the DC
- AD Corruption on a single DC
- Option 1: Restoring AD from backup
- NON-AUTHORITIVE RESTORE
- Option 2: Replication
- Option 3: Rebuild DC with Install from Media
- Option 1: Restoring AD from backup
- Recovery of Deleted or lost objects
- Authoritive Restore
- Global AD corruption
- Restore the first DC for the root domain
- Restore the first DC in each of the remaining domains
- Enable the DC in the root domain to be a GC
- Recover additional DCs in the forest by installing Active Directory
- Post recovery steps
- Site AD Infrastructure (hardware) failure
- Global AD Infrastructure (hardware) failure
- Single DC Hardware Failure (most common)
- Part 3: Recovery details
- Recovery Steps explained:
- To install the DNS Server service
- To disable a Global Catalog
- To raise the current RID pool
- To delete server and computer objects of removed DCs
- To remove the failed server object
- To remove the failed computer account
- To reset machine account password of the DC
- To reset krbtgt password
- Reset trust passwords on one side of the trust
- To enable the DC in the root domain to be a Global Catalog
- Precautions regarding different hardware
- Preventive and measurements:
- Backup strategies
- Virtualization
- Seizing FSMO ROLES
- What are they?
- Why are they so important?
- Things to remember about FSMO
- What happens if one role is non-existent?
- Important things to consider when restoring AD from backup
- Microsoft KB article 216993 explained
- Micrsoft GPMC explained
- References
Any comments, ideas or mails here are greatly appreciated.
EDIT: Checkmarks are put next to the things that are complete.
Popularity: 6% [?]
Where *nix and security meet the general public
NEED!
“this is WAY too big to be an online article”
Yes, it would completely fill up the internet tubes!
I was more thinking of it being many many pages. I’d rather have it as a downloadable PDF.
Consider having a ‘target audience’ or ‘who should read this book’ section.
Thanks homeboy, added it into the document.