This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Group Memberships not being added in Active Directory ( v 7.0 sp1)

We are importing users from HR system and creating a new Person record. Once created  we assign birthright group  membership using business roles.  Identity Manager show the user have  the groups but when I check in Active directory user and computers the user only have Domain Admin Users.

 We have Groups Membership assigned based in  the IT Data for Department and those groups are being projected correctly in AD.  Looks like the issue is only for Groups Membership for business roles.

This functionality was working perfectly and stop working without major changes in our environment. The only change we recall before we notice the issue was this https://documents.software.dell.com/identity-manager/7.0.1/one-identity-manager-connector-user-guide/setting-up-synchronization-with-the-one-identity-manager-connector/configuring-memberships-provisioning this was applied due Identity manager was removing users from groups.

All the users have the Groups Can be Inherit flag set.

I also created a new business role  for testing and for that role worked fine propagating groups membership to AD, but after couple days this new business role stop working like the other business role.

Parents
  • The DPRMemberShipAction table should be empty after all the jobs are correctly processed. When there are still entries in the table this is an indication that something went wrong. These entries should be carefully handled. First thing to do is to check the jobs why are failing, if there are no jobs that are failing one is most likely running still with the system 7.0.1.
    My suggestion is to run the statement posted in this thread to generate the jobs again. Then analyze what happens to these jobs. There will be one job per each unique ADSGroup in the DPRMemberShipAction.ObjectKeyBase.
Reply
  • The DPRMemberShipAction table should be empty after all the jobs are correctly processed. When there are still entries in the table this is an indication that something went wrong. These entries should be carefully handled. First thing to do is to check the jobs why are failing, if there are no jobs that are failing one is most likely running still with the system 7.0.1.
    My suggestion is to run the statement posted in this thread to generate the jobs again. Then analyze what happens to these jobs. There will be one job per each unique ADSGroup in the DPRMemberShipAction.ObjectKeyBase.
Children
No Data