Skip to main content

Clean Up Metadata

If you give the new domain controller the same name as the failed computer, then you need perform only the first procedure to clean up metadata, which removes the NTDS Settings object of the failed domain controller. If you will give the new domain controller a different name, then you need to perform all three procedures: clean up metadata, remove the failed server object from the site, and remove the computer object from the domain controllers container.
Requirements
  • Credentials: Enterprise Admins (metadata cleanup requires modifying the configuration naming context)
  • Tool: Ntdsutil.exe, Active Directory Sites and Services, Active Directory Users and Computers
To clean up metadata
1.       At the command line, type ntdsutil and press ENTER.
2.       At the ntdsutil: prompt, type metadata cleanup and press ENTER.
3.       At the metadata cleanup: prompt, type connections and press ENTER.
4.       At the server connections: prompt, type connect to server servername, where servername is the domain controller (any functional domain controller in the same domain) from which you plan to clean up the metadata of the failed domain controller. Press ENTER.
5.       Type quit and press ENTER to return you to the metadata cleanup: prompt.
6.       Type select operation target and press ENTER.
7.       Type list domains and press ENTER. This lists all domains in the forest with a number associated with each.
8.       Type select domain number , where number is the number corresponding to the domain in which the failed server was located. Press ENTER.
9.       Type list sites and press ENTER.
10.    Type select site number , where number refers to the number of the site in which the domain controller was a member. Press ENTER.
11.    Type list servers in site and press ENTER. This will list all servers in that site with a corresponding number.
12.    Type select server number and press ENTER, where number refers to the domain controller to be removed.
13.    Type quit and press ENTER. The Metadata cleanup menu is displayed.
14.    Type remove selected server and press ENTER.
At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed from the domain controller.
15.    Type quit, and press ENTER until you return to the command prompt.
If the new domain controller receives a different name than the failed domain controller, perform the following additional steps:
Note: Do not perform the additional steps if the new computer will have the same name as the failed computer. Ensure that hardware failure was not the cause of the problem. If the faulty hardware is not changed, then restoring through reinstallation might not help.
To remove the failed server object from the sites
1.       In Active Directory Sites and Services, expand the appropriate site.
2.       Delete the server object associated with the failed domain controller.
To remove the failed server object from the domain controllers container
1.       In Active Directory Users and Computers, expand the domain controllers container.
2.       Delete the computer object associated with the failed domain controller.

Comments

Popular posts from this blog

INSTALL CISCO VPN CLIENT ON WINDOWS 10 (32 & 64 BIT). FIX REASON 442

This article shows how correctly install Cisco VPN Client (32 & 64 bit) on Windows 10 (32 & 64 bit) using simple steps, overcome the ‘ This app can’t run on this PC ’ installation error , plus fix the Reason 442: Failed to enable Virtual Adapter error message . The article applies to New Windows 10 installations or Upgrades from earlier Windows versions and all versions before or after Windows 10 build 1511 .  To simplify the article, we’ve broken it into the following two sections: How to Install Cisco VPN client on Windows 10 (clean installation or upgrade from previous Windows), including Windows 10 build prior or after build 1511 . How to Fix Reason 442: Failed to enable Virtual Adapter on Windows 10 Figure 1. The Cisco VPN Client Reason 442: Failed to enable Virtual Adapter error on Windows 10 HOW TO INSTALL CISCO VPN CLIENT ON WINDOWS 10 (NEW INSTALLATIONS OR O/S UPGRADES) The instructions below are for new or clean Windows 10 inst...

Linux File and Directory Permissions

file & directory protection is a essential of any OS and Linux OS is no exception for it! These authorizations allow you to choose exactly who can access your files & directory, providing an overall improved system security. There was one of the major flaws in the older Windows operating-system where, by standard, all users can see each other people's information (Windows 95, 98, Me). For overcoming it, editions of the Windows based computer system such as NT, 2000, XP and 2003 lot more security features added. They fully support file & directory permissions, just as Linux system has since the beginning. Together, we'll now assess a directory listing from our Lab Linux system hosting server, to help us understand the information provided. a simple 'ls' command will give you the file and directory listing within a given directory, including the option  '-l' will display number of new areas that we are going to discuss here:

How to create a Hirens Boot CD 15.2 USB Disk

Hiren’s BootCD (HBCD) is a bootable CD that contains a set of tools that can help users to fix their computer if their system fails to boot. More specifically, HBCD contains hardware diagnostic programs, partition tools, data recovery utilities, antivirus tools and many other tools to fix your computer problems.  I write this article because I use Hiren’s BootCD frequently to troubleshoot computer problems, specially when a computer doesn’t boot anymore due to a virus attack or due to a corrupted file system. In this article you will find instructions on how to put Hiren’s BootCD on a USB flash drive (stick) in order to troubleshoot computer problems in the future.