Loading

IT Asset Management

Skip Feed
  1. IT Asset Management (ITAM) – February 2026 release - Now Available

     

    We are pleased to announce that the February 2026 release of Flexera One ITAM is available for customers in the EU and APAC regions. North American customers will receive access later this week. The first releases of 2026 introduce new features and enhancements, many of which are based on ideas from our ideation portal and direct feedback from customers.

     

    Enhanced Oracle WebLogic recognition

    This feature addresses previous gaps where WebLogic Server installations were not always identified by the Oracle FMW Recognition and now includes advanced detection capabilities.

    • Expanded detection rules ensure WebLogic Server configurations are identified, even when files are located outside standard locations.
    • Improved differentiation between active/configured WebLogic domains and backup or unused copies, providing more accurate visibility.
    • Enhanced evidence gathering from Oracle Fusion Middleware audit data, leveraging both configuration files and running process information for comprehensive recognition.

    These updates deliver more reliable and precise WebLogic Server detection across a wide range of environments, supporting greater accuracy in inventory and reporting. 

     

    Enhanced Oracle Consumption Summary by Partitioning Rule report

    The Oracle Consumption Summary by Partitioning Rule report has been enhanced with a new Points (non vCenter) column, delivering improved clarity and transparency for Oracle licensing analysis. This addition clearly separates and highlights consumption for Oracle installations running outside of vCenter environments, which were previously grouped with all cluster-level calculations. By making the non-vCenter portion explicit, the report enables more accurate and actionable insight into Oracle licensing, supporting better compliance and reporting decisions.

     

    Enhanced reporting logic for IBM PVU consumption on Nutanix VMs

    This release introduces a significant improvement to IBM PVU and VPC license reporting for virtual machines running on Nutanix AHV. By establishing precise VM-to-host relationships, the system enables reliable detection and classification of Nutanix AHV VMs, offering more accurate IBM PVU license consumption calculations and preventing previously overstated usage. This enhancement streamlines compliance tracking and strengthens overall reporting integrity for IBM licensing in Nutanix environments.

     

    Change: Container Installs Excluded from Unlicensed Installation Count

    As part of this release, we are introducing an update on how container-based installations are reported. Container installations are now excluded from the Unlicensed Installation count, providing customers with more accurate and reliable visibility into licensable installations. The reporting for container installs columns remain unchanged, ensuring clarity and consistency. This enhancement streamlines license tracking and reduces confusion.

     

    In addition to recent improvements, here are several key highlights introduced in the January update:

    Superior Oracle Database Management: License consumption for stand-by Oracle databases

    This enhancement resolves a persistent issue where SAM tools struggled to reliably detect and report Active-Passive (stand-by) Oracle database relationships due to the absence of a direct indicator. By introducing intelligent pairing and recognition of these nodes, Flexera One ITAM now ensures stand-by databases - such as those using DataGuard - are accurately accounted for, closing a critical gap in license management and compliance.

    With intelligent pairing, ITAM delivers consistent and accurate reporting of Oracle Options and Management Packs across all nodes, eliminating false exceptions and under-calculated consumption. 

    This improvement builds on a popular idea that has now been successfully implemented, further enhancing the solution in response to user feedback. Organizations gain clearer, actionable insights into Oracle license usage. Licensing for Options and Management Packs is automatically aligned between primary and stand-by nodes, ensuring compliance and full coverage. This enhances accuracy and helps customers make informed decisions.

     

    Flexera One ITAM APIs: New System Health and Tasks Endpoints

    Two new API endpoints have been added for Flexera One ITAM to enhance data access and monitoring capabilities, providing improved visibility into system health and task execution. These endpoints empower IT Asset Management customers with greater control by enabling automated checks on system health and task status. This reduces manual effort, boosts operational efficiency, and supports proactive monitoring for smoother IT Asset Management operations.

     

    Service Accounts supported by Flexera One ITAM API

    Responding directly to strong customer demand Flexera One ITAM API now fully supports service accounts. This key enhancement enables secure, automated, and scalable authentication to ITAM APIs using non-human, role-based identities rather than traditional user credentials.

     

    Inventorying Azure Uniform VMSS instances

    Flexera One ITAM now supports inventorying both Uniform and Flexible VMSS instances, ensuring comprehensive coverage of Azure VMSS deployments. Uniform instances are automatically included and displayed alongside Flexible ones, with no changes to the user interface.

     

    Tanium adapter now supports software usage tracking

    The Tanium adapter for IT Asset Management has been enhanced to include software usage tracking. Customers can now access application usage metrics - such as Last Used Date - directly within Inventory Device Properties, enabling improved license optimization and compliance reporting. This update streamlines visibility into software utilization and supports more informed decision-making.

     

    New optional fields added to the Oracle Instances view

    The Oracle Instances view now includes additional optional fields such as Corporate Unit, Cost Center, Environment, Location, and Licensable. These additions provide greater visibility and enable more detailed tracking of Oracle database instances across an organization. Notably, this enhancement was implemented in response to valuable user feedback received through the ideation process, demonstrating our commitment to continuously improve the solution based on customer input.

      

    Additional Detail

    Full details can be found in the Feature by Release announcement for February here and for the January here.

    Expand Post

  2. 📢Community questions from this week: Can you help?

    Happy Friday Everyone 👋

    Hope you have had a good week!

    We have a few questions that haven’t had an answer yet. If you've dealt with any of these scenarios in your own environment or maybe you’re a product pro who enjoys solving tricky problems: We’d love your input either way.

    WIFM (What’s in it for you?): Bragging rights and community karma?💁‍♀️

    Note: Some of these questions span multiple products, I'm posting here to reach our most active experts.

    As always thanks for helping out on our Community!

    Questions

    1.  Does Snow License Manager integrate with Splunk?
    2.   How to handle duplicate users in ITAM and SAAS manager?
    3. Where to download the latest Snow Agent?

     

     

    Expand Post

  3. Flexera Beacon Configuration Workflow Known Issue and Upcoming Change for ITAM Cloud Customers

    In versions 23.1 and 23.2 of the Flexera Beacons, you will notice that the ‘Download Configuration’ button under ‘Download and Import Configuration file’ (screenshot below) does not redirect you to a Flexera URL properly. This is currently a known issue due to inter-release dependencies but has an easy workaround with an existing alternative method (described below with link to documentation).

    Beacon Download Config_EditWe will be addressing this issue in version 23.3 with a change to simplify the configuration workflow. The ‘Download Configuration’ button will be removed completely to avoid having two different methods of configuring and simplify the process. The streamlined single method to configure the beacon after the change will be as follows. Since it's an existing method, we advise customers to use the same workflow for 23.1 and 23.2 beacons till the 23.3 beacon becomes available at the end of March 2025 and the ‘Download Configuration’ button no longer exists.

    1. Use the ‘Configure a Beacon’ (ITAM) option in the Flexera One web UI on the beacons page
    2. On that page, enter the details to configure a beacon, including pasting the Beacon UID from the beacon server, which is now made visible with a copy button
    3. Complete the configuration process and download the configuration from that page
    4. Import that configuration file into the beacon server using the ‘Import Configuration’ button as shown in the screenshot above. 

    As mentioned earlier, this is an existing method which has been documented in the following page: Creating and Registering an IT Asset Management Inventory Beacon

    The 23.3 change to the beacon, the removal of the 'Download configuration' button, will be applicable to both ITAM and ITV going forward and will be in line with ongoing efforts to unify the beacon processes for both products.

    Expand Post

    PaulReit likes this.

  4. New Features Added to IT Asset Management in January 2025

     

    Flexera One IT Asset Management January 2025 update includes the following new features and updates. 

    Note: For detailed information on these new features and updates, see the What's New in Flexera One / January 2025.

    New Features

     

    Ability to specify the cluster name in the Flexera Kubernetes Agent

    As Kubernetes does not have a native naming mechanism, the agent uses a variety of strategies to discover an appropriate name for the cluster; however, these strategies are not consistently reliable. This parameter allows you to directly assign a meaningful name to Kubernetes clusters. Note that this name is a display property, and the cluster is identified internally by a unique ID value.

     

    Support for Oracle Cloud Infrastructure (OCI) discovery by Flexera inventory agents

    Previously, IT Asset Management supported the three major cloud service providers (CSPs)—Azure, AWS, and GCP. If the FlexNet Inventory Agent is installed on a virtual system hosted with one of these CSPs. Now, OCI is also detected by the FlexNet inventory agent to identify VM’s running in the OCI public cloud. this information will be automatically fed into IT Asset Management.

    Important: This feature requires version 82 or later of InventorySettings.xml and version 16.0.1 or later of the FlexNet Inventory Agent.

     

    Addition of cluster information in inventory views and VM counts in Report Builder

    In this release, the inventory views and Report Builder have been enhanced to include cluster information and VM counts:

    • A new Cluster Name has been added to all the inventory views (such as Active Inventory, Ignored Inventory, Cloud Service Provider Inventory, and more) where the host name information is available. This column allows users to easily identify the cluster to which each host and VM belongs.
    • The Report Builder now displays the number of VMs per host and per cluster. These fields help users to automate and improve the process of license allocation based on VM density.

     

    FlexNet Beacon Now collects VMware vSAN inventory and recognized automatically

    Flexera FlexNet Beacon has been extended to collect VMware vSAN software information (a software-defined storage solution that is integrated directly into the ESXi hypervisor) and recognized as VMware inventory. You can find it as an application inventory record on the VMware Inventory page, along with all the relevant properties collected about how it is licensed, such as CapacityKeys assignedEvaluation, and more.

    Note: To collect the necessary vSAN information, FlexNet Beacon or ESXQuery tool version 23.1.0 or later (released with IT Asset Management version 2024 R2.1) is required.

     

    Improvements to the IT Asset Management license page

    The IT Asset Management License page displays the details of your IT Asset Management license. The Licensed products section on this page has been improved to provide clearer information and offer additional data about containers.

    • The numbers of licensed devices are now categorized into Client licenses and Server licenses. Each category includes number of licensed devices, active devices, and available licenses.
    • A new count Avg. active containers (90 days) is provided showing the average number of active containers over the past 90 days, together with the number of server licenses consumed by the active containers. Every 10 containers consume one server license. You can also view a chart displaying the daily active container counts over the past 90 days.

     

    Changes from Previous Releases

     

    Changes to supported compatibility with other products

    The following operating system versions have been added to the list of supported operating systems on FlexNet inventory agent:

    • Fedora Linux 41
    • Ubuntu 24.10
    • Windows Server 2025

    The following product versions have been added to the compatibility list of IT Asset Management with other products:

    • BMC Discovery (previously ADDM) 24.3
    • Citrix Virtual Apps server (previously XenApp server) 7.2407
    • Citrix Virtual Desktops (previously Citrix XenDesktop) 7.2407
    • EdgeSight for Citrix Virtual Apps (previously XenApp EdgeSight) 7.2407
    • IBM License Metric Tool (ILMT) or HCL BigFix Inventory on IBM DB2 9.2.37
    • IBM License Metric Tool (ILMT) or HCL BigFix Inventory on Microsoft SQL Server 9.2.37
    • OpenText Universal Discovery 24.4HCL BigFix Inventory 9.2.33 on Microsoft SQL Server

     

    We love to hear about your experiences, so let us know how things go with these updates by posting a comment here or in the Flexera One forum  Of course, the friendly Flexera Support team is also always standing by to take your call.

    Thanks for being a partner of Flexera on this journey.

    Expand Post

  5. Is it possible to automatically merge assets in the "All Assets" view?

    Hello, we have a business adapter fetching assets from our ITSM tool and stores them into the "All Assets" view in FNMS. Sometimes we have multiple records of assets with the same name but with different other variables such as serial number. The most recent one imported has the status of installed while all the others have the status of disposed. We have an issue where sometimes assets that are disposed are linked to an inventory device causing that device to show op on the "Ingored Inventory" view. We want the most recent asset and the one with the status of installed to be linked to its device.

     

    Now, I was wondering if we can solve this by somehow merging assets that have the same name, or maybe deleting the ones that are disposed so that only the newest one that has the status of installed is linked to its device and thus shows up in the "All Inventory" view rather then the "Ignored Inventory" view.

     

    Is this possible?

    Expand Post

    1 of 4
    • Yes, unique serial number for each Asset is the way to go. Ensure the system of record (CMDB) keeps Serial Numbers unique and has an accurate lifecycle status

  6. How does FNMS decide the location for an asset?

    Hello,

     

    We have an ITSM tool with assets that contain locations. We also have a business adapter that imports those assets from the ITSM tool into the "All Assets" page in FNMS. This business adapter runs every night at 20:00. Every night at 02:00 we run a reconcile. We notice that every time the reconcile runs, certain assets are getting their location changed. And during the evening when the business adapter runs, the assets get the location from the ITSM tool again. So the location of the assets are basically changing every day/night.

     

    Now I am wondering, where does FNMS get the location from? How does FNMS determine what location belongs to the asset?

     

     

     

    Expand Post

    • Your approach of importing assets from an ITSM data source like a CMDB is the recommended 'best practice'.

      However, there are FNMS system settings that can have an impact on the 'location' property of assets:

      1. 'Synchronize enterprise groups in device and asset properties' and 'Synchronize enterprise groups in asset and sub-assets properties': This means that the group properties - including location' - are syncronized between assets and inventories/sub assets. This means that if the location of the inventory linked to an asset changes, the location of the asset will change as well.
      2. 'Synchronize device location with site subnets': This will automatically set the location of inventories based on their IP address, which will impact the location of assets if the previous setting is activated.
      3. 'Synchronize enterprise groups in user and device properties': When you change the enterprise group allocations for a user, the same changes are made automatically to any devices assigned to that user.

      All syncronisations that impact asset group settings are immediate.

      Do you have any customization in your Compliance Import (reconcile) or any other process (business import) that might changes the location property of inventories or users? 

      Expand Post

  7. Flexera One ITAM & FlexNet Manager Suite Azure Integration Adapter Improvement

     

    We appreciate your ongoing feedback and collaboration. We recognize that managing the lifecycle of Microsoft Azure inventoried instances/VMs can be challenging, especially since the Azure management API does not explicitly provide the status of terminated or deleted instances.

    To address this, the integration between Flexera One ITAM, FlexNet Manager Suite, and Microsoft Azure has been enhanced to automatically manage Azure cloud instances/VMs that are not active anymore. This improvement reduces the time to value by automatically removing Azure instances that were inventoried but are not reported by the Azure Management API for the subscription accounts that are reported by the Azure adapter integration, as those instances have either been terminated or deleted.

     

    The Flexera One ITAM and FlexNet Manager Suite integration with Microsoft Azure Cloud includes two key components that maximize value:

    1. Flexera One ITAM Adapter: Provides Visibility into Current Azure Instances/VMs

    • Offers visibility into the current state of Azure instances/VMs running within Azure subscription accounts managed by the Flexera Azure adapter (Adapter granted permission to read).
    • Provides visibility into the current status of instances/VMs, which is essential for automating the lifecycle management of Azure instances/VMs.
    • Also provides insight into instances/VMs utilizing the Azure Hybrid Benefit.

    2. Flexera Inventory Agent: Inventories Customer-Managed Azure Instances/VMs

    • The Flexera Inventory Agent identifies instances hosted in Azure subscriptions and captures subscription and resource IDs.

    With this enhancement, the lifecycle management of Azure inventoried instances/VMs, tracked by the Flexera Inventory Agent, has been extended. Instances/VMs inventoried by the Flexera Inventory Agent but not reported by the Azure Adapter (for subscriptions managed by the Azure Adapter) will now be automatically removed, as they no longer exist.

    This extension improves time to value and ensures that the license position for any licensed products running on those inventoried instances is current. Instances that were reported by the inventory agent but no longer exist (according to the Azure Adapter integration) will now be accurately reflected.

     

    Recommendations

    To maximize value, Flexera recommends configuring the Flexera One ITAM and FlexNet Manager Suite Azure adapter integration to grant read access to Azure instances/VMs across all Azure subscriptions. This ensures that inventoried instances/VMs identified by the Flexera Inventory Agent, running within the Azure subscriptions recognized by the Flexera Azure Adapter, can be automatically removed when they no longer exist.

    Expand Post

    mfranz and PaulReit like this.
    • Hi, this is great news. Is there any documentation available on how to configure the Azure adapter to grant read access to Azure instances/VMs across all Azure subscriptions please? How would one know if this is already enabled or is this a feature that has just been released? I can see we have inventoried VMs that have not reported inventory for quite sometime and upon checking, these VMs no longer appear in Azure.

       

      Thank you

      Expand Post

End of Feed
7 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
7 Posts

Related Topics

    Loading
    IT Asset Management | Flexera