asked on 10/24/2018

How to replace a failed AD server.

I had a network with two file servers. Hyper-V1 which hosted Server1 and Exchange1; Hyper-V2 hosted Server2 and Exchange2. Exchange was installed on Exchange1, but not completely configured and operating. The hard drive with the virtual disks for Server1 and Exchange1 has failed completely. The two servers were using DFSR successfully, so the users are able to continue in an almost unaffected manner.

Both server1 and server2 were domain controllers. Server1 held the FSMO roles.

I am in the process of rebuilding Server1 to the same system that existed. While Exchange was not functioning, it was installed, and there are a lot of exchange entries when I open the ADSIedit tool.

What is the best way to clean up server2 of any reference to server1 before I rejoin the new server1 to the domain?

* Distributed File System Replication (DFSR)Windows Server 2012 Networking

Last Comment

Philip Elder

10/24/2018

ASKER CERTIFIED SOLUTION

Mal Osborne

10/24/2018

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

Wilf

10/24/2018

ASKER

Thanks for the quick response. The last note on the article indicates that Infrastructure Master (IM) should not be on the same server as the global catalogue, but there is only one server left, so should I seize IM also?

SOLUTION

Mal Osborne

10/24/2018

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

Wilf

10/24/2018

ASKER

Thanks again.

Wilf

10/24/2018

ASKER

Your help was very much appreciated

Philip Elder

10/24/2018

Get-ADForest  | Format-Table SchemaMaster,DomainNamingMaster
Get-ADDomain  | Format-Table PDCEmulator,RIDMaster,InfrastructureMaster

# Destination DC for Operations
$DestinationDC = "Server2"
$DestinationDC

# Transfer FSMO Roles

Move-ADDirectoryServerOperationMasterRole -Identity $DestinationDC -OperationMasterRole 0,1,2,3,4 -confirm:$false
Get-ADForest  | Format-Table SchemaMaster,DomainNamingMaster
Get-ADDomain  | Format-Table PDCEmulator,RIDMaster,InfrastructureMaster

# Seize FSMO Roles
Move-ADDirectoryServerOperationMasterRole -Identity $DestinationDC -OperationMasterRole 0,1,2,3,4 -Force -confirm:$False
Get-ADForest  | Format-Table SchemaMaster,DomainNamingMaster
Get-ADDomain  | Format-Table PDCEmulator,RIDMaster,InfrastructureMaster

Open in new window

In this case, use the last section to seize the FSMO Roles using PowerShell on the existing DC.

Then, clean-up Sites, DNS, Active Directory Users & Computers, and then check using the NTDSUtil method indicated above to verify clean-up was complete. Then DCPromo the newly stood up Server1 into the domain.