simonclarke69 asked a question.
RHEL V7.9 ELS DATE
We still cant see the ELS date for RHEL 7 (30 Jun 28), RHEL 8 AND 9 dates are present, is this a known issue or deprecation ?
Thank you
Skip Feed
simonclarke69 asked a question.
Free Text fields into ReportsMy management would like to see the comments/free text field from either the license or application module , into a report.
Is that possible ?
It does not filter for the export function to xls either.
Thank you
Question with a best answer. Best Answer
One of our in-house gurus hunted down a solution. It is the Licenses Issues Analysis Report.
The Licenses Issues Analysis report provides details on licenses and looks for potential issues. This includes exporting the Comments field, which is free text.
MercedesO likes this.1 of 2 - MercedesO (Flexera Software)
Thank you for sharing this with the rest of the Community @simonclarke69​
rinke.beimin asked a question.
What is the recommended best practice for upgrading FlexNet Manager Suite On-Premises from version 2024 R2 to version 2025 R2 while simultaneously migrating from Windows Server 2019 to Windows Server 2025?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.
Expand Post1 of 3 Hello Chris,
Thank you for your reply. We have indeed decided to upgrade to FNMS 2026 R1.
Following your recommendation, we will first shut down the old FNMS server and prevent it from communicating with the databases.
Regarding your points 2 and 3, would it make more sense to upgrade the databases first, before installing the FNMS 2026 R1 application server software? That way, we could point the new installation directly to the already-updated databases.
Or would this not work? My concern is that if we install the application server software first, as described in step 2, the existing databases are still on the FNMS 2024 R2 schema and therefore cannot be used by the 2026 R1 application until they have been migrated.
Regarding the database migration scripts, I am also not completely clear on the exact procedure.
Is the following documentation the correct procedure to follow?
If so, should I run the migration executable against all four FNMS databases, or is there a specific order in which the databases need to be migrated? For example, if I use the following command:
mgsDatabaseUpdate.exe -i InventoryManagerMigration.xml -nsu -d FNMSInventory [-l logFile]
Will the executable prompt me for the database connection details, such as the SQL Server instance, database user, and password? Or do these details need to be provided as command-line parameters or configured elsewhere beforehand?
I would appreciate some clarification on the recommended order of operations and the database migration procedure before we proceed.
Thanks in advance for your help.
Kind regards,
Expand Post
besica asked a question.
Entra ID SSO IntegrationI can't find something in the documentation, but in the 2025R1 version is there a way we can change our SSO to use EntraID?
- ChrisG (Flexera Software)
FlexNet Manager Suite supports SAML 2.0-compliant Identity Providers, of which EntraID is one example.
The following FlexNet Manager Suite 2025 R1 documentation describes how to configure this: Single Sign-On Support with SAML.
simonclarke69 asked a question.
RHEL EOS Dates flipped ?EOS DATES FOR:
Enterprise Linux 9.0 31/05/2027
Enterprise Linux 8.10 31/05/2029
Are these the wrong way round ?
Thank you
I now believe this may be related to RHEL's initial intention to extend to Jun 2028, then amend that date to May 2029.
JensAltner asked a question.
Import ProxMox hosts via Discovery and Inventory?We've migrated FNMS to 2026 R1 and want to take inventory of a ProxMox environment. Has anyone had experience with how to do this?
flexmananshah asked a question.
WebLogic Server Enterprise Edition does not cover CoherenceThis guidance appears incorrect: WebLogic Enterprise Edition does not include a licence for Coherence; only WebLogic Suite includes Coherence Enterprise Edition.
Although Coherence binaries are installed with WebLogic, software installation does not grant
a_cutler asked a question.
Libvirt error on Linux running ndtrackI'm testing the newest version of the agent, v18.0.0, on our Linux test box and after a successful install I tried running ndtrack to force and inventory scan and it failed with an error stating that there is no directory for libvirt. I looked into it and now understand what libvirt is and I see that this has been posted about in the past, for instance here https://community.flexera.com/s/FlexNet-Manager-Forum/Libvrtd-error/td-p/147257 . However I'm still not sure how to remedy this. Sure this doesn't mean that all Unix based machines with the newest agent require the libvirt API? Or is there a way around this that I'm not seeing?
Question with a best answer. Best Answer
In the case of the other forum thread you've referred to here, the failure to locate libvirtd daemon didn't cause the inventory gathering or upload to actually fail. Is that similar to what you're seeing, or are you seeing something different from what is shown in that thread?
If you can share any error details appearing in the agent's /var/opt/managesoft/log/tracker.log file that look to be related to this than that may help get more clarity around what is going on in your system.
- ChrisG (Flexera Software)
In the case of the other forum thread you've referred to here, the failure to locate libvirtd daemon didn't cause the inventory gathering or upload to actually fail. Is that similar to what you're seeing, or are you seeing something different from what is shown in that thread?
If you can share any error details appearing in the agent's /var/opt/managesoft/log/tracker.log file that look to be related to this than that may help get more clarity around what is going on in your system.
End of Feed
8 Chatter Feed Items
Skip Feed
- WebLogic Server Enterprise Edition does not cover Coherence
This guidance appears incorrect: WebLogic Enterprise Edition does not include a licence for Coherence; only WebLogic Suite includes Coherence Enterprise Edition.
Although Coherence binaries are installed with WebLogic, software installation does not grant
- 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.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?
Expand Post - Copy use rights from one license to another? Is it possible?
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
Expand Post - Prevent docker monitoring service from installing using command line
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?
Expand Post - High CPU Usage on AIX Devices
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"
Expand Post - Reconciliation stuck in progress after FNMS upgrade to 2024 R1
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
Expand Post
End of Feed
8 Chatter Feed Items
What is strange is my ELS field is populated for RHEL8 and RHEL9 , but not RHEL7. Is it true that the process for proving the RHEL7 ELS date is not the same as 8 and 9. AI thinks so ????!