Hi:
        Short story, a company we bought recently gave us a copy of one of 
their domain controlers so I could explore setting up a trust between there 
domain and our domain, in an isolated bubble of course, as preparation to doing 
a migration in production.  The DC they exported was not an operations master 
role holder, so one of the first things I did was use ntdsutil to seize the 
roles.  I started getting event 2092
This server is the owner of the following FSMO role, but does not consider it 
valid. For the partition which contains the FSMO, this server has not 
replicated successfully with any of its partners since this server has been 
restarted. Replication errors are preventing validation of this role.

I was under the impression that seizing a role was pretty final, but in doing 
some research I am not so sure anymore.  I found this site
https://standalonelabs.wordpress.com/2011/05/07/initial-synchronizations-of-domain-controllers/
that indicates that even if a role is seized using ntdsutil, the DC that seized 
the role still tries to talk to the DC that it seized the role from to tell it 
that the role has been seized and won't consider the transfer valid until 
that's done.  The site suggested deleting the replication link, which I did but 
still am getting the error.  I then used ntdsutil to seize the roles again, 
with no change.  I then removed the DC that held the operations master roles 
from Sites and Services, and still get the error.  All DCs involved are 2008R2 
and the forest is at the 2008R2 functional level.  My next step would be to go 
and clean up every single other site accept for the one this DC is in, and 
remove all other DCs from Sites and Services, but was wondering if there was 
something else I could do first to convince this guy that it really should take 
over these operations master roles.
Thanks.
Ryan
Ryan Shugart
LAN Administrator
MiTek USA, MiTek Denver
314-851-7414



MiTek Holdings, Inc., 2011-2014, All Rights Reserved
  ________________________________

This communication (including any attachments) contains information which is 
confidential and may also be privileged. It is for the exclusive use of the 
intended recipient(s). If you are not the intended recipient(s), please note 
that any distribution, copying, or use of this communication or the information 
in it is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately and then destroy any copies of it.

Reply via email to