how to force WID database re-seeding across AD FS farm nodes?

Hello @David Brown

In a WID-based AD FS farm, configuration replication is primary-to-secondary only. Before attempting any database “re-seeding,” I would first verify that every node agrees on which server is primary:

Get-AdfsSyncProperties

On each secondary, confirm it points to the correct primary. You can reset the synchronization relationship with:

Set-AdfsSyncProperties -Role SecondaryComputer `
  -PrimaryComputerName "ADFS01.contoso.com"

Microsoft documents this as the supported way to configure a WID farm member as secondary and identify the primary server. The secondary must also be able to reach the primary over the required synchronization connection.

You can also verify connectivity from each secondary:

Test-NetConnection ADFS01.contoso.com -Port 80

I would not manually delete/copy the WID database or modify it through SQL tools to force a reseed. If resetting the secondary relationship still produces 0x80004005, check Event Viewer → Applications and Services Logs → AD FS → Admin on both primary and secondary nodes for the underlying synchronization error.

The invalid SAML assertions are particularly important. Until synchronization is healthy, I'd temporarily remove affected secondary nodes from the load balancer so authentication is served by a known-good node.

If the WID synchronization remains corrupted, the safer recovery path is generally to remove and rejoin/rebuild the affected secondary farm node rather than manually manipulating the WID database.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.