SYSVOL Replication Fails

DrPing used Ask the Experts™
introducing a 2016 DC into an existing 2012 domain.
Single 2012 (not r2) server and DCDIAG ran clean before the new DC was added.
The domain function level was 2012, but I didn't realize the Forest function level was 2003.
(didn't seem to matter for the promotion, but I did upgrade it afterwards to 2012 hoping that would help my sysvol replication trouble)

The new 2016 DC added normally, and transferred the FSMO roles

(This may or may not matter, before the promotion the domain function level was 2012, but I didn't realize the Forest function level was 2003.
it didn't seem to matter for the promotion, however after the new DC was added, i did upgrade the Forest to 2012 as well)

Now DCDIAG has error: C:\Users\Admin>dcdiag -q
         Warning: DsGetDcName returned information for \\Server2012.wert.local, when we were trying to reach Server2016.
         ......................... Srever2016 failed test Advertising
         Unable to connect to the NETLOGON share! (\\Server2016\ne
         [Server2016] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
         ......................... Server2016 failed test NetLogons

The new server has a SYSVOL folder, and subfolders... but everything is empty. From all that I've read... I'm suppose to force the non-authoritative synchronization of SYSVOL.

However using the tool ADSIEDIT.MSC, and following the path to make the changes (CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<the server name>,OU=Domain Controllers,DC=<domain>)

It does not have the CN=DFSR-LocalSettings on either server.
Cannot make the edits recommended.

Maybe the original 2012 server never had DFS installed? (doesn't seem to be installed now, but it's been running the domain fine for several years)
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018

can you check if NTFRS (File replication service) is running on DC?

2003 forest functional level is not an issue at this point of time...

What I mean is that you might running Sysvol with FRS instead of dfsr and Sysvol did not replicated

In that case Sysvol non authoritative restore for FRS (burgflag) would help on 2016 DC

If issue still persists, you must have some issue with sysvol on 2012 DC itself, and we need to troubleshoot further
Distinguished Expert 2018

Was everything there before you transferred FSMO roles? Did you check???  Did you transfer roles or seize them?


I saw the information for the FRS non-authoritative restore, but thought that was particular to older server OS. Wouldn't 2012 server automatically be DFRS?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!


The roles were transferred, not seized... but I didn't check the sysvol before transferring them.
Managing Consultant
The migration from FRS to DFS doesn't happen automatically. You actually have to do it.
Distinguished Expert 2018

what happened to your original issue for which you have raised question..

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial