sysvol is not shared but it is replicated

abraham flores 251 Reputation points
2022-06-11T06:37:25.927+00:00

I promoted a new domain controller, but netlogon and sysvol were missing, I check this: ![210397-image.png][1] there is an event id 4604 indicating that replication has already started, I created a couple of GPOs an they were replicated between all three domain controllers, the rest of GPOs were also replicated, repadmin was not showwing any errors, I changed a SysvolReady registry, I perfomed a D2 restoration but still SYSVOL and netlogon were not shared on this DC. Can I just shared as a normal folder? [1]: /api/attachments/210397-image.png?platform=QnA

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,807 questions
0 comments No comments
{count} votes

Accepted answer
  1. Limitless Technology 39,786 Reputation points
    2022-06-14T07:40:41.487+00:00

    Hello

    Thank you for your question and reaching out. I can understand you are having issues related to SYSVOL folder not sharing.

    It can be issue with network connections that blocking Traffic of AD . Disable any Antivirus program or Windows firewall you may have for temporary purpose.

    Please try to force an authoritative, or non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
    https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization

    Please verify on new DC ip should be of Health DC and not of your Firewall or Router ip.
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares

    -------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--


3 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-06-11T12:27:15.667+00:00

    Might try demoting, reboot, promo it again.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. abraham flores 251 Reputation points
    2022-06-11T18:44:24.397+00:00

    Hi again,

    I applied the steps you recommended, and I also checked: 4604 indicating that replication has already started, I created a couple of GPOs an they were replicated between all three domain controllers, I deleted the two GPOs created (no problem showed), the rest of GPOs were also replicated, repadmin was not showing any errors, SYSVOL and Netlogon folders were shared.

    Before promoting the DC again, I renamed the sysvol folder and I got this message just once: Local path of replicated folder SYSVOL Share does not match the newly configured local path.
    Affected replicated folders: SYSVOL Share
    Description: The DFS Replication service detected that the local path of a replicated folder C:\Windows\SYSVOLOLD\domain in its database does not match the newly configured local path C:\Windows\SYSVOL\domain of the replicated folder SYSVOL Share. The service will replicate the new path, and the old replicated folder path in the database will no longer be tracked as a replicated folder. Event ID: 6406

    I have been testing and I do not see any errors, can I monitor this behavior and maybe ignore the message since after this, the event ID 4604 appeared.

    0 comments No comments

  3. Anonymous
    2022-06-11T18:47:49.893+00:00

    I renamed the sysvol folder and I got this message

    If it were me I'd get rid of this one, then confirm the domain health is 100% before attempting to add another.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.