After upgrading to FlexNet Manager Suite version 2022 R2, you may notice a decrease in the number of ComplianceUser records in the database or users in the user interface. These changes occur due to improvements to the user normalization process. This article details the normalization process updates and how they may affect you.
How does user normalization work?
When importing user data from multiple sources, such as Active Directory and SaaS products like Office 365 or Salesforce, the data is merged using the email address if it pertains to the same user. The merge prevents duplicate users from occurring.
SaaS products like Office 365 and Salesforce all include the email address when importing user data, but before the FlexNet Manager Suite 2022 R2 release, Active Directory did not, resulting in users not being able to merge and duplicates occurring.
After the change to import email addresses with Active Directory in 2022 R2, user records concerning the same user merge as expected, and the duplicate user record is deleted. This results in fewer overall records in the ComplainceUser table.
Which user gets priority during the merge?
Users with no SAMAccountName and domain merge into users with a SAMAccountName and domain using the email address to match. If more than one pair exists, the one with the primary connection or greatest ComplianceConnectionID is chosen.
How does this impact my environment?
Besides an expected reduction in users or ComplianceUser records, the manager column in the license properties page may be reset to empty or null.
