search for: intersitetopologyfailover

...Cheers, Denis PS : sorry for my parallel response to that thread, I didn't see your mail before hitting the send button. > > I've taken another look and it's plausible that the failover for inbound > connections won't occur for 2 hours thanks to the default of the > interSiteTopologyFailover variable on the site objects. I would be > interested as to result if you set the variable (which I think is in > minutes) to something much lower. > > This area is definitely not simple. And has a lot of room to improve > (One bug I see here is 'Last attempt @ NTTIME(0) was succ...

On 9/24/2016 7:32 AM, Denis Cardon wrote: > > the job of the samba_kcc script is to create the ntdsConnection > objects. Afterward the repsFrom/repsTo attribute are created in > accordance with the ntdsConnection objects (you can force the creation > using samba-tool drs replicate although). You can check that the > process is asynchronous when you join a new DC, the INBOUND

...y build up over time is an > open question (when DCs do go offline), I can't test every setup and > I'm sure there are edge cases. However if there are these additional > links for when you have spuriously unreliable DCs, they work just as > well as a fallback. > > The interSiteTopologyFailover attribute seems to be on the > NTDS-Site-Settings class. By default it probably isn't defined, but > the internal default value in both Samba and Windows is 2 hours. > > The ITSG is not the same as the bridgehead server. The ITSG is a > single DC in the site which coordinates...

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead

...reps over time. How often they build up over time is an open question (when DCs do go offline), I can't test every setup and I'm sure there are edge cases. However if there are these additional links for when you have spuriously unreliable DCs, they work just as well as a fallback. The interSiteTopologyFailover attribute seems to be on the NTDS-Site-Settings class. By default it probably isn't defined, but the internal default value in both Samba and Windows is 2 hours. The ITSG is not the same as the bridgehead server. The ITSG is a single DC in the site which coordinates all the DCs and picks br...

...within the KCC, but based on time delays and use of the old KCC, this may not be enough in its current state to be equivalent to a fresh domain. I've taken another look and it's plausible that the failover for inbound connections won't occur for 2 hours thanks to the default of the interSiteTopologyFailover variable on the site objects. I would be interested as to result if you set the variable (which I think is in minutes) to something much lower. This area is definitely not simple. And has a lot of room to improve (One bug I see here is 'Last attempt @ NTTIME(0) was successful' which ha...