I have a network with 3 domain controllers. On the DC with all the FSMO roles I am getting this error:
Log Name: DFS Replication
Date: 2/25/2016 3:14:40 PM
Event ID: 4012
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: TTLCloudDC01.ttlcloud.local
Description:
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 107 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 0D7C118A-F911-4868-A165-B7C41CFFC47A
Replication Group Name: Domain System Volume
Replication Group ID: 54492259-2310-4AFB-954A-A96C0EDF70DA
Member ID: EA8243B6-2A77-4C19-AED1-0E206C3A6049
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DFSR" />
<EventID Qualifiers="49152">4012</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-25T15:14:40.000000000Z" />
<EventRecordID>53991</EventRecordID>
<Channel>DFS Replication</Channel>
<Computer>TTLCloudDC01.ttlcloud.local</Computer>
<Security />
</System>
<EventData>
<Data>0D7C118A-F911-4868-A165-B7C41CFFC47A</Data>
<Data>107</Data>
<Data>C:\Windows\SYSVOL\domain</Data>
<Data>9061</Data>
<Data>The replicated folder has been offline for too long.</Data>
<Data>SYSVOL Share</Data>
<Data>Domain System Volume</Data>
<Data>54492259-2310-4AFB-954A-A96C0EDF70DA</Data>
<Data>EA8243B6-2A77-4C19-AED1-0E206C3A6049</Data>
<Data>60</Data>
</EventData>
</Event>
Would anyone know my best practice for a resolution?
Thanks
Dave