0 votes

I am trying to find a way to create Groups based off an OU and a list of options (check boxes) within the portal

For example:

  1. Select the Target OU to add groups to (Only select an OU)

    contoso.com / Users / Hosted Accounts

  2. Check each type of group you want to add

  • [x] Option 1
  • [ ] Option 2
  • [x] Option 3
  • [x] Option 4
  • [ ] Option 5
  • [ ] Option 6

Where the end result based on the Check box creates several Security Groups in the Target OU

OU: Hosted Accounts

  • Option 1 - Administrators
  • Option 1 - Managers
  • Option 1 - Users
  • Option 3 - Remote Administrators
  • Option 3 - Remote Developers
  • Option 4 - Readers
  • Option 4 - Writers
by (100 points)
0

Hello,

Could you, please, specify the version of Adaxes you are currently using? For information on how to check it, have a look at the following help article: https://www.adaxes.com/help/?HowDoI.ManageService.CheckAdaxesServiceVersion.html.

Also, we are not sure we understand how exactly the options are associated with the groups to be created. Could you, please, provide a live example of the desired workflow?

0

We are currently using 2017

I want to be able to select an OU. Check a box from a list of options based on thse check boxex creat one or more groups

0

Hello,

Thank you for the update. This can be done using the Modify Organizational Unit Web Interface action and a Business Rule triggering After updating a Organizational Unit. The action form will only contain Adaxes custom Boolean attributes (e.g. CustomAttributeBoolean1) that will be displayed as checkboxes. The Business Rule will trigger only if one of the custom attributes is modified and will execute a script that will create groups according to the attribute values. If this approach meets your needs, we will provide you with detailed instructions and the script.

0

Yes, please provide.

0

Hello,

Thank you for the confirmation. For us to provide you with detailed instructions and the script, please, also specify the following:

  • What types (Security or Distribution) and scopes (Universal, Global or Domain local) should the groups have? Will they be the same for all the groups?
  • Should all the groups be created right under the target OU?
  • Should the groups creation be logged in Adaxes?

Any additional details would be much appreciated.

Please log in or register to answer this question.

Related questions

0 votes
1 answer

I have 18 domains managed by Adaxes and have noticed that Admin (full access) t all objects acts normally, but for piecemeal scopes like Service Desk that scopes to individual ... role (including 16 denies) and expect it to grow as we add more domains.

asked Sep 20 by DA-symplr (40 points)
0 votes
1 answer

I had a script that would copy the values from adm-CustomAttributeTextMultiValue1 and save them into extensionAttribute15 as a comma seperated list. The script somehow got deleted and I can't seem to find the tutorial I used to create it before.

asked Jul 1 by jordan (110 points)
0 votes
1 answer

Automation of user creation based on ServiceNow ticket creation.

asked Jan 24 by tdetmer (20 points)
0 votes
1 answer

We're trying to setup a new action in our Web interface that runs on User's that are currently in an OU called 'New Starters' that is in all of our domains (An ... no results, There are no other fields we can use that are unique to accounts in those OUs

asked Feb 7, 2020 by richarddewis (260 points)
0 votes
1 answer

Hello, I'm wondering if there is something like the calculated property "%adm-RandomString%", but that also includes symbols. Is there another command that accomplishes this task, or ... 's characters? Any way I could get this done within the realm of Adaxes?

asked Jul 7 by NKB#2772 (50 points)
2,803 questions
2,535 answers
6,605 comments
62,552 users