Remove Active Directory Domain Controller Metadata

The GUI Metadata Cleanup Utility removes Active Directory domain controller metadata left behind after a domain controller is removed improperly or unsuccessfully (typically a dcp

4.5 Star
Add to favorites
Active Directory
E-mail Twitter Digg Facebook
Sign in to ask a question

  • This script caused me a real problem
    1 Posts | Last post December 09, 2016
    • Hello
      I used this script on a Windows 2000 domain, and it left the DC computer object behind which I can now not remove, the best thing I can do it move it out of domain controllers UO, bit I cannot delete it or rename it even of I change its primary group.
      The Server has gone from sites and services but still persists as s domain controller computer object. 
      I now need to install rebuild the original DC and place it back in the domain with the same name, but as mentioned I still have the original DC object in the domain with the same name.
      Please advise
  • Works flawlessly
    1 Posts | Last post March 09, 2016
    • After manually performing a metadata with ntdsutil I was unable to remove the server from Active Directory Sites and Services. This script removed it as soon as I hit the enter key to run it. Kudos to you, Clay!
  • have to run on all domain controllers except one that is being removed
    1 Posts | Last post July 20, 2015
    • i had to run it on all the domain controllers except the one i removed. could i have waited and it would have updated all the domain controllers automatically ?
  • Child domain servers
    1 Posts | Last post June 24, 2015
    • One more thing.. My server is located under domain not from the root domain.The script showing only servers form only. Please help
  • DC delete from a child ou
    1 Posts | Last post June 24, 2015
    • Hi,
       My domain controller located under child OUs. example under domain controller Ou, there is one more OU located test. Metadata need to be cleaned from the servers which is located under test. SO how to be modify the script?
  • Prerequisits for multi-domain environments
    3 Posts | Last post April 09, 2015
    • The script is running smoothly for the forest root domain in a W2K3 multi-domain environment. When I try to use it in a child-domain it does not list any domain controllers of that particular domain (logged in on the PDC of that child-domain with enterprise credentials).
      Pls help
    • Had the same issue with a child domain. I believe it's because the 'Configuration' container is in the root naming context. In the script where ever there is
      CN=Sites,CN=Configuration," & objRoot.Get("defaultNamingContext") replace "defaultNamingContext" with "rootDomainNamingContext". I believe it's required to be replaced in three locations.
    • Has this been tested? I have tried to change the "defaultNamingContext" to "rootDomaiNamingContext" but i am still not able to show the child domain domain controllers. I have tried changing the line: set objRoot=GetObject("LDAP://rootDSE") to our domain but it will not pick up any DC's in that domain.
  • Compatability with Server 2012 R2
    2 Posts | Last post February 18, 2015
    • I was able to save and run the script in an elevated command prompt. I found the DC listed, typed the name to confirm, script said metadata cleanup completed. But still the object exists in AD. Tried several runs with 2 old DC's, no luck. issue with 2012 R2?
    • Found the issue was the DC objects were protected from accidental deletion. Rookie mistake, remove the check box in AD and script worked.
  • Works with Samba 4
    1 Posts | Last post February 13, 2015
    • I just used this on an AD setup that has several DC's spread out over to sites, all running samba 4. It seemed impossible to remove a dead dc, but this script worked perfectly.
  • Download
    1 Posts | Last post December 30, 2014
    • didn't find the download i can get this scribt
  • Comments by the Script Author
    2 Posts | Last post October 15, 2014
    • My name is Clay Perrine. I am the author of this script.  I want to add some comments relating to the script.
      1.  It was never written for or tested with child domains. I did not consider them when I created the script.
      2.  It is possible to perform a copy and paste error that adds carriage returns to the script. This will break the script and it won't work correctly.
      3. The script was written with the limitations of vbscript. I would have liked to have a dropdown to select the DC, but that is not available in vbscript. That is the reason it won't display all of the DCs in large environment. You can still type the name manually.
      4. I did not provide the ability to remove multiple DCs in one pass. This was done on purpose to prevent removing a good DC accidentally.
      5. This script was written before the release of powershell.  There will not be a powershell version as the current OS has the functionality built in.
    • Also, the script does not touch the DNS entries at all.
1 - 10 of 22 Items