Forceful Removal of a Domain Controller

Know Your FSMO Locations

Make sure that the DC you are removing is not holding any of the FSMO Roles

Seizing FSMO Roles (The Last Resort)

If for what ever reason you can not do a clean transfer you will need to seize it

Do not put the Infrastructure Master (IM) role on the same domain controller as the Global Catalog server. If the Infrastructure Master runs on a GC server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a GC server holds a partial replica of every object in the forest.

Transferring the any hosted FSMO Roles

For the RID, PDC, and Infrastructure Master

For the Domain Naming Master role

For the Schema Master Role

regsvr32 schmmgmt.dll

Schema Snap-In

Schema Snap-In

Attempt a Force Removal

Clear the Metadata from AD

Cleanup DNS by Removing all References to the Removed server

In Active Directory Sites and Services - delete server