Loading
search-img

Snow License Manager

Skip Feed

  1. Snow Product Releases Blog — Hameed Iqbal (Flexera Software)

    September 21, 2026 at 11:10 AM

    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
    • 20 views

  2. carolai asked a question.

    September 15, 2026 at 1:38 PM
    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
    • 7 answers
    • 83 views
    Sascha and Tom Lineen like this.
    1 of 7

    • carolai

      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

    • carolai

      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

      Expand Post

  4. SebastianW asked a question.

    September 11, 2026 at 9:31 AM
    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 answer
    • 21 views

    • SamuelBaughan

      It does not offer this feature yet as far as I know.

      I am curious: What exactly is your use case for this type of info? What would you use it for inside of SLM?

  5. VNMan01 asked a question.

    September 7, 2026 at 10:07 AM
    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.

    Expand Post
    • 1 answer
    • 63 views
    Sascha likes this.

    • carolai

      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.

  6. SibylleRobelDUR asked a question.

    August 24, 2026 at 10:17 AM
    Snow License Manager / Reports
    Searching in Reports for customized fields

    Snow License Manager

    Report => All Reports => Standard Reports => Report : All Computers

    In these Report I can search for customized fields.

    But in the same path (Report => All Reports => Standard Reports) in the Reports : All Objects there ist no searching for customized fields possible.

    Why is that so ?

    If I could search in customized fields in one Report it should also be possible in another.

    How can I get the customized fields into the Criterias and the search ?

     

    And is there a report where I can read datas from computers under hardware, which the Agent read from the computer => especially the Monitors ?

     

    Expand Post
    • 1 answer
    • 31 views

    • AxelLa

      The simple answer is: there are no custom fields in objects.

       

      To get the monitor information: this requires a custom report (SQL query) in the database.

      I am not sure how complete the out-of-the-box monitor inventory works. I can see some monitors in my environments, but not on all computers.

      We added some PowerShell Scripts to the Agent to read monitor information including serialnumbers.

       

      Expand Post

    • liamLittlemore

      Could you explain a little bit more.

       

      Are you saying you removed netback from a server but since you have scanned & send a scan file but the application is still showing in SLM?

       

       

      Expand Post

  8. 1 of 2

    • SamuelBaughan

      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

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
28 Followers
2.68K Posts
975 Articles
10 members are discussing this topic.
+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Snow License Manager | Flexera