Copy member of from another user after creating a user

Question

Hello

I am trying to set up a script to copy the 'Members Of' from specific accounts to a new user account after creating the user.

Something very similar to this: https://www.adaxes.com/tutorials_AutomatingDailyTasks_AutomaticallyChangeGroupMembershipUsingScripts.htm

But listing each group one by one (there are around 20 per department), would not work for us.

I'm looking to do this per department, which I already have business rules for. And then, a script to simply copy all of the members of groups, from 'Template_Account" to "New user".

I tried to use something like this, but with no luck:

`Import-Module Adaxes $CopyFromThisUser = "HTB-Template" $CopymembersToThisUser = "%sAMAccountName%" Get-ADUser -Identity $CopyFromThisUser -Properties memberof | Select-Object -ExpandProperty memberof | Add-ADGroupMember -Members $CopymembersToThisUser

`

The ones I have found on here, do not meet our requirements and we would rather do this using accounts used as templates rather than having one large powershell to say which groups to add to. So that the service desk can easily make changes to the accounts as required due to the ever changing nature of the business.

Is someone able to help me with this?

Answer 1

Hello,

Have a look at the following script from our repository: https://www.adaxes.com/script-repository/copy-group-memberships-from-template-based-on-property-value-s490.htm. It allows you to specify property values (in your case the property is Department) and corresponding user accounts to copy membership from. If you have issues updating the script to meet your needs, please, provide all the possible details on the changes to be made and we will help you.

Comments

Hey

I did take a look at this earlier but it wasn't quite what I was after. However I've played around with it and it will do what we need it seems in a slightly different way.

How would I go about binding a 'sub department' to adm-CustomAttributeTextMultiValue1?

At the moment I had it to write the sub department to the postal code field which we use for other things outside of Adaxes, however if it can be done by binding this in a CSV import that would be ideal.

---

Hello,

How would I go about binding a 'sub department' to adm-CustomAttributeTextMultiValue1?

You just need to specify sub departments in the multi-valued attribute for users and then run the script for them. It will get all the values from the attribute and add the user to groups according to the specified templates. If group membership should be adjusted upon user creation, you can use the script in a Business Rule triggering After creating a user. In this case, the multi-valued attribute for sub departments should be present on the creation form in Adaxes Web Interface. For information on how to manage Web Interface forms, have a look at the following tutorial: https://www.adaxes.com/tutorials_WebInterfaceCustomization_CustomizeFormsForUserCreationAndEditing.htm.

however if it can be done by binding this in a CSV import that would be ideal.

Do we understand correctly that you are currently provisioning user accounts by importing a CSV file? If that is correct, you need to add the multi-valued attribute to the file and adjust your import script accordingly if necessary. The script for group membership update should still be executed in a Business Rule triggering After creating a user as it is mentioned above. Should you have issues adjusting the workflow to meet your needs, please, send us (support[at]adaxes.com) the import script in TXT format and a sample of the CSV file and we will help you.

---

You are correct in saying that we are looking at provisioning users using a CSV file, which our HR system will export.

For this reason I was looking at a way for the HR system to provide the required information, hence why with the current test I had it to add the sub department to the 'postal code' field in AD.

Would perhaps just changing $propertyName = "adm- CustomAttributeTextMultiValue1" to look at the postal code field in AD work?

I sent an email to support also in case they had further input on the export that we currently do.

---

Hello,

Yes, changing the $propertyName variable value to postalCode and updating the mapping for sub departments and corresponding user templates to copy membership from in the $propertyToTemplateMap variable should work just fine. The Business Rule will remain the same, you will just need to change the property in the condition: