Solved: DFS Replication error 4012

I moved a DC to a vm, demoted the old domain and promoted the new DC and dropped the old one all together. I'm getting DFSR 4012 replication errors on the New DC now. the solution below is what appears in the error. Under the replication tab in the dfs manager is "Domain System Volume" with the local domain as its proprieties.

Is this a serious problem?

Is the replication necessary without a second DC?

Will removing the "Domain System Volume" and re-adding it cause any issues with the dc or essentials experience?

==============================================================================
Error event 4012
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 74 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.

To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.

Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replication Group Name: Domain System Volume
=========================================================
dfs diag report

Summary of replicated folder status
The following table provides a high-level overview of replicated folder status on this server.

Replicated Folder Status # of Files Received DFS Replication Bandwidth Savings
SYSVOL Share Error 0 0.00%