Hi there,
I have a question regarding a set-up I have seen that I was hoping someone could advise with.
Essentially, The client had 3 domain controllers. DC1, DC2, and DC3. The servers are all 2003 SP3 Standard. The forest and Domain functional levels are Windows 2000.
DC1 and 2 are still there, DC3 is running as a member server and has the DHCP role installed along with some apps. However, it is still present in AD Sites and services. It seems it has been ungracefully demoted but onsite IT aren't providing further info. The object for DC is tomb-stoned and this was probably done some months back. I have cleaned up DNS. However, on DCs 1 and 2, I am seeing Event ID 1925, Event Source NTDS KCC (the attempt to establish a replication link for the following writeable controller directory partition failed) The event data points to DC 3 and the error value is 1753. There are no more endpoints available from the endpoint mapper.
In AD users and Computers, DC 3 is located in the Member Servers OU and is not in the Domain Controllers OU.
In AD Sites and services, when I go to Sites>Sitename>DC3>NTDS Settings and click delete, it gives me three options:
-I want to demote this DC and continue using it as a computer
-I want to restart AD Replication for this DC
-This DC is permanently offline and can no longer be demoted using DCPROMO.
If I choose the first option (as they are using the server), I get a message that I need to use DCPromo to demote the DC. However, DC3 does not even have the Domain Controller Role Installed.
If I use ntdsutil and metadata cleanup, I can see DC3 listed as a Domain Controller.
What is the safest way to fix this issue (removing DC3 as a DC in AD sites and services, resolving event id 1925)?
I can
- Use metadata cleanup. Following this, will I have to remove the server from the domain and then rejoin it to the domain? Will Metadata cleanup remove the 'member' server as well or will I need to take further steps to ensure the server can still be used as a member server (be able to log on to it, etc.)?
-Rename the server to Member1 from DC3. Use metadata cleanup to remove DC3. Rename Member1 to DC3 again (some apps and pcs require the same name and IP address).
Any other suggestions welcome.
Thanks very much.
Kind Regards
HA