Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"The current DC is not in the domain controller's OU" error message when you run the Dcdiag tool


View products that this article applies to.

Symptoms

If you run the Dcdiag tool against a domain controller that is in a child organizational unit of the "Domain Controllers" organizational unit, you may receive an error report that is similar to the following:

Doing primary tests Testing server: Default-First-Site-Name\DC1W2K Starting test: MachineAccount * The current DC is not in the domain controller's OU ......................... DC1W2K failed test MachineAccount

Note In this error message, DC is domain controller and OU is organizational unit.

↑ Back to the top


Cause

The problem may occur if domain controllers were moved from their original organizational unit to a child organizational unit of the "Domain Controllers" organizational unit. The "machineaccount" test of the Dcdiag tool performs a Lightweight Directory Access Protocol (LDAP) query with a scope that is set to LDAP_SCOPE_ONELEVEL to verify that the computer account of the domain controller is present in the "Domain Controller" organizational unit. If the domain controller is moved to a child organizational unit, the test fails.

↑ Back to the top


Resolution

Windows 2000

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 this specific problem.

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, submit a request to 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: 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

No prerequisites are required.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
  Date         Time   Version        Size     File name
  ------------------------------------------------------
  01-Dec-2003  20:16  5.0.2195.6826  217,872  Dcdiag.exe 


Windows Server 2003

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 this specific problem. 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: 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

No prerequisites are required.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
  Date         Time   Version        Size     File name
  ------------------------------------------------------
  18-Mar-2004  00:49  5.2.3790.142  281,600  Dcdiag.exe
Note The Windows Support Tools for Windows Server 2003 Service Pack 1 contain an updated version of Dcdiag.exe that corrects the problem that is described in this Knowledge Base article. For more information about the Windows Support Tools for Windows Server 2003 Service Pack 1 and about how to obtain these tools, click the following article number to view the article in the Microsoft Knowledge Base:
892777 Windows Server 2003 Service Pack 1 Support Tools

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For more information, 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

↑ Back to the top


Keywords: kbhotfixserver, kberrmsg, kbbug, kbfix, kbqfe, kbwin2000presp5fix, kbautohotfix, KB833436

↑ Back to the top

Article Info
Article ID : 833436
Revision : 15
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 286