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(163.2, 7.000000000000001%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
New server 2019 DC. Forest/domain level 2012r2.
New 2019 DC. NTDS and SYSVOL were set to a separate partition as I was lead to believe that this was better than having it on the system partition. This was done during dcpromo.
This is the first time I have set them on a separate partition.
When going to This PC - map network drive - \new2019dcservername\netlogon, I get an error.
Unable to connect 0x80070043.
Is this a result of the above being on a different partition or something else wrong?
How do I resolve this error while keeping the above on a separate partition?
I am able to do this with existing DC's where the above was set to the default locations.
If I have to move them back to the default c:\windows folders, please provide the cmd, cmdlets needed to do so.
Thanks
![](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)
You can try a non authoritative sync
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Sorry for the delay in response as I was unable to try this until I had time outside of office hours to try this in the event something got buggered up.
I did a non authoritative sync on the original DC and it replicated sysvol to the new DC.
However, they're not updating/syncing with each other after changes are made.
However, they're not updating/syncing with each other after changes are made.
How are you evaluating?
I stand corrected. Sysvol is now replicating.
Ok, good news then.
Testing method was making a text document in NETLOGON on DC1 and see if it appeared in NETLOGON on DC2.
Hello @Susan Dodds
I can recommend the next thread with a lengthy troubleshooting and analysis of the same issue:
Hope this helps with your query,
-----
--If the reply is helpful, please Upvote and Accept as answer--