Quantcast
Channel: Active Directory & GPO
Viewing all articles
Browse latest Browse all 20789

Retired DC causing replication errors

$
0
0

Hello all,

I've recently inherited a network that hasn't been updated in the better half of 8 years. I am in the process of upgrading to Windows Server 2008 R2 and I wanted to promote one of the servers to a DC for redundancy (currently we only have 1 DC).

The Current DC is a Windows Server 2003 SP2. I go to run adprep32.exe and find that it cannot prep the forest because they are failing to complete a replication cycle:

Adprep was unable to extend the schema.
[Status/Consequence]
The schema master did not complete a replication cycle after the last reboot. Th
e schema master must complete at least one replication cycle before the schema c
an be extended.
[User Action]
Verify that the schema master is connected to the network and can communicate wi
th other Active Directory Domain Controllers. Use the Sites and Services snap-i
n to replicate between the schema operations master and at least one replication
partner. After replication has succeeded, run adprep again.

After some research it turns out that the previous IT Director took offline the other DC without demoting it or adjusting the main DC.

My question is: What steps can I take to properly remove this old DC from my replication schema and correctly prep the 2003 SP2 server to integrate with my 2008 R2 SP1. Is it as simple as removing the server from AD Sites and Services? Long term (within a month) I plan on having 2 Domain Controllers both on 2008 R2.

Thank you


Viewing all articles
Browse latest Browse all 20789


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>