Windows Server 2012 Active Directory Deployment Series (vii) General uninstallation of domain controllers

If we don't need a domain controller, how do we handle it? If we let this domain controller disappear directly, then other domain controllers will not know this message, and every other domain controller will also try to make AD replication with this domain controller, the client may also send the user name and password to this non-existent domain controller for verification. Therefore, when we perform a domain controller offload, we prioritize the use of regular uninstallation, to automate the update of SRV records in DNS, and to synchronize messages in other domain controllers.

In Windows Server 2012, uninstalling a domain controller is actually "degraded" by doing the following:

Open Server Manager, click the Manage menu in the upper-right corner, select Remove roles and features,

If the domain controller is the last domain controller, the following is displayed Uninstall interface, tick "last domain controller in the domain",

Go to the uninstall screen, uncheck "Force delete", click Next,

Enter the local administrator password after the downgrade,

To view the script:

What if the downgrade fails?

Method One:

Forced demotion

Remove roles and services

Delete complete.

Method Two:

Delete with powershell command line

Windows Server 2012 Active Directory Deployment Series (vii) General uninstallation of domain controllers