This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 34%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi, We've built a new domain controller on server 2019, our existing domain is on a server 2012 server and we are looking to migrate to the new domain controller but run into problems with replication. Firstly on the new server the SYSVOL and NetLogOn folders were missing I've managed to get those working ok but what's puzzling me in in the SYSVol folder there's no policies folder totally missing. Seems to be replicating ok as when you look at group policies on the new server and make sure the correct server is highlight I can see all the group policies. So not sure where these are being stored. Must have done something wrong initialising this server as even when we select new server as the GC we cannot shut the existing server down. Any ideas will be appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Hi @BrendenWard
To fix the issue of missing sysvol and netlogon folders you can start by launch a non-authoritative synchronization of DFSR sysvol replication as mentioned in the link below:
If you still have the same issue, in this case you should demote and repromote impacted domain controller to force it to replicate correctly sysvol and netlogon folder.
Please don't forget to accept helpful answer
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 62%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hello BrendenWard, Thank you for posting in Q&A forum. May I know if there is only one DC in this domain? If so, did you check the health of this DC (you can run Dcdiag /v on this DC).
1.First, check if there are any network issues in your environment? If there are network issues, replication will definitely fail. 2.Check if the AD replication situation is normal. You can use repadmin\showrepl and repadmin\replsum commands or your own method to check the replication situation. Before troubleshooting on the SYSVOL problem, it is best to back up the SYSVOL folder on both domain controllers and back up the domain controllers using Windows Built-in Windows Back up tool.
3.AsI understand, the SYSVOL replication engine in your case is DFSR.
Reference:
sysvol replication for Forced Synchronous Distributed File System Replication (DFSR) replication - Windows Server | Microsoft Learn
Here is a similar thread for your reference.
How to fix SYSVOL policies not sync issue? - Microsoft Q&A
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy ZhouIf the Answer is helpful, please click "Accept Answer" and upvote it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 63%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMV%3C/text%3E%3C/svg%3E)
The "Policies" folder is still not replicated in the newly added additional domain controller [Win 2022] even after doing the "non-authoritative synchronization" steps.
Formatted 2022 domain controller, we renamed it, assigned a new IP address, and promoted the ADC again using the initial replicate from a different ADC (not from the PDC). This time, the replication went smoothly.