Jump to content

Recommended Posts

Posted

I've got a (windows 2k3) server which used to be a DC. It was demoted about 2 years ago, and is no longer a DC.

 

However, it still thinks it is!

 

When I go into Sites and Services, it isn't listed as a DC.

 

But if I go to the machine and try to change the name etc... it says it is a DC and I can't change the domain etc...

 

If I try to run dcpromo on it, it fails that also.

 

Problem is, I'm getting error '5805' and '5723' in the main AD logs.

 

Does anyone have any ideas what I should do to solve this?

Posted
It might be worth running through the metadata cleanup process described here ....

 

Clean up server metadata: Active Directory

 

Its mainly for cleaning up AD from a crashed server but it might help in your case ...

 

Ok, that doesn't work.

 

If I connect to an actual DC, the server is not listed. If I connect to the server in question, it is listed but then I get the error 'The connected server will not remove its own metadata.'

Posted

Thats normal if you try to do a Metadata cleanup on the server you are trying to clean if that makes sense because the system expects the server not to be there (cos its crashed) and you must do it on another DC to clean the crashed machine out of the system. If it doesnt show up when running metatdata on another DC also anywhere in AD then I think AD is ok and the problem lies with the demoted server

Sounds a bit drastic but how about backing up the data wiping it and re-installing the O/S. If the metadata system cant see it and its not anywhere in A/D then it sounds like the server is corrupt some where .. Just a thought have you checked to see if its got nothing running on it that could confuse the system ... DNS etc?

  • Thanks 1
Posted
Have you tried running adsiedit.msc? It will show you every object that AD knows about ... the old server may show up in there somewhere ..

 

Yup, no sign of the server in question.

Posted
Before a wipe maybe remove it Sites and Services manually and remove it from the group domain controllers.

 

It doesn't exist in the 'real' domain, on the working DCs, so there's nothing to remove.

 

On the server itself, I just get 'the DSA object could not be found'.

Posted
It doesn't exist in the 'real' domain, on the working DCs, so there's nothing to remove.

 

On the server itself, I just get 'the DSA object could not be found'.

 

Moment of stupidness! Sorry :)

  • Thanks 1
Posted
Trying it right now.

 

Fingers crossed, i know it has worked in the past for me when servers have done similar things to yours / the tombstone lifetime has expired.

 

:)

  • Thanks 2

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...