Common scenarios that generate analysis results

For most organizations, it is appropriate to check the data integrity of the Active Directory forest on a regular basis. Although running the Analyze command frequently may not be necessary for small networks with few domain controllers, there are several common scenarios that you should consider to determine how often you should check the forest for potential problems. The most likely reasons for data integrity issues stem from:

  • Multiple administrators performing concurrent operations.
  • Administrators using different domain controllers to perform a single operation.
  • Replication delays that allow duplicate or conflicting information to be saved in Active Directory.
  • Insufficient permissions that prevent an operation from being successfully completed.
  • Network problems that prevent an operation from being successfully completed.
  • Partial or incomplete upgrades that result in inconsistency of the information stored in Active Directory.
  • Using ADEdit rather than the Console to create, modify, or delete zone objects, which may lead to problems, such as inadvertently creating a circular zone structure or an empty profile.
  • Using third-party tools, such as ADSI Edit, to edit objects directly in Active Directory, which may lead to corrupted or invalid zone objects.

Running Analyze periodically helps to ensure the issues these scenarios can cause are reported in the Analysis Results, so you can take corrective action.