Domain Controller High Cpu Usage

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.

Domain controller high cpu usage. A new arena heap memory allocation was introduced in the windows server 2012 r2 version of directory services. Posted on 2009. First off let me state that i am happy that our monitoring system notified us of a problem.

They saw their domain controllers having a cpu usage way above what we normally saw. In this situation all the domain controllers in the forest may update all schema cache at the same time. A domain controller s main purpose in life is to leverage lsass to provide services to principals in your active directory forest.

Typically their domain controllers have between 0 15 cpu usage whereas now we saw all of their domain controllers running at 80 90 during business hours. In this scenario a svchost exe process that s running the windows remote management winrm service consumes 100 percent of cpu resources on the domain controller. The domain controller receives two or more winrm requests in a short period for example within 1 second.

A quick look showed us that the process which required this much cpu power was lsass exe. Especially the lsass exe process uses the most of the cpu usage. The first step to any kind of high lsass cpu troubleshooting is to identify what high really means.

Because of the high cpu usage i started to get more alerts of frs replication issues dns problems and i saw a snowball slowly gathering momentum. This results in a degradation of the responsiveness of the domain controllers. 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.

It causes a memory leak in the lsass exe domain controller role and dsamain exe of lightweight directory service lds process that may consume all the available memory on your windows server 2012 r2 domain controller or lds server. High cpu usage on server 2012 domain controller from wmi provider host we started having issues with our desktops not reading gpos since almost all of them go to this one dc i started looking there. Excessive cpu usage on domain controllers.