Jump to content

Recommended Posts

Posted

I have an odd feeling that one of my servers has become self aware (terminator style).

 

The long and short of it is that the server needs to be removed from hosting active directory. Using the obvious method of Manage My Server/add remove role etc - If you go through and tell the server it isn't the only domain controller in the domain, it kicks up an error saying "No other domain controlers can be found". However, if the box for "only domain controler left in the domain" is ticked the server comes up with the message "Other domain controllers found, server is unwilling to procede". Complete stuck here, tried running dcpromo in reverese with the exact same effect. Does this mean that the server is stuck on the domain?! Cannot remove it with/without network cable connected/after restart. Completetly stuck for ideas now.

 

Thanks for any advice.

 

Tom

Posted
DNS is the reason for the removal of the AD role. The stupid thing won't replicate because of who knows what, for some reason we didn't realise for months (on top of our game or what :D ) but the last sucesfull replication was in november, the same time the motherboard died and was replaced. Something fishy going on...
Posted
I have an odd feeling that one of my servers has become self aware (terminator style).

 

The long and short of it is that the server needs to be removed from hosting active directory. Using the obvious method of Manage My Server/add remove role etc - If you go through and tell the server it isn't the only domain controller in the domain, it kicks up an error saying "No other domain controlers can be found". However, if the box for "only domain controler left in the domain" is ticked the server comes up with the message "Other domain controllers found, server is unwilling to procede". Complete stuck here, tried running dcpromo in reverese with the exact same effect. Does this mean that the server is stuck on the domain?! Cannot remove it with/without network cable connected/after restart. Completetly stuck for ideas now.

 

Thanks for any advice.

 

Tom

I had a note of this on my PC for some reason - I don't know if it's any help to you

 

The most common problems involved DNS, so make sure the server can see the DNS server and resolve the name of another domain controller.

Is the other domain controller in the same site?

 

Another common reason for demotion problems is FSMO transfers. You may want to transfer the FSMOs from the server manually before trying to demote it.

 

Unfortunately, there is no way to force the machine to demote if it doesn't want to. You'd have to reinstall the operating system.

 

I presme you have looked here? http://technet2.microsoft.com/WindowsServer/en/library/f82e0fb0-552f-4b94-9ece-f550388976571033.mspx?mfr=true

Posted
the same time the motherboard died and was replaced

 

DNS.................if the motherboard was replaced, did it have onbard LAN?

 

Tell me you changed the IP when you put the new board in?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...