windows-server-2003 – 从死Windows域控制器中获取FSMO角色
我已经看到了关于这样做的其他问题和文件,但有些事情仍然让我困惑.以下是我看过的文件和问题: > Retire a Dead Windows 2003 Domain Controller 该环境包含两个Windows服务器和众多客户端.域控制器是运行Windows 2000 Native AD的Windows 2003 SP2.另一台服务器(根本不是DC)是Windows 2000 SP4(它托管病毒检查实用程序). 来自netdom query fsmo的结果: Schema owner missing.office.local Domain role owner myself.office.local PDC role missing.office.local RID pool manager missing.office.local Infrastructure owner missing.office.local The command completed successfully. dcdiag的结果: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\MYSELF Starting test: Connectivity The host 841d395a-2139-49d9-82c1-7c7e31ccb33b._msdcs.office.local could not be resolved to an IP address. Check the DNS server,DHCP,server name,etc Although the Guid DNS name (841d395a-2139-49d9-82c1-7c7e31ccb33b._msdcs.office.local) couldn't be resolved,the server name (MYSELF.office.local) resolved to the IP address (192.168.9.101) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... MYSELF failed test Connectivity Doing primary tests Testing server: Default-First-Site\MYSELF Skipping all tests,because server MYSELF is not responding to directory service requests Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : office Starting test: CrossRefValidation ......................... office passed test CrossRefValidation Starting test: CheckSDRefDom ......................... office passed test CheckSDRefDom Running enterprise tests on : office.local Starting test: Intersite ......................... office.local passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(PDC_REQUIRED) call failed,error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. ......................... office.local failed test FsmoCheck 这是我的问题(原谅我,如果他们是太多的初学者问题): >从netdom查询fsmo中列出的角色是否与我在其他地方列出的相同?例如,Domain角色所有者是否与Domain Naming Master相同? RID池管理器是否与RID角色相同? 另外 – 一个几乎相切的问题 – 如果我将域升级到Windows 2003 AD(现在或将来),这是否会改变FSMO角色的占用情况? PS:我怀疑DNS问题与尝试使用不支持Microsoft动态DNS的非Microsoft DNS有关;我认为有一个Windows DNS运行,但尚未审核它正常运行和设置.
对,就是这样.不知道为什么他们在那个特定的显示器上的名字略有不同.
癫痫发作本身?不是很多.被警告的大多数潜在问题都是关于在它的角色被抓住之后重新开启旧的DC – 即便如此,那里有很多歇斯底里的风险并没有很多;需要一些非常奇怪的场景才能打破癫痫发作而不是转移角色.为了暂时停下来,让我们回顾角色和潜在的风险: (编辑:ASP站长网) |