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...

How to Disable SSL for Webmin

Webmin is a Web application that enables administrators to manage Linux servers. Webmin runs on a Web server at port 10000. Miniserv is the name of the Web server application that handles the Webmin Web application. By default, Miniserv uses SSL. However, you can disable SSL for Webmin Miniserv by editing the configuration file for the Web application. With SSL disabled, you can access the Webmin application over a standard HTTP connection. Step 1 Open a terminal window on the Linux server. You can also SSH into the server if you do not have physical access to the machine. Step 2 Type the following command at the command prompt and press the “Enter” key: nano /etc/webmin/miniserv.conf This command opens the Miniserv configuration file in the Nano text editor.

Error 651: How to Fix it in Windows 7/8

If you are a windows user then it is possible that you have Face Error 651 Anytime. There are many windows user who get affected by this error code 651 while working online. If you are one of those windows user, then keep reading this article and carefully read out the following Detailed solutions which I have gathered after researching various websites, articles, forums etc. When using Windows 7 built-in PPPoE wizard with a modem working in bridge mode, it fails and error code 651 appears. The similar problem happens on Windows Vista or previous versions as well. For example, Error code 678 on Windows XP is equivalent to error code 651 on Windows 7. Error code 651 usually occurs when user tries to connect it’s broadband in windows 7 operating system. It shows a message that Your modem (or other connecting devices) has reported an error and Usually the message will be “Connection failed with error 651” .Fix Error 651 In such cases user tries to resta...