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

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

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

  4. 1 of 3

  5. Snow integration within the isolated Swift environment

    We would like to collect info (inventory ) on SNOW from all all servers within the SWIFTVAULT. The swift environment is isolated. Following our discussion with Flexera, Snow integration within the Swift environment can be achieved by deploying a new server inside the Swift zone and installing a dedicated Snow Inventory instance (collector) on it.This server will act as the central collector for all Snow agents in the vault and will be the only system allowed to communicate outside the vault. Please confirm the required installer package and any configuration specifics for a standalone Inventory Server in a restricted network zone.

    Expand Post

    • JohnSorensenDK (Flexera Software)

      @charisc​ 

      You seem to have received the requested guidance through opening a support case. Please feel free to share its resolution here if you think other forum members would benefit from it.

       

      Thanks,

      John Sorensen

      Expand Post

  6. Official release of Snow Integration Manager 26.1.0

     

    This release includes:

    • Enhanced Microsoft AD Discovery with configurable aggregation periods, global site name support, and optional discovery without credentials—giving customers more control over data scope, simpler configuration, and improved support for complex AD environments.

     

    • Optimized Microsoft Azure AD Discovery that retrieves only required activity fields—reducing unnecessary data collection, improving performance, and directly addressing customer security and data‑minimization concerns.

     

    • Extended connector compatibility and continuity, including support for BMC Helix ITSM v25.4, SQL Server 2022 & 2025 discovery via SCCM, and updated GitHub Enterprise APIs—ensuring uninterrupted integrations despite upstream API and platform changes.

     

    • Improved validation, accuracy, and reliability across connectors (Intune, Microsoft AD, Nutanix Acropolis)—helping customers avoid configuration errors and ensuring more accurate inventory and compliance data.

     

    • Platform-level updates with adoption of Calendar Versioning for clearer lifecycle and support expectations, plus updated Flexera branding in SIM—aligning SIM with the broader Flexera portfolio and roadmap.

     

    Release information

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 26.1.0

    Release Date: 31 March 2026

    Release Availability: GA

    Release Notes: Release Notes

    Product Documentation: SIM DocumentationITSM Documentation

    Distribution method: Installer available for downloads here

     

    Expand Post

    • any progress on the OLVM connector - it's only been 4 years...

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