This page categorizes the Active Directory troubleshooting information that is spread all over the Internet, so you can get to the resource you need to solve your specific issue.
You might want to check out these overviews, flow charts, and general Active Directory troubleshooting strategy resources if you are not quite sure where to start:
The following topics contain information that can help you gather more information about the problems that you are experiencing:
Starting with Windows Server 2008 the most frequently encountered event viewer messages have been targeted for more information. There are two big collections in the TechNet Library that we are planning to move onto the TechNet Wiki, so that a larger group
of people can help provide assistance in getting them documented.
There are also people working on a similar endeavor at
EventID.Net, where you can search for more information by providing the Event Source and ID. A similar mechanism exists on the TechNet
Errors and Events Message Center. This TechNet Wiki may one day be the best place to find more information on Events and Errors as there are several people working on fleshing these out on this platform. More about that in the following section.
The vision for this section is to link from each of the following event sources below to pages that discuss the event source and link out to specific Event IDs. The Event ID pages will then provide troubleshooting information specific to the event. We are
already working on this as you can see in
Event ID 1311. Our goal is for each page to provide the information that people will need to solve the issues they encounter. There are many people already committed to this effort and working on it. Still, we can use all the help we can get; if you are
inclined to help - we encourage you to do so.
There are many different factors that can limit the scale and performance of Active Directory. Here are articles that discuss them:
Resources that will help you troubleshoot Active Directory replication issues include:
Sometimes the reason for an access denied message may be related to something that is not immediately obvious. For example, it is possible that the computer was set to
Shutdown the system immediately if unable to log security events or the CrashOnAuditFail Registry value was set. You may have to log on interactively or directly to the console (Session 0). For more information, see
Services Denied and Computer Unresponsive When Security Event Log is Full." For more information about Session 0, see
Scheduled Tasks Run in the Context of Session 0 with Terminal Services and
How to Connect to and Shadow the Console Session with Windows Server 2003 Terminal Services and
Application Compatibility Session 0 Isolation.
Blogs with Troubleshooting Information