A few months ago I took over administration of a Server 2012 Essentials R2 server that was poorly administered by the company's last outsourced tech. support.
One of the remaining issues is that the server is throwing Event ID 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 257
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.
I've waded through what others have done to resolve this, but in most cases the fix involves multiple DCs. I don't get why the DC is trying to replicate at all when it's the only DC. I assume this is a left over artifact from a former migration
where the office may have had a second DC in the mix... but, there's only the 1 now.
Should we follow the steps for "How to perform an authoritative synchronization of DFSR-replicated SYSVOL (like "D4" for FRS)" in KB2218556 or just turn off the replication? I pretty much want to put it back to what it would have been out of the box for a single server environment.