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(246.4, 88%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I have an unusual replication issue and I do not want to force a non-authoritative restore when replication I feel is working for the most part just not the netlogon share but only when it comes to a particular DC. The policies folder on the sysvol replicates just fine and the netlogon share does as well but only if the action is initiated on one of the two DCs when it comes to creating a new file. When it comes to deleting that same file I can initiate from either DC and it deletes from both DCs fine.
Let me explain:
I have 2 DCs, on DC1 if I create a new file in the netlogon(scripts) folder in sysvol I immediately see it replicated to DC2. On DC2 if I create a new file, it never replicates to DC1. However, if I delete the file that was created on DC1 from DC2 netlogon directory, then I immediately see it deleted from both DCs. So it seems it is only the write attempt from DC2 to DC1 that is having the issue. Permissions have not been modified from default of course but I did verify via ADSI and all are correct/identical on all partitions compared to that on another one of our domains that is working as expected. There are no replication errors when I run any of the dcdiag checks and repadmin is also error free so I am trying to see if anyone can provide insight as to why this may be happening before I dive too deep with verbose corrective actions that might not be needed. Thank you.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
One option may be to move roles off, demote, reboot, promo the problematic one.
--please don't forget to upvote and Accept as answer if the reply is helpful--
I agree I just was really hoping to figure out this odd problem before going that route and see what others had to say but the demotion route is more than likely what I will attempt here soon.
Thank you for your feedback.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
![](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,
Repadmin command shows errors on AD replication and not sysvol replication .
Check if you get error related to sysvol replication on event viewer of each DC and when you launch dcdiag command.
Check if the network flow is ok between the two DC.
Don't hesitate to share with us the message error.
Please don't forget to mark helpful answer as accepted
Thank you yes I am aware of repadmin only monitoring AD rep I was just mentioning that one as well if anyone was wondering if I had any other kind of replication issues period. In regards to dcdiag I also mentioned in my question that all dcdiag rep checks return with no failures. No errors in event logs either. It is quite strange, especially when the policies directory replicate as expected between all DCs regardless of the initiating DC. I think I am just going to demote the problem child and re-promote before getting into the weeds any deeper.
Thank you for your feedback though.
Sounds like the simplest / best plan.
--please don't forget to upvote and Accept as answer if the reply is helpful--