DFS Replication error 4012

8fort8
8fort8 used Ask the Experts™
on
I moved a DC to a vm, demoted the old domain and promoted the new DC and dropped the old one all together. I'm getting DFSR 4012 replication errors on the New DC now. the solution below is what appears in the error. Under the replication tab in the dfs manager is "Domain System Volume" with the local domain as its proprieties.

Is this a serious problem?
Is the replication necessary without a second DC?
Will removing the "Domain System Volume" and re-adding it cause any issues with the dc or essentials experience?



==============================================================================
Error event 4012
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 74 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
Replication Group Name: Domain System Volume
=========================================================
dfs diag report

Summary of replicated folder status
  The following table provides a high-level overview of replicated folder status on this server.
 
  Replicated Folder Status # of Files Received DFS Replication Bandwidth Savings
SYSVOL Share                          Error                       0                                 0.00%
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
I had similar issue about a year ado and did a lot of research.
This was answered last Feb at:
http://www.experts-exchange.com/questions/28353972/dfs-replication-error-event-4012-server-2012.html
Here is also a good article (there are many):
http://windowsitpro.com/print/windows-server-2012/fixing-broken-sysvol-replication

Author

Commented:
pjam
 The solution requires demoting the DC. There is only 1 DC in the system demoting it will destroy the domain, and lose the users, enrolled computers,  and shares no?
Commented:
@8fort8,

Check on the post I made in your other question regarding this issue:

http:/Q_28918395.html#a41427223

-saige-

Author

Commented:
The solution was as it_saige pointed out to force the local dc to recognize itself was authoritative. This is kind of a sketchy process though and documentation frequently assumes too much to comfortably trust your not destroying something else. Having modified the settings to false and 1 (not easy to find) It is now replicating without any errors to sysvol directory. Still not sure if that's required without any other DCs on the network because the documentation states " The SYSVOL directory must be present and the appropriate subdirectories must be shared on a server before the server can advertise itself on the network as a domain controller. Shared sub directories in the SYSVOL tree are replicated to every domain controller in the domain. ". The ambiguity being is the implication the advertisement is being uniquely used only for the DCs ? I suspect not because the exchange server stopped posting strange errors as well when the replication was fixed.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial