下午好，
我们有两个虚拟 DC 和一个本地物理只读 DC。当我们将数据中心移至异地并设置一个热备份站点时，我们将 DC 改为 v，而 DC1 是主架构。在排除另一个问题时，我们发现主 DC (DC1) 存在问题。当我尝试修改组策略时，它出现错误，无法找到我们的域。
当我检查操作主机时，显示错误并列出 (DC1)。当我运行 netdom query fismo 时，结果指向 (DC2)。在 DC2 上，操作主机是 DC2。
当我在 dc1 上运行 dcdiag 时：
Directory Server DiagnosisPerforming initial setup: Trying to find home server... Home Server = AOBVADC001 * Identified AD Forest. Done gathering initial info.
Doing initial required tests
Testing server: Col-DC\AOBVADC001 Starting test: Connectivity ......................... AOBVADC001 passed test Connectivity
Doing primary tests
Testing server: Col-DC\AOBVADC001 Starting test: Advertising Warning: AOBVADC001 is not advertising as a time server. ......................... AOBVADC001 failed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems.
Running enterprise tests on : swaco.org Starting test: LocatorCheck Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. ......................... swaco.org failed test LocatorCheck Starting test: Intersite ......................... swaco.org passed test Intersite
在第二个 DC 上，dcdaig
Directory Server DiagnosisPerforming initial setup: Trying to find home server... Home Server = AOBVADC002 * Identified AD Forest. Done gathering initial info.
Doing initial required tests
Testing server: Col-DC\AOBVADC002 Starting test: Connectivity ......................... AOBVADC002 passed test Connectivity
Doing primary tests
Testing server: Col-DC\AOBVADC002 Starting test: Advertising ......................... AOBVADC002 passed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. Starting test: SystemLog Contact the administrator to install the driver before you log in again. A warning event occurred. EventID: 0x000016AF Time Generated: 11/25/2014 08:15:40 Event String: During the past 4.24 hours there have been 145 connections to this D omain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined site s and may connect to any Domain Controller including those that are in far dista nt locations from the clients. A client's site is determined by the mapping of i ts subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites. The names and IP addresses of the c lients in question have been logged on this computer in the following log file ' %SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot% \debug\netlogon.bak' created if the former log becomes full. The log(s) may cont ain additional unrelated debugging information. To filter out the needed informa tion, please search for lines which contain text 'NO_CLIENT_SITE:'. The first wo rd after this string is the client name and the second word is the client IP add ress. The maximum size of the log(s) is controlled by the following registry DWO RD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Paramete rs\LogFileMaxSize'; the default is 20000000 bytes. The current maximum size is 20000000 bytes. To set a different maximum size, create the above registry valu e and set the desired maximum size in bytes. ......................... AOBVADC002 failed test SystemLog
我相信我知道我需要对 DC1 做什么，但是自从大学毕业后我还没有这样做过。
我相信我会关闭 DC1 的 dcpromo，然后再打开 dcpromo。如果愿意，我可以将 FSMO 转移回 DC1，但实际上我不在乎。
对我的问题有什么想法吗？
答案1
在我看来，您遇到了 DNS 问题。我认为实际上没有发生与 FSMO 相关的事情。首先确保 AOBVADC001 计算机能够获得域的良好 DNS 解析。