locked
Re-Promote DC with same name after dcpromo /forceremoval RRS feed

  • Question

  • You guys helped me with a previous post “Correcting 2003 AD Sites and Services configuration”.

    We introduced a second domain controller in the site, and then did the force removal followed by the metadata cleaned, up as well as DNS entries, and related objects in AD Sites and Services.

     

    The question I have now is:

    After the dcpromo /forceremoval, and metadata cleanup, is it ok to re-promote the once bad DC back into AD without changing it’s name?

     

    I guess I’m concerned about information that may be lingering in the system’s local registry, or possibly something in AD?

    Monday, April 19, 2010 6:17 PM

Answers

  • Yes I still think yes, you have done all the necessary work and should be good to go. Flattening like Paul said is also an option.

     

    Thanks

     

    Mike


    http://adisfun.blogspot.com;
    • Marked as answer by MichAda Monday, April 19, 2010 7:21 PM
    Monday, April 19, 2010 7:10 PM

All replies

  • Yes - you should be able to promote a computer with the same name as the original DC...

    Before you to though, make sure to go through each step of http://support.microsoft.com/kb/555846

    If you are re-promoting the DC you previously demoted, I'd suggest reinstalling the OS - although ultimately this depends on the reason for demoting it...

    hth
    Marcin

    Monday, April 19, 2010 6:30 PM
  • Yeah that is fine, when you did the /forceremoval and metadata it got rid of the old references for that old DC (DC-GUID).   There shouldn't be any lingering info.

     

    http://blogs.technet.com/askds/archive/2009/06/05/dc-s-and-vm-s-avoiding-the-do-over.aspx

     

    DS team also outlined the /forceremoval, metadata cleanup, repromote process in that article (towards the end)

     

    Thanks

    Mike


    http://adisfun.blogspot.com;
    Monday, April 19, 2010 6:31 PM
  • It is ok as the others pointed out, but if this is only a DC and you previously had problems I personally would flatten it and start over.  That is my personal preference but it will work w/o doing that.

     

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    Microsoft's Thrive IT Pro of the Month - June 2009
    http://www.pbbergs.com

    Please no e-mails, any questions should be posted in the NewsGroup This
    posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, April 19, 2010 6:40 PM
  • Thanks for the link.

    Not "a computer with the same name" the same computer, with the same name.

    I believe everthing in the article has been done.

    Reason for the demotion was the system had been tombstoned and was not able to replicate changes made at the site it was a member of.

    No hardware changes to the system, just dcpromo /forceremoval, metadata cleanup, removed records in DNS, and Sites & Services.  It is now a member of a workgroup.  I was about to attempt to REJOIN the same system to domain, then DCPromo back into AD as a DC for that site.

    Did not know if that would be OK, without having to change the name.

    So...would you still think "yes"?

    Monday, April 19, 2010 7:05 PM
  • Yes I still think yes, you have done all the necessary work and should be good to go. Flattening like Paul said is also an option.

     

    Thanks

     

    Mike


    http://adisfun.blogspot.com;
    • Marked as answer by MichAda Monday, April 19, 2010 7:21 PM
    Monday, April 19, 2010 7:10 PM
  • Thanks for the info.

    You've all been very helpful.

    I don't know if there can be more than one answer, but you've all assisted.

    : )

    Monday, April 19, 2010 7:25 PM
  • Domain join and DCPROMO seemed to work just fine, the DC has replicated around and such, but I forgot to install DNS first, so no big deal...AD integrated..., so usually after installing DNS, the system replicates within just a few minutes.  For some reason this server is not replicating the domain/forest DNS zone.

    Any idea?

    I'm leaving to go home for the night, so the forward lookup zone may be there in the morning.

    Monday, April 19, 2010 11:10 PM
  • Zone finally populated, just not as fast as I wanted.

    Tuesday, April 20, 2010 12:27 PM