DFSR errors After successfully promoting new server, transferring FSMO roles, and Demoting old server

Question

I installed a new Domain Controller (Server 2022) and transferred all FSMO roles, and other roles from the old server. I then Demoted the old server (2012 R2) using DCPromo etc. And did some metadata cleanup.

I now see error messages about DFSR:

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 248 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.

The old DC is long gone... and Only changes to Group Policy etc have happened on this new server anyway. Is there a way to Seize the DFSR role to this server and get rid of these messages?

All other DCDIAG comes back clean besides the Error messages for DFSR.

Answer 1

Hi JWinsor566,

Thank you for posting in the Microsoft Community Forums.

It seems there is old server that has been disconnected for more than the survival time of the logical deletion and cannot be rigorously replicated. You can delete the old server if it is no longer in use. If there is still a FSMO on the server in question, you need to transfer or seize the FSMO its, then de-domain it, then purge the data.

Transfer or seize Operation Master roles - Windows Server | Microsoft Learn

Step-By-Step: Manually Removing A Domain Controller Server [1e69-40cc-263-4759] (microsoft.com)

Clean up AD DS server metadata | Microsoft Learn

Best regards

Neuvi Jiang

============================================

If the answer is helpful, click "Accept Answer" and vote for it.

Answer 2

All FSMO roles were transferred successfully, then the old server was Demoted successfully. This is specific to DFRS as far as I can tell. The DCDIAG comes back clean besides:

Starting test: DFSREvent

     There are warning or error events within the last 24 hours after the 

     SYSVOL has been shared.  Failing SYSVOL replication problems may cause 

     Group Policy problems. 

     ......................... Server failed test DFSREvent

Is there any way to "Seize" DFRS?

Best Regards

Answer 3

Hi JWinsor566,

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 248 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.

The old DC is long gone... and Only changes to Group Policy etc have happened on this new server anyway. Is there a way to Seize the DFSR role to this server and get rid of these messages?

What I mean is to do what I said before with the old DC of this error message. Even if your old DC is no longer in use, you still need to operate on him because the DFSR system will still make a copy of it.

Best regards

Neuvi Jiang

Answer 4

The Old server has been OFF/ Decommissioned for a year. Not on the network or powered on for that matter.

Answer 5

Hi JWinsor566,

It's closed, but the DC should still be in the domain? If it is in the domain, it has to be de-domained, and if there are FSMOs on the DC, it has to be seized according to the link I gave above, and then its metadata has to be cleaned up.

Best regards

Neuvi Jiang