locked
Windows failed to apply the group policy registry settings. Group policy settings might have its own log file. RRS feed

  • Question

  • Hi Experts!

    We have some issue with GPO in active directory 2016. The issue was occurred when we upgrade the AD 2008R2 to windows 2016 using clean installation method. 

    Background of the issue : 

    2008R2 Active Directory was being upgraded to Windows server 2016 using clean installation method. After migrated they noticed that some of GPO policy is missing and there was an replication has test passed in dcdiag. 

    1. We run DC DIAG 

    Windows failed to apply the group policy registry settings. Group policy settings might have its own log file.

    Event ID : 0x0000043D

    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 problem

    2 . Repadmin /showrepl




    Homer Sibayan

    Friday, July 24, 2020 11:19 AM

All replies

  • I can see you have recently recovered your domain, from prior posts.

    GPO requires SYSVOL and DFSR to be in a healthy condition for correct operation.

    It seems your SYSVOL and DFSR has errors, the article may help you diagnose and resolve those

    https://support.microsoft.com/en-au/help/2958414/dfs-replication-how-to-troubleshoot-missing-sysvol-and-netlogon-shares


    Don [doesn't work for MSFT, and they're probably glad about that ;]


    • Edited by DonPick Friday, July 24, 2020 11:07 PM
    Friday, July 24, 2020 11:05 PM
  • Hi 

    Where do i use the method of Authoritative synchronization for DFSR replicated sysvol ? to the DC who have the problem with GPO after being promoted or to the updated DC which looks like not replicated the policies to newly promoted DC. 

    I just want to understand too  when do i need to use Authoritative and non Authoritative method. 

    Is there any downtime or impact to the user during performing Authoritative and non-authoritative method? 


    Homer Sibayan

    Sunday, July 26, 2020 2:36 AM
  • Hi 

    Where do i use the method of Authoritative synchronization for DFSR replicated sysvol ? to the DC who have the problem with GPO after being promoted or to the updated DC which looks like not replicated the policies to newly promoted DC. 

    I just want to understand too  when do i need to use Authoritative and non Authoritative method. 

    Is there any downtime or impact to the user during performing Authoritative and non-authoritative method? 


    Homer Sibayan

    As per the linked article, do not rush to perform any kind of authoritative restore, instead, perform the troubleshooting steps in KB2958414, and only if confirmed move to the steps in KB2218556.

    If you do need to perform authoritative restore, the concept is that you will determine one DC to use as the source of the "good" SYSVOL data and that is the authority, which is replicated to all other DC's.

    As to downtime or impact, no more than you are already suffering due to GPO/SYSVOL issues.


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Sunday, July 26, 2020 11:03 AM
  • Hello,

    Thank you for posting in our TechNet forum.

    According to your description, there is GPO issue on the Windows server 2016 DC. Hope the provided information is helpful.

    Whether our AD environment is healthy, we can check as below:

    1. We should check if all DCs work fine by running Dcdiag /v on every DC.
    2. And check if AD replication is working properly by running repadmin /showrepl and repadmin /replsum on every DC.
    3. Check if we can run gpupdate /force successfully on every DC.
    4. Check if the SYSVOL and Netlogon are shared by running net share on every DC.
    5. Check if there is any error when running gpresult /h C:\report.html on every DC.

    As per our description, there is error message when running Dcdiag on 2016 DC. And there is no error when running repadmin /showrepl on 2016 DC. We could kindly check the above 3,4,5 to check whether there is any other error.

    For any question, please feel free to contact us.

    This "Directory Services" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 

    Best regards,
    Hannah Xiong

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

    Monday, July 27, 2020 6:25 AM
  • Hi Hannah Xiong, 

    thanks you for posting your comments. We already perform a Force authoritative Synchronization DFSR sysvol replication and we have successfully synchronized the DC01 on site A and DC02 on site B. Unfortunately, i 've got an error encountered after running "GPupdate /force" to refresh the policy after performing the force Authoritative Synchronization DFSR sysvol. See below. 

    Also, Prior before Force Authoritative we have perform some pre-requisites : 

    Evaluate the Stated of DFS Replication on all Domain Controllers

    1. Check for the Sysvol share



    Homer Sibayan


    • Edited by Remoh_10 Monday, July 27, 2020 12:19 PM
    Monday, July 27, 2020 12:13 PM
  • 2. Check DFS Replication state

    3.Check Event logs for recent errors or warnings

    4. Check the Content Freshness configuration

    5.Query all domain controllers in the domain, run the following command 


    Homer Sibayan

    Monday, July 27, 2020 12:15 PM

  • Homer Sibayan

    • Edited by Remoh_10 Monday, July 27, 2020 12:21 PM
    Monday, July 27, 2020 12:17 PM
  • Hi Homer,

    You are welcome. Thank you so much for your feedback.

    We can try to follow the steps below to troubleshoot.

    1. Logon the 2016 DC, open “run” and enter \\name.com\sysvol\name.com\Policies\GUID\gpt.ini. Click “Enter” to check whether we could access this gpt.ini file. If not, what is the error message? Besides, is there any information in the gpt.ini files?

    Then try to access the following path to see which level can be accessed normally. As we know, to apply the group policy, we must firstly be able to access the corresponding gpt.ini file. 
    \\name.com
    \\name.com\sysvol
    \\name.com\sysvol\name.com
    \\name.com\sysvol\name.com\Policies
    \\name.com\sysvol\name.com\Policies\GUID
    \\name.com\sysvol\name.com\Policies\GUID\gpt.ini



    2. On one DC, we can try to create a new file or folder in the following path, then check whether this new file or folder can be copied to the same path on other DCs automatically.
    \\name.com\sysvol\name.com\Policies

    3. As for the event 1058, we could also refer to this article to troubleshoot.
    https://social.technet.microsoft.com/wiki/contents/articles/1456.event-id-1058-group-policy-preprocessing-networking.aspx

    Thank you so much for your time and support.

    Best regards,
    Hannah Xiong

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

    Tuesday, July 28, 2020 5:31 AM
  • Hi 

    Upon opening the path i can't see the gpt.ini on the sysvol policies. 

    \name.com\sysvol\name.com\Policies\GUID\gpt.ini there is no gpt.ini . The following path is accessible

    \\name.com
    \\name.com\sysvol
    \\name.com\sysvol\name.com
    \\name.com\sysvol\name.com\Policies
    \\name.com\sysvol\name.com\Policies\GUID
    \\name.com\sysvol\name.com\Policies\GUID\gpt.ini

    Please see the dcdiag report 

    C:\Users\Administrator.PETCAD1100>dcdiag

    Directory Server Diagnosis

    Performing initial setup:
       Trying to find home server...
       Home Server = petsvr1100
       * Identified AD Forest.
       Done gathering initial info.

    Doing initial required tests

       Testing server: MANILA\PETSVR1100
          Starting test: Connectivity
             ......................... PETSVR1100 passed test Connectivity

    Doing primary tests

       Testing server: MANILA\PETSVR1100
          Starting test: Advertising
             ......................... PETSVR1100 passed test Advertising
          Starting test: FrsEvent
             ......................... PETSVR1100 passed test FrsEvent
          Starting test: DFSREvent
             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.
             ......................... PETSVR1100 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... PETSVR1100 passed test SysVolCheck
          Starting test: KccEvent
             ......................... PETSVR1100 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... PETSVR1100 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... PETSVR1100 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... PETSVR1100 passed test NCSecDesc
          Starting test: NetLogons
             ......................... PETSVR1100 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... PETSVR1100 passed test ObjectsReplicated
          Starting test: Replications
             ......................... PETSVR1100 passed test Replications
          Starting test: RidManager
             ......................... PETSVR1100 passed test RidManager
          Starting test: Services
             ......................... PETSVR1100 passed test Services
          Starting test: SystemLog
             An error event occurred.  EventID: 0x00000422
                Time Generated: 07/28/2020   17:47:04
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   17:51:56
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{5321F835-ED40-49B4-A2B5-89160413ECCB}\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: 07/28/2020   17:52:05
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   17:54:08
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{808C64E1-8E4D-4EAE-9928-395B323C8829}\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: 07/28/2020   17:57:05
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:01:53
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:01:53
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{808C64E1-8E4D-4EAE-9928-395B323C8829}\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: 07/28/2020   18:04:35
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{808C64E1-8E4D-4EAE-9928-395B323C8829}\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: 07/28/2020   18:06:53
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 0xC0001B61
                Time Generated: 07/28/2020   18:07:54
                Event String: A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
             An error event occurred.  EventID: 0xC0001B61
                Time Generated: 07/28/2020   18:08:11
                Event String: A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
             An error event occurred.  EventID: 0xC0001B61
                Time Generated: 07/28/2020   18:08:29
                Event String: A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
             An error event occurred.  EventID: 0xC0001B61
                Time Generated: 07/28/2020   18:09:29
                Event String: A timeout was reached (30000 milliseconds) while waiting for the File Replication Service service to connect.
             An error event occurred.  EventID: 0x00000422
                Time Generated: 07/28/2020   18:11:53
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:16:53
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:17:51
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{808C64E1-8E4D-4EAE-9928-395B323C8829}\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: 07/28/2020   18:21:54
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:26:54
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:31:54
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:36:54
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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: 07/28/2020   18:39:13
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{808C64E1-8E4D-4EAE-9928-395B323C8829}\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: 07/28/2020   18:41:54
                Event String:
                The processing of Group Policy failed. Windows attempted to read the file \\petcad1100\SysVol\petcad1100\Policies\{9A923EA7-E714-4E6C-BB49-2080A62E653F}\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:
             ......................... PETSVR1100 failed test SystemLog
          Starting test: VerifyReferences
             ......................... PETSVR1100 passed test VerifyReferences


       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation

       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones 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 : petcad1100
          Starting test: CheckSDRefDom
             ......................... petcad1100 passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... petcad1100 passed test CrossRefValidation

       Running enterprise tests on : petcad1100
          Starting test: LocatorCheck
             ......................... petcad1100 passed test LocatorCheck
          Starting test: Intersite
             ......................... petcad1100 passed test Intersite

    _______________________________________________________

    Gpresult /r

    C:\Users\Administrator.PETCAD1100>gpresult /r

    Created on 28/07/2020 at 6:41:49 PM


    RSOP data for PETCAD1100\Administrator on PETSVR1100 : Logging Mode
    --------------------------------------------------------------------

    OS Configuration:            Primary Domain Controller
    OS Version:                  10.0.14393
    Site Name:                   MANILA
    Roaming Profile:             N/A
    Local Profile:               C:\Users\Administrator.PETCAD1100
    Connected over a slow link?: No


    COMPUTER SETTINGS
    ------------------
        CN=PETSVR1100,OU=Domain Controllers,DC=petcad1100
        Last time Group Policy was applied: 28/07/2020 at 6:36:54 PM
        Group Policy was applied from:      petsvr1100.petcad1100
        Group Policy slow link threshold:   500 kbps
        Domain Name:                        PETCAD1100
        Domain Type:                        Windows 2008 or later

        Applied Group Policy Objects
        -----------------------------
            Google_Chrome
            Default Domain Controllers Policy
            NTP SERVER(TIME SYNC)
            NEAR_SITE
            Certification_Global
            Firewall
            Windows10_Block_Apps
            PET_Default
            Default Domain Policy
            MIS_Local_Admin
            NTP SERVER(TIME SYNC)

        The following GPOs were not applied because they were filtered out
        -------------------------------------------------------------------
            EV_PC-Restrict
                Filtering:  Denied (Security)

            Local Group Policy
                Filtering:  Not Applied (Empty)

            WindowsUpdateBlock
                Filtering:  Denied (Security)

        The computer is a part of the following security groups
        -------------------------------------------------------
            BUILTIN\Administrators
            Everyone
            BUILTIN\Pre-Windows 2000 Compatible Access
            BUILTIN\Users
            Windows Authorization Access Group
            NT AUTHORITY\NETWORK
            NT AUTHORITY\Authenticated Users
            This Organization
            PETSVR1100$
            Domain Controllers
            NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS
            Authentication authority asserted identity
            Denied RODC Password Replication Group
            System Mandatory Level


    USER SETTINGS
    --------------
        CN=Administrator,CN=Users,DC=petcad1100
        Last time Group Policy was applied: 28/07/2020 at 6:01:53 PM
        Group Policy was applied from:      petsvr1100.petcad1100
        Group Policy slow link threshold:   500 kbps
        Domain Name:                        PETCAD1100
        Domain Type:                        Windows 2008 or later

        Applied Group Policy Objects
        -----------------------------
            PET COVID19
            Google_Chrome
            PET SCREENSAVER
            Firewall
             Desktop shortcut
            Windows10_Block_Apps
            PET_Default
            Default Domain Policy
            Outlook_Cached-Settings

        The following GPOs were not applied because they were filtered out
        -------------------------------------------------------------------
            Local Group Policy
                Filtering:  Not Applied (Empty)

        The user is a part of the following security groups
        ---------------------------------------------------
            ERROR: An unexpected error occurred.


    C:\Users\Administrator.PETCAD1100>


    Homer Sibayan


    • Edited by Remoh_10 Tuesday, July 28, 2020 10:57 AM
    Tuesday, July 28, 2020 6:46 AM
  • Hello Homer,

    Thank you so much for your feedback.

    To further troubleshoot, we would like to check with you about the below points: 

    1, How many DCs are in AD environment? 
    2, If there are other DCs, do the DCs work fine? We could run Dcdiag /v on the DCs and check whether there is any error message.
    3, On the DCs, we could check whether we could see the gpt,ini files. 
    4, We could run repadmin /showrepl * /csv >C:\showrepl.csv to check the AD replication of all DCs. 

    Thank you so much for your time and support.


    Best regards,
    Hannah Xiong

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

    Thursday, July 30, 2020 7:58 AM
  • Hi hannah,

    1, How many DCs are in AD environment?  - 2 DC both AD 2016 / DC01 in site A and DC02 in site B
    2, If there are other DCs, do the DCs work fine? We could run Dcdiag /v on the DCs and check whether there is any error message. - yes sysvol replication and domain controller replication works fine. only the GPO policy is not .

    3, On the DCs, we could check whether we could see the gpt,ini files.  yes, actually before we don't see gpt file but i restored it one by one to all policies folder. 
    4, We could run repadmin /showrepl * /csv >C:\showrepl.csv to check the AD replication of all DCs. 

    showrepl_COLUMNS,Destination DSA Site,Destination DSA,Naming Context,Source DSA Site,Source DSA,Transport Type,Number of Failures,Last Failure Time,Last Success Time,Last Failure Status
    showrepl_INFO,ILOILO,PETIADSVR,DC=petcad1100,MANILA,PETSVR1100,RPC,0,0,2020-07-30 16:36:17,0
    showrepl_INFO,ILOILO,PETIADSVR,"CN=Configuration,DC=petcad1100",MANILA,PETSVR1100,RPC,0,0,2020-07-30 16:36:17,0
    showrepl_INFO,ILOILO,PETIADSVR,"CN=Schema,CN=Configuration,DC=petcad1100",MANILA,PETSVR1100,RPC,0,0,2020-07-30 16:36:17,0
    showrepl_INFO,ILOILO,PETIADSVR,"DC=DomainDnsZones,DC=petcad1100",MANILA,PETSVR1100,RPC,0,0,2020-07-30 16:36:18,0
    showrepl_INFO,ILOILO,PETIADSVR,"DC=ForestDnsZones,DC=petcad1100",MANILA,PETSVR1100,RPC,0,0,2020-07-30 16:36:18,0
    showrepl_INFO,MANILA,PETSVR1100,DC=petcad1100,ILOILO,PETIADSVR,RPC,0,0,2020-07-30 16:41:55,0
    showrepl_INFO,MANILA,PETSVR1100,"CN=Configuration,DC=petcad1100",ILOILO,PETIADSVR,RPC,0,0,2020-07-30 16:41:55,0
    showrepl_INFO,MANILA,PETSVR1100,"CN=Schema,CN=Configuration,DC=petcad1100",ILOILO,PETIADSVR,RPC,0,0,2020-07-30 16:41:55,0
    showrepl_INFO,MANILA,PETSVR1100,"DC=DomainDnsZones,DC=petcad1100",ILOILO,PETIADSVR,RPC,0,0,2020-07-30 16:41:55,0
    showrepl_INFO,MANILA,PETSVR1100,"DC=ForestDnsZones,DC=petcad1100",ILOILO,PETIADSVR,RPC,0,0,2020-07-30 16:41:55,0


    Homer Sibayan

    Thursday, July 30, 2020 9:02 AM
  • Hi Homer,

    Thank you so much for your feedback.

    According to the provided information, the AD replication works fine. As for the SYSVOL replication, we also said that it works fine. Have we did the below test?

    On the two DCs, we can try to create a new file or folder in the following path, then check whether this new file or folder can be copied to the same path on other DC automatically.
    \\name.com\sysvol\name.com\Policies

    By the test, we could check whether SYSVOL replication works fine and which DC will replicate and which one not. 

    Besides, as mentioned, there are two DCs in two sites. Both the DCs have dcdiag issues, which indicate the GPO policy issue. After restoring the SYSVOL folder, we could see the gpt.ini files on the two DCs, right? 

    If possible, we could have a check of the DNS issue. To check about this, we could try the below:

    Run nslookup to check whether the domain could be successfully resolved.
    Run Ping IP address of DNS server and FQDN to check whether it could connect to DNS.
    Run Ping domain name to check whether it could connect to the domain.



    Thank you so much for your time and support.

    Best regards,
    Hannah Xiong

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

    Friday, July 31, 2020 6:28 AM