Article ID: 216364 - Last Review: February 21, 2007 - Revision: 2.2 Domain Controller Server Object Not Removed After DemotionThis article was previously published under Q216364 SYMPTOMS
After you demote a domain controller to a server, the object that represents the server in the Active Directory Sites and Services Manager snap-in remains.
CAUSE
This issue occurs because the server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
RESOLUTIONWARNING: If the server object contains any child objects named "NTDS Settings," these are objects that represent the server as a domain controller and should be automatically removed by the demotion process. If this does not work, or a demotion could not be performed (for example, on a computer with malfunctioning hardware) these objects must be removed by using the Ntdsutil utility before you delete the server object. After an administrator verifies that all other services with a dependency on the server object have been removed, or if the domain controller is being rebuilt and the decommissioning of the server could not be performed gracefully, an administrator can delete the server:
For more information about the Ntdsutil utility, refer to the Support Tools documentation on the Windows 2000 CD-ROM in the \Support\Tools folder. MORE INFORMATION
An administrator may safely delete the server object in the Active Directory Sites and Services Management snap-in after all services have been removed and no child objects exist.
| Article Translations
|

Back to the top
