Loading
Skip Feed
  1. 1 of 4
    • Hi Jannine,

       

      I agree that sometimes the "License Required" field seems incorrect, but we have seen many opportunities where an application can be paid OR free, depending on the use, the type of business, the features you use, etc ...

      As a result, there will be situations where you will need to check and maybe edit this field in SLM, after all, there is a reason why Snow made this field editable 😉

      This highlights the importance of a proper control of software installation by either policy or technical enforcement, to ensure that the IT department is aware of new software installed. Then the Software Asset Management team steps in and examine the real license requirement.

       

      Application Category is something different, it indicates roughly what the purpose of the application is. The list comes from a doc about software standards, can't remember which.

      Expand Post

  2.  

    Pre-Release notification on SAM Core - Snow Atlas: Support for importing Excel files (xlsx)

     

    Release information: You can now import asset data using Excel (.xlsx) files in addition to CSV when importing changes to your assets in SAM Core. This removes the need to convert spreadsheets before importing, letting you work with the file format you already use.

    What problem are we solving? SAM Core previously only accepted CSV files for asset imports. Customers who maintained business processes built around Excel spreadsheets had to convert their files before every import - a manual step that added friction and increased the risk of errors. Excel import was supported in the previous version of the product, making this a regression for customers who migrated to Snow Atlas.

    Summary Info

    • Release Domain: SAM on Atlas - Asset Imports
    • Release Tier: Minor Release
    • Release Availability: GA
    • Release Date: 8 June 2026

    Before Scenario

    • Asset imports only accepted CSV file format.
    • Customers with Excel-based business processes had to manually convert files to CSV before importing.
    • Workflows that previously worked with xlsx imports in the legacy product required rework after migrating to Snow Atlas.

    Negative Consequences

    • Additional manual steps required for every import cycle for customers using Excel.
    • Increased risk of data errors introduced during file conversion.
    • Business processes built on Excel imports had to be changed following migration to Snow Atlas.

    After Scenario - Key Enhancements

    • Excel Import Support: Asset imports now accept .xlsx files across all supported asset types, including Computers, Users, and Agreements.
    • No change to existing CSV imports: All existing CSV-based import workflows continue to function as before.
    • Updated UI: The import interface now clearly communicates that both CSV and Excel file formats are supported.

    Positive Business Outcomes

    • Reduced friction for SAM Managers who maintain import workflows using Excel.
    • Eliminated need for manual file conversion prior to import, reducing processing time and error risk.
    • Restored parity with legacy import behaviour, supporting a smoother transition to Snow Atlas for migrating customers.

     

    Expand Post

  3. SPerigo likes this.
    1 of 8
    • Any update on this matter? We have a client that is using SLM for more than a decade, and is relying on the report share functionality. If this is not available in Atlas, this could be a deal breaker for them.

      This feature has been requested since 2022, and SAM teams worldwide rely on reporting back to management, even in the form of custom reports that are being shared. Their worth is in the value they present to management. If you ask me, this is a vital functionality that deserves more attention from the dev team.

      Competitors already have this functionality.

      Expand Post

  4. Has anyone had success configuring Custom Connectors ?

    if you have had success, for what applications? - I have set up WDesk, Workiva & no new data is populating in SaaS Management - the advice is that this is a limitation for the Workiva application - so interested to hear of success with other applications?


    SeanMag likes this.

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

    • MercedesO (Flexera Software)

      Hi Tobias, thanks for reaching out: Please send an email to community@flexera.com with the subject "Account deletion request" and we will take care of the rest. If there's anything we could have done better to improve your experience, also let us know.

  6. How to monitor Think-Cell usage? (Powerpoint add-on)

    We are required to monitor Think-Cell usage in the business and need to remove licences from users who are no longer using it. I had generated an "Applications per user" report to show last used usage information for the think-cell application.

     

    Snow Atlas has detected some of our users as to have last used Think-Cell months ago, however we have received direct feedback that they have actually used it daily or in the previous week.

     

    As Think-Cell is a plugin used by Powerpoint, I can understand its a bit complicated for the metering to be accurate.

     

    I have also found some old community posts with this same/similar question:

     

    Hoping to see if there is any further development into the metering of Think-Cell. Also, keen to see if anyone else has found any workaround to monitor Think-Cell usage.

    Expand Post

    BiaFerrari likes this.
    1 of 4

  7. BiaFerrari likes this.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. Has anyone had success configuring Custom Connectors ?

    if you have had success, for what applications? - I have set up WDesk, Workiva & no new data is populating in SaaS Management - the advice is that this is a limitation for the Workiva application - so interested to hear of success with other applications?


    SeanMag likes this.
  2. 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?


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


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