Can't remove Active Directory Role?

[abillybob]

Hi All

 

So currently we have 3 servers... Not sure why. 1 is a terminal server that has AD installed and the other 2 consist of a physical DC and a Virtual DC. I'm wanting to remove the role from the terminal server but every time I try via dcpromo.exe I get this response which stops be dead in my tracks.

 

I'm not sure what to do at this point, as far as I can see any chances I make on the physical box replicate to this terminal server? Also I know I hate the fact we have a .local domain this is to be changed!

 

 

Thanks

[ADMaster]

That message is strange, I thought it was flexible single master operations role, that message says floating.

 

I'd start by checking the replication health, and trying to move the fsmo roles off that DC manually before demoting.

 

Does that server have DNS, the message indicates a DNS problem to me.

Are the DNS settings of the server pointing to the other DCs or itself?

[abillybob]

DNS is no longer installed it was when I posted this thread but since you said I removed it and pointed the server to a new DNS server but still the same issue persists!

 

How would I go about checking the replication health and the FSMO roles?

 

Thanks for your help

[snagrat]

Command “netdom query fsmo” will show who is the current role owner

 

I would also be looking at event viewer for replication errors

[abillybob]

Command “netdom query fsmo” will show who is the current role owner

 

I would also be looking at event viewer for replication errors

So using that command gives me PIC-DC which is correct although looking through event viewer I can see some replication errors but how would I go about fixing this?

 

This is the replication status for the following directory partition on this directory server. Directory partition:DC=ForestDnsZones,DC=pic,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours:1 More than a week:1 More than one month:1 More than two months:1 More than a tombstone lifetime:0 Tombstone lifetime (days):180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency ".

[ADMaster]

The three commands that should help are;

dcdiag

repadmin

replmon

 

This will give you the current health / status and allow you to force a replication.

[HPlum78]

Here is a good GUI tool https://www.microsoft.com/en-gb/download/details.aspx?id=30005

[HPlum78]

One other thought have you ran that netdom command on all of your DC's. Do they all report the same? You may have to break out ADSI edit here.....