Sysvol not updating scotty mccreery and gabi dugal dating
I can't believe Microsoft hasn't emphasized this more.
This is a clear case where having advance notification would have better prepared customers. This is also the specific vulnerability that Microsoft has stated it will NOT fix for Windows Server 2003, which reaches end of life on July 14, 2015.
Another good test is to run the propagation test, then run the propagation report, which will show if data is actually being replicated.
Both of the propagation options are located as part of the Create Diagnostic Report action.
In this case, you must format the new disk, recreate the partitions as they were before the crash, reinstall Windows 2000 Server on the primary partition, restore whatever data files you had on the computer, and then restore your distributed services, including the entire Active Directory.
Because you use the Backup tool to restore the distributed services (including Active Directory), the restore operation is nonauthoritative.
The update only provides the ability to harden Group Policy, not the actual protection against the vulnerability.One of the best ways to check the health of the SYSVOL replication using DFSR is to install the Distributed File System management tools on a machine. For a machine, they're found under Features, Remote Server Administration Tools, Role Administration Tools, File Services Tools, DFS Management Tools.After installation, launch the DFS Management tool, which will show the Domain System Volume group that contains the SYSVOL Share replicated folder (see screen shot below).This occurs when a DFSR JET datavase is not shut down cleanly and Auto Recovery is disabled.To resolve this issue, back up the files in the affected replicated folders, and then use the Resume Replication WMI method to resume replication.
Microsoft KB article 3000483 gives guidance on extra steps required to fully protect the environment against the vulnerability.