DFSReplication Stoped - (9226) Multiple volumes share de same volume id

Question

Hi,

I deployed 2 Domain Controllers WS2019. This servers was deployed using a Sysprep image. The problem is that every 3-5 days I see at the eventvwr on both DC the next EventID.

The DFS Replication service stopped replication on the replicated folder at local path C:\Windows\SYSVOL\domain.

Additional Information:
Error: 9226 (Multiple volumes share the same volume serial number which prevents DFSR from finding the right volume)
Additional context of the error:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 851F4D4F-297D-4EA0-9EF3-B9F679456AE0
Replication Group Name: Domain System Volume
Replication Group ID: F4669745-C8F5-475A-B32F-C0B01D0F1C34
Member ID: F562374D-95CE-4BD6-B96E-23B308E67F87

Before 7 minutes, appears an event that says "The DFS Replication service successfully initialized the replicated folder at local path C:\Windows\SYSVOL\domain.
"

I check domain controllers health using dcdiag, repadmin and run a sysvol health check from dfs console and everything seems ok.
If I get the volume ID on every Domain Controller I can see that are the same

wmic volume get serialnumber,name

Name SerialNumber
\?\Volume{af59f799-0000-0000-0000-100000000000}\ 1947396764
C:\ 2618530139

C:\Users\administrador>dir C:
Volume in drive C has no label.
Volume Serial Number is 9C13-995B

I checked the sysvol folder and the policies folder contains the same number of folders on every DC.

Considering the health checks are correct, it seems like we can skip this error, but I'd like to know if anyone has been able to fix this issue or if they have finally skipped it.

The solution seems to be to change the volume IDs but I don't know what effect this would have at the sysvol level.

Thanks everyone for your help.

Best regards

Answer 1

Hi,

There are no errors in the dcdiag and the repadmin command and everything works well except received the event 9226 event every 3-5 days, right?

Any possibility that the backup operation caused a pause for the sysvol replicaiton?

Did you check the backup schedule on all the DCs?

Best Regards,