Most RecentMost ViewedMost LikesRestrictions for Unauthenticated RPC Clients: The group policy that punches your domain in the face First published on TechNet on Apr 08, 2011 Hi folks, Ned here again. Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration-Down and Dirty Style First published on TechNet on May 22, 2008 Hi, Ned here again. DFSR SYSVOL Migration FAQ: Useful trivia that may save your follicles First published on TechNet on Jan 05, 2009 Hi, Ned here again. Streamlined Migration of FRS to DFSR SYSVOL Learn three faster alternative ways to migrate from FRS to DFSR The End is Nigh (for FRS) – updated for WS2016First published on TECHNET on Jun 25, 2014 Hi folks, Ned here again.Active Directory DFSR headache We have 23 DC's, all but one of which are 2012R2. The one-off, I upgraded a couple weeks ago directly from 2012R2 to 2019. For the past year or two we've had 2 DC's that weren't doing SYSVOL replication. I thought I had fixed that before I started with the process of getting them upgraded to 2019, but now that I've done one server, it looks like I was incorrect. So here's what's driving me nuts. Using the "status" tab of the Group Policy Management MMC, things are either horribly FUBAR, or humming along perfectly, depending (apparently) on the OS of the computer I'm running the MMC from. If I run it from a Windows 10 workstation or the Server 2019 DC, things look bad. I show 15 servers with replication "in progress", of which 13 show a status under the SYSVOL column of "Inaccessible", and 2 show a "Contents" issue with a single GPO. If I run the MMC from the 2012R2 DCs or from a Win 8.1 VM I spun up on a hunch, I show all 22 DCs in perfect sync (both AD and SYSVOL) with the baseline DC. When I use a file/folder comparison tool on the contents of the SYSVOL folder for each DC, not one of them matches the contents on the PDC. Although there are no "orphaned" files or folders, the date modified doesn't match on a varying number of files and/or folders for each DC (sometimes off by years). The closest is actually the 2019 DC, which only shows mismatches on the contents of 3 GPOs. The DFSR event logs don't show any regularly occurring errors other than losing replication for a bit between DCs when one goes down for system state backup. I ran a dcdiag /a /c, and didn't see any errors in there aside from the DFS test failing due to the above-mentioned errors caused by backups, some system event log errors due to a deleted computer account, and one DC had a typo in the secondary DNS entry on its network adapter settings. There are also no errors when I run repadmin /showrepl. I've tried running both non-authoritative and authoritative replications using the instructions https://docs.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization, and neither made any difference at all. Any suggestions? SolvedWhat does DCDIAG actually… do? First published on TechNet on Mar 22, 2011 Hi folks, Ned here again. Monthly Mail Sack: I Hope Your Data Plan is Paid Up Edition First published on TechNet on Sep 14, 2012 Hi all, Ned here again with that thing we call love. The Case for Migrating SYSVOL to DFSRFirst published on TechNet on Apr 22, 2010 Hello folks, Ned here again.Intermittent Mail Sack: Must Remember to Write 2013 EditionFirst published on TechNet on Jan 07, 2013 Hi all, Jonathan here again with the latest edition of the Intermittent Mail Sack.
