Sysvol not updating

14-Apr-2020 05:14 by 2 Comments

Sysvol not updating - Afrigha sex web

It was as if it had replicated the empty SYSVOL to the PDC instead of the other way around. Yes, we could have started from scratch, but that would not have been a good political decision.And we really didn't have root cause to justify it.

No SYSVOL or Netlogon share, no SYSVOL tree on the second domain controller.

However This does give you a “usual suspect” to check and may actually be the answer.

Policy Error: Version mismatch on dc1.domain.org, DS=65580, sysvol=65576 Friendly name: Default Domain Controllers Policy Error: Version mismatch on dc2.domain.org, DS=65580, sysvol=65576 Details: ------------------------------------------------------------ DC: dc1.Friendly name: Default Domain Controllers Policy Created: 7/7/2005 PM Changed: 6/18/2012 PM DS version: 1(user) 44(machine) Sysvol version: 1(user) 40(machine) Flags: 0 (user side enabled; machine side enabled) User extensions: not found Machine extensions: [] Functionality version: 2 ------------------------------------------------------------ DC: dc2.Friendly name: Default Domain Controllers Policy Created: 7/7/2005 PM Changed: 6/18/2012 PM DS version: 1(user) 44(machine) Sysvol version: 1(user) 40(machine) Flags: 0 (user side enabled; machine side enabled) User extensions: not found Machine extensions: [] Functionality version: 2 Your issue is caused by a version mismatch between the Default Domain Controllers Policy DS and Sysvol portions, not a difference between the two DC's.

You are fully responsible for any steps you use from this blog post.

If you do not understand what you are doing, either hire someone who does, or call Microsoft for support! With Power Shell it is possible to use an existing object as a template to update or create another object.

I would recommend referring to the KB for details, but this is how you solve the problem of no SYSVOL on any DCs. I also set the "DO_NOT_REMOVE" directory attributes to Hidden and Read. Remember the junction points connect a "real" directory to a "mirrored" directory.

Step 1: Stop the FRS service on both DCs and create the SYSVOL tree on the PDC. The \SYSVOL\domain is the real (Source) directory connected to \SYSVOL\SYSVOL\corp.net, a junction point.

SYSVOL was replicated, and we had the SYSVOL share. It's something we ran into that you should be aware of. When SYSVOL was deleted from the PDC, it also deleted two custom Group Policies.

When SYSVOL was replicated after the rebuild, errors were logged in the event log complaining about these two policies.

The FRS event log was logging Event ID 13508 events but no 13509 events.

He tried forcing SYSVOL replication, using KB 290762 -- setting BURFLAGS value on the PDC to D4 and on the other DC to D2 -- but something went wrong and it wiped out the SYSVOL tree on the primary domain controller.

WARNING/DISCLAIMER: I provide this information on a FYI basis.