Loading
Skip Feed
  1. Does anyone experience problems with SLM 26.3.0.
    SLM updated on Friday 04/09/2026. So plenty of time for the update to do it things.

    My problems -

    Applications menu and sub menu took long time to load for some and took forever for others. For example "Search Applications" took forever, i.e. nothing show up for more than 1 hour.

     

    Same with Computers menu and sub menu.

    Cloud - Office 365 same.


    Sascha likes this.
    • I think you meanwhile got a solution for your problem.

      I only can say, that I installed 26.3 already in test, and did not experience that performance issues.

      But there is an error in compliance calculation.

  2. How do you manage user based licenses and assignments for users, who have more than one userID

    Meanwhile a lot of application license metrics are based on users.

    In our environment we have many users, that work with several userID's. And in our environment that are valid userid's.

    Unfortunately in Snow License Manager it is not possible to group several UserID's to one person, assign the license to that person and then all license requirements for the different userID's will be covered.

    I am aware, that there are many ideas in Snow Ideas Board to cover that requirement, I also created an idea several years ago and voted for others.

    Unfortunately it seems Snow is not able to provide a solution for this.

     

    Does anybody have implemented a workaround for that ?

    I would be really interested in new ideas.

    Expand Post

    Sascha and Tom Lineen like this.

    • Snow updates SRS rules on daily basis, normally in the evening

      But you need a licensekey for SRS and enable software recognition updates in SUS

      In SUS you also can see, when last SRS update was done.

      image

  3. ANNOUNCEMENT: "Files per computer" report Reimagined, Complete, Performant, and Trusted

     

    We are introducing two major enhancements to the Files per Computer report:

    Performance and reliability improvements

    1. These have been significantly improved through enhancements to data processing and data loading mechanisms.
    2. As a result, report data is loaded and displayed much faster, overall processing performance is improved, and additional mechanisms have been introduced to provide better visibility in case data is not processed as expected.

     

    Control over Linux and Unix raw software data inclusion

    1. You can now manage the inclusion of Linux/Unix data in the report via a new setting in the UI (SAM Core settings → Asset management → Files per computer report)

     

    When enabled, Linux and Unix raw software data is included in the report. Because this data can significantly increase report volume, we recommend enabling it only when necessary, as it may impact report processing time and overall performance.

     

    After enabling the setting, the data becomes visible once:

    1. The relevant computers report new inventory data, and
    2. The overnight data maintenance process completes.

     

    If the setting is disabled, the data is removed from the report after the next overnight data maintenance process.

     

    Example

    • Inventory reported: June 10
    • Overnight processing completes: June 11 (early morning)
    • Data visible in report: June 11

    If the setting is later disabled on June 12, the Linux/Unix data will no longer appear in the report after the overnight processing completes on June 13.

     

    For more information, please check the following link docs.flexera or feel free to contact me (aleksandar.chubrinoski@flexera.com).

     

    Kind regards,

    Aleksandar Chubrinoski.

    Expand Post

  4. 🌟 What’s New: Report Export Service & SharePoint Integration 

    We’ve introduced several improvements to make exporting data from Snow Atlas faster, more reliable, and easier to integrate into your workflows. 

     

    🚀 New Report Export Service 

    A modernized export engine now powers all report downloads, delivering: 

    • More stable exports for large datasets 
    • Asynchronous processing for improved performance 
    • Clearer status updates and notifications 

    This new service is the foundation for future enhancements in scheduled exports and additional export destinations. 

     

    📤 Export Directly to SharePoint 

    You can now send report exports straight to a SharePoint document library. This enables: 

    • Automated distribution via Microsoft 365 workflows 
    • Centralized storage for reporting outputs 
    • Reduced manual steps for teams using SharePoint daily 
    • Reports delivered in their original file format in SharePoint 

     

    ⚠️ Export Size Limitation 

    To ensure consistent performance, exports currently support up to 1,000,000 rows. We’ll continue to evaluate this threshold as usage grows.

     

    🧪 Quality You Can Trust 

    This release has been validated through: 

    • Automated testing of code and product from the smallest granular functionality to the end‑to‑end use cases 
    • Testing performance of reports both in terms of reliability and speed to export up to the 1M‑row limit 
    • Security and compliance checks 
    • Real‑world scenario testing, including SharePoint connectivity and failure‑mode handling
    • Early Access program with a subset of customers, and addressing the feedback

     

    📄 Relevant product documentation update 

     

     

    Expand Post

    Scott Waugh and D.Wahlqvist like this.

  5. Certification of Snow for ServiceNow ITSM Connectors – Australia Release

     

    We are excited to announce that the Snow for ServiceNow CMDB and Catalog connectors have been successfully certified for the latest ServiceNow Australia release.

    Both applications are now available for download on the ServiceNow App Store and are fully compatible with the Australia release, enabling a seamless and fully supported integration experience.

     

    What this means for you

    • Continued alignment with the latest ServiceNow platform updates
    • Ongoing compatibility and support for your integration use cases
    • Confidence in using certified, production-ready applications

     

    Important note

    For customers and partners already using these integration connectors, no action is required. This certification does not introduce any changes or require updates to:

    • Existing Snow for ServiceNow CMDB and Catalog applications
    • Associated connectors configured in Snow Integration Manager. However, it is recommended to be on the latest version of Snow Integration Manager to benefit from the latest updates and patches

     

    Expand Post

    Scott Waugh and Hameed Iqbal like this.

  6. Pre-release notification: Edit of multiple agreements (standard fields) in SAM on Snow Atlas

     

    Release summary:

    We are excited to introduce Edit of multiple agreements (standard fields) in SAM on Snow Atlas. This enhancement enables you to update multiple agreements in a single operation, directly from the Agreements list, eliminating repetitive manual updates and reducing reliance on APIs or technical support.

     

    ·       Release date: June 18, 2026

    ·       Product domain: SAM on Snow Atlas

    ·       Release availability: Early Access (EA)

     

    What is included?

    • Multi-editing capability: Select and update up to 1,000 agreements of the same type in one action.
    • Standard field updates: Modify key agreement attributes across multiple records simultaneously.
    • Smart field behavior: Fields with identical values are pre-filled, while differing values remain empty for selective updates.
    • In-app experience: Perform all updates directly from the Agreements list without APIs, imports or external tools.
    • Permission consistency: Uses existing edit permissions with no additional configuration required.

     

    Why it matters?

    • Removes repetitive work: Eliminates the need to update agreements one by one.
    • Saves significant time: Multi-editing that previously took time can now be completed in seconds.
    • Improves data consistency: Apply changes across multiple agreements simultaneously, reducing the risk of errors.
    • Reduces technical dependency: Enables users to perform multi-editing without relying on APIs, imports, or technical teams.
    • Frees up time for strategic work: Allows teams to focus on higher-value activities such as compliance, optimization, and vendor management.

     

    Note

    • Support for editing custom fields on agreements is currently in development and will be delivered in a future iteration.
    • Our teams are actively working on expanding this capability as part of ongoing improvements to multi-editing.

     

    Expand Post

    Scott Waugh likes this.

  7. Release Notification on SAM Core - Snow Atlas: Updated licensing compliance for VMware vSphere

     

    To align with the latest VMware subscription model introduced by Broadcom, Snow Atlas now includes enhanced compliance logic and reporting capabilities:

    • Core-based licensing compliance: License compliance is now calculated based on the latest VMware subscription model, which requires a minimum of 16 cores per CPU.
    • Updated License compliance summary report: The report now reflects the core-based licensing logic, ensuring accurate tracking and reporting of VMware entitlements.
    • VMware bundle categorization: SAM on Snow Atlas now identifies and categorizes VMware bundles in accordance with the latest Broadcom licensing structure.

     

    Why this matters:

    Previously SAM core did not account for the minimum requirement of 16 cores per CPU when calculating license requirements for the VMware vSphere family. This could result in incorrect "over assignment" flags for servers that actually met the licensing threshold. With this enhancement, compliance calculations now correctly apply the per-CPU minimum, giving you an accurate license position.

     

    Quality:

    This release has been validated through:

    • VMware licensing logic: The updated VMware vSphere licensing rules (covering VVF, VVS, VCF, and associated bundles ) have been validated through manual functional testing to ensure that compliance calculations correctly reflect the new per-CPU core-based minimum requirements.
    • Compliance reporting: The License compliance summary report has been tested end-to-end to confirm it accurately reflects the updated licensing rules.

     

    Release info:

    ·       Release date: June 22, 2026

    ·       Product domain: SAM on Snow Atlas

    ·       Release availability: GA

    ·       Product documentation: VMware vSphere 8.0 Enterprise Plus | Snow Atlas Documentation

    Expand Post

    Scott Waugh likes this.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. How do you manage user based licenses and assignments for users, who have more than one userID

    Meanwhile a lot of application license metrics are based on users.

    In our environment we have many users, that work with several userID's. And in our environment that are valid userid's.

    Unfortunately in Snow License Manager it is not possible to group several UserID's to one person, assign the license to that person and then all license requirements for the different userID's will be covered.

    I am aware, that there are many ideas in Snow Ideas Board to cover that requirement, I also created an idea several years ago and voted for others.

    Unfortunately it seems Snow is not able to provide a solution for this.

     

    Does anybody have implemented a workaround for that ?

    I would be really interested in new ideas.

    Expand Post

    Sascha and Tom Lineen like this.
  2. Custom Metrics in Atlas.
    How do I enter a manual figure for and Application where I've ensured that the Custom Metric is added to the Application?

     

    Having created Custom Fields, against the Organization category, and associated complementing Custom Metrics, how do I set a manual figure for such an Application? I've ensured that the Custom Metric is added to the Application.

     

    Thanks,

    Warren

    Expand Post

  3. Open Source Mapping in Snow

    Hello,

     

    We use Snow SLM.

    We’re now facing the challenge of needing to better monitor open source software—beyond what’s possible with the standard “License Required (Y/N)” flag.

    In other words, a correct mapping of which FLOSS license applies to which application and version. 

    As far as i know, SLM doesn’t offer any other out-of-the-box features to automatically capture this kind of information. Am I correct?

    How do other companies or the community handle this? Do you use custom fields that are filled in manually or via the Import Manager? Maybe Flexera has a product/solution for that?

     

    Thanks for your input

    Expand Post

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


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


End of Feed
8 Chatter Feed Items
Loading
Snow Atlas | Flexera Community