One DC is pulling FSMO from an AD server that doesn't exist, other DC sees FSMO fine


Active Member
Sep 17, 2021
I have 2 DC, one onpremDC, one hostedDC. There was some previous work where an RDS server was made a DC and FSMO moved to it, then the hostedDC was made the DC & FSMO moved to it, then AD removed from the RDS server. However, the onpremDC still sees the RDSserver as holding all the FSMO (even though it is no longer an AD server). Each DC was only pointing to itself for DNS, so I fixed that, however "netdom query fsmo" from onpremDC still shows the RDSserver (that doesn't exist as an AD server now) as the holder. HostedDC shows itself as fsmo holder (which it should be). Obviously AD/dns/replication issues abound(per dcdiag/replmon). Onprem will be going away soon anyways, so I was wondering should I put more time in trying to fix onpremDC (thought was it wouldn't take long to fix it, then it could be cleanly decommissioned)? I am not 100% sure AD is perfectly healthy with cloudDC (all clients are only pointing to cloudDC currently & "seem" to be working), otherwise, I would be tempted to just decom onpremDC and run through any metadata/cleanup needed to purge any reference to onpremDC & if there are any leftovers of RDS-DC. Eventually, I'll add a second hostedDC for the environment, but that is not currently scheduled. If I should fix onpremDC first, how do I tell it to pull the correct server as the fsmo role holder, assuming that is the big issue that needs to be fixed first? All server 2016.
Top Bottom