Hi Abhilash,
The reason why you are getting more users from the MGSBI Active Directory adapter compared to the standard Active Director (AD) interface most likely is the 'User Blacklist' used for filtering users in the standard AD interface.
You can see the list of black-listed user names in the FNMS Web UI under "(cogs) > System Settings > Users". This list contains account names available on any Windows computer, like 'Administrator' and 'Guest'. The list also contains generic accounts using the percent sign ('%') as a wildcard. You don't want these standard accounts to be counted as real users.
In case you want to check the list of AD users imported by your Business Adapter for Windows accounts to be filtered, you can run the following SQL statement on the staging table where you store users:
SELECT
[ComplianceUserID]
,[UserName]
,[SAMAccountName]
FROM [ComplianceUser] cu
LEFT JOIN [ComplianceDomain] cd ON cd.ComplianceDomainID = cu.ComplianceDomainID
WHERE EXISTS
(
SELECT 'x'
FROM [UserNameBlacklist] unb
WHERE cu.SAMAccountName LIKE unb.UserName
OR (cd.FlatName IS NOT NULL
AND (cd.FlatName + '\' + cu.SAMAccountName LIKE unb.UserName))
)
This statement assumes that you did import the users into tables named [ComplianceUser] and [ComplianceDomain] built like the original tables in the [FNMSCompliance] database, and that you have the black-listed users stored in a column [UserName] in a table named [UserNameBlacklist].
A quick word of warning: Be careful when replacing the FNMS standard Active Director (AD) interface by a Business Importer. The import process (compliance reader) relies on the standard [FNMSInventory].[ADUser] table being populated by the Active Director (AD) interface. Any users not found in the standard user table will be deleted from the users visible in the FNMS Web UI (stored in the [FNMSCompliance].[ComplianceUser] table) when running a compliance import.
Customizing the SQL code used in the compliance import (READERs and WRITERs) might be an option when working in an FNMS on-premises environment. You don't have that option when working in the Cloud.
The best practice approach for populating user data in FNMS would be:
- Use the standard Active Director (AD) interface for importing users from AD. This interface will import the "Full name"", Account name" and "Domain name" user properties only.
- Use a Business Adapter for augmenting the user information imported from AD with additional user properties, like "First Name", "Last Name" and "Email".
