Symptoms

Assume that you perform a schema update in a Windows Server 2008 R2-based Active Directory forest. The size of the Active Directory databases in the forest is large, such as 100 gigabytes (GB). In this situation, all the domain controllers in the forest may update all schema cache at the same time. Therefore, the domain controllers experience high CPU usage. Especially, the Lsass.exe process uses the most of the CPU usage. This results in a degradation of the responsiveness of the domain controllers.

Note Most operations on the domain controllers are affected by this behavior.

Resolution

Hotfix information

To resolve the issue, install this hotfix on all domain controllers in the forest.

This hotfix introduces a new capability that lets forest administrators to postpone index creation to a point in time that they decide. By default, domain controllers create indexes when they receive the appropriate schema change through replication. After you apply this hotfix, you can defer the index creation by using a new attribute, dSHeuristics. The details of this attribute are as follows:

  • Set the nineteenth byte of the dSHeuristics attribute to 1 until the following occurs:

    • The domain controller receives the UpdateSchemaNow rootDSE mod. This triggers a rebuild of the schema cache.

    • The domain controller is restarted. This requires that the schema cache be rebuilt and, in turn, the deferred indexes are rebuilt.

    For more information about the dSHeuristics attribute, go to the following Microsoft website:

    General information about the dSHeuristics attribute

  • Any attribute that is in a deferred index state is logged in the event log every 24 hours. More specifically, the following events are logged accordingly:

    • 2944: Index deferred (logged one time)
      The event message resembles the following:

      Any index changes that are associated with a schema change are being deferred.

    • 2945: Index still pending (logged every 24 hours)
      The event message resembles the following:

      Index changes associated with a previous schema change are still pending. This is because the forest-wide ds-heuristic flag fDisableAutoIndexingOnSchemaUpdate is set. This flag, when set, disables automatic indexing of existing attributes on schema update. To ensure optimal performance from this DC, force an index creation by performing a rootDSE attribute modification on schemaUpdateNow and set it to 1. This behavior can also be turned off by resetting dsHeuristic fDisableAutoIndexingOnSchemaUpdate to 0, then DCs running Windows Server 2008 R2 SP1 or later will automatically rebuild indices as they receive this change.

    • 1137: Index created (logged one time)
      Note This is not a new event.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1).

For 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:

976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ntdsai.dll

6.1.7601.22350

2,745,856

06-Jun-2013

05:19

x64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about deferred index creation in Windows Server 2012, go to the following Microsoft sites:

General information about deferred index creation
Follow me and learn Windows Server 2012 – Deferred Index Creation
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.1.7601.22350_none_4f4686d4e9041b3e.manifest

File version

Not applicable

File size

3,531

Date (UTC)

06-Jun-2013

Time (UTC)

05:52

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×