<div>
Thank you both so much. &nbsp;I split the points because I will use both of your answers.
</div>


Thank you both so much.  I split the points because I will use both of your answers.

<div>
<div class="content wysiwyg-content">
I have (2) Windows 2000 servers and am trying to retire Server 1. &nbsp;Created a Windows 2008 R2 Core host and a Windows 2008 R2 guest called Server 3. &nbsp;Upgraded the AD and made Server 3 a DC with all of the FSMO roles. &nbsp;Applied Windows updates to Server 3 and it will not come back up. &nbsp;Had not setup backup or taken a snapshot yet. Tried a Startrep that is stuck. &nbsp;So I need to remove Server 3 from the AD and rebuild or replace it. &nbsp;I could build a Server 4 in a virtual environment. &nbsp;I have researched 2 possible approaches. &nbsp;1). Sieze the roles and move them to Server 1. &nbsp;Remove Server 3. &nbsp;Clean up the metadata. &nbsp;Rebuild Server 3 with the same name and repromote to a DC. or 2) Create Server 4 and promote it to DC. &nbsp;Sieze and move the roles to Server 4. &nbsp;Then remove Server 3 and clean up metadata. &nbsp;<br />
<br />
Has anyone done this? &nbsp;Which would be the better way to handle the situation? &nbsp;What gotshas are likely?
</div>
</div>


I have (2) Windows 2000 servers and am trying to retire Server 1.  Created a Windows 2008 R2 Core host and a Windows 2008 R2 guest called Server 3.  Upgraded the AD and made Server 3 a DC with all of the FSMO roles.  Applied Windows updates to Server 3 and it will not come back up.  Had not setup backup or taken a snapshot yet. Tried a Startrep that is stuck.  So I need to remove Server 3 from the AD and rebuild or replace it.  I could build a Server 4 in a virtual environment.  I have researched 2 possible approaches.  1). Sieze the roles and move them to Server 1.  Remove Server 3.  Clean up the metadata.  Rebuild Server 3 with the same name and repromote to a DC. or 2) Create Server 4 and promote it to DC.  Sieze and move the roles to Server 4.  Then remove Server 3 and clean up metadata.  

Has anyone done this?  Which would be the better way to handle the situation?  What gotshas are likely?

Best method to replace 2008 R2 server DC in Active Directory

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.