Determine if the problem is caused by a one-time occurrence, or if the upstream domain controller(s) can't support replication by using DFS Replication.ĭeleting the DFS Replication database from the volume shouldn't be required and is discouraged. What follows are general steps to investigate the missing shares.
In addition, it prevents determining the cause of the issue and averting future occurrences of the issue. It's unnecessary in most cases, and it may cause data loss if done incorrectly. The process reinitializes DFS Replication if SYSVOL isn't shared on domain controllers according to How to force an authoritative, or non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS). This section contains recommended methods for troubleshooting and resolving missing SYSVOL and Netlogon shares on domain controllers that replicate by using the DFS Replication service. Frequently (but not limited to), the upstream servers have stopped replication because of a dirty shutdown (event ID 2213). An upstream domain controller's DFS Replication service is in an error state.ĭomain controllers without SYSVOL shared can't replicate inbound because of upstream (source) domain controllers being in an error state.DFS Replication is used to replicate the SYSVOL Share replicated folder.The environment contains domain controllers running versions of Windows earlier than Windows Server 2012 R2.The affected domain controller was recently promoted.The following symptoms or conditions may also occur: SYSVOL and Netlogon shares aren't shared on a domain controller. This article provides the steps to troubleshoot the missing SYSVOL and Netlogon shares in Windows Server 2012 R2.Īpplies to: Windows Server 2012 R2, Windows Server 2008 R2 Service Pack 1 Original KB number: 2958414 Symptoms
0 kommentar(er)
