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

     

    What’s 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.
    • 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.
    • Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across agreements.
    • For each agreement value or setting:
      • Only changed values are updated.
      • If the selected agreements share the same value, it appears in the edit view.
      • If the selected agreements have different values before the change, you will see "Values differ" in the edit view.

     

    Why this 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.

     

    What’s next?

    • Support for editing custom fields for agreements is currently in development and testing, with an EA release planned for early Q4.
    • The improved performance and new backend architecture will also allow users to edit up to 10,000 agreements of the same type in a single action.

     

    Release Info:

    ·      Release date: September 24, 2026

    ·      Product domain: SAM on Snow Atlas

    ·      Release availability: General Availability (GA)

    ·      Documentation: https://docs.flexera.com/snow-atlas/sam-core/sam-core-user-interface/agreements/manage-agreements

     

    Expand Post

  2. Why are users of Adobe Acrobat 2026 Professional Subscription not exclusively identified through Snow?

    Why are users of Adobe Acrobat 2026 Professional Subscription not exclusively identified through Snow? All authorized users have an Adobe Acrobat 2026 Professional Subscription. However, non‑authorized users who are using Adobe Acrobat 2017 are also listed. Why can’t Snow distinguish between them?


    MajaHamer likes this.
    • Hi,

      It depends where you look and how you get the data.

      There are 2 ways you can get the list of users:

      • The Adobe Cloud Connector
        • I do not use this connector (see the documentation on how to set up if necessary), but if it works a bit like the Microsoft 365 connector, then it will connect to the cloud portal and pull a list of all users and probably also usage information. This list should only show official users belonging to your Adobe "tenant".
      • The standard application detection and metering
        • This will list all users how have been inventoried as using any application including Adobe Acrobat 2017. This is regardless of whether they used it on an inventoried computer, inventoried VM or inventoried RDS or VDI environment.

      Can you confirm which scenario you are having?

      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

    1 of 3
    • I see ... although I struggle to understand how this is different from tracking all the specifics of each EULA.

      What I mean is that each product comes with specific rights, some of those rights are not based on any metric that can be recorded by an agent (some medical software, for example, is paid for doctors, but free for nurses, others can only be used on a single screen, and yet other applications have much weirder use rights), and technically, you would need to track that too.

      The fact that FLOSS comes with a set of known license terms that are much more flexible than paid software makes me believe that there is much more value in tracking use rights for non-FLOSS. I am not sure of the full value of tapping into a database tagging each app to those GPL or MIT terms under all their versions and flavours ... unless I am missing something.

      That said, if you see the value in that, I assume that exporting such list (if you find one) and importing it as a custom field would only need to be done once in a while, it could be manual. Now, how to handle all the FLOSS available on GitHub? Impossible to import any custom field for those, they are not even recognized in SLM yet. This is to me a much bigger concern ...

      Expand Post

  4. 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.
    1 of 7
    • Yes I also already voted for that, years ago 😒

      The idea has enough votes, I think. Also a long time has gone by. Snow's Max Schönhuber already anwered 4 years ago, this is considered by Product management.

      Because it still is not implemented, it unfortunately looks like Snow cannot implement that.

       

      Meanwhile I think perhaps an additional field in a license could at least be used as workaround.

       

      In any case we need 2 fields for quantity in a license, real license quantity and entitlement quantity.

      That could be also used for Windows Server licenses, we always need to add the entitlement quantity (16), but cannot add the real license quantity ( 1 / 8)

      That's why I already implemented a custom field to know the real license quantity, that helps for SA renewals.

       

      In case of user licenses that perhaps could be used to add the real license quantity 1, and change entitlement quantity based on number of userid's of that user, so we can assign all userid's to that license and then compliance can be calculated correctly.

       

      Yet for Visual Studio license assignments, I use a SQL script, that updates a custom field when a user has assigned a VS license and based on that custom field I use compliance exclusions. But this I can't do for all licenses with user metric, that why I asked for ideas.

       

      But also @SamuelBaughan​  idea using powershell scripts or export/import could be helpful.

      Expand Post

  5. 1 of 2
    • Could it be that the application is licensed per user but no metering is registered?

      This could be because either the user is actually not using the app, or because the detection rules do not include an EXE file that can be used to link metering with the application itself.

      Possible solutions: Try seeing if an EXE file can be used to identify the application (preferred), or set the application to Metric = Installation/Computer so all installations will show as requiring a license (really, this second solution is a dirty hack, it takes all the benefit of tracking properly your licenses ... but if you know for sure that all users are using it, the numbers should still be correct)

      Expand Post

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

  7. Enhanced SaaS Management - Certificate based authorization support for EntraID, M365 and MS Defender 

    Release date: September 16, 2026

     

    This release delivers Certificate-Based Authentication (CBA) as an alternative authorization method for the Microsoft Entra ID, Microsoft 365 (M365), and Microsoft Defender connectors in Flexera One SaaS Management (FOSM).

     

    Building on the existing OAuth2 Client Credentials method (Client ID + Client Secret), customers can now configure and authorize Microsoft connectors using customer-managed certificates tied to their Azure (Entra ID) app registrations.

     

    This release achieves functional parity with FSM, satisfies strict regulatory compliance mandates such as DORA (Digital Operational Resilience Act), and supports enterprise security policies requiring stronger authentication mechanisms without disrupting or forcing deprecation of existing client credential configurations.

    Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. 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

  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 SaaS Management | Flexera Community