0

My old Primary Domain Controller died after a series of power problems. I tried to follow this set of instructions http://kpytko.pl/active-directory-domain-services/seizing-fsmo-roles/ to get another windows server to be the Primary Domain Controller.
When I got to the "verify" part, things didn't go according to the instructions. When I:
"netdom query fsmo" I get:
"The specified domain either does not exist or could not be contacted. The command failed to complete successfully."
I have no experience with doing something like this. What could have gone wrong, or what can I do to finish the process?

Improve this question
9
  • 2
    You have a secondary DC that also is a global catalog? That error sounds not like your pdc failed, but like you have no dc left at all that is qualified - in which case it is "goodbye domain" time.
    – TomTom
    Jun 9, 2016 at 10:10
  • I thought this one was set up as a secondary. but perhaps I was misinformed. :s Is there a way to tell?
    – Steven Hook
    Jun 9, 2016 at 11:08
  • The previous steps in the seizure seemed to go as expected
    – Steven Hook
    Jun 9, 2016 at 11:09
  • Sorry, I meant to post this, but then it was too long, and then the edit expired.: The previous steps in the seizure seemed to go as expected dropbox.com/s/78z5tgrwea4xzmb/seizure.txt?dl=0
    – Steven Hook
    Jun 9, 2016 at 11:20
  • Did you or did you not already have another Domain Controller in the domain? That's the question we need answered before we can provide you an answer.
    – joeqwerty
    Jun 9, 2016 at 11:41

1 Answer 1

Reset to default
0

Thanks for all the comments and questions. In the end I wasn't able to find out what was going wrong with seizing the domain. I brought the old controller back online after salvaging a power supply, and everything seems to be fine so far. If anything breaks, I guess I will have to create a new domain.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .