locked
Unable to demote server 2008 R2 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a secondary DC that I need to demote and replace. Initially the problem was a degraded array that seems to have corrupted the OS beyond proper functionality. Programs don't run and I get multiple version.dll missing messages even though its there and I have also replaced it.

    No FSMO roles on this DC. It was the CA and I have managed to save the CA backup.

    When I run dcpromo it locks after the remove DNS prompt and eventually gives me an error stating that a critical error has occurred and server will restart . Wizard unable to determine status of active directory domain services.

    My goal is to replace the failing controller with all the same settings and naming.

    Also if I'm replacing a DC should I elect to remove the DNS or let it stay? Unclear if it's picked up by the new controller or if the connections \ pointers are recreated by the promotion process. 

    Regards,

    Steve Gee

    Currently exploring the force demotion articles.

    Wednesday, August 20, 2014 7:31 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The simplest approach would be to shut down the server, perform a metadata cleanup and then rebuild the server from scratch.

    http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

    Tony www.activedir.org Blog: www.open-a-socket.com

    • Proposed as answer by Dirk Popelka Wednesday, August 20, 2014 8:18 PM
    • Marked as answer by Amy Wang_ Monday, August 25, 2014 2:11 AM
    Wednesday, August 20, 2014 7:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In addition to Tony's posted article, you'll want to clean up DNS NS entries, as well as if the FRS is still referencing the orphaned DC.

    Complete Step by Step Guideline to Remove an Orphaned Domain controller or a DC that's been demoted using the /forceremoval switch. This includes seizing FSMOs, running a metadata cleanup, cleanup DNS (Nameservertab), AD Sites (old DC references), transfer or fix time settings, WINS settings, etc.
    Published by Ace Fekay, MCT, MVP DS on Oct 5, 2010 at 12:14 AM
    http://blogs.msmvps.com/acefekay/2010/10/04/complete-step-by-step-to-remove-an-orphaned-domain-controller/

    Remove FRS Entry:
    In ADSI Edit, connect to the Domain NC (Default Name Context), then expand and drill down to:
    1. Domain.com (your domain name)
    2. System
    3. File Replication Service
    4. Click on Domain System Volume (SYSVOL)
    5. Do you see the old DC in there? If so, carefully just delete that object, and nothing else.

    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    • Proposed as answer by pbbergs [MSFT] Thursday, August 21, 2014 11:59 AM
    • Marked as answer by Amy Wang_ Monday, August 25, 2014 2:11 AM
    Thursday, August 21, 2014 2:51 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The simplest approach would be to shut down the server, perform a metadata cleanup and then rebuild the server from scratch.

    http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

    Tony www.activedir.org Blog: www.open-a-socket.com

    • Proposed as answer by Dirk Popelka Wednesday, August 20, 2014 8:18 PM
    • Marked as answer by Amy Wang_ Monday, August 25, 2014 2:11 AM
    Wednesday, August 20, 2014 7:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In addition to Tony's posted article, you'll want to clean up DNS NS entries, as well as if the FRS is still referencing the orphaned DC.

    Complete Step by Step Guideline to Remove an Orphaned Domain controller or a DC that's been demoted using the /forceremoval switch. This includes seizing FSMOs, running a metadata cleanup, cleanup DNS (Nameservertab), AD Sites (old DC references), transfer or fix time settings, WINS settings, etc.
    Published by Ace Fekay, MCT, MVP DS on Oct 5, 2010 at 12:14 AM
    http://blogs.msmvps.com/acefekay/2010/10/04/complete-step-by-step-to-remove-an-orphaned-domain-controller/

    Remove FRS Entry:
    In ADSI Edit, connect to the Domain NC (Default Name Context), then expand and drill down to:
    1. Domain.com (your domain name)
    2. System
    3. File Replication Service
    4. Click on Domain System Volume (SYSVOL)
    5. Do you see the old DC in there? If so, carefully just delete that object, and nothing else.

    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    • Proposed as answer by pbbergs [MSFT] Thursday, August 21, 2014 11:59 AM
    • Marked as answer by Amy Wang_ Monday, August 25, 2014 2:11 AM
    Thursday, August 21, 2014 2:51 AM