none
从windows 2008 server standard sp1 32迁移主域控至windows 2016 server standard 64出现错误 RRS feed

  • 问题

  • 我再迁移域后有一项测试不通过,有一项有错误,麻烦帮我看看如果解决这个问题,

    以下是检查信息:主域控

    dcdiag

    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server =  PDC01
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: jltest\ PDC01
          Starting test: Connectivity
             .........................  PDC01 passed test Connectivity
    Doing primary tests
       Testing server: jltest\ PDC01
          Starting test: Advertising
             .........................  PDC01 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.
             .........................  PDC01 passed test FrsEvent
          Starting test: DFSREvent
             .........................  PDC01 passed test DFSREvent
          Starting test: SysVolCheck
             .........................  PDC01 passed test SysVolCheck
          Starting test: KccEvent
             .........................  PDC01 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             .........................  PDC01 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             .........................  PDC01 passed test MachineAccount
          Starting test: NCSecDesc
             .........................  PDC01 passed test NCSecDesc
          Starting test: NetLogons
             .........................  PDC01 passed test NetLogons
          Starting test: ObjectsReplicated
             .........................  PDC01 passed test ObjectsReplicated
          Starting test: Replications
             .........................  PDC01 passed test Replications
          Starting test: RidManager
             .........................  PDC01 passed test RidManager
          Starting test: Services
             .........................  PDC01 passed test Services
          Starting test: SystemLog
             An error event occurred.  EventID: 0x00003006
                Time Generated: 12/09/2020   08:27:09
                Event String:
                The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:28:34
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:33:34
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:34:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:34:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{944435D1-F03A-462C-847E-82EA86F536BC}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:34:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{79A0CC6E-ED8D-4EE9-BA34-597639F3F040}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00002720
                Time Generated: 12/09/2020   08:34:36
                Event String:
                The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:38:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:43:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:48:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00003006
                Time Generated: 12/09/2020   08:50:36
                Event String:
                The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:53:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   08:58:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   09:03:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   09:08:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00002720
                Time Generated: 12/09/2020   09:10:32
                Event String:
                The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   09:13:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   09:18:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             An error event occurred.  EventID: 0x00003006
                Time Generated: 12/09/2020   09:19:58
                Event String:
                The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 12/09/2020   09:23:36
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\jltest.com\sysvol\jltest.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
             .........................  PDC01 failed test SystemLog
          Starting test: VerifyReferences
             .........................  PDC01 passed test VerifyReferences

       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : jltest
          Starting test: CheckSDRefDom
             ......................... jltest passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... jltest passed test CrossRefValidation
       Running enterprise tests on : jltest.com
          Starting test: LocatorCheck
             ......................... jltest.com passed test LocatorCheck
          Starting test: Intersite
             ......................... jltest.com passed test Intersite

    2020年12月9日 11:28

全部回复

  • 你好,

    请问您环境中有几台DC?老的DC是否还在?

    首先建议检查DC间的复制是否正常:

    Repadmin /showrepl >C:\repl.txt

    然后请检查Sysvol 文件是否能在两台DC之间复制。

    Best Reards,


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2020年12月10日 2:56
  • 共有4台DC,老的DC还在,DC间复制正常,

    Sysvol 文件不能在两台DC之间复制,互访需要需要账户密码。


    DC=jltest,DC=com
        Default-First-Site-Name\jltest2 via RPC
            DSA object GUID: ec70ae4f-6bd2-4142-a371-8ee1f533210f
            Last attempt @ 2020-12-10 11:32:40 was successful.
    CN=Configuration,DC=jltest,DC=com
        Default-First-Site-Name\jltest2 via RPC
            DSA object GUID: ec70ae4f-6bd2-4142-a371-8ee1f533210f
            Last attempt @ 2020-12-10 11:32:40 was successful.
    CN=Schema,CN=Configuration,DC=jltest,DC=com
        Default-First-Site-Name\jltest2 via RPC
            DSA object GUID: ec70ae4f-6bd2-4142-a371-8ee1f533210f
            Last attempt @ 2020-12-10 11:32:40 was successful.
    DC=ForestDnsZones,DC=jltest,DC=com
        Default-First-Site-Name\jltest2 via RPC
            DSA object GUID: ec70ae4f-6bd2-4142-a371-8ee1f533210f
            Last attempt @ 2020-12-10 11:32:40 was successful.
    DC=DomainDnsZones,DC=jltest,DC=com
        Default-First-Site-Name\jltest2 via RPC
            DSA object GUID: ec70ae4f-6bd2-4142-a371-8ee1f533210f
            Last attempt @ 2020-12-10 11:32:40 was successful.

    2020年12月10日 3:55
  • 你好,

    客户端需要能访问任何一台DC的sysvol 文件,

    DC间,sysvol 需要能访问,复制。

    您说的互访具体是怎么访问的?


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2020年12月10日 5:47
  • 你好:

    就是一台主域服务器不能访问另一台。

    客户端更新组策略弹出如下错误:

    gpupdate /force
    正在更新策略...
    无法成功更新计算机策略。遇到下列错误:
    处理组策略失败。Windows 尝试从域控制器读取文件 \\JLTEST.com\sysvol\jinling.com\Policies\{0E853061-2FE5-4E96-80B5-B6CACA166F8C}\gpt.ini,但是没有成功。只有解决此事件后才会应用组策略设置。该问题可能是暂时的,并可能由下 列一个或多个原因引起:
    a) 到当前域控制器的名称解析/网络连接。
    b) 文件复制服务延迟(在另一域控制器上创建的文件尚未复制到当前域控制器)。
    c) 分布式文件系统(DFS)客户端已被禁用。
    无法成功更新用户策略。遇到以下错误:
    处理组策略失败。Windows 尝试从域控制器读取文件 \\JLTEST.com\SysVol\jinling.com\Policies\{B2A440AD-2718-4998-B4EB-F7600655A23D}\gpt.ini,但是没有成功。只有解决此事件后才会应用组策略设置。该问题可能是暂时的,并可能由下 列一个或多个原因引起:
    a) 到当前域控制器的名称解析/网络连接。
    b) 文件复制服务延迟(在另一域控制器上创建的文件尚未复制到当前域控制器)。
    c) 分布式文件系统(DFS)客户端已被禁用。
    若要诊断故障,请查看事件日志或从命令行运行 GPRESULT /H GPReport.html 来访问有关组策略结果的信息。

    2020年12月16日 3:05
  • 你好,

    首先请确认是否是某一台DC的sysvol文件不能同步。

    如果是这样,可以在这台有问题的DC上对sysvol文件夹做非权威还原(不是权威还原)(也就是强制此台DC上的SYSVOL文件从别的DC上进行复制)

    具体步骤可以参考:

    https://docs.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization

    在进行操作之前,请备份SYSVOL文件(C盘内的其他位置)

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2020年12月16日 4:21
  • 你好,

    如果有任何进展,欢迎在此更新。

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2020年12月18日 1:35