Is there a way to change what criteria is used to cross reference data when moving an object between OU's?

Question

For context, up until now, we had a business rule in place stopping accounts from being created for users with the same name e.g. Jacob Smith and Jacob Smith.

This business rule has been removed as it was preventing creation of accounts, and the user (e.g. Jacob Smith) has now been created, however, now when trying to move the new object into the same organisational unit/business unit as the original object, this errors and explains 'The object already exists on 'treename'

I suspect it has a configuration behind what I can see and still has detection for duplicated display names?

Unsure on where to check, or how to, if possible, remove this. Any help would be most appreciated!

Thanks

Answer 1

Hello Charlie,

The behavior is expected. It comes from AD and is not related to Adaxes. It is not possible to have two accounts with the same name in the same OU. The only option is to use a business rule triggering Before moving a user. The rule should either cancel the operation if a duplicate user is found or generate a unique name for the user being moved. The following tutorial will be helpful: https://www.adaxes.com/help/ValidateModifyUserInputWithScript.