If the machine that holds any FSMO role dies and the System State of that
machine is not restored then the roles need to be recreated (i.e. seized)
since the original role holder is not available. If the System State of
that machine is going to be restored then you should not try to seize the
roles since they will be returned.
In AD replication we use loose consistency - the state of any one DC may be
different from the others but given time they will all settle down to a
consistent set of objects. The whole purpose of the Operations Masters
role is to ensure that the specific information for that role is consistent
and updated on one machine only.
In your case, did you first transfer the roles to another machine? If so,
then the role is available and did not need to be seized. If, however, all
the roles were on the DC that crashed then you needed to seize the role.
If replication is working correctly then you should not have to reboot, but
when things don't happen as expected a reboot sometimes helps. Reboot the
FSMO role holder first and then see if the others recognize the role. If
not, then you can reboot them as well.
If they still don't recognize the role, who do they think has the role?
Ensure AD replication is working successfully. Also, run dcdiag /v to see
if there are any errors generated regarding the role holders and its
response.
The following article might also prove useful in determining where the
others are pointing for RID Manager$ using adsiedit:
283595 HOW TO: Change the Role Owner of the Operations Master After a
http://support.microsoft.com/?id=283595
David Pharr, (e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Ian" <
[email protected]>
| Sender: "Ian" <
[email protected]>
| Subject: Move of RID problems
| Date: Thu, 5 Feb 2004 12:54:45 -0800
| Lines: 12
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcPsKkkBrrV5HraITVi1JJJiBoKFGg==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.win2000.active_directory
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.active_directory:65656
| NNTP-Posting-Host: tk2msftngxa09.phx.gbl 10.40.1.161
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| I have a win2k AD. My first server had a problems and I
| had to replace the system drive. So the RID and all the
| Master Operations had to be moved to a different server.
|
| I found this out after the fact to I had to Seize the FSMO
| role.
| I did this for the RID and it shows up on the domain
| controler that I preformed the operation on as the RID
| master but not on any other servers.
| Do I have to reboot the other servers for this operation
| to complete.???
|
|
