Loading
Skip Feed
  1. Release notification on SAM Core - Snow Atlas: Add License entry point on Application detail pages

    Release information:

    You can now navigate to the Add License page directly from any Application detail page tab in SAM on Snow Atlas. When you navigate this way, the Application Name field is pre-populated automatically, making it faster to complete the license record.

    What problem are we solving?

    The release of the new Application detail pages in July 2025 removed the ability to create a license directly from the Application context. Users had to navigate away from the application they were working with, open the Add License page independently, and manually search for and select the application - adding unnecessary steps to a common workflow.

    Summary Info

    • Release Domain: SAM on Atlas - Applications
    • Release Tier: Minor Release
    • Release Availability: GA
    • Release Date: 12 May 2026

    Before Scenario

    • Users could not initiate license creation from the Application detail page.
    • Users had to navigate to the Add License page independently and search for the application manually.
    • Application context was lost during the license creation workflow.

    Negative Consequences

    • Increased steps for a common day-to-day SAM workflow.
    • Higher risk of data entry errors when manually selecting the application on the Add License page.
    • Reduced efficiency for SAM Managers and Compliance Analysts managing licensing at scale.

    After Scenario - Key Enhancements

    • Add License Entry Point: An Add License entry point is now available on all Application detail page tabs, keeping users in context throughout the workflow.
    • Pre-populated Application Name: The Application Name field on the Add License page is automatically filled based on the application navigated from, reducing manual input and improving accuracy.
    • Editable Pre-population: The pre-populated field remains editable, supporting scenarios such as versionless applications or licenses scoped across an application family.

    Positive Business Outcomes

    • Reduced friction for SAM Managers and Compliance Analysts in high-frequency licensing workflows.
    • Improved data entry accuracy through application context carried into the Add License page.
    • Faster license creation with fewer steps from discovery to record completion.

     

    Expand Post

    • So good to see this functionality returned to Sam Core - Thankyou!!

  2. 📢Question Roundup for this week[22nd May]: Snow Atlas & Database Security

    Hello All,

    If you are UK based like me, hope you are keeping cool and getting ready for the heatwave this weekend!☀️

    There were a lot of good discussions in the community this week, particularly around Snow Atlas and system visibility. I want to give a massive shout-out and thank you to active contributors @SamuelBaughan​  @liamLittlemore​  @jonas.nilsson.external@fujitsu.com​  for brilliant insights on the Windows 11 visibility thread. Kudos also to @mhambsch​  for sharing what's worked for you on our classic Oracle database configuration thread.

     

    As forums are peer driven spaces built on collective expertise, it is great to see members helping each other get more value from Flexera solutions. If you’re new or just need a refresher here is a guide on how to contribute.

    We have  just two open posts from this week that still need an answer, check them out below:

     

    Open questions

    Flexera One

    • How to detect TLS versions across IT estate using Flexera Agent [reply here]

    Snow License Manager

    •  Does Snow License Manager support application categories like freeware and commercial shareware [reply here]

     

    🔥Top Discussions & Solutions This Week

     

    Many thanks,

    Mercedes

    Expand Post

  3. SPerigo likes this.
    • Lerrie Antonio (Flexera Software)

      Hi Nicole,

       

      In Snow Atlas, reports cannot currently be shared with other users as reusable or saved report configurations. Customised reports are only visible to the user who created them, which is a current limitation of the platform.

      There is an existing idea submitted for this feature that you can vote on here:

      https://ideas.snowsoftware.com/ideas/SNOW-I-2367

      If it receives enough votes, the product team may consider reviewing and implementing it in a future update.

       

      Thanks,

      Lerrie

      Expand Post

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

  5. What is the INV_FILE_FILTER exactly

    What is that SLM SMACC Basic setting exactly about?

     

    The official doc says:

    INV_FILE_FILTER: File extension filter for data sources (only applies to Windows OS based files). Defines the type of inventory files that will be transferred to SLM by adding or removing file endings in the comma-separated list.

     

    I see in SLM that files with other extensions are also transferred from INV to SLM (*.tmp, *.dll, *.00, ...). Why are they passed on to SLM? Are the detection rules applied or not to those files with other extensions? What is the use of this filter if it applies only to Windows OS based files? How is it different from the filter <IncludeCriteria> <FileType> in the local snowagent.config?

     

    This thread shows that is does more than what it appears to do: https://community.flexera.com/s/question/0D5PL00000NvxJ90AJ/adding-00-to-the-invfilefilter-setting

    Do we still need to add the magical ".00" in this list of extensions?

    Expand Post
    Question with a best answer.

    Best Answer

    Your agent can be configured to scan for specific file extensions. It will report all those files to the Inventory server.

    But not all files will be transferred over to the SLM server during the Data Update Job, only the ones specified in the INV_FILE_FILTER setting. You would usually want to have the same file extensions in both the agent configuration and the SLM SMACC.

     

    Here is one case where maybe you would have a different list of file extensions: You use another method to report more file extensions but they do not come from your agent. For example, you develop a custom method to scan for specific DLL files on some clients to detect a specific app, but you do not want the Snow agents to scan for all DLLs (there are too many of them on each client). In this case, your agent would not list the DLL extension in its config file, but the SLM SMACC would.

     

    I hope that helps

    Expand Post

    1 of 4

  6. 📢Question Roundup for this week[8th May]: AI, Agent Schedules and Hyperthreading

    Hello All,

    Great to see peer to peer discussions starting to emerge in our forums: If any of the topics resonate, please share your thoughts to keep conversations flowing.

    Huge Shout out to @Ladhawala​ on this great topic on AI: Join the discussion

    What AI capabilities and real-world use cases are currently available in ITAM Flexera One, and has anyone successfully implemented them?

    How are you finding the new bulk deletion feature? Share your honest take with @GregMisso​ 

    If you are passing through today, we have some new questions to solve in our forums, check them out below:

     

    Open questions

    Flexera One

     

    FNMS (FlexNet Manager Suite)

    Snow License Manager

    Many thanks,

    Mercedes

    Expand Post

    SamuelBaughan likes this.

  7. 1 of 4
    • Just to add to what @Max_Schoenhuber​ has explained, my understanding is that the cutoff would be bound to the amount of metering data you keep (see the settings in your Snow Console on the SLM server).

      I can't prove it, but the figures we have seem to indicate that this is the case.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. I have an app that references the native windows file IsInet32.dll but I want to use the linux equivalent of this file libhasp_linux_x86_64.so so that I could deploy my app to linux distribution.

    I have an app that references the native windows file IsInet32.dll but I want to use the linux equivalent of this file libhasp_linux_x86_64.so so that I could deploy my app to linux distribution.

     

    I've search the net even AI chatgpt but forwarded me to this site. Is there a way to download the SDK that should contain the said file libhasp_linux_x86_64.so?


  2. We have recently migrated SLM to a new SQL server. This used to exist on the same server as SNOW Automation Platform. Now they are on different servers, SNOWAP cannot connect to SLM for the application import. can they exist on 2 separate servers?

    We have recently migrated SLM to a new SQL server. This used to exist on the same server as SNOW Automation Platform. Now they are on different servers, SNOWAP cannot connect to SLM for the application import. They are now on two different servers but the workflow for application import fails. If anyone has any advice on this that would be great


  3. How do i securely configure an on-prem OCP environment as 'connected' to enable Snow Atlas Container visibility?

    We recently upgraded to Snow Atlas one driver being the ability to enable containers visibility. Unfortunately, Snow Atlas does not support 'disconnected OCP' clusters for containers visibility. I would be glad to learn from anyone with an on-prem OCP environment that is connected to the internet securely and containers visibility is configured and working well. How do you securely configure a connected OCP environment to enable this visibility?


End of Feed
8 Chatter Feed Items
Loading
Snow Optimizer for SAP