我们在两台不同的服务器上安装了 DFS。
运行健康报告未发现任何错误,并且通常一切正常,但是:
在某些计算机上,文件会随机保存在 DFS 文件夹中,但实际上不会出现在其他计算机上或物理上服务器上。有时,如果以同一用户身份登录,它们会出现在其他计算机上,但其他用户(包括管理员)将无法看到它们。
其他文件,只是消失了。
更新:
DFS Replication Health Report (Show All)
Data collected on: 15 December 2015 at 11:43:32 (GMT0:00)
Replication Group: TeachingData (NSNET.NET)
Reference member: SRV-FS02 (srv-fs02.nsnet.net)
Server scope: Selected 2 of 2 servers
DFS Replication bandwidth savings: 0.00%
Server health: Servers with no errors or warnings (1) Servers unavailable for reporting (0)
Servers with DFS Replication errors (1) Servers with DFS Replication warnings (1)
Report Loading. Please wait . . .
ERRORS (1 server with errors)(Show All)
SRV-FS02 (1 error) (View Server Details)
Cannot access the local WMI repository.
WARNINGS (1 server with warnings)(Show All)
SRV-FS02 (1 warning) (View Server Details)
Reference member returned no replicated folders.
SERVERS UNAVAILABLE FOR REPORTING (All servers reporting)
SERVER DETAILS (2 servers)(Show All)
Rendering content. Please wait . . .
SRV-FS02(Show All)
DNS name: srv-fs02.nsnet.net
Domain name: NSNET.NET
Reference domain controller: --
IP address: fe80::a888:789d:b82:1354%16,192.168.0.67
Site: Default-First-Site-Name
Time zone: (GMT0:00)
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication reporting mechanism cannot access the WMI (Windows Management Instrumentation) namespace to retrieve certain reporting information. Error ID: 0x80041002.
Last occurred: 15 December 2015 at 11:43:32 (GMT0:00)
Suggested action: For information about troubleshooting WMI errors, see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the reference member returned zero replicated folders.
Last occurred: 15 December 2015 at 11:43:33 (GMT0:00)
Suggested action: For information about troubleshooting backlog problems, see The Microsoft Web Site.
答案1
我们遇到了同样的问题,并提交了 Microsoft Case。他们最终删除了 .TMP 文件扩展名排除项并重新设置。这解决了我们的问题。