Hello,
When I make a copy of account, all attributes are copied except the attribute 'ou'. Should I apply a specific configuration?
Thank you for your response Yoann HAMON
Hello Yoann,
There attributes that are flagged as to copy and not to copy in the Active Directory schema. The 'ou' attribute is a one that is not to copy.
Is this issue critical for you?
In our schema, this attribute is flagged as to copy.
We use this attribute to define the first level of our chart organization and it is obviously more convenient if it is copied when we copying an account
We will include the functionality to copy the 'ou' attribute together with a user account into our next version Adaxes 2012.2.
However, if you need this feature urgently, we can make a custom build.
If it possible, I'd like to. Our HelpDesk must use Adaxes in the beginning of September and it would be great if this feature was present.
OK, then we'll prepare a build by Monday.
Today we released a minor update for Adaxes 2012.1 that fixes this issue. Now, when a user account is copied via Adaxes, its 'ou' attribute is copied as well.
You can download the latest build here. Upgrade instructions.
Excellent, it is as expected !
Thanks a lot
I am trying to trigger processing outside of Active Directory when an account is created based on the source user account that was used. Does Adaxes store the source account anywhere?
When a new user account is created by copying an existing one, is it possible to prevent the new account from becoming a member of security groups in a specific OU (when the ... same way as the account being added to the group, which I need for audit purposes.
an OU is created in the Active Directory. but when I'm trying to select that in "password policy". the Adaxes is not allow for me to choose OU. only AD users and groups can be selected. is there any way to choose OU?
We are using the SeeAlso attribute to store who is responsible for specific accounts. We do not wish to use the Manager field, because the Manager/Direct Report structure is ... to, for example, extende the expiration date of an account. Is that possible?
I am unsure how to deal with this because of how Adaxes treats one identity account as two different objects, an AD and AzureAD user account, and both has different last logon values. What is a good way to combine the data?