DFS Replication does not work for NETLOGON and SYSVOL after Windows Server 2019 joining Windows Server 2012 AD

Question

I have upgraded all Windows Server 2012 DCs from using FRS to DFS successfully with a new SYSVOL_DFSR folder shared as SYSVOL. DFS replication is fine for NETOLOGON and SYSVOL. When joining a Windows Server 2019 to this domain, domain logon function is fine, but DFS replication on NETLOGON and SYSVOL does not work. No NETLOGON and SYSVOL share is recreated. I have tried to change the SysvolReady flag to 1 in HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters and created a scripts folder in C:\Windows\SYSVOL\domain. The NETLOGON and SYSVOL share folders were created. However, DFS replication still did not work. (Note: When joining 2019 Server to 2012 AD, I specified the default SYSVOL folder instead of SYSVOL_DFSR). What should I do in order to let DFS work in 2019 DC with 2012 DCs?

Answer 1

You can follow along here.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

May I know whether there is any risk on the current 2012 AD when performing Step 3 of the provided URL (force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS))?

Answer 3

In order to proceed with the migration forest function level must set to windows server 2008 or later. So if your organization not done this yet first step is to get the forest and domain function level updated.

You can verify if the system uses the FRS using dfsrmig /getglobalstate , To do this

1) Log in to domain controller as Domain admin or Enterprise Admin
2) Launch powershell console and type dfsrmig /getglobalstate. Output explains it’s not initiated DFRS migration yet.

reference：https://www.rebeladmin.com/2015/04/step-by-step-guide-for-upgrading-sysvol-replication-to-dfsr-distributed-file-system-replication/

Tip: This answer contains the content of a third-party website. Microsoft makes no representations about the content of these websites. We provide this content only for your convenience.

Hope this information can help you
Best wishes
Vicky

Answer 4

May I know whether there is any risk on the current 2012 AD when performing Step 3 of the provided URL (force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS))?

Definitely do the non-authoritative synchronization, or the much simpler method may be to demote 2019, reboot, promo it again.

--please don't forget to Accept as answer if the reply is helpful--