OK, I solved it. The "repadmin /regkey" wasn't working .. until I actually ran it from the \windows\syswow64 folder, and used the DC name in capitals. <shrug>
Dunno why it worked that way, when issuing the command didn't work anywhere else, even tho repadmin was in the PATH. Anyway, it created the reg key, and now all 3 DCs show all "successful", when I do "repadmin /showreps".I've got a 53 min or so delta, but I can live with that. So all that's left (I think) is to remove the reg key, and make sure that if the DC VMs are powered on, at least every week or two, and perhaps execute a script to kick off a replication, to avoid this problem in future. Maybe a cobination of a vsphere scheduled task, or a PowerCLI script that does all that ... Thanks everybody. On Tue, Aug 21, 2012 at 4:21 PM, Michael Leone <[email protected]> wrote: > OK, so the 2 DCs in the child domain seem to be replicating; a > "repadmin /showreps" comes back as successful, on each DC. But not on > the parent DC - I still get failures because too much time has > elapsed. > > Here is what I am wondering - the "repadmin /regkey <DC FDQN> > +allowDivergent" seemed to work on both child DCs, and I even see the > key in the registry - > > HKLM\System\CurrentControlSet\Services\NTDS\Parameters and I see > "Allow Replication with Divergent and Corrupt Partner", value 1, on > both child DCs. > > I do *not* see that key on the parent domain, and running the > "repadmin /regkey" doesn't seem to do anything; it just spits back the > command line help. > > Maybe I have to manually go add that key, on the parent DC? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
