Content Freshness
With Windows Server 2008, Microsoft introduced a setting called Content Freshness protection to protect DFS shares from stale data. DFS also use a multi-master database similar to AD. It also has a tombstone time limit similar to AD: 60 days by default. So, if there is no replication beyond that time and by re-enabling replication in a DFS member, can create stale data. This is similar to lingering objects in AD. To prevent this, we can define a value for MaxOfflineTimeInDays. If the number of days since the last successful DFS Replication is more than the MaxOfflineTimeInDays value, then it will prevent the replication. In such a situation, you will be able to see event 4012. After Windows Server 2012, this feature is enabled ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access