I have a domain with a single Server 2008 (not R2) DC. I'm now trying to add a second DC running 2008 R2. dcpromo completed without any issues but the NETLOGON and SYSVOL shares will not show up on the new DC.
Looking around on the first DC I noticed that it is logging event 6002 source DFSR every 8 hours and appears to have started about the time I promoted the second DC. Also at that time there is 1 event logged with ID 6804.
On the new DC I'm getting DFSR event IDs 5002 and 4612 every 8 hours.
I've tried Googling these events but have not been able to find a solution yet. Here are the event details:
Old server:
Text
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Log Name: DFS Replication
Source: DFSR
Date: 2/2/2014 5:46:32 PM
Event ID: 6804
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: servermr01old.mr.8thjd.local
Description:
The DFS Replication service has detected that no connections are configured for replication group Domain System Volume. No data is being replicated for this replication group.
Additional Information:
Replication Group ID: 85DB0FC0-76A1-4F6F-BB0A-C2C614891F94
Member ID: 2739F328-DA00-4B37-8BDC-7922132D7C82
|
Text
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | Log Name: DFS Replication
Source: DFSR
Date: 2/3/2014 9:25:27 AM
Event ID: 6002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: servermr01old.mr.8thjd.local
Description:
The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information.
Additional Information:
Object DN: CN=Domain System Volume,CN=DFSR-LocalSettings,CN=SERVERMR01OLD,OU=Domain Controllers,DC=mr,DC=8thjd,DC=local
Attribute Name: msDFSR-MemberReference
Domain Controller: servermr01old.mr.8thjd.local
Polling Cycle: 60 minutes
|
New server:
Text
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | Log Name: DFS Replication
Source: DFSR
Date: 2/3/2014 7:58:27 AM
Event ID: 5002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ServerMR01.mr.8thjd.local
Description:
The DFS Replication service encountered an error communicating with partner servermr01old for replication group Domain System Volume.
Partner DNS address: servermr01old.mr.8thjd.local
Optional data if available:
Partner WINS Address: servermr01old
Partner IP Address: 192.168.2.2
The service will retry the connection periodically.
Additional Information:
Error: 1753 (There are no more endpoints available from the endpoint mapper.)
Connection ID: DC1E4B3A-5952-47E2-8E60-4933EFD925C5
Replication Group ID: 85DB0FC0-76A1-4F6F-BB0A-C2C614891F94
|
Text
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | Log Name: DFS Replication
Source: DFSR
Date: 2/3/2014 7:58:27 AM
Event ID: 4612
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ServerMR01.mr.8thjd.local
Description:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner servermr01old.mr.8thjd.local. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: F70657C1-407D-4F4B-82B8-DF96A8D07EC6
Replication Group Name: Domain System Volume
Replication Group ID: DC1E4B3A-5952-47E2-8E60-4933EFD925C5
Member ID: E86329D7-340D-4B36-BD16-007D9EAE469D
Read-Only: 0
|
I should add that prior to doing any of this I had renamed the first DC from "servermr01" to servermr01old" using netdom by following the steps in this technet article so that may be playing into the issue as well.
Any help on resolving this would be greatly appreciated.