Loading
Skip Feed
  1. Flexera Analytics (Cognos): how to relate Purchases to Contracts for spend-per-contract-term reporting?

    Hi all,

     

    I am building a management report in Flexera Analytics (Flexera One ITAM) that ranks publishers by purchase spend per calendar year. The purchase side works well: using only Publisher name and Purchase amount from the Flexera Asset Management Model (relational), filtered on Purchase date before auto aggregation, the figures match the All Purchases view exactly.

     

    The next step is to spread multi-year purchases across the contract term (contract start date to expiry date). For that I need the link between a purchase and its contract. In the product this link exists (Contract properties > Purchases tab, and Contract no. on the purchase), but I cannot find it in either Analytics package:

    • Flexera Asset Management Model (relational and dimensional): the Purchases folder has no contract field, and the Contracts folder has no purchase field. Combining both in one list yields a cross product (every purchase amount repeated per contract).

    • Flexera Data Models: same picture.

    • The FNMS Schema Reference for the Analytics models does not list a relationship either.

     

    Questions:

    1. Is there a supported way in Flexera Analytics to report purchase amounts by contract, or to get contract start and expiry dates onto a purchase row?

    2. If not, is the relationship planned for a future release of the Analytics packages, or should this be raised as an Idea?

     

    The calculation needs to stay inside the platform (scheduled Analytics report, no external spreadsheet), so I am looking for a way to get contract start and expiry dates onto the purchase rows within Flexera Analytics itself. Any pointers welcome.

     

    Thanks!

     

    Expand Post

  2. Waters NuGenesis Product Recognition

    Hello,

     

    During the review of Waters software recognition, I noticed that Flexera reports the following applications:

     

    - NuGenesis Unify

    - NuGenesis Transfer

     

    However, according to our software inventory and application catalog, we currently use:

     

    - NuGenesis 8 NMD User

     

    I would like to understand whether:

     

    - NuGenesis Unify and NuGenesis Transfer are components of NuGenesis 8 NMD User;

    - the recognition is behaving as expected;

    - an updated recognition rule exists for NuGenesis 8 NMD User.

     

    Could you please confirm the expected product mapping and advise whether any inventory files (NDI) or additional evidence would be required?

     

    Thank you.

    Expand Post

    • Hi,

      seems like "NuGenesis 8 NMD User" is the license name (metric: named user), and "NuGenesis Unify" and "NuGenesis Transfer" are components for the Application "NuGenesis 8".

      Recognized components could identify a usage of an Basic Application on top of them, but must not be licensed separately (check you contracts).

      If "NuGenesis 8 NMD User" is listed as an Application, that should be wrong or somehow that application was created locally.

       

      I checked that on my db and i can find only the following SoftwareTitleProducts:

       

      NuGenesis Lab Management System

      NuGenesis Electronic Laboratory Notebook

      NuGenesis File Capture Modules

      NuGenesis Scientific Data Management System (SDMS)

      NuGenesis SDMS Software Development Kit

      NuGenesis Transfer

      NuGenesis UNIFY

       

      The InstallerEvidence_S Table showing, that "[...]Unify" is set to be ignored.

      So in standard this Evidence could not be relevant for entitlement consumption calculation (component).

      "[...]Transfer" is listed as an Application and is not set to be ignored, so this could be relevant for license consumption (commercial).

       

      But you'll need to double check that with your contract data.

       

      Check:

      • Your "NuGenesis 8[...]" License(container) including all Application which consume license entitlements
      • if "NuGenesis Transfer Application v8.0" is the main Application, or maybe an other "NuGenesis[...]" Product like "NuGenesis Scientific Data Management System (SDMS)", and setup upgrade /downgrade rules
      • If "[...]Transfer" is commercial and "[...]Unify" the component, and the consumption is correct based on (named) user assignment
      Expand Post

  3. Certara Phoenix Product Recognition

    Hello,

     

    While reviewing the software recognition for Certara products, I noticed that Flexera currently recognizes only the main product "Phoenix".

     

    On our environment, we also use additional Phoenix components such as:

     

    - Phoenix NLME

    - WinNonlin

     

    My question is:

     

    Is it possible to recognize and report these components separately within Flexera One, or are they intentionally consolidated under the generic Phoenix application?

     

    The objective is to obtain a more detailed view of installed Certara products and improve license and application tracking.

     

    Could you please confirm the expected behavior and advise whether additional recognition rules are available?

     

    Thank you.

    Expand Post

    • Hi,

      did you try to create your own recognition construct using dedicated "Applications" for these known "Evidences", and assign them to a predefined "License"?

      If the Evidences can not be clearly separated from the already known (names are equal etc.), possibly a filescan or other inventory settings can help gathering that data.

      Regards,

      Steve

      Expand Post

  4. Flexera Beacon Upgrade (19.x to 22.4) – ManageSoftDL and RL Application Error

    Hi Team,

     

    We are using Flexera One and recently upgraded our Flexera Beacon from version 19.x to 22.4. As part of our upgrade roadmap, we are planning to upgrade the Beacon further to the latest available version.

     

    However, after upgrading from version 19.x to 22.4, we encountered an issue while testing connectivity to the ManageSoftDL and ManageSoftRL virtual directories from the Beacon server. The test fails with the following error message:

    "Server Error in '/ManageSoftDL' Application. Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0'"

     

    It is worth noting that the Parent Beacon connectivity test is successful, indicating that communication between the Beacon and its parent is working as expected. The issue appears to be specific to the ManageSoftDL/ManageSoftRL web applications.

     

    Please find the attached screenshot for reference.

     

    We would appreciate your guidance on the possible cause of this issue and the recommended steps to resolve it.

     

    Regards,

    Ravi Ladhawala

     

    Expand Post
    Question with a best answer.

    Best Answer

    Hi @mag00_75​ ,

     

    Thanks for your response.. Following discussions with the Flexera Support team, their investigation revealed that the Newtonsoft.Json version referenced in the Web.config file was not updated as part of the Beacon upgrade. The team provided the required configuration changes, which were subsequently applied. As a result, access to the ManageSoftDL and ManageSoftRL application URLs was successfully restored.

     

    Regards,

    Ravi Ladhawala

    Expand Post

    • Hi

      I think support had a hotfix for that release, reach out to them with a ticket if you cant use a newer beacon version.

  5. Flexnet 11.19.7 supports TLS query

    I have used openssl s_client -connect <iP>:27002 -tls1_2 command it shows SSL handshake has read 1413 bytes and written 284 bytes

    Verification error: self-signed certificate

     Verify return code: 18 (self-signed certificate)

     

    it shows TLS works, certificate validation doesn't?


    • JohnSorensenDK (Flexera Software)

      @ankitaibm​ 

      Is this question related to Flexera One, or are you working with one of Revenera's FlexNet products, as then you should raise the question in either of the Revenera Community forums?

       

      Thanks,

      John Sorensen

      Expand Post

  6. New in IT Visibility: Device Domain Visibility and Technopedia Subversion for Software Evidence

     

    Available with IT Visibility

     

    We're excited to share two enhancements that give you greater clarity and precision when working with device and software evidence data in IT Visibility.

     

     1. Domain column added to the Devices page

    IT Visibility now displays the domain of a device on the Devices page (Inventory > IT Visibility Devices > Devices).

    The Domain column is visible by default in the device list, and the Domain field appears on the Device Properties tab when you open a device.

     

    Why this matters: IT Visibility identifies devices using a composite key of hostname, domain, and serial number. Two devices that share the same hostname but belong to different domains are stored as distinct records. The Domain column and field help you understand why devices with identical hostnames appear as separate records.

     

    With this update, you can:

    • View the domain of each device in the device list.
    • Filter and sort the device list by domain.
    • Search for devices by domain using the global search.
    • Export device domain data in CSV format.

    For more information, see Identifying Devices Using Evidence.

     

    2. Technopedia Subversion field added to Software Evidence

    IT Visibility now shows the Technopedia Subversion field in the following locations, along with their evidence detail pages:

    • The Installer Evidence, File Evidence, and OS Evidence views on the Software Evidence page.
    • The Software Evidence - Installer, Software Evidence - File, and Software Evidence - OS tabs on the Device Detail page.

    Why this matters: The Technopedia Subversion field shows the subversion stage of a Technopedia release, for example

    RC1,GA, or Beta. This helps you distinguish between releases that share the same version string but differ in release type, such as a Release Candidate versus a General Availability build.

     

    Note: The Technopedia Subversion column is not visible by default. To show it, use the column chooser on the relevant tab.

     

    With this update, you can:

    • View the Technopedia Subversion for each evidence item on the Software Evidence page and the Device Detail page.
    • Search for evidence by Technopedia Subversion using the global search.
    • Export the Technopedia Subversion value in CSV downloads for all three evidence types.

    For more information, see Identifying Applications Using Evidence and Identifying Devices Using Evidence.

     

    Release Notes

    Expand Post

  7. Deleting SCCM connection - when does it no longer show in WebUI?

    We have a legacy SCCM server. It has been removed from the beacon and it has been disabled in Data Imports. Now we are trying to delete it. A verification pop-up is displayed with the note:

    Are you sure you wish to remove this data feed?

    Note: Until this feed is disabled or removed on the beacon, this feed will continue to be recreated.

     

    As stated, the feed has been disabled AND it has been removed from the beacon, but it still shows as inventory source, although it shows disabled. Is there a delay in it actually being removed from the WebUI list?

    Thanks -Jon

    Expand Post

  8. Problem with Flexera Agent Communication to Beacon

    Hi, good morning.

     

    We are currently experiencing a communication issue between the Flexera agents and the Beacon. Although the agents are successfully collecting inventory data from the devices, the information is not being transmitted to the platform, preventing the inventory process from being completed.

     

    The behavior observed indicates that local data collection is working as expected; however, communication with the Beacon is not being established. We have already performed several infrastructure and configuration validations without success so far.

     

    Has anyone experienced a similar issue? Is there any additional configuration required on the agents to explicitly point them to the Beacon or associate them with it?

     

    Any guidance or suggestions would be greatly appreciated.

     

    Thank you!

    Expand Post
    Question with a best answer.

    Best Answer

    Hi

    If the installation and mgssetup.ini file was not correctly setup for the installation you can basically run this command to run the policy download manually

     

    flxconfig.exe --download-server http://beaconserver.xxxx.com

     

    But highly recommended to look into the logfiles as Max mentioned. Sometimes the logs can also reside in your user profile so also check %TEMP%\Managesoft

    Expand Post
    mag00_75 by mag00_75

    1 of 3
    • Hello, good afternoon. Thank you very much for the tips, they were extremely helpful! We encountered an issue with the tenant that had been provided to us, but it has now been resolved. After the update, I ran a new test and, after reviewing the logs and manually triggering the policy download, everything worked as expected. Thank you very much for your support!

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
35 Followers
2.26K Posts
1.48K Articles
37 members are discussing this topic.
Loading
Flexera One | Flexera