A backlink can be made on a schema object on the schema master like so:
1. Create a subclass of OrganizationalUnit with dMD included in possSuperiors.
2. Create an instance of that subclass in schema partition
3. Put the DN of that instance into the "managedBy" field of some object like the Administrator user.
This creates the backlink. When the changes are replicated, the DC receiving the changes will produce the error: "schema_data_add: we are not master: reject add request". This happens because backlinks are created dynamically on the DC rather than as part of the replication. In our example, only 'managedBy' is sent, not 'managedObjects', which is the backlink list.
Not a big deal, but it would be nice to test Windows behaviour on this one and bring Samba into compliance.