connection failure to domain after migrating to new domain controller

Question

when I turn off the old domain controller i should be replacing it with the new domain, the new domain upon opening users and computers or domains and trusts it shows "naming information cannot be located because the specified domain either does not exist"
The FSMO roles are all on the new domain, how can I fully migrate/replace from old to new, as I want to shut the old domain controller and make the new domain controller take over with the same IP
here are the files
for the following commands
Dcdiag /v /c /d /e (run on PDC emulator)
repadmin /showrepl (run on any domain controller)
ipconfig /all (run on EVERY domain controller)
https://rosenfieldhealth-my.sharepoint.com/:f:/p/hassan_khaled/Euufo_Rdv0dMtTa3jHNKOJYBx3uqObvd0qZXwzPXietfPg?e=6eIV4C

Answer 1

The DFS Replication service stopped replication on the folder with the following local path: E:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 538 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

I don't know if there were other domain controllers that are now gone? This is problematic because it tombstoned a long time ago. Usually, tombstoned domain controllers must be deleted and rebuilt.

Maybe you have backups that can be restored.

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Answer 2

without losing any of data

We have no idea. The sysvol data may have already been lost from 538 days ago. May need to look for backups with which you could restore from, then confirm health on restored domain is 100% before beginning the upgrade process again.

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Answer 3

That's the problem the domain controller above is not really functional because it is tombstoned. and the new one you stood up cannot complete the promotion process because of this. You could try doing an an authoritative sync on the old one, then check health once again, and if it comes up free and clear of errors (dcdiag, system and dfs replication event logs) then you could try demote, reboot, promo the new one again.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization#how-to-perform-an-authoritative-synchronization-of-dfsr-replicated-sysvol-replication-like-d4-for-frs