FlexNet Manager Suite On-Premises includes Last Logged On User, Calculated User, and Assigned User properties for inventories, as well as an Assigned User property for assets.

This article explains the differences between these fields, how they are populated, and how to synchronize assigned users between inventories and assets.

How the user fields are populated

Last Logged On User

The Last Logged On User is the user who was logged on when inventory was gathered through FlexNet Manager Suite, Citrix, SCCM, or another compliance data source.

The Last Logged On User may appear as None when any of the following conditions are true:

1. The target machine does not belong to a domain, such as WORKGROUP.
2. No one has previously logged in to the machine.
3. The Active Directory import has not been performed for the domain.
4. The logged-on user is included in the User blacklist in System Settings.

In Windows, the Last Logged On User value is obtained using the WMI key:

Win32_ComputerSystem.UserName

If the logged-on user runs ndtrack manually and does not have administrative privileges, this value may appear as NULL. In this case, you should also use:

[Win32_LoggedOnUser].Antecedent

These settings work only if a user is logged on when inventory is collected. If no user is logged on, which is common for servers, a Last Logged On User value is not available. If Calculated User and Last Logged On User data is not available for Windows systems and servers, first check whether a user was logged on during inventory collection.

For macOS, FlexNet inventory agent version 17 or later collects information about the currently logged-in user, including their domain. This is required for Mac software licensing when using Named User licenses.

However, macOS does not track the last logged-in user. If no one is logged in when FlexNet inventory agent runs, macOS returns system. If you want the user name to appear in inventory, carefully review your inventory collection schedules to align them with user working hours. Alternatively, use allocations of license entitlements to the user or users in question.

Relying on inventory from macOS may cause the user name record to alternate between the actual user name and system, depending on whether the user was logged in at the time of each day's inventory collection.

Calculated User

The Calculated User is the user whose account appeared most often among the last 10 Last Logged On User values.

Assigned User

The Assigned User field is not automatically populated unless you synchronize it with Calculated User or use a customization, such as a Business Adapter, to populate it.

If neither method is used, you must assign this field manually for each inventory or asset.

It is common to choose the calculated user as the assigned user, but this is not always the case. Assigned User overrides Calculated User.

The fields are populated in the following order:

1. Last Logged On User must be populated first.
2. Calculated User appears when there are at least 10 Last Logged On User values.
3. Assigned User is populated when Calculated User is present and synchronization between the two fields is enabled.

If you use a Business Adapter to populate Assigned User, the third step does not apply.

Synchronize Assigned User with Calculated User

You can either use a Business Adapter, which is considered a customization, or synchronize the Assigned User field for an asset from that of the linked inventory.

To enable synchronization:

1. Open System Settings in the Web UI.
2. Select the Inventory tab.
3. Under Change Management, locate Synchronize assigned user with calculated user and ensure that it is selected.
4. Click Save in the bottom-right corner of the page.

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.

The first inventory import after the check box is enabled sets the assigned user to the calculated user for every device. If you enable the check box and save the dialog, a warning message advises you that this will occur.

There is a known issue that can prevent 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 issue using the following SQL:

UPDATE dbo.ComplianceTenantSetting

SET SettingValue = '1'

WHERE SettingNameID = 66