I’ve even added two additional domain controllers and added/removed countless member servers and workstations in that time. The domain has been functioning properly since that time with NO issues at all. PS C:\Windows\system32> netdom query fsmo I performed metadata cleanup (via NTDSUTIL) at that time too.Īs you can see, the FMSO roles are being handled properly: I did have to seize the FSMO roles when that happened – all of which are now being handled by a server called “RED”.
“CRIMSON” is a very old Domain Controller that failed like 7 years ago. Operations which require contacting a FSMO operation master will fail until this condition is corrected.įSMO Role: CN=Infrastructure,DC=DomainDnsZones,DC=,DC=localįSMO Server DN: CN=NTDS Settings\0ADEL:0484546d-5c60-4f08-9cfa-fa79b970d626,CN=CRIMSON\0ADEL:fbeda01d-bcde-4c8f-81f3-4da3e26e9044,CN=Servers,CN=Lexington,CN=Sites,CN=Configuration,DC=,DC=local
Ownership of the following FSMO role is set to a server which is deleted or does not exist. Looking at the event logs I get this bit of information: “The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.” I run through DCPROMO and it fails saying:Īctive Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=,DC=local toĪctive Directory Domain Controller \\red.local. I’m trying to remove a 2008 R2 Domain Controller from my domain.