Sysvol not updating shipston on stour dating

20 Sep

At this point, we double-checked to make sure the SYSVOL tree and the policies were all correct. We had already found that using KB 290762 wiped out SYSVOL on the PDC, so we didn't want to do that again.

Keep in mind this is not the only explanation for “could not be found” errors, as in, it could really be missing or something else is wrong with the OS.It seems that AD replication was working and DNS was healthy, but FRS was not.No SYSVOL or Netlogon share, no SYSVOL tree on the second domain controller.The solution was to create the SYSVOL tree, including junction points and proper ACLs.Of course, we also had to create the default domain policy and the default domain controller policy.