What I miss from your task list is: Assign a Beacon to scan the IP subnets where the vCenter servers to be scanned are located In addition to a discovery rule, you need an Inventory rule that targets the vCenter servers and uses an action that has both 'Discover VMWare infrastructure' as well as 'Gather VMware infrastructure inventory' enabled On your vSphere server(s), you must have an Active Directory account configured that has (at least) read access to the data on your vCenter server The account - user name and password - that you configured on your vCener server(s) must be configured in the password store on the Beacon that is executing the inventory rule for scanning the vCenter(s). Most of this is documented in the "Collection from Virtual Environments" help page in the "Gathering FlexNet Inventory" help file. In case you still have issues with scanning VMware, it is recommended to check the log files on the Beacon and enable additional logging specifically on the VMware scanning activity if needed. ... View more

Hi Donald, During a recent lengthy support case (#01944043) related to NFS file system scanning, I learned that in addition to the documented 'nfs' file system type, there is a number of additional NFS related file system types (tmpfs,ufs,lofs,cifs) that you can use as options for the 'IncludeFileSystemType' command line parameter for the Flexera agent. As an example, on many Unix/Linux systems, the root-directory "/" is mounted as a FS from type "tmpfs".  In case the command line statement for running the Flexera agent provided by @dhoagland1 does not run successfully, can you try to modify the statement to include additional NFS file system types please, like in: ndtrack -t machine -o IncludeNetworkDrives=True -o IncludeFileSystemType=tmpfs,nfs -o IncludeDirectory="/opt/wls;/opt/tomcat"   ... View more

Hi Martin, From one Softline FNMS expert to another Softline expert  😁 ... The FNMS Business Import Tool (MGSBI) is not a good tool for deleting any data. MGSBI is designed for INSERT and UPDATE statements on the [FNMSCompliance] database. For deleting (removing) any existing allocation for users or computers on any FNMS license, you'll have to use SQL for deleting the corresponding entries on the [SoftwareLicenseAllocation_MT] table or [SoftwareLicenseAllocation] view ... ... View more

Hi Matthias & Chris, The error message that @mschwach reported obviously is related to the temporary SQL table #IncomingDiscoveredDevices not being created correctly. This temporary table should be created in the 'SyncDiscoveredDevice.xml' WRITER module by calling a stored procedure named 'CreateIncomingDiscoveredDeviceTemplate'. For testing, I would suggest running the following SQL command in SQL Server Management Studio please: select * from CreateIncomingDiscoveredDeviceTemplate() The command should return an empty table. There is a statement in 'SyncDiscoveredDevice.xml' where this procedure is used for creating an empty table named #IncomingDiscoveredDevices. If calling the stored procedure succeeds, you should check if any customization has been done to the 'SyncDiscoveredDevice.xml' WRITER file before you upgraded to FNMS 2021 R1. The error that @ChrisG noticed in line #1210 in the LOG file is a known issue for FNMS 2020 R2 (#02454249 BUG Error related to SQL MERGE). This #02454249 issue does not prevent the completion of the compliance import and it is not related to the "Invalid object name '#IncomingDiscoveredDevices'" error message. According to the Flexera support, this #02454249 issue has been addressed in FNMS 2021 R1. It is interesting that @mschwach observed this issue after upgrading FNMS to the FNMS 2021 R1 release. ... View more

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

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