Ultimate uninstall of domain controllers, Active directory series XV

The idea of this forced uninstall approach is to go into Directory Services Restore mode, so that you can avoid corrupted active Directory and enter the system in Safe mode. You can then forcibly change the domain controller to a stand-alone server by modifying the registry, and then manually delete the Active Directory database. After that, the domain controller becomes a member server, but the services and registry keys used by the domain controllers are also retained in the system. If you want to do a better job, you can temporarily upgrade this computer to a domain domain controller, upgrade completed immediately after the domain controller uninstall, such a complex operation can basically ensure that the unloading effect and running dcpromo/forceremoval roughly equivalent.

We take Florence as an example to demonstrate the operation process. Florence is a itet.com domain controller, because Active Directory corruption does not enter the system, we first need to use Directory Services Restore mode to enter the system, when the system is started we press the F8, as shown in the following figure, choose to enter Directory Services Restore mode.

Directory Services Restore Mode does not load Active Directory, so you can avoid the problems caused by corrupted Active Directory, as shown in the following illustration, where we can successfully access the system through the Directory Services Restore mode.

Login into the system, we have to modify the registry key to force the domain controller into a stand-alone server, run Regedit, as shown in the following figure, to navigate to the Hkey_local_machine\system\currentcontrolset\control\ Productoptions\producttype, this key value determines the identity of the server.