Loading
Skip Feed
  1. 📢Question Roundup for this week[12th June]: Integration challenges & inventory visibility 

    Hello Everyone,

    It’s been a busy one in the forums, thank you again to everyone who joined our Microsoft 365 Community discussion on we hope you got some valuable insights.

    We also have a number of questions that could benefit from peer responses, if you’ve come across any of the below before please take a second to reply.

    Open questions

    [Flexera One]

    [FlexNet Manager Suite On-Premises]

    [App Broker]

    [Snow License Manager]

    [Snow inventory]

    Thanks so much in advance for taking a look, every reply makes a difference and helps keep the community moving forward 🙏

    Mercedes

     

    Expand Post

  2. Official release of Snow Integration Manager 26.2.0

     

    We are pleased to announce the release of Snow Integration Manager 26.2.0

     

    This release includes:

      

    • Red Hat Enterprise Virtualization connector: Added SaveRawData diagnostic capability
    • VMware vSphere connector: Added SaveRawData diagnostic capability
    • File-based discovery connector: Fixed incorrect IP address formatting issue under certain regional settings
    • BMC Helix ITSM connector: Fixed duplicate CI record creation in CMDB
    • Microsoft SCCM connector: Improved UI usability for low-resolution screens
    • Red Hat Enterprise Virtualization connector: Fixed IP address parsing for hosts and VMs
    • Red Hat OpenShift connector: Fixed inventory file creation failure after aggregation
    • Red Hat OpenShift connector: Improved handling of null/invalid datetime values during API processing
    • Nutanix Acropolis connector: Improved handling of assigned and learned IP addresses
    • HPUD connector: Fixed duplicate matching records caused by identical versionid entries

     

    Customer Impact:

     

    New Features (SaveRawData – RHEV & vSphere)

    • The addition of the SaveRawData capability enables customers to capture raw API responses locally, providing greater transparency into source data and facilitating easier validation against connector output. This enhances troubleshooting efficiency, reduces reliance on extended support cycles, and enables faster diagnosis and resolution of connector-related issues.

    File-based Discovery (IP Formatting)

    • IP address values are now processed independently of system regional settings, ensuring consistent and accurate formatting across environments and eliminating discrepancies caused by locale-specific formatting differences in discovery data imports.

    BMC Helix ITSM Connector (Duplicate CIs)

    • Improved validation logic ensures that existing configuration items are correctly updated rather than duplicated, resulting in more accurate CMDB data and improved data reliability for downstream ITSM processes.

    Microsoft SCCM Connector (UI Issue)

    • User interface adjustments ensure that configuration form buttons remain visible even on lower screen resolutions, improving usability and accessibility for users operating in constrained display environments.

    Red Hat Enterprise Virtualization Connector (IP Parsing)

    • Enhanced IP address parsing ensures that host and virtual machine IP addresses are accurately captured from API responses, improving inventory completeness, licensing accuracy, and datacenter hierarchy representation.

    Red Hat OpenShift Connector (Inventory Data Creation Failure)

    • Resolution of the internal encryption issue ensures that inventory files are successfully generated after data aggregation, enabling reliable Snowpack creation and uninterrupted downstream processing.

    Red Hat OpenShift Connector (Datetime Handling)

    • Improved handling of null and malformed datetime values increases connector stability, reducing failures during test connection and data collection and enabling more consistent OpenShift data ingestion.

    Nutanix Acropolis Connector (IP Data Completeness)

    • Support for both assigned and learned IP addresses ensures more complete and accurate inventory data collection from Nutanix environments, improving data quality and visibility.

    HPUD Connector (Duplicate Matching Records)

    • Corrected mapping logic ensures that only a single valid record is matched when processing entries with identical versionid values, eliminating duplicate matching errors and improving overall data consistency and integrity.

      

    Release information

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 26.2.0

    Release Date: 10 June 2026

    Release Availability: GA

    Release Notes: Release Notes

    Product Documentation: SIM Documentation, ITSM Documentation

    Distribution method: Installer available for downloads here

    Expand Post

    • JohnSorensenDK (Flexera Software)

      @CvetStoy​ 

      The Snow inventory agent isn't certified per build version, so all versions supporting Windows 11 would in general support build version 26200 of it. However, the recommendation would be to deploy the latest 26.x version.

       

      I also saw this other thread ... our computers are not reporting in Snow... where the recommendation was to look into the log files, and if you're still struggling and need assistance troubleshooting your issues then you may want to contact Flexera Support.

       

      Thanks,

      John Sorensen

      Expand Post

  3. SLP API Troubleshooting article feedback

    I have feedback on Snow Inventory Server support article https://community.flexera.com/s/article/Optimal-API-endpoint-configuration. In it there is a reference to values that should be present in the SnowInventory and SnowLicenseManager databases for optimal SLM API operation to occur. Following the article, I had our SQL team run these commands first, and they did not help:

     

    EXEC SnowInventory.slm.GetServerAddress;

    EXEC SnowLicenseManager.inv.UpdateServerAddress;

     

    It is unclear in the article that these 2 services are a vital step of the troubleshooting process. I had to restart them in order for the SLM API values appear:

     

    Inventory Server: Snow Inventory Server service

    License Manager Server: Snow Software Inventory Service

     

    Please update or replace this article to help Snow administrators resolve SLM API issues in the future.

    Expand Post

  4. How can I know which report was created by whom?

    Hello. SLM user here.

    Some users were creating reports and sharing them with everybody (who knows why).

    I just want to know who created the reports to contact them and unshare.

    Is there any query that can give me the report name + creator name?

    SLM on prem.

    Thank you in advance

    Expand Post
    Question with a best answer.

    Best Answer

    Good day, @Inverno​ 

     

    Hope you are doing well.

     

    Give below SQL query a try, hopefully that helps. That will give the Report Name, along with the user who created the report with their First Name, Last Name and Email.

     

    Select a.CID, a.ReportID, a.ReportName, a.Description, b.UserName, b.FirstName, b.LastName, b.Email from SnowLicenseManager.dbo.tblSystemUserReports a

    join SnowLicenseManager.dbo.tblsystemuser b on a.UserID = b.UserID

     

    Kind regards,

    Randy Teng

    Expand Post
    Randy Teng by Randy Teng (Flexera Software)

    MercedesO and liamLittlemore like this.
    1 of 8
    • Support is in general really good at resolving factual errors, but they are focusing on actual errors. If it's something that is not really a defect, then they tend to brush that aside.

      I don't know how you formulated yourself, but in general be very clear that you have an actual functional impact (in this case, it sounds like wantonly shared reports is not a big problem ... ? )

       

      Having said all that - I would encourage you to browse around in the SnowInventory and SnowLicenseManager databases. I don't mean that you should become an expert xD But you can actually do quite a lot of analysis on your own. And if you're stuck, throw out a question here in the community :)

      Expand Post

    • Randy Teng (Flexera Software)

      Hi @jyothi.venkiteela@mitie.com​ 

       

      Good day! Hope you are doing well. Below is a general advice in nature.

       

      Most common issues are the following:

      1.Wrong syntax in the snowserver.config

      2.Changes in the Database, for example new DB instance, reset password for the service account, or different account now being used than before

      If you look at your snowserver.log and if you see saying you unable to communicate to the Database, then most likely it's about the changes on your Database.

      I would suggest trying to reconfigure by following below steps by having the correct information.

      Step 1 

      Step 2 

      Make sure you enter the new changes. Take note that you won't be able to start the service if this information are wrong.

       

      Step 3 

      Otherwise, continue to work with the Support Engineer assigned to your support ticket.

       

      Kind regards,

      Randy Teng

       

      Expand Post

  5. liamLittlemore likes this.
    • Do you have the agent installed on the duplicate devices or do these come from an integration such as BMC or Vcenter?

  6. 1 of 3

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
3 Followers
4.34K Posts
9 members are discussing this topic.
Loading
Data Services & Inventory | Flexera