Add them to the [FNMSCompliance].[ResponsibilityType]  table  😊 . ... View more

Yes, the views in the "Management View" area in the FNMS Web UI are stored in the [EcmSettings] table in the  [FNMSCompliance] database. If you truncate this table, all customized views in the FNMS Management View Index section that have been saved by any user will be lost. Basically, this works similar to when a user customizes a view by adding additional columns or by applying a filter. In the [EcmSettings] table, FNMS stores the ID of the current user ([ComplianceOperatorID] column), the view and action ([SettingKey] column) in a URL like format like (ctx://Applications/List_Grid/Installed/View/67) and the actual settings for the view in XML format ([SettingValueString] column). Unfortunately, there is no documentation specifically on the meaning of the XML data in the [SettingValueString] column in this table. ... View more

Hi Janice, For #1: Especially for SUN and Oracle Java, it is common that the 'ProductVersion' and 'FileVersion' properties for file evidence linked to an application is not consistent with the application version itself. The SQL statement below retrieves all applications where the version numbers don't match. With ARL #2590, this statement returns 440 rows. You can see the results in the Excel file attachment 'JavaFileEvidence VersionNoNotMatching.xlsx'.  For #2 & #3: If you change the WHERE condition in the SQL script to check for non-empty [FilePath] data, you'll see a lot of strange file path data including the one that you reported. This does not result in problems with application recognition as the file path is not used for this purpose. I have no idea who 'brian.t.gallagher' might be  😁 and why local Java file evidence information from his computer has been picked for the FNMS ARL :-). Basically, providing [FilePath] information with the ARL especially for Windows seems to be a waste of disk space and network bandwidth though.   SELECT st.[FullName] ,stt.[DefaultValue] As SoftwareTitleType ,stp.[ProductName] ,stv.VersionName AS Version ,ste.EditionName As Edition ,oms.DescriptionDefaultValue As OperatorManageState ,stc.DefaultValue AS [SoftwareTitleClassification] ,ge.Path AS [Category] ,st.[ReleaseDate] ,st.[HasInstalls] ,fe.FileName ,fe.FileVersion ,fe.ProductName ,fe.ProductVersion ,fe.Company ,fe.FilePath ,eer.RuleDefaultString AS EvidenceExistenceRule FROM [SoftwareTitle] st JOIN [SoftwareTitleType] stt ON st.[SoftwareTitleTypeID] = stt.[SoftwareTitleTypeID] JOIN [SoftwareTitleProduct] stp ON st.[SoftwareTitleProductID] = stp.[SoftwareTitleProductID] LEFT OUTER JOIN [SoftwareTitleVersion] stv ON st.[SoftwareTitleVersionID] = stv.[SoftwareTitleVersionID] LEFT OUTER JOIN [SoftwareTitleEdition] ste ON st.SoftwareTitleEditionID = ste.SoftwareTitleEditionID JOIN [OperatorManageState] oms ON st.[OperatorManageStateID] = oms.OperatorManageStateID JOIN [SoftwareTitleClassification] stc ON st.SoftwareTitleClassificationID = stc.SoftwareTitleClassificationID JOIN GroupEX ge ON ge.GroupExID = st.CategoryID JOIN SoftwareTitleFileEvidence stfe -- provides the [FileEvidenceID] ON stfe.SoftwareTitleID = st.SoftwareTitleID JOIN [FileEvidence] fe ON fe.FileEvidenceID = stfe.FileEvidenceID JOIN [EvidenceExistenceRule] eer on eer.EvidenceExistenceRuleID = stfe.EvidenceExistenceRuleID WHERE 1 = 1 AND (fe.Company LIKE 'Oracle%' OR fe.Company LIKE 'SUN%') AND stp.ProductName LIKE '%JAVA%' AND LEFT(stv.VersionName,1) <> LEFT(fe.FileVersion,1) ORDER BY fe.Company, st.[FullName]    ... View more

You must download the FNMS 2016 R1 SP1 version of the “Business Adapter Studio” (BAS) tool. Later versions of BAS (FNMS 2017 R1 and higher, including FNMS 2020 R1) are throwing the error that you describe when trying to insert data loaded from a Web Service into the target database. This issue has been submitted to support (Case #01235581) and has been filed as an enhancement request (JIRA "FNMS-45808 Add Support for FNMS Cloud API in Business Adapter Studio"). ... View more

Hi Rob, All native FNMS reports are stored in the [FNMSCompliance].[ComplianceSavedSearch] table. The 'Device Installation Details' report that you are interested in is executing a stored procedure named 'ReportDeviceInstallationDetail'. This stored procedure has two parameters (@ComputerId, @RowLimit). The second @RowLimit parameter (maximum number of rows to be returned in the report) is optional. To test this, for @ComputerId you need a valid 'ComplianceComputerID' value from the [ComplianceComputer] table. Let's assume that @ComputerId=5. To retrieve installation details for this computer, you only have to execute the following statement from Microsoft SQL Server Management Studio (SSMS):   EXEC ReportDeviceInstallationDetail 5   Performance of this stored procedure is lousy though. If you want to use the SQL of the stored procedure for running it on multiple computers, you should consider rewriting it and/or storing the output of the stored procedure in a caching table.   ... View more

Hi Dan, To my knowledge, if you open an "Action" in the "Discovery and Inventory Rules" part of FNMS, the following activities are kind of a cheat, and don't belong there: Microsoft Hyper-V Microsoft SQL Server The reason why I consider these activities to be a "cheat" - "misleading" actually might be a more polite way to describe it - is that if you enable any of these activities, FNMS will not do any IP port scanning, but will try to do a remote inventory on the target computer. The 'discovery' of these applications relies on the remote inventory results. The Flexera agent executed on the target system(s) remotely will report the Hyper-V or SQL Server on the target system. You can achieve the same result by enabling "Gather hardware and software inventory from all target devices" in the "General hardware and software inventory" section of this document. All prerequisites for doing a remote inventory - like having a valid account for the target system configured in the Beacon password store - apply here. For proving this, the best way is to monitor the Beacon activity when the rule is executed on the Beacon. On the "Action", you have to: Disable "Gather hardware and software inventory from all target devices". In the "Microsoft SQL Server" section, enable "Discover Microsoft SQL Server" and/or "Discover Microsoft Hyper-V" Create a rule by combining this "Action" with a valid "Target" that covers some computers running SQL Server. Preferably, these target computers should NOT have a Flexera agent installed (yet). Trigger the download of the rule to the Beacon that is responsible for scanning devices in the "Target". After the rule has been downloaded to the Beacon, you can trigger execution of the rule manually from the Beacon UI. When looking at the Beacon LOG files after following these steps, you will see that when the rule is executed, the Beacon tries to do a remote inventory (try to execute the Flexera agent remotely) on target devices. Even if you did not enable "Gather hardware and software inventory from all target devices". This is different from the real discovery of Oracle databases - where the Beacon tries to connect to the Oracle listener on the target devices using the IP ports specified in the "Action" as described by @ChrisG. ... View more

No, for defining a target in FNMS, you don't have to manage subnets. You can use one of the alternatives that can be selected when you configure a target. However, you might be confusing different ways for monitoring software usage: Collecting usage data for applications that are used interactively is done by a background task. On Windows, this task is a Windows service named "Flexera Inventory Manager security service" that is running permanently. This Windows service will track usage for applications that are used interactively only. Collecting usage data specifically for Oracle database products relies on the Oracle introspection performed by the Flexera agent - using the Oracle GLAS (LMS) SQL scripts - as you suspected. This is relevant for licensing, as Oracle rules define that certain database Options like 'Partitioning' are licensable only if they are installed AND used. Usage for Microsoft server products including Microsoft Exchange and SQL Server is based on the Flexera Agent evaluating Microsoft Client Access (CAL) connections to the server. This is a third - independent - way to collect application usage data that can be used for certain Microsoft server products only. Technically, the Flexera agent looks at LOG data on the server that track client access. This CAL tracking feature can be enabled or disabled by configuring a target in FNMS only, you cannot switch it on when installing the Flexera agent. Costs for tracking usage data in terms of additional database/disk usage is low. Keep in mind that for countries with "challenging" legal restrictions like Germany and France, you typically need approval from the 'Workers Council' before switching usage tracking on (using option #1 on the list above). ... View more

Hi Mathias, It's probably nice to "be on a roll"  😄 ? For enabling the usage tracking, you don't have to redeploy agents or reconfigure agents individually. This feature can be enabled or disabled remotely by using the FNMS 'Target' feature. Basically, you: Go to 'Discovery & Inventory > Inventory > Discovery and Inventory Rules' On the 'Targets' tab, use the 'Create a target' button for configuring a new target Give your target a name and use one of the options under "Define machines to target" for selecting target computers. Using 'Site or subnet' usually is a good choice. Under "Application usage options", select 'Allow application usage tracking on these targets' There is no need for using this target in a rule in FNMS.  As with the other options that you can configure for a target, usage tracking will be enabled on a device if: At least one target matches the device where usage tracking is allowed. No target matches the device where usage tracking is denied (Do not allow) Keep in mind that applications are tracked if they are being used interactively only. In a datacenter, you probably have servers running applications like Oracle databases or Microsoft Exchange. These server applications are used by connecting to them over the network. This sort of 'usage' will not be tracked. ... View more