Exclude copied user accounts from being added to security groups in a certain OU.

Question

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 copy group membership option is selected)?

Currently I use a script in the "After creating a user" business rule to remove them from those security groups. However, the removal is not reflected in the Adaxes log in the same way as the account being added to the group, which I need for audit purposes.

Answer 1

Hello Mark,

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 copy group membership option is selected)?

Unfortunately, there is no such possibility. Removing users from groups in a Business Rule triggering After crating a user is the correct approach to achieve what you need.

However, the removal is not reflected in the Adaxes log in the same way as the account being added to the group, which I need for audit purposes.

Most probably, the script performs the updates in AD directly and thus they are not reflected in Adaxes logs. Please, post your script here or send to us (support[at]adaxes.com) and we will update it to log group membership updates.

Comments

This is the (asyncronous) script I use to remove them after user creation:

$UserDN = "%distinguishedName%"

Start-Sleep -Seconds 60

#remove from all appropriate groups
$groups = Get-ADPrincipalGroupMembership -Identity $UserDN | ? {$_.distinguishedname -like "*OU=SpecificOU*"}

foreach ($group in $groups) {
    $GroupDN = $group.distinguishedName
    $Context.LogMessage("Removing from: $GroupDN", "Information")
    Remove-AdmGroupMember -Identity $GroupDN -Members $UserDN -Confirm:$false
}

---

Hello Mark,

As we mentioned in the previous post, the script performs removal from group directly in AD avoiding Adaxes pipeline. For the pipeline to be applied, you need to specify the -AdaxesService and -Server parameters when executing the Remove-AdmGroupMember cmdlet. For details, have a look at the following SDK article: http://adaxes.com/sdk/Remove-AdmGroupMember. We updated the script accordingly, find it below. In the script, you need to replace the value of the -Server parameter with the required one.

$UserDN = "%distinguishedName%"

# Get DNs of current groups the user is member of
try
{
    $groupDNs = $Context.TargetObject.GetEx("memberOf")
}
catch
{
    $Context.LogMessage("User %name% is not a member of any groups.", "Information")
    return
}

# Remove from all appropriate groups
foreach ($groupDN in $groupDNs)
{
    if (-not($groupDN -like "*OU=SpecificOU*"))
    {
        continue
    }

    $Context.LogMessage("Removing from: $groupDN", "Information")
    Remove-AdmGroupMember -Identity $GroupDN -Members $UserDN -AdaxesService localhost -Server "dc.domain.com" -Confirm:$false
}

---

That works! The log is now showing the removals as well.

Thank you very much!