June 2017
Beginner to intermediate
742 pages
18h 29m
English
Content preview from Mastering Active Directory
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,
Start your free trial
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 Active Directory. It also has a tombstone time limit similar to AD. It is 60 days by default. So, if there was no replication more than that time and a re-enabling replication in a DFS member, can create stale data. This is similar to lingering objects in AD. To protect from this, we can define a value for MaxOfflineTimeInDays. If the number of days from the last successful DFS replication is more than MaxOfflineTimeInDays, it will prevent the replication. In such a situation, you will be able to see event 4012. After Windows Server 2012, this ...