I copied the wrong error. :)
This is the replication status for the following directory partition on the local domain controller. Directory partition: DC=ForestDnsZones,DC=dysstudent,DC=local The local domain controller has not received replication information from a number of domain controllers within the configured latency interval. Latency Interval (Hours): 24 Number of domain controllers in all sites: 1 Number of domain controllers in this site: 1 The latency interval can be modified with the following registry key. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours) To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>". For more information, see Help and Support Center at ________________________________ From: Owens, Michael [mailto:[email protected]] Sent: Wednesday, August 19, 2009 10:07 AM To: NT System Admin Issues Subject: RE: Selecting a domain controller to get GPOs from I know what the replication problem is, the sysvol needs rebuilt. We can fix the server but I was told that it wasn't broken. So in frusteration (after showing the powers that be) the error message, I figured a work around was in order. :) This directory partition has not been backed up since at least the following number of days. Directory partition: DC=DomainDnsZones,DC=dysstudent,DC=local 'Backup latency interval' (days): 384 It is recommended that you take a backup as often as possible to recover from accidental loss of data. However if you haven't taken a backup since at least the 'backup latency interval' number of days, this message will be logged every day until a backup is taken. You can take a backup of any replica that holds this partition. By default the 'Backup latency interval' is set to half the 'Tombstone Lifetime Interval'. If you want to change the default 'Backup latency interval', you could do so by adding the following registry key. 'Backup latency interval' (days) registry key: System\CurrentControlSet\Services\NTDS\Parameters\Backup Latency Threshold (days) For more information, see Help and Support Center at ________________________________ From: Maglinger, Paul [mailto:[email protected]] Sent: Wednesday, August 19, 2009 10:02 AM To: NT System Admin Issues Subject: RE: Selecting a domain controller to get GPOs from Rather than that, I would try to figure out what's causing the replication issues. Have you checked the event logs or ran a dcdiag? ________________________________ From: Owens, Michael [mailto:[email protected]] Sent: Wednesday, August 19, 2009 8:57 AM To: NT System Admin Issues Subject: Selecting a domain controller to get GPOs from Is there a way to choose which DC a machine goes to by default? I have a few domain controllers that are at remote sites, that are giving me replication issues. I am not allowed to touch these servers. However, whenever I change a GPO... it doesn't replicate to these 2 servers. I know this, because my servers for some reason automatically point to the problem domain controllers. I don't want to change the entire network, I just want to change all 7 of my servers so they all get the most recent policy. Can this be done? ________________________________ This message, and any response to it, may constitute a public record and thus may be publicly available to anyone who requests it in accordance with Chapter 149 of the Ohio Revised Code. ________________________________ This message, and any response to it, may constitute a public record and thus may be publicly available to anyone who requests it in accordance with Chapter 149 of the Ohio Revised Code. ________________________________ This message, and any response to it, may constitute a public record and thus may be publicly available to anyone who requests it in accordance with Chapter 149 of the Ohio Revised Code. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
