Share via

DFSR Issue

Anonymous
2024-06-25T14:19:08+00:00

Site 1

AD1 2012 server DC integrated DNS holder of all roles forest/domain level 2012

AD2 2012 server DC integrated DNS

site 2

AD3 2019 server DC integrated DNS

AD4 2019 server DC integrated DNS

My goal is to remove the 2012 DCs and replace them with 2022. They need the same name and IP.(last guy had a lot of hardcoded stuff that is too much to remover and change over and hard coded some sync tools with our Azure cloud. Mind you this infra is totally on prem.

I went ahead and built out a new 2022 server for the first DC which will be AD2. demoted the old one, changed the name and IP and removed it from the domain. Shut it down.

Spun up the new 2022 server, went through the DC promo ritual, installed what i needed to install and after all is said and done, I went and had a look at the sysvol folder and its empty. Its been over 24 hours. Any tests I run on replication and on the DFS side come back with no errors.

Net share does not bring up the sysol resource as it does on the other servers.

ran dfsrmig .getyglobalstate and its at 3 where it should be. What am I missing?

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-26T08:37:54+00:00

    Hello

    Good day!

    For the last command, after you run this command and open the result file, you can see it likes below.

    I have no Netlogon share nor sysvol.

    A: You can try the solution in the link below.

    Troubleshoot missing SYSVOL and Netlogon shares for Distributed File System (DFS) Replication - Windows Server | Microsoft Learn

    Best Regards,
    Daisy Zhou

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-06-25T15:38:17+00:00

    the showrepl and replsum both came back Ok, but the last one I had this. I also noticed that viewing the netshare again, I have no Netlogon share nor sysvol.

    Win32 Error 8419(0x20e3): The DSA object could not be found.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-06-25T14:50:12+00:00

    Hello Paul D 68,

    Thank you for posting in Microsoft Community forum.

    I went ahead and built out a new 2022 server for the first DC which will be AD2. demoted the old one, changed the name and IP
    A: You had better or should change the name and IP address of the 2022 server machine before you join it to domain, after that you join the machine to domain and promote it as Domain Controller.

    I went and had a look at the sysvol folder and its empty
    A: Please check the SYSVOL and Netlogon folder are shared, and you can see them by running net share command.

    Do you mean the SYSVOL folder is empty on new Domain Controller? If so, please check whether the AD replication is OK, please run commands below on PDC.

    repadmin /showrepl >C:\rep1.txt

    repadmin /replsum >C:\rep2.txt

    repadmin /showrepl * /csv >c:\repsum.csv

    If all the results are OK, it seems AD replication is OK.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    Was this answer helpful?

    0 comments No comments