> From: [email protected] [mailto:[email protected]] > On Behalf Of Edward Ned Harvey (lopser) > > Whenever there is an urgent change (password change, account disable, etc) > those get pushed all around immediately, inter and intra-site. > > But non-urgent changes (changes to group membership, etc) have to follow > a replication schedule (or manual replication). If you go into sites and > service, > right-click on the NTDS connection between two servers, you can "replicate > now." You can also go to properties, you have a replication frequency > schedule there, and the maximum frequency is 4 times per hour. You seem > to be saying that schedule is ignored.
Sorry, I take it back. What I wrote above is wrong. I've been reading KB articles like crazy this morning. http://technet.microsoft.com/en-us/library/cc961787.aspx Urgent changes do not include password change, but do include account lockout. Urgent changes are replicated everywhere that supports change notification, but without waiting the normal few seconds or few minutes that change notification may normally require. Password changes are treated higher priority than regular change notifications, but not as high priority as urgent changes. Change notification applies, as Jefferson said - within a site, change notification means replication within a few seconds (the KB articles sometimes speak ambiguously, perhaps as high as 5 minutes). You can enable change notification across sites, but by default it is not enabled, and the final and slowest replication mechanism kicks in - the inter-site transport which is periodic and set to 180 minutes by default. There is still the matter of the Schedule on the NTDS replication object. In this article: http://technet.microsoft.com/en-us/library/cc961612.aspx They say the schedule determines how frequently periodic replication occurs, but in the very same article, they say within a site, replication is triggered by changes, and in this article, http://technet.microsoft.com/en-us/library/cc759160(v=ws.10).aspx they say inter-site replication is determined by the inter-site transport schedule (which is 180 mins by default, and is not the same as the NTDS object schedule). So if you can follow simple case-analysis logic, and believe everything you read, you have to conclude that the NTDS object replication schedule isn't used by anything. Because within a site, change notification is used, and inter-site transport is used for inter-site. _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
