Mandatory uninstall of domain controllers, Active directory family 14

Why do I need to force uninstall on a domain controller? If the domain controller is unable to communicate with the replication partner, and the correction is hopeless, we will consider a forced uninstall. For example, I have seen a unit with 10 domain controllers, there are 7 can not replicate each other, mainly administrators mistakenly think that the more domain controllers the better ... in such cases, we can decisively hand over the domain controller and forcibly unload it. The principle of forced uninstall of domain controllers is also very simple, that is, uninstall no longer notify replication partners, directly to delete the ad. This is a relatively simple way to uninstall, but in fact, subsequent operations are cumbersome, such as the need to manually clear the domain controllers that are forcibly unloaded in Active Directory, and manually clear the SRV records in DNS. Therefore, if it is not a last resort, it is better to use conventional unloading.

As shown in the following illustration, we will use the topology shown in the following figure to show you how to perform a forced uninstall of a domain controller, and the target of our forced uninstall is the Firenze of the Shanghai site.

One force uninstall domain controller

First, we open the cmd command prompt on the unloaded domain controller Firenze, and the function of the Dcpromo/forceremoval,forceremoval parameter is to perform a forced uninstall, as shown in the following figure. The uninstall Wizard prompts us that this uninstall method will not update Active Directory data for other domain controllers.

Next we need to set the password for the Firenze local administrator.