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

  2. Flexera's Snow Atlas Office Hours (Topic: License Compliance & Optimization) Tuesday 20 October

    You are invited to join us for our Best Practices and Office Hours focusing on Snow Atlas. For this call, our topic is License Compliance and Optimization. We will discuss effective license position (ELP), entitlements vs consumption, analyzing your position, opportunities to optimize, and other best practices. Please share with your colleagues if they are interested in joining.

    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

    Look forward to having you join the conversation.

    Thanks,

    The Flexera Snow Atlas team

     

    Expand Post

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


  4. Official release of Snow Integration Manager 26.3.0

     

    We are pleased to announce the release of Snow Integration Manager 26.3.0

     

    This release includes: 

     

    ·      Oracle Linux Virtualization Manager connector: Added a new connector for collecting inventory from OLVM environments into SAM on Snow Atlas and Snow License Manager.

    ·      Discovery data from file connector: Added support for populating the DiscoveryDate field in discovery manifests.

    ·      ServiceNow ITSM connectors: Added a configurable page size for computer data retrieval.

    ·      ServiceNow ITSM connectors: Fixed OAuth authentication through connector-configured proxy servers.

    ·      HCL BigFix connector: Fixed duplicate device identity attributes that could cause incorrect device merges.

    ·      VMware vSphere connector: Fixed BIOS serial-number formatting for inventoried virtual machines.

    ·      VMware vSphere connector: Fixed proxy configuration restoration after aggregation.

    ·      BMC Discovery connector: Improved handling of software records with missing names.

    ·      HCL BigFix connector: Fixed missing records when processing large paginated datasets.

    ·      Microsoft Hyper-V connector: Fixed authentication for service accounts specified in UPN format.

    ·      Red Hat OpenShift Virtualization connector: Corrected host and datacenter identity mapping.

    ·      Snow XML connector: Improved processing of network adapter data without a MAC address.

    ·      HCL BigFix connector: Improved validation of software-instance and software-metric inclusion rules.

     

    Customer Impact:

     

    Oracle Linux Virtualization Manager Connector

    Before this release: Customers using Oracle Linux Virtualization Manager, including those transitioning from the legacy Oracle VM platform, did not have a supported SIM connector for collecting OLVM virtualization inventory into SAM on Snow Atlas or Snow License Manager. This resulted in limited visibility into OLVM-managed hosts, virtual machines, clusters, and their relationships, increasing reliance on manual collection or alternative approaches.

    After this release: The new connector automatically collects inventory from OLVM environments through the OLVM API and imports OLVM-managed hosts, virtual machines, clusters, and their relationships into SAM Core on Snow Atlas and Snow License Manager. This expands virtualization inventory coverage, reduces reliance on manual processes, and helps customers transitioning from Oracle VM to OLVM maintain visibility across their virtualized environments to support license-compliance processes.

    For configuration information, refer to the Oracle Linux VM connector user guide.

     

    Discovery Data From File Connector

    ·      The addition of the DiscoveryDate field provides a consistent discovery timestamp, improving metadata consistency and reliable processing across discovery sources.

    ServiceNow ITSM Connectors

    ·      The configurable page size improves computer-data retrieval reliability by allowing customers to adjust the number of records retrieved according to their environment and payload size.

    ·      OAuth requests now use the proxy settings configured in the connector, supporting reliable ServiceNow authentication in environments that require proxy communication.

    HCL BigFix Connector

    ·      Corrected device identity mapping prevents distinct devices from being incorrectly merged, improving device identification and host-to-virtual-machine relationships.

    ·      Improved pagination ensures complete processing of large datasets, reducing the risk of missing software inventory records.

    ·      Improved filtering validation prevents inconsistent software-instance and software-metric selections, supporting more complete and reliable inventory data.

    VMware vSphere Connector

    ·      Preserving BIOS serial numbers exactly as reported by VMware vSphere improves consistency when comparing or combining data from multiple inventory sources.

    ·      Correct restoration of proxy settings allows subsequent connector operations to use the appropriate network configuration without restarting Snow Integration Manager.

    BMC Discovery Connector

    ·      Filtering software records with missing names prevents malformed records from disrupting downstream processing while preserving valid software inventory data.

    Microsoft Hyper-V Connector

    ·      Correct handling of UPN-formatted service accounts supports successful authentication and data aggregation against remote SCVMM servers.

    Red Hat OpenShift Virtualization Connector

    ·      Corrected host and datacenter mapping improves the accuracy of reporting, grouping, and license allocation in Snow Atlas and Snow License Manager.

    Snow XML Connector

    ·      Allowing network adapter data without a MAC address aligns validation with the XML schema and improves XML data-processing reliability.

     

    Release information

     

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 26.3.0

    Release Date: 2026-09-21

    Release Availability: GA

    Release Notes: SIM 26.3.0 Release Notes

    Product Documentation: SIM Documentation, ITSM Documentation

    Distribution method: Installer available for downloads here

    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

  6. Allocation Issues

    Hi Team,

     

    I am facing allocation issue in Named User License. Since, the license is mapped to correct application and we have more than 1000 installed in our environment for that application. But there is no consumption and also user allocation not showing in the tool. Users are still using the application. What should be done for showing allocation of the users in the license? Any help?image


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

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


  2. Allocation Issues

    Hi Team,

     

    I am facing allocation issue in Named User License. Since, the license is mapped to correct application and we have more than 1000 installed in our environment for that application. But there is no consumption and also user allocation not showing in the tool. Users are still using the application. What should be done for showing allocation of the users in the license? Any help?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
8 Chatter Feed Items
Loading
Snow License Manager | Flexera Community