Loading
Skip Feed
  1. 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?


  2. 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

  3. 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

  4. 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!

  5. How to manage duplicate inventory entries from Azure?

    Hi,

    We have increasing number of inventory devices from AWS and Azure with duplicate entries.

     

    For previous issues with duplicates I was seeing different serial numbers so wrote a power query to identify them and imported through a business adapter to set the duplicates to ignored and into a duplicates sub-location.

     

    The current duplicates have matching names, serial numbers, VM UUID, IP and MAC address so the only differentiator is last inventory date. I've updated the business adapter to use Inventory Date and am looking to match on Serial number and last inventory date but this is not working (with no log I can find which explains why).

     

    Has anyone successfully used inventory date as a field match in business adapter studio and if so what date format is it expecting - I'm in the UK so using dd/mm/yyyy as per how the date is displayed in the UI. Is it expecting US date format or a date and time stamp and is Inventory Date actually supported as a matching property for the Computer object?

     

    If anyone has any other ideas to identify the duplicates and manage them without creating views that I then need to manually trudge through I'd be glad to hear them, or a way to stop the duplicates being created in the first place? I did find a previous fix for duplicate Azure machines when in a "Stopped (Deallocated)" state but these were producing different serial numbers so were simple to deal with.

     

    Thanks,

    Andy

    Expand Post

    • JohnSorensenDK (Flexera Software)

      @andytyson​ 

      I can see that you're working with Flexera Support and Engineering teams to get this issue resolved.

       

      Thanks,

      John Sorensen

      Expand Post

  6. Virtualisation Data Collected from vCenter, but VM Host Associations Missing in All Inventory

    Has anyone experienced an issue where virtualization data from VMware vCenter is being collected successfully in Flexera One, but the VM-to-host relationships are not being reflected in All Inventory and in License Consumption?

     

    In our environment, the vCenters are connected and virtualization data appears to be available. When we run the VMs Inventory Gaps from vCenters report, we can see the expected relationships, including:

     

    • Virtual Machine
    • Host
    • Cluster
    • vCenter

     

    However, when reviewing All Inventory and License Consumption, the virtual machines are not mapped to their respective hosts.

     

    We are trying to understand:

     

    • Have other Flexera One users encountered this behaviour?
    • Are there specific configuration settings, inventory import considerations, or reconciliation requirements that could cause VM-to-host relationships to appear in the virtualization reports but not in inventory?
    • What troubleshooting steps would you recommend to validate why the virtualization relationships are not being applied?

     

    The reason this is important is that the missing host mappings are impacting virtualization recognition and licence calculations. Virtual machines are being treated as standalone devices and consuming licences individually, rather than inheriting coverage from the licensed host. This is resulting in higher-than-expected licence consumption and potentially inaccurate compliance reporting.

     

    Any insights or recommendations from others who have experienced a similar issue would be greatly appreciated.

    Expand Post

    VanHallman likes this.
    • JohnSorensenDK (Flexera Software)

      @Mmabotse​ 

      I cannot reproduce this, and as no other forum members have confirmed they experience the same, I would recommend opening a support case and request assistance for troubleshooting the issue.

       

      Thanks,

      John Sorensen

      Expand Post

    • There are two ways Flexera One can obtain user information, including email addresses:

       

      Via the Active Directory Adapter (through the Flexera Beacon)

       The Beacon connects to on-premises Active Directory and imports user information such as usernames, email addresses, group memberships, and organisational details into Flexera One.

       

      Via the Microsoft Entra ID SaaS Connector in Flexera One SaaS Management (FOSM)

       The Entra ID connector uses Microsoft Graph APIs to retrieve user and organisational data directly from Entra ID, including user profiles, email addresses, groups, and application assignments.

      Expand Post

  7. New default start month for AWS bill connects created through the API

    Summary

    Beginning August 4, 2026, we're rolling out a change to how new AWS bill connects handle the optional 'effectiveFrom' field.

    If you create an AWS bill connect through the API and leave 'effectiveFrom' blank, 'effectiveFrom' will now be defaulted to the current month (UTC). Previously, leaving it blank imported all available historical billing data.

    Existing bill connects are not affected.

    If your integration depends on historical data, set 'effectiveFrom' when creating the connection.

     

    Does this affect me?

    You're affected if all of the following apply:

    • You create new AWS bill connects through the FinOps Onboarding API using the IAM Role or IAM User endpoints
    • Your requests don't include the 'effectiveFrom' field
    • You expect those new connections to import historical billing data

     

    You're not affected if:

    • Your bill connects already exist. Connections created before this change keep their current behavior. Those without an 'effectiveFrom' value will continue to import all available billing months. Nothing changes retroactively.
    • You already set 'effectiveFrom' in your requests. Explicit values work exactly as before.
    • You use a cloud provider other than AWS. This change applies to AWS bill connects only.
    • Updating an existing bill connect is also unchanged. This only affects what happens at creation.

     

    What to do

    1. Review any scripts or automation that create AWS bill connects.
    2. If you need historical data, add 'effectiveFrom' to your create request with the earliest month you want, in YYYY-MM format. For example: "effectiveFrom": "2024-01". Any month from 2014-01 up to the current month is accepted.
    3. Already created a connection and missing history? You can update its 'effectiveFrom' to an earlier month at any time to import the additional months.

     

    If you create bill connects in the Flexera One UI

    You'll now see an Effective From field when setting up an AWS bill connect, pre-filled with the current month.

    Adjust it before saving if you want historical data. No more guessing where ingestion will start.

     

    Why we're making this change

    An unset start month made it unclear when data ingestion would begin, and often triggered years of unintended historical import.

    Defaulting to the current month makes every new connection's start point explicit and predictable, and you stay in control by setting the value yourself.

     

     

    Expand Post

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