时间戳

首页 > 解决方案 > No SYSVOL or NETLOGON shares created after fresh install

active-directory - No SYSVOL or NETLOGON shares created after fresh install

问题描述

I created a fresh, brand new, Windows Server 2016 instance this morning. (Let's call it DC2) Then I added the Active Directory Domain Controller role. No SYSVOL or NETLOGON shares were created. This machine is meant to be a replica of the existing DC. (let's called that one DC1) Eventually, I mean to transfer the FSMO roles to DC2 and then decommission DC1. (DC1 is a Windows Server 2008 R2 instance. So this is part of that natural infrastructure-upgrade process that we all have to do now and then)

Uncertain where the problem is, I installed the DFS Management Tool on both machines. It shows nothing under namespaces and nothing under replication. I'm not sure if it even should show anything here. I got this idea from reading about this problem. When I right check and choose "Add Replication Groups to Display", it reports "There are no replication groups in this domain. Again, I'm not certain that this is where I should be looking.

For debugging purposes, I turned off the firewall on both machines and rebooted them.

Next, I ran this:

NTFRSUTL DS dc1
NTFRSUTL DS dc2

This shows the settings for File Replication Service. I'm uncertain how to read it to tell if it's OK. It does appear to mention that DC1 and DC2 are there and that there's a share on DC1 (SYSVOL). I don't see it mentioning the share on DC2. Which I guess could be part of the problem.

This works and shows a database in there

DIR \\dc1\admin$\ntfrs\jet
DIR \\dc2\admin$\ntfrs\jet

I have not yet tried to mess with the Burflags yet. That looks like the next logical step. But there are warnings about this, so I wanted to ask for ideas before attempting this:

https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi

标签： active-directorywindows-server

解决方案

Burflags做到了。

目前，Active Directory 可以使用 FRS 或 DFS-R 同步 SYSVOL 和 NETLOGON 文件。这是 Windows 中存在的两种不同的文件同步系统。激活的取决于您拥有的 Windows 版本和域的功能级别。就我而言，我有 FRS。

这里有很长的说明：

FRS - https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi

DFS-R - https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

最初，我尝试从我的一个非同步副本进行非权威恢复。这并没有解决它。最后，我不得不做一个权威的恢复。

我执行了如下高级步骤：（我可以这样做，因为我的网络很小）

  • 确定哪台机器拥有最好的 SYSVOL 副本
  • 将 FSMO 角色转移给它
  • 通过使用检查它是否有效netdom query fsmo
  • 关闭所有副本
  • 执行权威恢复（我在 FRS，所以我使用了 Bursflags）
  • 等一两分钟
  • 调出副本
  • 稍等片刻
  • 它奏效了（跳个小舞）:-)

由于我在 FRS 上并且我在一个小型网络上，所以我采取了简单的方法并关闭了副本。如果您有更大的设置，您可能需要更密切地遵循 Microsoft 的步骤。

此外，还有许多其他的事情会导致您的 AD 不同步，您必须检查它们是否都已修复，否则您可能会再次回到这个位置（并且您也可能丢失了 GPO以及）

推荐阅读