Completely Delete the metadata in the Domain Controller

	An error occurred while accidentally deleting the domain controller. Therefore, this error occurs when you rename the domain: Cannot connect and bind to the domain naming FSMO. cannot continue.: specified directory The Service property or value does not exist. 8202 There is no way. You can only try to completely delete the domain controller metadata deleted by mistake: The procedure is as follows:
1.	Click Start and point toProgram", Pointing to" attachment ", and then clicking" command prompt ".
2.	At the command prompt, type ntdsutil, and then press Enter.
3.	Type metadata cleanup, and then press Enter. The administrator can perform the delete operation based on the given options, but other configuration parameters must be specified before the deletion.
4.	Type connections and press Enter. This menu is used to connect to the server where these changes will occur. If the user currently logged on does not have the management permission, you can specify the credential to use before establishing a connection. To do this, type set credsDomainnameUsernamePasswordAnd then press Enter. If the password is blank, enter null as the password parameter.
5.	Type connect to serverServernameAnd then press Enter. A confirmation message is displayed, indicating that the connection has been established successfully. If an error occurs, check whether the domain controller used in the connection is available and whether the creden。 you provide have administrative permissions on the server. Note:: If the server to be connected is the server to be deleted, the following error message is displayed when you try to delete the server mentioned in Step 15: 2094 error. You cannot delete a DSA object. Zero X 2094
6.	Type quit, and then press Enter. The clear metadata menu appears.
7.	Type Select Operation target, and then press Enter.
8.	Type list domains, and then press Enter. A list of all the fields in the forest is displayed, and each domain has an associated number.
9.	Type select domainNumber, And then press Enter.NumberThe ID associated with the domain of the server to be deleted. The domain you selected is used to determine whether the server to be deleted is the last domain controller of the domain.
10.	Type list sites, and then press Enter. A site list is displayed. Each site has an associated number.
11.	Type select siteNumber, And then press Enter.NumberIs the ID associated with the site of the server to be deleted. A confirmation message is displayed, listing the selected site and domain.
12.	Type list servers in site, and then press Enter. A list of all servers in the site is displayed, and each server has an associated number.
13.	Type Select ServerNumber, WhereNumberThe ID associated with the server to be deleted. A confirmation message is displayed, listing the selected server, the Domain Name System (DNS) Host Name of the server, and the computer account location of the server to be deleted.
14.	Type quit, and then press Enter. The clear metadata menu appears.
15.	Type Remove selected server, and then press Enter. A confirmation message is displayed, indicating that the deletion is successful. If the following error message is displayed: 8419 error (0x20e3) DSA object not found This indicates that the "NTDs Settings" object may have been deleted from Active Directory because other administrators have deleted the "NTDs Settings" object, alternatively, you can run the dcpromo utility to successfully Delete this object and then perform this operation again. Note:: This error may also occur when you try to bind the domain controller to be deleted. The domain controller to which ntdsutil is bound cannot be the domain controller to be deleted by clearing metadata.
16.	In each menu, type quit to exit the ntdsutil utility. A confirmation message is displayed, indicating that the connection is successfully disconnected.
17.	In Delete the cname record in the _ msdcs. <root domain of the Directory forest> area of DNS. If you want to reinstall and upgrade the DC, a new "NTDs Set "object, which will have a new guid and a matched cname record in DNS. You do not want the existing DC to use the old cname record. The best practice is to delete host names and other DNS records. If the lease time on the Dynamic Host Configuration Protocol (DHCP) Address allocated for the offline server is exceeded, the IP address of the faulty DC can be obtained from the other client.

Since the "NTDs Settings" object has been deleted, you can delete the computer account, the WordPress member object, the cname (or alias) record in the _ msdcs container, the (or host) record in the DNS) record, The trustdomain object of the deleted subdomain, and the domain controller.