High CPU usage by the ndtrack.exe component of the FNMS agent

High CPU usage by the ndtrack.exe component of the FNMS agent


The ndtrack component of the agent causes high CPU usage.


When the FlexNet Inventory Agent runs the ndtrack.exe component to gather inventory, a high CPU usage is recorded. This is a feature of the agent by design and is not a defect. The ndtrack component is designed to allow the operating system to manage resources according to priority, so the Agent can take as much available CPU resources as available if nothing else is running as a higher priority. By design, the operating system will hand back CPU resources to any running applications with a higher priority.


The LowProfile setting determines the CPU priority of the FlexNet Inventory Agent on the device where it is executing.

When set to True (which is the default value if nothing is specified), the FlexNet Inventory Agent process runs with low priority. For UNIX-like systems, this sets the nice level of the process to 10. On recent Windows platforms, it uses background processing mode (PROCESS_MODE_BACKGROUND_BEGIN). On legacy Windows platforms where this is not supported (such as Windows XP and earlier), it uses a priority of idle (IDLE_PRIORITY_CLASS).

When set manually to False, the same processes run with normal priority which is the most common mode and could be competing with other processes.

Full information on the LowProfile setting is available on page 302 of the 'GatheringFlexNetInventory.pdf' file available from docs.flexera.com (also attached below).

Additional Information

To set the LowProfile to False to use less CPU utilization, you can configure it by:

A) Setting the value in the registry hive [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Tracker\CurrentVersion](Windows)

B) Adding the line 'LowProfile=True' to the /var/opt/managesoft/etc/config.ini configuration file under the section [ManageSoft\Tracker\CurrentVersion] (non-Windows)

LowProfile=VALUE [True/False]

  • Excessively large directory scans are the most common cause of high CPU usage. For example, if you are scanning the root ('/') directory across all of your Linux devices, then this could create a significant overhead, as the tracker component will recurse through all subdirectories by default.
  • If these settings need to changed, navigate to Discovery & Inventory -> Settings -> File evidence in the Web UI (see attached .PNG below to illustrate):
  • The agent executables are not multi-threaded

If none of the above solutions seems to explain your scenario, then it is recommended to ensure that your operating system (+ version) is compatible with the agent version that you are running.

You can check the System Requirements documentation -> Prerequisite Software -> FlexNet inventory agent section to verify this.

Was this article helpful? Yes No
100% helpful (1/1)
Version history
Revision #:
4 of 4
Last update:
‎Jul 07, 2020 03:21 AM
Updated by: