Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Later this year I will be handing over support of my church’s active directory servers to someone else and would like to know what kind of information is important to document and share. Are there any good example documents that I could use?

share|improve this question
up vote 11 down vote accepted

First, be careful not to document Active Directory itself. Microsoft has already done that. It is not your responsibility, and it will reduce the time you have to document the configurations, policies, and procedures specific to your installation.

Here is a list of things that you should document.

  • Explain your computer, user, domain, and OU naming conventions.
  • Describe your OU hierarchy and the reasoning behind it.
  • Briefly describe the main functions of your Group Policy Objects and why you organized them as you did.
  • Describe your network numbering conventions and DHCP configuration, if applicable.
  • Describe your DNS configuration.
  • Describe your Windows Firewall exceptions.
  • List the the Windows Server roles and third-party software installed on each server.
  • Note the locations of Active Directory's FSMO roles.
  • Describe the organization's policy for when to add new user accounts or revoke existing user accounts.
  • Describe the organization's policies for user restrictions (related to GPO details above).
  • If you are responsible for the network as well, provide a building wiring diagram.
share|improve this answer
  • Standard tasks:
    • Create/delete users
    • Grant/revoke permissions
  • Things that separate your installation from out-of-the-box AD:
    • Changes in group policies
    • Schema extensions
share|improve this answer
* Which server has the FSMO roles, and why * Cronic Issues you have/had * Thoughts you had on ways to to improve reliability – James Cape May 19 '09 at 12:30

A great tool to document your servers is

share|improve this answer

Might be OTT for a smaller church, but the Microsoft Active Directory Topology Diagrammer is pretty funky. It automatically generates a diagram of your Active Directory topology in Visio.

Diagrams can be made of servers, domains, sites, routing groups, admin groups and connectors. It shouldn't take long to produce some nice illustrations that you can use to supplement your written handover notes.

Screenshot here (on a Sun blog!)

share|improve this answer
Ooh must try that. – PowerApp101 May 19 '09 at 13:07
MS certainly give us some nice toys! – Adam May 19 '09 at 13:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.