I believe need to force one server to be authoritative, none are recognizing each other.
Have a 3 server domain where the domain is not syncing:
- new user account email address will not work
- new user accounts added to the domain on Server1 do not sync to Server2
- DNS changes on Server1 do not sync to Server2
Server1 will call A.domain.local - is 2008 R2 standard
Server2 will call W.domain.local - it 2008 SP2 standard
Server2 will call T.domain.local - is 2003 SP2 standard (this one is not a domain controller)
There were two old servers still listed in DNS and still listed as DCs -- I have eliminated these from A.domain.local
A.domain.local is a exchange server and has all the exchange server roles and features
From the event log, can see that there were replication errors going back a long time. Also can see that about 4 weeks ago the replication errors increased. And then the "decreased".
I think we need to make one of the servers authoritative and force the rest to sync to it, I believe it needs to be A.domain.local as that is where almost all user and DNS changes have been made in the last year.
What do we need to do to force this to happen?
What do we need to check before forcing A.domain.local to be the authoritative server?
-----------------------------------------------
From event log - this error has been on the server going back six month that the log covers. Count of servers not replicating changes. See the 3 events below for time line.
----------------------------------------------------
This one started 6 months ago and continued until 4 weeks ago:
This is the replication status for the following directory partition on this directory server.
Directory partition:
DC=ForestDnsZones,DC=domain,DC=local
This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
1
Tombstone lifetime (days):
180
Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically
blocked from future replication until it is reconciled.
------------------------------------------------------------
This started 4 weeks ago:
This is the replication status for the following directory partition on this directory server.
Directory partition:
CN=Configuration,DC=domain,DC=local
This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.
More than 24 hours:
2
More than a week:
2
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
1
Tombstone lifetime (days):
180
------------------------------------------------------
And this is current:
This is the replication status for the following directory partition on this directory server.
Directory partition:
CN=Configuration,DC=domain,DC=local
This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
0
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180