Had vsfs0704 as DC in server 2019 was trying to sync to old dc that was accidentally deleted.
Built a new one in Server 2022 VM50 and connected to the domain. Was able to get all objects, but never able to really sync with vsfs0704. That server was accidentally deleted.

I built another new server vm75 – when I run all the commands, it looks like it syncs successfully. However, logs say differently. For instance, I CAN create objects in VM75 and they WILL appear in VM50. However, group policy files, etc are not syncing as sysvolume is blank on VM75. I also had seized all the FSMO roles on VM50. No matter what I try, I cannot replicate truly VM50 to VM75. Error logs still show BOTH machines trying to replicate with vsfs0704. VM75 is in a constant state of 2 whereas VM50 has a state of 4.

Event logs vm50
Error 5008 The DFS Replication service failed to communicate with partner VSFS0704 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: VSFS0704
Optional data if available:
——————————————————-
event logs vm75

error 5008
The DFS Replication service failed to communicate with partner VSFS0704 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: VSFS0704.AI.COM

Optional data if available:
Partner WINS Address: VSFS0704
Partner IP Address:

The service will retry the connection periodically.

Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 2333389A-218D-48D0-95B2-98883E2B9D22
Replication Group ID: 2641C01E-BE73-44D3-A564-8D7C73AD3DB9
————————————————————-
Error 4612
————————
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner VSFS0704. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
————————-
Any ideas? I do not have domain backup at all.

IF I rebuild from scratch, and I rejoin laptops/PC’s on the domain, will it pick up the desktop settings, etc or will it show the end users a blank desktop?

Thanks!

It is days like this I wish I could solely move to Linux as I find it easier to fix issues than Windows. However, I cannot for the time being 🙁