How to Populate the Assigned User, Calculated User and Last Logged on User Fields in FlexNet Manager Suite On-Premises
This KB article addresses the question of how to populate the fields Assigned User, Calculated User and Last Logged on User and what the difference is between them.
This article will discuss three aspects in particular in FlexNet Manager Suite On-Premises:
1. the difference between the fields Assigned User, Calculated User and Last Logged on User;
2. how to populate these fields; and lastly
3. how to synchronise the assigned users between inventories and assets.
It is important to understand that each property being populated is dependent on the other in this order:
- Last Logged on User needs to be populated first
- Calculated User will then appear if there are at least 10 Last Logged on Users
- Assigned User will be populated if the Calculated User is present and the synchronisation is enabled between the two. Note: as above, if you're using a business adapter to pull in the Assigned User, then this does not apply.
- Open System Settings in the Web UI
- Click on the Inventory tab
- Under the "Change Management" section, locate "Synchronize assigned user with calculated user" and ensure it is checked.
- Click the "Save" button in the bottom right of the page.
Now when the calculated user is updated for a device, the assigned user is also updated. Changes to the assigned user do not affect the calculated user. Note that the first inventory import after the check box is turned on sets the assigned user to the calculated user for every device. If you turn this check box on and save the dialog, a warning message will advise you that this is going to happen.
In Windows the Last Logged On user value is obtained using the WMI key of Win32_ComputerSystem.UserName. If the logged on user is running ndtrack manually and does not have administrative privileges then this may appear as NULL in which case you should also use: [Win32_LoggedOnUser].Antecedent.
These settings only work if a user is logged on when inventory is collected. If no user is logged on (common for servers) then you won't get a LastLoggedOnUser value. Therefore if Calculated and Last Logon data is not available for Windows System and Servers, you should first check if a user was logged on during inventory collection.
There is a known issue that can prevent the synchronization of calculated and assigned users - FNMS-19365: Synchronize assigned user with calculated user does not work as setting is moved to SettingName and ComplianceTenantSetting.
You can work around this using the following SQL:
UPDATE dbo.ComplianceTenantSetting SET SettingValue = '1' WHERE SettingNameID = 66