So I need an approval process before adaxes executes a custom command to create a user. Basicaly an HR group and a Privacy group have to approve. what i have is set up like this: First Approval goes out but the second one waits until the first one has been approved. I want them to go out at the same time.
Hello,
The behavior is by design. To achieve the desired, you need to have a single action and specify both groups in the approvers list:
If somone from grouP 1 approves, will it still require someone from group 2 to approve?
So I tested this out and If any user in either group approves, the action will take place. Unfortunetly I need both groups to independantly approve. So if a user in groupA approves the action doesn't happen until both approve.
The behaviour is expected. Unfortunately, it is not possible to achieve what you need with a single Send this operation for approval action. You can only use the approach from your initial request.
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.
You do not need to create a trust between AD domains to manage them with an Adaxes service. When registering an AD domain, an account with administrative permissions ... control the user access to the managed resources, the Adaxes service uses Security Roles.
We have two needs for a telephone property. Must be formatted (xxx) xxx-xxxx Must not start with (999) We already have the regexp for #1 ^([(]{1}[0-9]{3}[)]{1}[ ]{1}[ ... )$ I was wondering if there is away to also add #2 - Must not start with (999)? Thank you
I would like to change department without a script just yet if possible on multiple accounts. If I cant do this then I will entertain custom script Thanks :)
We would like to be able to export logs from the Adaxes service? Is there a way to do this either through the service or reporting?