Hi jiwaniec, I'm assuming that with 'device keycode; you are referring to a software serial number associated with a license? The software serial number is not used for matching devices with licenses for license consumption calculations in any FNMS license consumption rule. The Flexera agent - like most other Inventory agents- does not retrieve serial numbers from devices, at least not without customizations being done. Basically, storing a software serial number on a license is done for documentation purposes. So if a device consuming from a license that has software serial numbers stored falls off the network, the entitlement consumed by this device can be consumed by another device that has the same application installed. Any software serial numbers stored on the license don't have any impact. ... View more

FNMS on-prem customers would have the option to do a slight customization to the SQL code in the 'User.xml' FNMS WRITER (in the "Update user data" section in this file). Since you are working in the FNMS Cloud, your best bet probably is to file a new idea in the 'Ideas' area here in the Community. ... View more

Hi Chris, Based on the 😁 , I believe there potentially has been some irony or even a little sarcasm in the comment from @mewinger  ... ... View more

Also, only in the Cloud version, you will see a 'Log off' menu entry on your user in the FNMS UI. With the on-premises version of FNMS, you have to close your browser window :-). ... View more

Hi While I usually agree with @kclausen aka 'Captain Kirk', my understanding is that the FNMS Beacon software used for the on-premises version of FNMS and for the Cloud basically is the same thing. Assuming that you have access to the Flexera Cloud or to Flexera ONE, follow these steps for redirecting an existing on-prem FNMS Beacon to the Cloud: Manually edit the 'BeaconServicesEndpoint' setting in the Windows registry on your Beacon to point to the Flexera Cloud. For North America, use: https://app.flexera.com (standard port 443) For the EU, use: https://app.flexera.eu (standard port 443) Follow the standard process for registering a Beacon in the Cloud. This includes importing the Beacon configuration file that you downloaded from the Cloud into your Beacon. When configuring the FlexNet Beacon endpoints in the 'Parent connection', make sure the following endpoints are configured: For North America: https://us-west-2.beacons.flexeraeng.com/inventorybeacons For EU: https://eu-central-1.beacons.flexeraeng.com/inventorybeacons After completing these steps, the Beacon will be communicating with the Flexera Cloud only. ... View more

Hi Alex, There is no way to configure such a report using the report builder available from the FNMS UI, unfortunately. Assuming that you work with an on-prem version of FNMS, you can extract this information from the [FNMSCompliance] database using the following SQL: ;WITH cteInstalledApplicationCount (ComplianceComputerID, InstalledApplicationCount) AS ( SELECT ia.ComplianceComputerID , COUNT(ia.SoftwareTitleID) AS InstalledApplicationCount FROM [InstalledApplications] ia GROUP BY ia.ComplianceComputerID ) SELECT cc.ComplianceComputerID , cct.DefaultValue AS ComputerType , cc.ComputerName , ciac.InstalledApplicationCount FROM [ComplianceComputer] cc JOIN [ComplianceComputerType] cct ON cc.ComplianceComputerTypeID = cct.ComplianceComputerTypeID JOIN cteInstalledApplicationCount ciac ON ciac.ComplianceComputerID = cc.ComplianceComputerID All you need to do is expose this SQL query as a report in the FNMS UI. ... View more

Hi, In most FNMS environments, the amount of file evidence exceeds the amount of installer evidence. Application recognition in FNMS is mainly based on installer evidence though. For file evidence, there are some parameters that you may want to look into: Which source inventory system is being used? The labels in your post indicate that your inventory data are imported from ADDM and SCCM. In case you are NOT importing inventory data from a Flexera inventory database, you should look into the configuration settings and raw inventory data of your source inventory system. If you are collecting inventory data using Flexera agents installed locally and using the global FNMS inventory configuration settings, you can configure the amount of file evidence to be collected in FNMS in the 'Policy' visible in the UI in the "Discovery & Inventory > Settings" section. Folders to be scanned for file evidence can be configured independently for Windows, Unix/Linux and Mac OS. If you are collecting inventory data running Flexera agents manually, you must use command line options like 'IncludeDirectory' for collecting file evidence. If you run the Flexera agent 'ndtrack' without any such command line option, no file evidence will be collected. The second question - why the file evidence does not contain an installation path or why the file path is not exposed in the UI  - depends on the version of FNMS. With FNMS 2019 R2 or later, the raw file path is exposed in the FNMS UI. Generally, the path for file evidence will not matter for application recognition. In case the same file evidence has been detected in more than one folder, most versions of FNMS will not report the file path. The objective is to minimize the amount of data that need to be collected and processed during a compliance import. ... View more

Hi Sreerama, Contrary to Inventories, Hardware Assets in FNMS can have a parent-child relationship. You could use a simple Business Adapter for importing the information on blade enclosures as well as on devices from ADDM as assets and sub-assets. The blade enclosures will become your parent assets and would not be linked to any Inventory data, as an enclosure is not a device asset (not running any operating system). The blades contained in the blade enclosure will become sub-assets that are linked to the parent enclosure asset, and will generally be linked to an inventory. In this scenario, both Inventories as well as Assets will be imported from your ADDM data source. ... View more

Agree with Adrian. It might be easier if you could re-use the DNS alias name of the old Beacon(s) for the new replacement Beacon(s). That way, you don't have to do any changes to the Beacon configuration in FNMS, to the FNMS Policy (Beacon Names), FNMS Rules or to the FNMS subnet configuration. Some additional thoughts: When installing your replacement Beacon servers using a newer Windows OS, a new Beacon can use the same Beacon name, DNS name and same BeaconUID value as the old Beacon. The BeaconUID value is being created and initialized with a random string when the Beacon software is being installed. You can find the existing BeaconUID value in the Windows registry on the old Beacon here: HKLM / Software / WOW6432Node / ManageSoft Corp / ManageSoft / Common Update the BeaconUID value on the new Beacon to match the BeaconUID of the old Beacon after installing the Beacon software, but before configuring the parent connection. For Business Adapter XML configuration files: In case you have stored credentials with encryption, you may have to open the XML configuration file in Business Adapter Studio and save a copy where credentials are not encrypted. In case you are using HTTPS on your Beacon(s) and you are re-using DNS names, the HTTPS certificate could be transferred from the old Beacons to the new Beacons and configured in IIS, too. When updating HTTPS certificates and/or Beacon DNS names, an updated certificate (CERT file) will have to be copied to all computers running a Flexera Agent on a non-Windows OS.   ... View more

Hi Shaun, Assuming that you work this is an on-premises version of FNMS and that you have access to the [FNMSCompliance] database, run the following SELECT statement for retrieving all contracts with the users that have a specific role on the contract (before executing the SQL, replace 'ResponsibilityType.Signatory' with the correct role that you are interested in, please):   SELECT c.ContractName , cu.SAMAccountName , rt.ResourceString AS [ResponsibilityType] FROM [ComplianceResponsibility] cr JOIN [Contract] c ON c.ContractID = cr.ContractID JOIN [ResponsibilityType] rt ON rt.ResponsibilityTypeID = cr.ResponsibilityTypeID JOIN [ComplianceUser] cu ON cu.ComplianceUserID = cr.ComplianceUserID WHERE rt.ResourceString = 'ResponsibilityType.Signatory'   After you confirmed that the previous SQL retrieves all contract responsibilities that you would like to remove, you can run the following statement to delete the responsibilities: /* Deleting the responsibilities */ DELETE FROM [ComplianceResponsibility] WHERE ComplianceResponsibilityID IN ( SELECT cr.ComplianceResponsibilityID FROM [ComplianceResponsibility] cr JOIN [ResponsibilityType] rt ON rt.ResponsibilityTypeID = cr.ResponsibilityTypeID WHERE rt.ResourceString = 'ResponsibilityType.Signatory' ) As usual, before deleting any data from a production FNMS environment, creating a backup of the [FNMSCompliance] database is generally recommended 😁 . ... View more

Hi, Requirements for deploying Win32 Apps with Microsoft Intune are similar to requirements for deploying applications using Microsoft SSCM. Standard command line options for MSIEXEC can be used. However, configuration settings for the Flexera Agent should be provided using the 'mgssetup.ini' file included in the deployment package. The required components for installing the Flexera agent are contained in the ZIP file that can be downloaded from the FNMS Web UI on the 'Discover & Inventory > Settings' page. In addition to the files and folder that you listed, the 'setup.ini' file should be included into your package. In the FNMS online documentation, you find instructions on 3rd party deployment of the Flexera agent, as well as documentation how you can customize the Agent installation on Microsoft Windows. ... View more