ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved broken sysvol replication

    IT Discussion
    6
    13
    1.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Mike DavisM
      Mike Davis
      last edited by Mike Davis

      I'm troubleshooting broken sysvol replication across 3 Server 2012 R2 boxes and a 4th that maybe 2008 R2. (It's offline right now.) When I go in to DFS Management, I see nothing.
      0_1475813283979_DFS.png

      Where do you go from there? Do you still follow the steps for forcing a sync of DFSR?

      1 Reply Last reply Reply Quote 0
      • J
        Jason Banned
        last edited by

        Are you sure you've switched it to DFS replication from the FRS

        1 Reply Last reply Reply Quote 0
        • Mike DavisM
          Mike Davis
          last edited by

          no, in fact, dcdiag says:
          DC1 failed test FrsEvent

          1 Reply Last reply Reply Quote 0
          • Minion QueenM
            Minion Queen Banned
            last edited by

            Umm go to bed. IT can wait till the morning.

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Minion Queen
              last edited by

              @Minion-Queen said in broken sysvol replication:

              Umm go to bed. IT can wait till the morning.

              IT waits for no man.

              travisdh1T 1 Reply Last reply Reply Quote 3
              • travisdh1T
                travisdh1 @scottalanmiller
                last edited by

                @scottalanmiller said in broken sysvol replication:

                @Minion-Queen said in broken sysvol replication:

                Umm go to bed. IT can wait till the morning.

                IT waits for no man.

                Or Woman/MinionQueen

                1 Reply Last reply Reply Quote 1
                • Mike DavisM
                  Mike Davis
                  last edited by

                  So removed the DC that was causing a ton of errors. Now in dcdiag I'm down to:
                  Starting test: FrsEvent
                  There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL
                  replication problems may cause Group Policy problems.

                  as the only error in dcdiag.

                  1 Reply Last reply Reply Quote 0
                  • Mike DavisM
                    Mike Davis
                    last edited by

                    and that is the reason I started looking in to this. My group policies weren't working and files in sysvol weren't being copied.

                    1 Reply Last reply Reply Quote 0
                    • Mike DavisM
                      Mike Davis
                      last edited by

                      I tried:
                      ntfrsutl forcerepl dc4 /r "domain system volume (sysvol share)" /p dc1

                      but I'm not sure it did anything.

                      1 Reply Last reply Reply Quote 0
                      • momurdaM
                        momurda
                        last edited by

                        Are you getting Event ID 13555 under the FRS Application and Service Log in Event Viewer?
                        For more than one or more of your DCs? If so, you might have to do a bit of work.

                        1 Reply Last reply Reply Quote 0
                        • Mike DavisM
                          Mike Davis
                          last edited by

                          I have two DCs throwing a 13555 when I do a net stop ntfrs and net start ntfrs
                          The third DC is throwing 13508.

                          1 Reply Last reply Reply Quote 0
                          • momurdaM
                            momurda
                            last edited by

                            I had these errors in the past as well; usually after something bad happened to a server, like a power failure or something.
                            My solution was to find a DC without errors(hopefully you have at least one of those), move fsmo roles to that, then demote-then-promote the DCs with the 13555 errors.
                            There is probably another way to do it; but IME using forcerepl didn't work.

                            Mike DavisM 1 Reply Last reply Reply Quote 0
                            • Mike DavisM
                              Mike Davis @momurda
                              last edited by

                              got it working. I did the burflags thing. On the server throwing the 13508, I backed up sysvol, stopped ntfrs and changed the registry key:
                              HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\BurFlags to D4 , started ntfrs, and then went to the other two domain controllers.
                              On them I stopped ntfrs and changed:
                              HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\BurFlags to D2
                              and started ntfrs.

                              after a few minutes the logs were clean. I logged in to a workstation and group policy didn't throw any errors.

                              1 Reply Last reply Reply Quote 7
                              • 1 / 1
                              • First post
                                Last post