How to Re-build SYSVOL DFSR replication group without Demoting/Promoting DC<\/a> \nto perform an authoritative restore of SYSVOL but still, nothing is replicating.<\/p>\nDomain/Forest function level: Windows Server 2012 R2<\/p>\n
dcdiag /v /c /e /q:<\/p>\n
From AD2<\/p>\n
[DC1] No security related replication errors were found on this DC!\n\n To target the connection to a specific source DC use /ReplSource:<DC>.\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n [AD1] No security related replication errors were found on this\n\n DC! To target the connection to a specific source DC use\n\n /ReplSource:<DC>.\n\n There are warning or error events within the last 24 hours after the\n\n SYSVOL has been shared. Failing SYSVOL replication problems may cause\n\n Group Policy problems. \n ......................... AD1 failed test DFSREvent\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:16\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.0.0.1 using any of the configured protocols; requested by PID 1a54 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:16\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 1a54 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n ......................... AD1 failed test SystemLog\n\n [AD2] No security related replication errors were found on\n\n this DC! To target the connection to a specific source DC use\n\n /ReplSource:<DC>.\n\n There are warning or error events within the last 24 hours after the\n\n SYSVOL has been shared. Failing SYSVOL replication problems may cause\n\n Group Policy problems. \n ......................... AD2 failed test DFSREvent\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 22:50:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 22:55:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:00:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:05:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:10:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:15:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:20:03\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0xC00009C9\n\n Time Generated: 06/06/2024 23:23:59\n\n Event String:\n\n The server could not bind to the transport \\Device\\NetBT_Tcpip_{FECFF037-2243-4DEA-8F94-D3C9FBE1DCA9} because another computer on the network has the same name. The server could not start.\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:25:03\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:30:04\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:35:05\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:40:05\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:41:21\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\sysvol\\domain.local\\Policies\\{31B2F340-016D-11D2-945F-00C04FB984F9}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:45:06\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n ......................... AD2 failed test SystemLog\n\n<\/code><\/pre>\nFrom DC1 (PDC)<\/p>\n
[DC1] No security related replication errors were found on this DC!\n\n To target the connection to a specific source DC use /ReplSource:<DC>.\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n [AD1] No security related replication errors were found on this\n\n DC! To target the connection to a specific source DC use\n\n /ReplSource:<DC>.\n\n There are warning or error events within the last 24 hours after the\n\n SYSVOL has been shared. Failing SYSVOL replication problems may cause\n\n Group Policy problems. \n ......................... AD1 failed test DFSREvent\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:16\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.0.0.1 using any of the configured protocols; requested by PID 1a54 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:16\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 1a54 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n ......................... AD1 failed test SystemLog\n\n [AD2] No security related replication errors were found on\n\n this DC! To target the connection to a specific source DC use\n\n /ReplSource:<DC>.\n\n There are warning or error events within the last 24 hours after the\n\n SYSVOL has been shared. Failing SYSVOL replication problems may cause\n\n Group Policy problems. \n ......................... AD2 failed test DFSREvent\n\n ** Did not run Outbound Secure Channels test because /testdomain: was\n\n not entered\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 22:55:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:00:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:05:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:10:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:15:02\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:20:03\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0xC00009C9\n\n Time Generated: 06/06/2024 23:23:59\n\n Event String:\n\n The server could not bind to the transport \\Device\\NetBT_Tcpip_{FECFF037-2243-4DEA-8F94-D3C9FBE1DCA9} because another computer on the network has the same name. The server could not start.\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:25:03\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:30:04\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:35:05\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:40:05\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:41:21\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\sysvol\\domain.local\\Policies\\{31B2F340-016D-11D2-945F-00C04FB984F9}\\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: \n\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:45:06\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:52\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.0.0.1 using any of the configured protocols; requested by PID 1cc8 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n An error event occurred. EventID: 0x0000272C\n\n Time Generated: 06/06/2024 23:47:52\n\n Event String:\n\n DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 1cc8 (C:\\Windows\\system32\\dcdiag.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.\n\n An error event occurred. EventID: 0x00000422\n\n Time Generated: 06/06/2024 23:50:06\n\n Event String:\n\n The processing of Group Policy failed. Windows attempted to read the file \\\\domain.local\\SysVol\\domain.local\\Policies\\{52E146AF-FF25-4A6E-A60E-55239F4C1ACE}\\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: \n\n\n ......................... AD2 failed test SystemLog\n<\/code><\/pre>\nIs there any way I can resolve this?<\/p>","upvoteCount":0,"datePublished":"2024-06-07T03:57:33.813Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/1","author":{"@type":"Person","name":"spiceuser-nl7d","url":"https://community.spiceworks.com/u/spiceuser-nl7d"}},{"@type":"Answer","text":"
Start by checking your DNS setup on the NICs of your domain controllers. The vast majority of replication issues are caused by misconfigured DNS. Verify that first and we can go from there.<\/p>\n\n \n
<\/div>\n
\n
Active Directory DNS Refresher<\/a> Windows<\/span><\/span><\/a>\n <\/div>\n \n It’s DNS. It’s always DNS. No, DNS is fine, it’s not DNS, trust me. \nIt was DNS. \nI’m posting because in the last few weeks we’ve had a few posts that turned out to be misconfigurations with DNS in a domain environment. Things like Domain controllers pointing at themself first for DNS, or having a public DNS server on the NIC of the Domain Controller or the clients. Hopefully this will help some people get out in front of potential issues. \nThe general rules for DNS in an AD E…\n <\/blockquote>\n<\/aside>\n","upvoteCount":2,"datePublished":"2024-06-07T05:12:33.289Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/2","author":{"@type":"Person","name":"PatrickFarrell","url":"https://community.spiceworks.com/u/PatrickFarrell"}},{"@type":"Answer","text":"Was AD1 replicating before AD2 was added? and is it still? \nIf not then I would (first check DC1 holds all roles then) demote AD1 and AD2, check DC1 fully works. check frs is migrated to DFSR then re promote a AD1. check replication.<\/p>","upvoteCount":0,"datePublished":"2024-06-07T09:58:05.825Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/3","author":{"@type":"Person","name":"matt7863","url":"https://community.spiceworks.com/u/matt7863"}},{"@type":"Answer","text":"
You should never manipulate sysvol or any folders in DCs as they are automatically created and managed by DCs<\/p>\n
How long did you wait for the replication ? Sometimes it may take up to 72 hours to complete.<\/p>\n
Check your DNS IP addresses in all the DCs ? Can show the IP configs for DNS in all the 3 DCs ?<\/p>","upvoteCount":1,"datePublished":"2024-06-07T10:39:49.071Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/4","author":{"@type":"Person","name":"adrian_ych","url":"https://community.spiceworks.com/u/adrian_ych"}},{"@type":"Answer","text":"
Thanks @PatrickFarrell<\/a>, I confirmed DNS as follows: \nPrimary/Secondary: Other 2 DC’s \nFallback: 127.0.0.1<\/p>\nnslookup domain.local returns all 3 DC’s.<\/p>\n
Forward and reverse lookups are resolving properly. Any ideas next?<\/p>","upvoteCount":0,"datePublished":"2024-06-07T12:57:00.971Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/5","author":{"@type":"Person","name":"spiceuser-nl7d","url":"https://community.spiceworks.com/u/spiceuser-nl7d"}},{"@type":"Answer","text":"
AD1 WAS replicating at one point, but is no longer replicating.<\/p>\n
All domain controllers have migrated successfully to the Global state (‘Eliminated’).<\/p>\n
Im VERY hesitant to demote AD1/AD2 as DC1 is on the hospital bed. It was a physical DC that died, which I barely got back up, and migrated to a temporary VM.<\/p>","upvoteCount":0,"datePublished":"2024-06-07T13:02:02.490Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/6","author":{"@type":"Person","name":"spiceuser-nl7d","url":"https://community.spiceworks.com/u/spiceuser-nl7d"}},{"@type":"Answer","text":"
Are AD1 & 2 fully working? \nIf you disable (turn off, disconnect from network) DC1 can you: \nlogon (not using cached credentials, so first time on that device)? \nsuccessfully change a password? If this works the next 2 should: \nadd a user? domain join a device? \nIf all that works then it is just sysvol/netlogon issues. but if some of that fails you have other replication issues and removing and re-promoting makes sense.<\/p>\n
If all the tests pass you could transfer the roles to AD1 and remove DC1 then try to fix your replication issues.<\/p>","upvoteCount":0,"datePublished":"2024-06-07T14:30:02.365Z","url":"https://community.spiceworks.com/t/sysvol-wont-replicate/1084147/7","author":{"@type":"Person","name":"matt7863","url":"https://community.spiceworks.com/u/matt7863"}}]}}
Start by checking your DNS setup on the NICs of your domain controllers. The vast majority of replication issues are caused by misconfigured DNS. Verify that first and we can go from there.
It’s DNS. It’s always DNS. No, DNS is fine, it’s not DNS, trust me.
It was DNS.
I’m posting because in the last few weeks we’ve had a few posts that turned out to be misconfigurations with DNS in a domain environment. Things like Domain controllers pointing at themself first for DNS, or having a public DNS server on the NIC of the Domain Controller or the clients. Hopefully this will help some people get out in front of potential issues.
The general rules for DNS in an AD E…
2 Spice ups