Re: Problem removing Active Directory
From: Jonathan Hassell (jhassell_at_carolina.rr.com)
Date: 08/26/04
- Next message: Peter: "Re: Xcopy between win2000 and win2003 servers"
- Previous message: Consultant: "Re: Templates for XP SP2"
- In reply to: Joćo Portela: "Problem removing Active Directory"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 13:28:13 -0400
I assume this domain no longer exists in production and you're getting this
error message because the child domain seems to have left a "ghost" within
AD. In this case, you can use NTDSUTIL to get rid of the orphaned domain.
KB 230306 helps with this. The good stuff is pasted below.
1.. Determine the domain controller that holds the Domain Naming Master
Flexible Single Master Operations (FSMO) role. To identify the server
holding this role:
1.. Start the Active Directory Domains and Trusts Microsoft Management
Console (MMC) snap-in from the Administrative Tools menu.
2.. Right-click the root node in the left pane titled Active Directory
Domains and Trusts, and then click Operations Master.
3.. The domain controller that currently holds this role is identified
in the Current Operations Master frame.NOTE: If this changed recently, not
all computer may have received this change yet due to replication.
For additional information about FSMO roles, click the article number
below to view the article in the Microsoft Knowledge Base:
197132 Windows 2000 Active Directory FSMO Roles
2.. Verify that all servers for the domain have been demoted.
3.. Click Start, point to Programs, point to Accessories, and then click
Command Prompt.
4.. At the command prompt, type: ntdsutil.
5.. Type: metadata cleanup, and then press ENTER.
6.. Type: connections, and then press ENTER. This menu is used to connect
to the specific server on which the changes will occur. If the currently
logged-on user is not a member of the Enterprise Admins group, alternate
credentials can be supplied by specifying the credentials to use before
making the connection. To do so, type: set creds domainname username
password , and then press ENTER. For a null password, type: null for the
password parameter.
7.. Type: connect to server servername (where servername is the name of
the domain controller holding the Domain Naming Master FSMO Role), and then
press ENTER. You should receive confirmation that the connection is
successfully established. If an error occurs, verify that the domain
controller being used in the connection is available and that the
credentials you supplied have administrative permissions on the server.
8.. Type: quit, and then press ENTER. The Metadata Cleanup menu is
displayed.
9.. Type: select operation target, and then press ENTER.
10.. Type: list domains, and then press ENTER. A list of domains in the
forest is displayed, each with an associated number.
11.. Type: select domain number, and then press ENTER, where number is the
number associated with the domain to be removed.
12.. Type: quit, and then press ENTER. The Metadata Cleanup menu is
displayed.
13.. Type: remove selected domain, and then press ENTER. You should
receive confirmation that the removal was successful. If an error occurs,
please refer to the Microsoft Knowledge Base for articles on specific error
messages.
14.. Type: quit at each menu to quit the NTDSUTIL tool. You should receive
confirmation that the connection disconnected successfully.
-- Jonathan Hassell Author, Managing Windows Server 2003, O'Reilly http://www.oreilly.com/catalog/mwinsvr2003/ "Joćo Portela" <joao.portela@netvisao.pt> wrote in message news:ehCGFEviEHA.2992@TK2MSFTNGP12.phx.gbl... >I can't remove AD by running dcpromo. the system gives an error message > saying is can't be removed because there is a child domain. > How do i remove the child domain then? > >
- Next message: Peter: "Re: Xcopy between win2000 and win2003 servers"
- Previous message: Consultant: "Re: Templates for XP SP2"
- In reply to: Joćo Portela: "Problem removing Active Directory"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
