I'm rebuilding my entire config bc of the event 6331. I'm now getting the error Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: An object with DN "CN=Bert de Jong,OU=Afdeling A,OU=Actief,OU=FIM-ILM,DC=FIM-ILM,DC=local" already exists in management agent "ADMA". I cant figure out what the problem is, it seems that it wants to replace the user instead of updating it ?

This is the error I get now after changing something in HR source and sync it to the fimma Microsoft.MetadirectoryServices.FunctionEvaluationException: Error encountered during evaluation of Sync Rule: 'AD user synchronisatie (inbound & outbound)'. Details: An object with DN "CN=Bert de Jong,OU=Afdeling B,OU=Actief,OU=FIM-ILM,DC=FIM-ILM,DC=local" already exists in management agent "ADMA". at Microsoft.MetadirectoryServices.FunctionLibrary.AttributeFlowMappingHandler.ExecuteOutboundTransformation(CSEntry csentry, MVEntry mventry, String strSyncRuleGuid, String xmlExpression, String workflowParameterTypes, String workflowParameterValues)

The DN must be unique in a connector space. Your provisioning logic tries to provision a new Bert de Jong, which alrady exists in the target CS. You either need to remove Bert from the target CS or join him to the metaverse object. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Oke, time for a more stupid question then, but how do I join him to the metaverse object ? I thought that would happen on auto if he can match the relationship criteria ? Just trying to understand now though, I went back to a clean install bc I had no time to loose

You can only join from a connector space to the metaverse. There is no "forward-join" - from the metaverse to the connector space. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

I think I get it. No problems anymore now in my new config so its good Thanks