![](\"http:\/\/lh4.ggpht.com\/_A3o0EjLYCNg\/TX_LeG6s7bI\/AAAAAAAAE54\/7o8LFI6oLIY\/image_thumb%5B1%5D.png\")
\nAfter some googlings, you’ll probably comes across this<\/a>. Which will tell you that you need to edit the objects attribute to an active DC role owner.<\/p>\n
If you decided to look in the dcpromo log file, you probably noticed that the fsmroleOwner is pointing to an old Server, which was probably the PDC at one point within the domain.<\/p>\n
Even though it took a decent amount of time to troubleshoot, I’ll keep this post short. Just check out MS tech guy: Chris Davis blog about the issue.<\/a><\/p>\n Grab FixFSMO.vbs from MS support articles, or Davis’s blog and run it against the object in DN notation on a PDC or the DC you wish to have as the FSMO owner. Jan 2018 Update<\/strong><\/em><\/p>\n Funny I don’t recall this one all that well, but great blog post by Chris which covers the nitty gritty pretty well, considering it’s a direct MS technet blog unlikely to go down. Good job.<\/p>\n","protected":false},"excerpt":{"rendered":" Scenario: You are about to remove the final Physical Domain Controller from your infrastructure, As you’ve done this before you figure it’ll be a piece of cake and will go about you day.. Instead you’re presented with this! After some googlings, you’ll probably comes across this. Which will tell you that you need to edit … <\/p>\n
\nex. cscript fixfsmo.vbs DC=DomainDnsZones,DC=Contoso,DC=com<\/p>\n