How to Troubleshoot High LSASS.EXE CPU Utilization on an Active Directory Domain Controllers

Symptoms

This issues symptoms may be seen in the following ways when this issue is occuring:
  • A System Center Advisor alert has triggered which calls out that the Lsass.exe process is utilizing a consistently large percentage of the CPU's capabilities (CPU utilization counter).
  • During normal operation, a domain controller is responding slowly or not at all to client service requests for authentication or directory lookups.
  • Active Directory domain clients consistently or frequently stop requesting service from a domain controller and instead locate a different domain controller to gain services from.
  • Performance monitoring using Perfmon.msc or Task Manager reveals that the Lsass.exe process is utilizing a consistently large percentage of the CPU's capabilities (Process Object, % Processor Time counter).

Cause

High LSASS.exe CPU utilization can be caused by many different single or combined issues. Nearly each cause and resolution for these issues are unique. However, included in Windows Server 2008 and later is the tool which assists in determining what the problem cause is. That tool is the Performance Monitor's Active Directory Data Collector Set.

Resolution

To begin resolving this issue, run the Performance Monitor's Active Directory Data Collector Set on that domain controller while the problem is occurring. This tool uses performance counters and tracing to monitor the issue and then compiles a report which will show details of potential problems which need to be investigated as possible causes.


To run the Active Directory Data Collector follow these steps:
  1. Open Server Manager on a Full version of Windows Server 2008 or later, or go to Start > Run > Perfmon.msc and then press enter.
  2. Expand Diagnostics > Reliability and Performance > Data Collector Sets > System
  3. Right-click on Active Directory Diagnostics and then click Start in the menu which appears.
  4. The default setting will gather data for the report for 300 seconds (5 minutes), after which it will take an additional period to compile the report. The amount of time needed to compile the report is proportional to how much data has been gathered during the period.
Once the report has compiled, look under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics to view the report or reports which have been completed.

The report contains eight broad categories under Diagnostic Results which will contain information and conclusions in the report. These will not always tell the exact cause of the problem but can be used to determine where to investigate in order to find the exact cause.

Items to look at when facing high CPU utilization by Lsass.exe are the Diagnostic Results portion of the report, which will show general performance concerns. In addition, examining the Active Directory category will detail what actions-such as what LDAP queries are effecting performance-the domain controller is busy doing at that time.

Domain controllers are often most effected by remote queries from computers in the environment asking "expensive" queries, or subjecting them to a higher volume of queries. The Network portion of the report can be useful in determining the remote clients which are communicating most with the domain controller while the diagnostic was gathering data.

More Information

Lsass.exe (Local Security Authority Subsystem Service) is the process which, on an Active Directory domain controller, is responsible for providing Active Directory database lookups, authentication, and replication.

Additional information on how to troubleshoot the Lsass.exe process using a great deal of CPU utilization on an Active Directory domain controller is available at the AskDS Team Blog Post:

"Son of SPA: AD Data Collector Sets in Win2008 and beyond"
http://blogs.technet.com/b/askds/archive/2010/06/08/son-of-spa-ad-data-collector-sets-in-win2008-and-beyond.aspx



Properties

Article ID: 2550044 - Last Review: May 16, 2011 - Revision: 1

Feedback