
Heiko_Fuchs asked a question.

Heiko_Fuchs asked a question.

JensAltner asked a question.
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?

Hi Jens,
long time, no see ;)
For getting an useful Proxmox inventory i suggest using the Proxmox REST API.
With the Business Adapter Studio you'll need to get NODE and QEMU VM data, and in addition a common agent inventory for software recognition.
API:
Extract the complete list of VMs, and after that every VM data seperately.
CLICK for the API documentation.
regards,
Steve

simonclarke69 asked a question.
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 just quickly looked up both in Technopedia:
If you believe any of this is incorrect, then I would recommend that you open a support case and request content updates, and please make sure to include the relevant documentation for challenging it being correct.
Thanks,
John Sorensen

simonclarke69 asked a question.
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

There are many releases of each, e.g. for RHEL 7: 7.1 - 7.9, and according to a quick search in Technopedia RHEL 7.9 is on Extended Support from Red Hat until May 31, 2029. Not sure if that explains your findings without more details provided?
Thanks,
John Sorensen

simonclarke69 asked a question.
My 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
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.
Thank you for sharing this with the rest of the Community @simonclarke69​

flexmananshah asked a question.
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

I would recommend that you open a support case (if you haven't already) and request a content update to the SKU and related product use rights, if you believe that it's incorrect.
Please also feel free to share more details here about your findings (SKUs, redacted screen shots, etc.) if you want other opinions from the forum members.
Thanks,
John Sorensen

besica asked a question.
I can't find something in the documentation, but in the 2025R1 version is there a way we can change our SSO to use EntraID?

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.

rinke.beimin asked a question.
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.

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,
Hi @Heiko_Fuchs​ ,
the list of Operating Systems, considered as Isserver=1, is available here: https://docs.flexera.com/flexera-one/it-assets/system-menuparent/fnms-license-page/active-servers#recognizing-server-operating-systems.
cheers Oli