*>>I can have a mesh connection between 10 DCs without undue negative impact.*
I would argue that this thread suggests otherwise... :) Regards, *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market...* On Wed, Sep 17, 2014 at 1:07 PM, Michael Leone <[email protected]> wrote: > On Tue, Sep 16, 2014 at 8:39 PM, Webster <[email protected]> wrote: > >> AD does not require a full mesh replication configuration. that is one >> of my "10 Things in AD" that I talk about. Some admins believe the KCC is >> broken because it doesn't create a connection between every DC. Imagine >> how cumbersome that would be in an AD with hundreds of DCs. >> > > Yes, I know. And I agree, it's impractical as a default. But for a small > org such as mine, I can have a mesh connection between 10 DCs without undue > negative impact. > > So we did. :-) > > > >> >> webster >> >> Sent using OWA for iPad >> ------------------------------ >> *From:* [email protected] <[email protected]> >> on behalf of Michael Leone <[email protected]> >> *Sent:* Tuesday, September 16, 2014 1:27:16 PM >> *To:* [email protected] >> *Subject:* Re: [NTSysADM] Confused about domain replication times >> >> >> >> On Tue, Sep 16, 2014 at 1:11 PM, Free, Bob <[email protected]> wrote: >> >>> You should get rid of the manual COs.. (including automatically >>> created objects that have been modified). The KDC won't manage them. A >>> manual object means you know something the KDC doesn't which isn't often >>> the case. >>> >> >> >> Configuring Change Notification on a MANUALLY created Replication >> partner >> >> http://blogs.technet.com/b/askds/archive/2013/01/21/configuring-change-notification-on-a-manually-created-replication-partner.aspx >> >> Change Notification on a manually created replication partner is >> configured by doing the following: >> >> 1. Open ADSIEDIT.msc. >> 2. In ADSI Edit, expand the Configuration container. >> 3. Navigate to the following location: >> >> \Sites\SiteName\Server\NTDS settings\connection object that was >> manually created >> 4. Right-click on the manually created connection object name. >> 5. In the Attribute Editor tab, double click on Options. >> 6. If the value is 0 then set it to 8. >> >> >> Won't that resolve the issue? And make sure that each DC replicates >> with each and every other DC? (there aren't automatically created links >> from/to every server, for obvious reasons. But in a 10 DC environment, with >> high speed links, why not?) >> >> >> >
