For instructions to collect the query processing details, refer to the links in the "More Information" section.
When you enable NTDS diagnostics event logging to have the "15 Field Engineering" value set to level 5, you may see events such as the following that report queries as inefficient:
When you run the problematic query by using the STATS control, you may receive a summary that resembles the following:
The query is marked as inefficient based on the relation between objects visited and objects returned. The reason that it visits so many objects is that it does not use the best selection of indices.
Note This issue also occurs on Windows 8.1, Windows 8, and Windows 7 on computers that have the AD LDS server role installed.
To resolve this issue in Windows 8, Windows Server 2012, Windows 7, or Windows Server 2008 R2, install the hotfix that is described in this article.
- LDAP queries that reference attributes that are not defined in the AD schema may be serviced more slowly by AD DS or AD LDS servers that have the KB 2862304 fix installed or that run Windows Server 2012 R2.
- Microsoft is aware of this issue, and we are working on an update to KB 2862304. More information will be posted to this article when the updated fix is available.
- To work around this issue, use one of the following methods, as appropriate:
- Change the queries to reference existing attributes.
- Add currently undefined attributes to the AD schema.
- Direct relevant LDAP queries to AD DS or AD LDS servers that do not have update 2862304 or hotfix 2862304 installed. This includes Windows Server 2012 R2 RTM DCs.
Update information for Windows 8.1 and Windows Server 2012 R2For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
Hotfix information for Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2A 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 one of the following operating systems:
- Windows 8.1
- Windows Server 2012 R2
- Windows 8
- Windows Server 2012
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 R2 (SP1)
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.
Article ID: 2862304 - Last Review: Jan 21, 2015 - Revision: 1