The Dcdiag.exe tool takes a long time to run in Windows Server 2008 R2 and in Windows 7

Article translations Article translations
Article ID: 979294 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • An Active Directory forest has many domain controllers that are located at different sites.
  • You run the domain controller diagnostics tool (Dcdiag.exe) at the command prompt on a computer that is running Windows Server 2008 R2 or Windows 7.
  • You use some switches to reduce the discovery scope of the Dcdiag.exe tool.

    For example, assume that you use the /a switch to limit the scope to the current site. Or, assume that you use the /s switch to limit the scope to the current server.
In this scenario, the Dcdiag.exe tool takes a long time to run.

CAUSE

This issue occurs because the Dcdiag.exe tool ignores the switch that is used when it collects initial topology information. This behavior causes the Dcdiag.exe tool to try to contact all the domain controllers in this Active Directory forest to collect their information. Therefore, you experience the issue that is described in the "Symptoms" section.

Note When the Dcdiag.exe tool runs, the first operation that it performs is to collect initial topology information.

RESOLUTION

To resolve this issue, install the following hotfix on all computers that are running Windows Server 2008 R2 or Windows 7 and that have the Dcdiag.exe tool installed.

Hotfix information

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

Prerequisites

To apply this hotfix, your computer must be running Windows 7 or Windows Server 2008 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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 7 and 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 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 and for Windows 7" 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 x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dcdiag.exe6.1.7600.20617453,63214-Jan-201007:36x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dcdiag.exe6.1.7600.20617674,30414-Jan-201008:10x64
For all supported IA-64-based versions of Windows Server 2008 R2

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 the Dcdiag.exe tool, visit the following Microsoft Web site:
Dcdiag
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

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size1,458
Date (UTC)14-Jan-2010
Time (UTC)18:24
PlatformNot Applicable
File nameX86_7966957dbc748599aaa47fded81df9ac_31bf3856ad364e35_6.1.7600.20617_none_6769b9cce531f35c.manifest
File versionNot Applicable
File size737
Date (UTC)14-Jan-2010
Time (UTC)18:24
PlatformNot Applicable
File nameX86_microsoft-windows-d..-commandline-dsdiag_31bf3856ad364e35_6.1.7600.20617_none_4cdcab4b783fbdc1.manifest
File versionNot Applicable
File size2,581
Date (UTC)14-Jan-2010
Time (UTC)08:03
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_375dc3514ad7c9199f092bf04fbaa828_31bf3856ad364e35_6.1.7600.20617_none_0b39ca1805dc6b28.manifest
File versionNot Applicable
File size741
Date (UTC)14-Jan-2010
Time (UTC)18:24
PlatformNot Applicable
File nameAmd64_7966957dbc748599aaa47fded81df9ac_31bf3856ad364e35_6.1.7600.20617_none_c38855509d8f6492.manifest
File versionNot Applicable
File size739
Date (UTC)14-Jan-2010
Time (UTC)18:24
PlatformNot Applicable
File nameAmd64_microsoft-windows-d..-commandline-dsdiag_31bf3856ad364e35_6.1.7600.20617_none_a8fb46cf309d2ef7.manifest
File versionNot Applicable
File size2,585
Date (UTC)14-Jan-2010
Time (UTC)08:50
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,998
Date (UTC)14-Jan-2010
Time (UTC)18:24
PlatformNot Applicable
File nameX86_microsoft-windows-d..-commandline-dsdiag_31bf3856ad364e35_6.1.7600.20617_none_4cdcab4b783fbdc1.manifest
File versionNot Applicable
File size2,581
Date (UTC)14-Jan-2010
Time (UTC)08:03
PlatformNot Applicable

Properties

Article ID: 979294 - Last Review: February 22, 2010 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Ultimate
Keywords: 
kbprb kbsurveynew kbexpertiseadvanced kbhotfixserver kbautohotfix kbqfe kbfix KB979294

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com