Loading
Skip Feed
  1. Eptura Products on Invoice Not Found in Snow License Manager

    Hi Everyone,

    I am currently adding a new license entitlement in Snow License Manager and have encountered an issue.

    When I search for Eptura products, Snow only returns 4 products. However, none of these product names match the product names shown on our supplier invoice.

    Because of this, I am unable to determine which application should be linked to the license entitlement.

    Could anyone please advise on the following:

    1. How can I identify the correct Snow application when the invoice product name is different?
    2. Is there a way to view product aliases or alternate names in Snow?
    3. If the product is not available in Snow's recognition catalog, what is the recommended approach for adding the license?
    4. Should a custom application be created in such cases?

    Any guidance or best practices would be greatly appreciated.

    Thank you

    Expand Post

  2. Flexera's Snow Atlas Office Hours (Topic: License Compliance & Optimization) Tuesday, October 20 at 10:00am, ET/3:00pm, GMT

    You are invited to our monthly Snow Atlas session designed around the topics that matter most to your team.

    Hosted by our SME’s, these sessions are built to help you accelerate time to value, adopt new features, and solve your toughest use cases alongside peers. Each session is 30 minutes of focused training followed by 30 minutes of open Q&A and discussion — so you can learn best practices and get your real-world questions answered in the same hour.

    For this call, our topic is License Compliance and Optimization. We will discuss effective license position (ELP), entitlements vs consumption, analysing your position, opportunities to optimize, and other best practices.

    Please share with your colleagues if they are interested in joining.

    Tuesday, October 20 at 10:00am, ET/3:00pm, GMT

    This session will focus on License Compliance & Optimization.

    Click the link below to add the meeting to your calendar.

    What to expect

    • 60 minutes — 30 min training, 30 min live Q&A and open discussion
    • Led by Snow Atlas experts — practical guidance, not slideware
    • Bring your questions — real answers to real estate, configuration, and optimization challenges
    • Exclusively for Snow Atlas customers — hosted live on Microsoft Teams

    Why attend

    • Faster time to value from the features you're already paying for
    • Direct access to product and services experts in a live, interactive format
    • Practical, repeatable best practices you can apply immediately
    •  A touchpoint with the Snow Atlas team

    Look forward to having you join the conversation.

    Thanks,

    The Flexera Snow Atlas team

     

    Expand Post

  3. EA Release notification: Edit of multiple licenses (standard fields) in SAM on Snow Atlas

     

    Release summary:

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

     

    What’s included?

    • Multi-editing capability: Select and update up to 10,000 licenses across different license metrics and assignment types, updating only the fields that are applicable to the selected licenses.
    • Standard field updates: Modify key license attributes across multiple records simultaneously.
    • In-app experience: Perform all updates directly from the Licenses list without APIs, imports, or external tools.
    • Permission consistency: Use 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 licenses.
    • For each license value or setting:
      • Only changed values are updated.
      • If the selected licenses share the same value, it appears in the edit view.
      • If the selected licenses have different values before the change, you will see "Values differ" in the edit view.

     

    Why this matters?

    • Simplifies organizational changes: Update ownership, cost center, department, or other standard fields across hundreds of licenses after mergers, acquisitions, restructures, or team changes.
    • Supports mixed license estates: Apply updates across licenses with different license metrics and assignment types in a single operation, reducing the effort required to maintain diverse software portfolios.
    • Accelerates data cleanup initiatives: Correct outdated or inconsistent license information across large numbers of licenses without editing each record individually.
    • Improves data consistency: Ensure common attributes remain aligned across the license estate, reducing errors and improving reporting accuracy.
    • Reduces technical dependency: Enables users to perform large-scale updates directly in the product without relying on APIs, imports, or technical teams.
    • Saves significant time: Activities that previously required numerous manual updates can now be completed in a single operation, freeing teams to focus on compliance, optimization, and vendor management.

     

    What’s next?

    • Support for editing of custom fields for licenses is planned for Q4 and is currently in development.

     

    Release info:

    • Release date: 08th October 2026
    • Product domain: SAM on Snow Atlas
    • Release availability: Early Access (EA)

     

    Expand Post

  4. Offline installer for SLM 26.2 & 26.3

    When I try to run Snow Update service on our single Snow server that is hosting SLM, SIM & Inventory Server, it fails and the error details make it look like it's trying to downgrade the database? Anyone have any offline installers (for Internet restricted server) for SLM 26.2 & 26.3? When I go to the website & click on "Latest Version" it downloads SnowLicenseManagerSetup_9.32.0 instead.

     

    image

    Expand Post

  5. imageQ&A: Software investigations in Snow Atlas

    Wednesday 4 November from 3.30pm – 4.30pm GMT/ 10.30am – 11.30am ET

    Join the Snow Atlas team for a community Q&A on using the Files per computer report  in software investigations.

    Whether you’re new to software investigations or have used it for years, bring your questions. For example, How can I find a particular file or software version? What should I do if an application isn’t recognised?

    Submit your question in advance

    This is a forum based Q&A taking place here in the Flexera community there is no webinar/event registration, videocall or presentation. Use the form above to submit questions in advance. On 4th November, use the thread to post any additional questions in the comments; our experts will respond during the Q&A window.

    Would you like an email reminder with a link to thread? Select “Yes” in the form and enter your email address .

    Expand Post

    • Regardless of the SAM tool being used, I would avoid creating assumed contractual terms when no agreement documentation is available. Record the entitlement based on the evidence that exists (invoice, PO, license certificate, etc.) and clearly distinguish known facts from assumptions. I generally assume purchases were made in good faith, but compliance positions should be based on demonstrable evidence rather than inferred rights. If agreement details are later obtained from the vendor, they can be linked retrospectively.

      Expand Post

  6. Correction Release: SharePoint scheduled report exports no longer fail due to duplicate file names

     

    What was happening?

    A scheduled report export to SharePoint could fail with a "Name already exists" error when a file with the same name already existed in the target location or when multiple users generated the same report simultaneously. In these situations, SharePoint rejected the upload and the report was not delivered.

     

    What has been changed?

    Every export now receives a unique file name. Export file names have been updated to include additional identifiers, helping prevent conflicts when files with the same name are generated or uploaded concurrently:

    • Milliseconds in the timestamp
    • A 6-character unique ID (GUID) suffix (Example : AdobeCC_20260930123000001_2e0d0c)

     

    What this means for you?

    • Scheduled exports should no longer fail due to duplicate file names.
    • Reports scheduled for SharePoint delivery should arrive more reliably.
    • Exported file names will look slightly different because they now include a more precise timestamp and a unique ID suffix.

     

    Is any action required?

    Existing schedules will continue to run without interruption, and the update is applied automatically. If downstream integrations, such as Power BI, depend on the exported files, review and update any file name references as needed to ensure those integrations continue to operate correctly.

     

    Release Info:

    Product: SAM on Snow Atlas(Report export to SharePoint)

    Type: Correction

    Release date: 21 September 2026

    Expand Post

End of Feed
End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
3 Followers
7.53K Posts
11 members are discussing this topic.
Loading
Software & License Management | Flexera