Troubleshooting Active Directory Performance With The Performance Console

By Author: Mike Jones
Total Articles: 256
Comment this article

As you learned in Lesson 1 70-270 Exam, the Performance console provides a graphical way to view Active Directory performance by using System Monitor. The Performance console also provides a means to log activity, view logs, or send alerts by using Performance Logs And Alerts. To troubleshoot problems indicated by System Monitor, you must be able to analyze and interpret the results of each counter you have selected for monitoring.
Analyzing and Interpreting Performance-Monitoring Results
There are four steps in the process of analyzing and interpreting performance-monitoring results:
1.Establish a baseline.
2.Analyze performance-monitoring results.
3.Plan and implement changes to meet the baseline.
4.Repeat steps 2 and 3 until performance is optimized.
Establishing a Baseline A baseline is a measurement derived from the collection of data over an extended period during varying workloads and user connections, representing acceptable 70-293 Exam performance under typical operating conditions. The baseline ...
... indicates how system resources are used during periods of normal activity and makes it easier to spot problems when they occur. You can establish a baseline for system performance by performing routine monitoring over periods ranging from clays to weeks to months. During this period of routine monitoring, find out the types of work being done by the system and the days and times when the work is being done. Knowing about the work being done by the system can help you to associate types of work with resource usage and to determine the reasonable parameters of performance during those intervals. When you have gathered performance data over a period that represents the typical events in your organization, you can determine the acceptable performance levels. These performance levels comprise your baseline.
To troubleshoot problems indicated by error and warning messages in the directory service log, examine details about the message by double-clicking the error or warning message.
All of the entries in the Diagnostics subkey have the MCSE Exam data type and a default value of 0. Leave logging levels set to 0 unless you are investigating a problem. Increasing the logging level increases the detail of the messages and the number of messages emitted and can degrade server performance.