This article introduces a hotfix that adds performance data to the Active Directory event log on a Windows Server 2012, Windows Server 2008 SP2 or Windows Server 2008 R2 Service Pack 1 (SP1)-based domain controller. After you install this hotfix, the domain controller enables additional filters to log the following performance data:
Note You can collect the performance data in the Active Directory event log to analyze the cause of a failure.
|Call time (in milliseconds)|
|Pages read from disk|
|Pages pre-read from disk|
|Clean pages modified|
|Dirty pages modified|
Hotfix informationAfter you install this hotfix, the work that is required to troubleshoot issues that involve unexpectedly high CPU usage in the Lsass.exe process and long logon times is reduced. More specifically, the additional filters that are described in the "Symptoms" section are added to event ID 1644. When the Field Engineering logging level is set, event ID 1644 can also be logged when a Lightweight Directory Access Protocol (LDAP) query exceeds a time threshold. The time threshold is configured in a DWORD value named Search Time Threshold (msecs) that is located under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\ParametersWhen the Field Engineering logging level is enabled and the Search Time Threshold (msecs) registry entry is not used or set to 0, the default value of the time threshold is 30,000 milliseconds.
For example, when you set the Search Time Threshold (msecs) registry entry to 100 millisecond, the DWORD value of the registry entry resembles the following:
"Search Time Threshold (msecs)"=dword:00000064
"15 Field Engineering"=dword:00000005
For more information about how to use event 1644 to troubleshoot LDAP query performance issue, go to the following Microsoft website:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012, Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 2800945 - Last Review: May 20, 2015 - Revision: 1