Is done at: Show Windows operating system build number in hardware details | Ideas (aha.io) ... View more

When disabling the certificate check on your Flexera agents, the certificate on the FNMS Beacon is ignored. The HTTPS protocol provides only encryption as security on the transfer, without validating that the agent is contacting the correct inventory beacon server. More detailed information on these two options for the Flexera agent can be found in the 'Gathering FlexNet Inventory' documentation: CheckServerCertificate CheckCertificateRevocation ... View more

I know, this is actually an old thread on a slightly different issue, but as the discussion went in this direction, I am going to post this here. I just spent some time playing this through again in my test lab. I can only guess that with the new release, more people will run into this issue. Therefore let's try to structure this a bit for everyone else: End of '21, early '22, updated packages for FNMS 2021 R1 were released (cert, DB mig & installer). Reason was the certificate used for registering the CLR assembly was no longer valid. Database migration (e.g. 2020 R2 > 2021 R1) consists of multiple steps, of which some rely on the old certificate, one on the new certificate. To be exact: 16.0 > 16.1 > 16.2 > 16.3 > 16.4 > 16.5 still run with the old certificate. Only 16.5 > 17.0 need the new one. So when migrating, make sure not to replace the certificate right away. If you did so and need to restore the old cert, you can still take it from the 2020 R2 release (as 2021 R1 downloads do no longer contains the old cert). If you want to update the certificates, I guess you'll need to remove the "chain" User - Login - Certificate > see code below Then register the new Certificate, Login, User using the latest package. Be sure to do this only after you ran the early migration steps. Then re-run the migration and it should finish the last step. Use this to remove the old User, Login and Certificate: USE master; DROP USER FlexeraUser; DROP LOGIN FlexeraLogin; DROP CERTIFICATE Flexera; PS:  SET TRUSTWORTHY ON is not a solution, as mentioned above, it works around the actual security feature here. Edit: Formatting ... View more

Hi, Thanks for your answer. I am using FNMS 2021 R1.  The server became an appliance vcenter server. Where we cannot install agent anymore. But an old agent was installed before (agent version 14).  I will try to delete this  device and hope that it will come back (we added this device in vcenter rules) Regards, Yasmina ... View more

Hi Tracy,  As per this thread on-prem since 2017 r2 release there is an initial limit out of the box for 250, but can be increased if needed. https://community.flexera.com/t5/FlexNet-Manager-Forum/How-to-increase-user-licenses-for-Flexera-Analytics-Cognos/td-p/126995   ... View more

Hello,  sadly I don't have access to the sub-folder of my Beacon. I had to request the installation files separately... So I couldn't try out the .deb file. ... View more

Hi pkadam73, An upgrade (migration) to a newer release of FNMS will not be affected by any problems with SQLCMD. The SQL scripts used for migrating the FNMS databases are excecuted using a tool 'mgsDatabaseUpgrade' that is provided with the FNMS migration scripts. The 'mgsDatabaseUpgrade' tool has no dependency on SQLCMD. However - as mentioned by @Ronny_007 - for importing the Flexera libraries, you must have a recent version of SQLCMD installed on your FNMS Batch Server.   ... View more

I can't think of any reason why the license warning message would appear for one user but not another (unless the 2nd user did see the message and has dismissed it). In my experience, all users will see this message. NB. The license warning message is a different type of message from the messages in the SystemShutdown table that @erwinlindemann has mentioned. ... View more

Yes. If you are working in an on-prem FNMS environment), t he  standalone Business Adapter Studio allows  using the [FNMSCompliance] SQL Server database as the target for importing the data . When running the standalone Business Adapter Studio from a standalone Beacon, setting up the connection to the [FNMSCompliance] database will require network access to the SQL Server, and most likely a SQL Server account that has WRITE privileges to the database though. In case you are working with FNMS in the Cloud, you have to use a local staging database. Using a staging DB allows doing some cleanup and normalization on the data before uploading the data into your production system, too. ... View more

Thanks for the detailed response @erwinlindemann , that is very helpful!   Cheers  👍 ... View more

Thank you so much.....its working fine now ... View more

That is correct. For any reports built in the FNMS UI, only links to standard FNMS objects are supported. ... View more