Our DsGetNCChanges implementation returns objects without the correct ordering
and reports a tmp_highest_usn which is higher than what we sent to the client (destination dsa).
It's likely that we return the same highwatermark more than once within
one replication cycle.
Windows DC's sometimes interrupt a replication cycle and resume with on older
As we currently don't detect that the destination dsa uses an unexpected
highwatermark, it can happen that the some objects (or linked attributes)
are not replicated correct. The destination dsa will never get them.
Created attachment 8377 [details]
Patches for v4-0-test
Karolin, please pick this.
Pushed to autobuild-v4-0-test.
Pushed to v4-0-test.
Closing out bug report.