FSMO problems..please help.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Good afternoon.
About a month or so ago one of our DC crashed. It is back up but we're now
experiencing different issues. By reserching previous posts I now pretty much
now that I have to seize the RID master in order to fix this issue, but I
have a couple of questions:
1. The server like I said is up now, and it's still a DC (by the way we have
two other DCs) So I assume I have to force-demote it before I sieze it with
Ntdsutil.exe. Am I correct here?
2. I don't want to get rid of this server since we have a couple of apps in
it that we need. Can this server still be a member server with the same name
and everything? or do we have to totally bring it down?

please advice and thanks in advance.
 
Try transferring the role first. If you seize the role, you will have to
reformat the server so that a server with the same SID doesn't appear.

Mike Ober.
 
I think if you Seize the roles, you cannot plug this DC back in the network
after seizing the roles. Once all the roles have veen moved to another
working DC, you can plug the old DC in a stand alone hub and manually go
about removing links for other DCs from this one untill it thinks that it is
the only DC in the domain, run dcpromo and demote it to a stand alone
server. once it is a stand alone server, you should be able to plug it back
in the main network and promote it as a additional.

I had done something like this years ago and it did not cause any problem. I
also could not afford to format the DC due to various reasons.

Once you have your old DC on a stand alone hub with nothing else plugged in
to the hub, you can go to ntdsutil and seize the other DCs from the old one
and clear them up so the old DC thinks it is the only DC left. It is very
important that when doing this, nothing else should be connected to the old
DC.

Nim
 
Good afternoon.
About a month or so ago one of our DC crashed. It is back up
but we're now
experiencing different issues. By reserching previous posts I
now pretty much
now that I have to seize the RID master in order to fix this
issue, but I
have a couple of questions:
1. The server like I said is up now, and it's still a DC (by
the way we have
two other DCs) So I assume I have to force-demote it before I
sieze it with
Ntdsutil.exe. Am I correct here?
2. I don't want to get rid of this server since we have a
couple of apps in
it that we need. Can this server still be a member server with
the same name
and everything? or do we have to totally bring it down?

please advice and thanks in advance.
Click to expand...

it is not clear to me if you have restored the DC or if you have
reinstalled it using the same name as the old server...

could you give more information with more specifics?
 
Thanks for you replies guys.
Jorge, we reinstalled the OS using the same name and restored the the system
state from backup. Tomorrow morning, I will try what Nimish suggested. Any
other suggestion beore then will be greatly appreciated.
 
Thanks guys, and I apologize for not thanking you before. I've been busy. I
did what nimish propossed and it worked like a charm!!! Thanks again everyone.
 
Back
Top