Change Notification Between Sites
By default, changes are replicated between sites according to a schedule and not according to when changes occur. For this reason, the greatest replication latency across the forest is the sum of the greatest replication latencies along the single longest replication path of any directory partition.
For special circumstances, you can configure change notifications on connections between sites. By modifying the site link object, you can enable change notification between sites for all connections that occur over that link. Use ADSI Edit to enable change notification between sites.
To enable change notification between sites
- In ADSI Edit, expand the Configuration container.
- Navigate to the Inter-Site Transports container, and select CN=IP. (You cannot enable change notification for SMTP links.)
- Right-click the site link object for the sites for which you want to enable change notification, and then click Properties.
- In the Select a property to view box, select options.
- In the Edit Attribute box, if the Value(s) box shows <not set>, type 1 in the Edit Attribute box. If the Value(s) box contains a value, you must derive the new value by using a Boolean BITWISE-OR calculation on the old value, as follows: old_value BITWISE-OR 1. For example, if the value in the Value(s) box is 2, calculate 0010 OR 0001 to equal 0011. Type the integer value of the result in the Edit Attribute box; for this example, the value is 3.
- Click OK.
Enabling change notifications across site links propagates all change notifications. With change notification between sites set, changes propagate to the remote site with the same frequency that they are propagated within the source site, including changes that warrant urgent replication.
From: Ayers, Diane
Sent: Monday, November 17, 2003 5:02 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Inter-site Urgent replication
Sent: Monday, November 17, 2003 4:12 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Inter-site Urgent replication
From: Gil Kirkpatrick [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 4:42 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Inter-site Urgent replication
Hi Diane,
My understanding (haven't tried it myself) is that urgent intersite replication observes the intersite replication schedule. You can work around this by enabling intersite notifications, but then that effectively circumvents any replication schedule.
That's my understanding anyway.
-gil
-----Original Message-----
From:
Ayers, Diane [mailto:[EMAIL PROTECTED]] On Behalf
Of Ayers, Diane
Sent: Monday, November 17, 2003 4:04 PM
To: [EMAIL PROTECTED]
Subject: Inter-site Urgent replication
Greetings
In an effort to localize our authentication traffic, we recently implemented a multi-site configuration moving away from our single mega-site (single domain). All DCs are on high bandwidth links but we are trying to reduce authentication across the WAN. All inter-site transports are configured for a maximum replication frequency (15 minutes).
An assumption on my part (and probably erroneous) is that urgent replication triggers such as account lockouts will still bypass inter-site replication schedules and be replicated to all DCs in the domain. We're getting a smattering of reports that the events such as account lockouts are not getting replicated quickly. Putting 2 and 2 together, it looks like urgent replication is not carried between sites. Is my assumption correct and can I enabled urgent replication between sites?
Diane
