Loading
Skip Feed
  1. amitap asked a question.

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

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

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

  5. Scalable Computers Import on SAM Core

     

    You can now import and update large numbers of computers in SAM Core more reliably than ever before. The enhanced Computers Import capability introduces scalable processing for computer metadata and custom fields, allowing administrators to load and maintain large computer estates without running into timeout issues or manual record-by-record updates.

     

    What's New?

    Import computer metadata at scale

    Import thousands of computer records through the Computers Import workflow. Large imports are processed asynchronously in the background, enabling reliable handling of enterprise-scale datasets without impacting system responsiveness.

     

    Support for Custom Fields

    Computer imports now include support for Custom Fields. You can populate and update both standard computer metadata and organization-specific custom attributes using a single import file, eliminating the need for separate maintenance activities.

     

    Reliable Background Processing

    Import operations are executed using scalable background processing designed to handle large volumes of records. Users can continue working in SAM Core while imports are running, improving productivity and reducing interruption.

     

    Live Progress Visibility

    Track the status of your import as it progresses. Administrators receive clear feedback on the operation's current state, helping them understand whether an import is in progress, completed successfully, or requires attention.

     

    Detailed Error Reporting

    When an import completes, the results clearly indicate whether all records were processed successfully or if any records encountered issues. Validation errors and failed rows are presented with detailed information, making troubleshooting straightforward.

     

    Why This Matters

    The enhanced Computers Import capability helps SAM administrators:

    • Import and maintain large computer estates reliably without timeout limitations.
    • Update computer metadata and custom fields through a single import process.
    • Monitor long-running import operations with clear progress visibility.
    • Identify and resolve import errors quickly through detailed reporting.
    • Retry only failed records instead of re-importing entire datasets.
    • Improve data quality and consistency across the estate while reducing administrative effort.

     

    Summary

    Release domain: Computers

    Release tier: Minor

    Release dates (edited):

    UK cluster was enabled on 9th of September,

    Australia cluster on 1st of October,

    West Europe cluster on 5th of October, and

    East US cluster on 7th of October.

    Expand Post

    Daniel Wahlqvist likes this.

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

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

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


End of Feed
End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. amitap asked a question.

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


  3. Report full computer name instead of Hostname

    We are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the 'Computer Name' column in the inventory is reported as the HostName . For example if the computer DNS name is systemA.lab.net it's reported as systemA.

     

    Q: How can we get it to show the full computer name including domain?


  4. Domain Name Inventory Inconsistencies

    We are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the domain name is reported as the domain ShortName (down-level domain name) on Windows whereas on Linux the FQDN of the domain is reported. For example if the domain is lab.net on Linux it's reported as lab.net but on windows as LAB.

     

    Q: How can we get Windows to report the FQDN of the domain it's joined to?

     


  5. Why does my DataExplorer backup give me an unhandled exception during Snow Inventory upgrade?

    I cannot run the Snow Inventory Data Explorer (a prompt from the Snow Inventory installer) to export all my computers from Snow (to back it all up prior to an upgrade) while I'm trying to upgrade Snow Inventory Server from v6 to v25.1.

     

    When I run the installer it asks for the SQL db connections (which I think are correct because I can login to SQL from that machine as that account) but it gives me an unhandled exception error saying it invalid object name 'client' (see exception below) and then just crashes. I couldn't find any logs in Event Viewer nor any for DataExplorer under C:\Program Files\Snow Software\Logs\ directory.

     

    I'm upgrading the following components versions below, is there any way to get this data backed up without having ot go through the DataExplorer backup process? Any assistance would be greatly appreciated, thanks in advance!

    Inventory 6 -> 25.1

    LicenseMgr 9 -> 26.1

    Integration 6.3 -> 26.2

     

     

     

    Unhandled Exception (truncated):

     

    ************** Exception Text **************

    System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'Client'.

      at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

      at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

      at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

      at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

      at System.Data.SqlClient.SqlDataReader.get_MetaData()

      at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)

      at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)

      at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)

      at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

      at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

      at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

      at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

      at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)

      at SnowSoftware.DB.DataFactory.ExecuteSPDataSet(String StoreProcName, String[] ParamNames, String[] ParamValues) in c:\Development\Snow Data Transfer\Source\DataFactory.cs:line 37

      at SnowSoftware.SnowDataTransfer.TransferManager.GetComputerList(String connectionString, String siteName, String computerName) in c:\Development\Snow Data Transfer\Source\TransferManager.cs:line 43

      at SnowSoftware.SnowDataTransfer.frmMain._btnTransfer_Click(Object sender, EventArgs e) in c:\Development\Snow Data Transfer\Source\frmMain.cs:line 218

      at System.Windows.Forms.Control.OnClick(EventArgs e)

      at System.Windows.Forms.Button.OnClick(EventArgs e)

      at System.Windows.Forms.Button.WndProc(Message& m)

      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ClientConnectionId:400a19c0-0677-44cc-a603-4c153db35a40

    Error Number:208,State:1,Class:16

    Expand Post

End of Feed
End of Feed
8 Chatter Feed Items
Loading
Snow Optimizer for SAP | Flexera Community