No - the usage period on existing applications should not be updated when an ARL update is applied. However new applications which are created when an ARL update is applied will get a default usage period of 3 months so those records will need to be changed to (in this example) 4 months after applying the ARL update. ... View more

A procedure for doing this with FlexNet Manager Suite On-premises would be: Execute SQL queries like the following against the compliance database to set the usage period for   all applications published in the reference ARL as well as locally defined applications: UPDATE SoftwareTitleEx_MT SET UsagePeriod = 4 -- Update usage period for reference ARL applications (months) UPDATE SoftwareTitle_MT SET UsagePeriod = 4 -- Update usage period for local applications (months)​ Note that the 1st query above will need to be re-executed after any ARL update if you want the 4 month period to apply to new applications added to the ARL in that update. Create a "dummy" local application and set its usage period in the UI to 4 (months). This is to workaround a problem whereby usage data is only imported from an inventory source for the last 3 months or the longest usage period for any locally defined application (whichever is longer). Note that usage data from more than 3 months ago are ignored if inventory readers are run in "disconnected" mode - that is, from a beacon (which is always the case with FlexNet Manager Suite Cloud). You can only have a usage period longer than 3 months if your inventory readers are run in "connected" mode - that is, on the batch server of a FlexNet Manager Suite On-premises installations. ... View more

One approach to configure a process to import a set of files that are found in a directory would be to write a PowerShell script that invokes MGSBI.exe for each file that is found. Use your preferred task scheduler (such as Microsoft Task Scheduler) to automate execution of the script on an appropriate schedule. I've attached an example of such a script. This script is not complete or usable as-is: it depends on a range of functions which are not defined in the script. So treat this as an example of a starting point for your own inspiration, not a complete working solution. ... View more

I don't think similar capability to tie records in IT Visibility to different parts of the organization is available yet, although something along these lines is being considered to be added in the future as it is a very useful capability in FlexNet Manager Suite. ... View more

The minimal XML content that should appear in an NDI file to be ultimately imported by FlexNet Manager Suite as installer evidence is the following: <Package Name="Name-of-the-package" Version="Version-of-the-package" Evidence="Your-evidence-type"> <Property Name="Publisher" Value="Publisher-of-the-package"/> </Package>   ... View more

@winvarma - I'm not aware of any specific activity planned in the near term related to this. You may wish to add a comment about specifically what capability you would like to see and add your vote to the following Idea to express your interest: FNMS-I-32 ... View more

First of all, be aware that gathering inventory from Oracle Database 8i can only be done by a beacon (aka "direct collection of Oracle inventory") - this old Oracle Database version doesn't provide the interfaces required for the agent to be able to gather Oracle Database inventory. With newer Oracle Database versions, using the agent to gather inventory is generally easier to do and typically gives more reliable results. In relation to the specific questions noted: See the following page for guidance on credentials required for direct collection of Oracle inventory: Credentials for Direct Collection of Oracle Inventory The Oracle OLE DB Provider (32-bit) version 10.2.0.3 or later prerequisite noted in the FlexNet Manager Suite System Requirements must be installed on the beacon in order to perform direct collection of Oracle inventory. ... View more

@Run4Fun - either approach that you've described would work just fine in terms of allowing you to track a license position. However to best make the data held in FlexNet Manager Suite model the real world, I think creating a separate license record for the Oracle Database installs covered by the embedded license is probably going to be the clearest way to approach this: this will allow you to attach appropriate contracts, purchases and documents to that license record to keep track of the actual terms of the embedded license separately from terms you have for direct (non-embedded) licenses covering regular Oracle Database installations. ... View more

@mfranz - the problem is known to affect the FlexNet Manager Suite 2019 R1 release. It is likely to affect all other current versions of the Inventory Adapter Studio too, but as far as I know that hasn't been explicitly verified. ... View more