I look at this answer and it for an old version. How can this be done with the current version?
Have a look at the following help article: https://www.adaxes.com/help/PropertyForDisplayNames.
Adaxes, the tool that just keep on giving! Thanks for the guidance.
When the UPN being created is the same as an existing one except for the case. For instance, the new UPN is sally.fields but there's an existing Sally.Fields. The ... but then fails to create the AD account indicating that the UPN is not unique forestwide.
Can you point me to documentation to upgrade from Adaxes 2019.2 ver 220.127.116.11230 to the current version please?
Can you clarify the answer as it's a bit confusing? Will there be new major release available this month?
we've migrated over to Application ID authentication...can this be updated to utilize this instead?
As the title says is it still a requirement?