Louis did the correct thing with the role seizure and metadata cleanup. However as being previously employed as a AD Support Engineer in Microsoft's Directory Services EPS Support group, one thing I'd like to point out to the 'error' that Louis experienced while seizing the FSMO roles: ntdsutil, by default, will ALWAYS attempt a transfer first, even when you explicitly type in the 'seize' command at the ntdsutil prompt. If he had read all the output from the command he would of noticed the output, 11 lines down saying: "Transfer of Schema FSMO failed, proceeding with seizure..." And obviously, just like a forced demotion of a DC, the AD database will not be globally updated of the changes done (such as the orphaned FSMO records) But nonetheless, he did the right thing.
Good job Louis
Keep Up with TechRepublic