Subject: Best Practice for Upgrading and Migrating FlexNet Manager Suite On-Premises

Hello,

We currently have FlexNet Manager Suite On-Premises version 2024 R2 running on Windows Server 2019. We are planning to both upgrade to version 2025 R2 and migrate the application to a new server running Windows Server 2025.

We would like to confirm the recommended best practice for this scenario.

Our understanding is that the safest approach would be to:

1. Install version 2024 R2 on Windows Server 2025.

2. Connect the existing database.

3. Verify that the application is functioning correctly.

4. Perform the upgrade from version 2024 R2 to version 2025 R2.

However, we would like to know whether the following approach is also supported and recommended:

1. Install version 2025 R2 directly on Windows Server 2025.

2. Connect the existing database from the version 2024 R2 environment.

3. Complete the upgrade as part of the first connection/startup.

Is this approach supported, or is it necessary to first install the existing version before upgrading? If installing version 2025 R2 directly is supported, are there any prerequisites or additional considerations we should be aware of?

Thank you in advance for your guidance.

Subject: Request updated FNMS Docker Monitor binary built with Go 1.25.7+ (CVE‑2025‑68121)

Hello Team,

Our security scanner (Prisma Compute) detected that the FNMS Docker Monitor component:

C:\Program Files (x86)\ManageSoft\Container\fnms-docker-monitor.exe

is built with Go

crypto/tls

version 1.25.3, which is vulnerable to CVE‑2025‑68121.

According to the Go project, the vulnerability is fixed only in:

• Go 1.24.13
• Go 1.25.7
• Go 1.26.0‑rc.3

Can you please provide the latest FNMS Container Monitor / Inventory Agent installer or updated

fnms-docker-monitor.exe

built with Go 1.25.7 or later, so we can apply the remediation?

Hi everyone.

Is there a way to copy use rights from one license to another?

We have a license with tons of upgrade and downgrade rights like this one:

We need to create another license with the same rights and then add some additional restrictions.

Any idea how to avoid doing it manually? Perhaps duplicate the original license and then change it's name and other properties?

Some SQL query?

Thanks in advance,

Pawel

Hi, how is it possible to disable docker monitoring from installing by default?

I tried in setup.ini:

CmdLine=/l*v "%TEMP%\FlexNet Inventory Agent.msi.log" REMOVE=docker

But that only made ALL custom installation options as disabled in GUI installation.

Also is there a complete reference somewhere for setup.ini where we would see all potential command line options?

I was just hoping to find so more solid information regarding this. I was able to find this information:

IOJ-1927932 Agent, Inventory:

Invalid inventory directory exclusions using wildcards may cause high CPU usage and ndtrack process seg faults on UNIX-like operating systems

Please don't specify wildcard within the path set to configure include or exclude directory paths e.g. */oracle/*backup/

From this article - https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/Status/Issues/UnresolvedIssues.htm

But I was hoping to be able to go back to my team with some more solid information.

We currently have 3 AIX machines that are currently AIX 7.2.5.208 TL05. The team has had ongoing issues with these machines for the past few years and high CPU usage. But we haven't had any other teams reporting the same sort of issues with AIX machines.

They have increased all different specs to do with the machines but still face the same issues. With even more CPU/virtual hardware that gets added the more resource's ndtrack just ends up using.

Is there any solid explanation I can give the team besides " using wildcards may cause high CPU usage and ndtrack process seg faults on UNIX-like operating systems"

Hello Flexera Community,

Is the below reconciliation gap is known issue? If yes - is there any workaorund to fix this

Import step "Write WMIEvidence: Populate the ManageSoft rules to imported evidence mapping and WMIEvidence table" runnig for longer then usual.

Recon logs before upgrade -

2025-01-31 22:14:34,703 [INFO ]    Writer step 'Write WMIEvidence: Populate the ManageSoft rules to imported evidence mapping and WMIEvidence table' with non-default execution path (Fallback) meets condition TestingOrFallback.

2025-01-31 22:49:39,778 [INFO ]    Matched 3247698 records to existing WMI Evidence without wildcards

2025-01-31 22:49:39,778 [INFO ]    Matched 386 records to existing WMI Evidence with wildcards

2025-01-31 22:49:39,778 [INFO ]    Added 36516 new WMI Evidence records from the source database connections.

2025-01-31 22:49:39,778 [INFO ]    Matched 36516 records to WMI Evidence that was just added

2025-01-31 22:49:39,778 [INFO ]    Successfully processed in 35 minutes, 5 seconds

Recon logs after upgrade -

2025-02-08 21:36:00,969 [INFO ]    Writer step 'Write WMIEvidence: Populate the ManageSoft rules to imported evidence mapping and WMIEvidence table' with non-default execution path (Fallback) meets condition TestingOrFallback.

2025-02-09 21:53:03,359 [INFO ]    Matched 3261896 records to existing WMI Evidence without wildcards

2025-02-09 21:53:03,359 [INFO ]    Matched 384 records to existing WMI Evidence with wildcards

2025-02-09 21:53:03,359 [INFO ]    Added 12244 new WMI Evidence records from the source database connections.

2025-02-09 21:53:03,359 [INFO ]    Matched 12244 records to WMI Evidence that was just added

2025-02-09 21:53:03,359 [INFO ]    Successfully processed in 1 day, 0 hours, 17 minutes, 1 second

what exactly is changed which is taking longer then usual (more then 24 hours) to complete this writer step.

Thanks,

Awadh