SYSVOL Replication Issues Windows Server 2019 Eval

AidenTheBotLol 21 Reputation points
2021-03-01T04:09:50.4+00:00

Hi

I have not been able to find someone with this exact issue however I have three Windows Server 2019 Evaluation Editions running for testing and educational purposes. I created this active directory on Windows Server 2019 and I had group policies set to auto config for Windows Hello For Business. I am looking at the local group policy folder on my PC which is joined to the AD and it has not synced my AD polices.

I have each servers DNS pointing at each other and 127.0.0.1 as the third DNS option in each server.

I go to run the command "dfrs /setglobalstate 1" and it will return with
Unable to create DFSR Migration log file.
Unable to create DFSR Migration log file. Error 5 Current DFSR global state: 'Eliminated' New DFSR global state: 'Prepared'
Invalid state change requested.

I think this is because Windows Server 2019 does not need to migrate but every guide that I have read uses this to sync between their servers or maybe I am reading false sources.

Any help is appreciated,

Windows for business Windows Client for IT Pros Directory services Active Directory
Windows for business Windows Server User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-03-02T00:07:38.19+00:00

    Hi,
    If the first DCs in your environment was 2019 server, the FRS won't be used .
    In your situation , i would check the gpresult firstly with the command :gpresult /h report.html.
    If possible , you can show a screenshot of that.
    And i would also recommend you check if the replication is working in the domain with command :
    Dcdiag /v >c:\dcdiag1.log
    Repadmin /showrepl >C:\repl.txt
    Best Regards,

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-03-01T13:35:06.38+00:00

    That's correct. Server 2019 OOB uses DFSR, Server 2016 is the last operating system where FRS was an option (from directory upgrade) for active directory replication technology. Server 2003 was the last operating system to use FRS OOB when creating a new domain.

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


  2. Anonymous
    2021-03-01T16:53:38.377+00:00

    Might check the event logs for clues, other things to try are a non-authoritative synchronization, or try demote, reboot, promo again.
    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

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

    0 comments No comments

  3. Anonymous
    2021-03-02T00:57:41.983+00:00

    I'd check the DFS Replication service is running on all members and that ports required are flowing between sites.
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts
    https://www.microsoft.com/en-us/download/details.aspx?id=24009

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

    0 comments No comments

  4. Anonymous
    2021-03-04T04:03:52.983+00:00

    Hi,

    Since there are 1726 error and 1722 error, i would also suggest you check if DFS Replication service is running on all members and the firewall configuration .
    Following link for your reference:

    Active Directory replication error 1722: The RPC server is unavailable
    https://social.technet.microsoft.com/Forums/WINDOWS/en-US/d27bd902-034e-4230-9516-0ede42308193/event-5014-dfsr-error1726?forum=winserverfiles

    I would delete the logs due to security reason.

    Best Regards,

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.