We have a requirement where we will have to move an account from one OU to a different OU in AD(depending on the condition if it is a deleted user), which we have accomplished through Move an Account capability of AD Connector. However on collection, the new OU details are not getting updated to the user because he is a deleted user.
So we created a separate Collector which will specifically collect from the new OU, and we gave it Create user=Yes in the Unification. So it now creates a dummy user with same User ID and has the new OU details. But the previous original user's OU Details also change to the new OU Details for some reason and it also changes all the other attributes of the original user to null.
Is there any workaround for this problem? The intended requirement is even if the user is moved from one table to another table both these should be considered a single entity with the exception of the OU change details.