Loading
Skip Feed
  1. Official release of Snow Integration Manager 26.2.0

     

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

     

    This release includes:

      

    • Red Hat Enterprise Virtualization connector: Added SaveRawData diagnostic capability
    • VMware vSphere connector: Added SaveRawData diagnostic capability
    • File-based discovery connector: Fixed incorrect IP address formatting issue under certain regional settings
    • BMC Helix ITSM connector: Fixed duplicate CI record creation in CMDB
    • Microsoft SCCM connector: Improved UI usability for low-resolution screens
    • Red Hat Enterprise Virtualization connector: Fixed IP address parsing for hosts and VMs
    • Red Hat OpenShift connector: Fixed inventory file creation failure after aggregation
    • Red Hat OpenShift connector: Improved handling of null/invalid datetime values during API processing
    • Nutanix Acropolis connector: Improved handling of assigned and learned IP addresses
    • HPUD connector: Fixed duplicate matching records caused by identical versionid entries

     

    Customer Impact:

     

    New Features (SaveRawData – RHEV & vSphere)

    • The addition of the SaveRawData capability enables customers to capture raw API responses locally, providing greater transparency into source data and facilitating easier validation against connector output. This enhances troubleshooting efficiency, reduces reliance on extended support cycles, and enables faster diagnosis and resolution of connector-related issues.

    File-based Discovery (IP Formatting)

    • IP address values are now processed independently of system regional settings, ensuring consistent and accurate formatting across environments and eliminating discrepancies caused by locale-specific formatting differences in discovery data imports.

    BMC Helix ITSM Connector (Duplicate CIs)

    • Improved validation logic ensures that existing configuration items are correctly updated rather than duplicated, resulting in more accurate CMDB data and improved data reliability for downstream ITSM processes.

    Microsoft SCCM Connector (UI Issue)

    • User interface adjustments ensure that configuration form buttons remain visible even on lower screen resolutions, improving usability and accessibility for users operating in constrained display environments.

    Red Hat Enterprise Virtualization Connector (IP Parsing)

    • Enhanced IP address parsing ensures that host and virtual machine IP addresses are accurately captured from API responses, improving inventory completeness, licensing accuracy, and datacenter hierarchy representation.

    Red Hat OpenShift Connector (Inventory Data Creation Failure)

    • Resolution of the internal encryption issue ensures that inventory files are successfully generated after data aggregation, enabling reliable Snowpack creation and uninterrupted downstream processing.

    Red Hat OpenShift Connector (Datetime Handling)

    • Improved handling of null and malformed datetime values increases connector stability, reducing failures during test connection and data collection and enabling more consistent OpenShift data ingestion.

    Nutanix Acropolis Connector (IP Data Completeness)

    • Support for both assigned and learned IP addresses ensures more complete and accurate inventory data collection from Nutanix environments, improving data quality and visibility.

    HPUD Connector (Duplicate Matching Records)

    • Corrected mapping logic ensures that only a single valid record is matched when processing entries with identical versionid values, eliminating duplicate matching errors and improving overall data consistency and integrity.

      

    Release information

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 26.2.0

    Release Date: 10 June 2026

    Release Availability: GA

    Release Notes: Release Notes

    Product Documentation: SIM Documentation, ITSM Documentation

    Distribution method: Installer available for downloads here

    Expand Post

  2. 1 of 7
    • SLM is not compatible with Azure SQL PaaS because a SQL agent on the SQL server is required to run SLM.

  3. The end of life and end of support dates for few softwares

    Snow Inventory Oracle Hardware Scanner 2.0 (Linux)

    Snow Inventory Server 6.8

    Snow Management and Configuration Center 2.0

    Snow Software SRS Client 3

    Snow Automation Platform 3.9

    Snow Inventory Oracle Middleware Scanner 2.0 (Linux)

    Snow Active Directory Discovery 4.5

    Snow Integration Manager 5.45

    Snow Inventory Agent 6.9

    Snow License Manager 9.8

    Snow Inventory Agent 6.8 (Mac)

    Expand Post

    1 of 2

  4. intend to implement an advanced filter within SNOW License Manager. The objective is to identify duplicate license records based on the 'BIOS Serial Number' and 'Last Scanned Date'.

     intend to implement an advanced filter within SNOW License Manager. The objective is to identify duplicate license records based on the 'BIOS Serial Number' and 'Last Scanned Date'. From the resulting filtered data, I wish to retain only the most recent entry (i.e., the one with the latest 'Last Scanned Date') and subsequently delete all other duplicate records. Is it still possible in SNOW?


    • Detlev Eufinger (Flexera Software)

      Hi,

      yes this is basically possible via an SQL procedure. (Only Snow LicenseManager onPrem).

      If you need help creating such a procedure, please contact your Snow/Flexera sales representative.

       

      Note: You should also think about why there are duplicates in the system in the first place!

      Expand Post

  5. Can we use one Automation Platform License key on two servers in parallel?

    We are migrating AP to Windows 2022 server. We enter the license key on the new server it shows license compliance -2. Is it ok to ignore it as we are using the same key for a cutover time?


  6. How to enable ITSM Enhancer for Snow ServiceNow Integration?

    I am in the process of creating POC for Snow - ServiceNow Integration I have recieved the License for ITSM Enhancer . I am bit confused weather it's an appliaction that we need to install and configure or It's just I need to have license to do the integration.

     

     


  7. 1 of 4
    • Community Manager (Flexera Software)

      @Colin Hardie​ Hi Colin, thanks for your interest in ITSM Enhancer. As noted by some of the previous commenters, Snow did go through a product repackaging. As part of this we renamed Snow for ITSM as ITSM Enhancer.

       

      Simply, it is the integrated connector between Snow License Manager and the list of supported ITSM tools (i.e. ServiceNow, BMC). In SLM you get the benefit of the discovery and inventory,(in new speak - Adoption Tracker), and normalization (Data Intelligence Service), which stand alone. If you want to ingest all that data in ServiceNow, mapped to the right areas of the CMDB that is interpretable and usable then you require the connector, ITSM Enhancer. This is how you can achieve automated, cleaned, and normalized software title data to populate your CMDB. It is a capability that even the ServiceNow team comes to Snow to deliver to their customers.

      Expand Post

  8. i am new to Productivity Optimiser and we are currently setting it up for software installs etc. is there a way in the store to add a request for a laptop?

    i am new to productivity optimiser, and cant seem to work out how to add an store item for a laptop or other hardware device, with the usual fields asked for delivering kit...  , and then have it go through approvals etc, and then possibly have an email or API call into the supplier to deliver the device

     

    total newbie here, and ay help would be greatly appreciated


End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. i am new to Productivity Optimiser and we are currently setting it up for software installs etc. is there a way in the store to add a request for a laptop?

    i am new to productivity optimiser, and cant seem to work out how to add an store item for a laptop or other hardware device, with the usual fields asked for delivering kit...  , and then have it go through approvals etc, and then possibly have an email or API call into the supplier to deliver the device

     

    total newbie here, and ay help would be greatly appreciated


  2. What to consider in terms of SLM server integration with Automation Platform when migrating SLM server to a new one?

    We are migrating SLM and Inventory servers to a new version. We have Autmation Platofrm configured to deploy software imported to AP to users machines in the comapny, via SCCM co Is there any setting in AP where we ned to chnage Snow servers credentials?


  3. Engine Measurement Period Start & End Dates in SOS correct?

    Hello,

    we recognized while comparing old to current measurements of SAP Engine, that the measurement for same period is now lower that before:

     

    e.g.

    01 June 2020: Engine xyz was metered for period 01.01.2019 to 31.12.2019 with a value of 100

    01-Sept 2020: Engine xyz was metered for period 01.01.2019 to 31.12.2019 with a value of 85

     

    SAP Engines with this problems are for example:

    0370 NetWeaver Gateway - Anzahl Aufrufe des GW (ODC) pro Jahr

    0372 NetWeaver Gateway - Anzahl Gateway Benutzer pro Jahr

    8100 Shared Service Framework – Serviceanforderung FIN 

    8101 Shared Service Framework – Serviceanforderung HR

    8102 Shared Service Framework - Kontaktdatensätze 

     

     

    By logic we do not see many reasons for the changes, as we did not remove any SAP systems (we just added some in between):

     

    Possible reasons:

    a) SAP data has been changed for the period between the two measurements (not very likely, that this is possible for the past). Also it happend to many engines/systems, which make it more unlikely.

     

    b) The metering period shown in SOS is a default value in SOS and is wrong (e.g. Last 12 month instead of shown "last year")

     

    c) The field in SAP, which defines the metering period(and is show in SOS) and which is actually used, are not the same.

     

    Engine start End

     

     

    Please share you thoughts and experience. Thank you in advance.

    Expand Post

  4. Been thrown in the deep end with no training.

    Hi All, not sure if this is the best place to ask; I have recently been given the task of dealing with SLM in our organisation (along with my other duties, so I can only dedicate 1-2 days a week on SLM).

     

    SNOW has picked up 700+ unique applications that require licenses. I have tried to contact users who have said software etc but no one can provide me with specific invoices (all done via SAP and departments don't get copies)

     

    its all a bit of a mess; and Im wondering how does someone with no formal SLM training / experience deal with a situation like this?

    • do I have to remove said software from the estate as we cant prove anyones paid for it / if its still valid
    • do I approach vendors and ask them if we are licences (potentially opening a can of worms of my organisation if we are not licenced and have been using software)
    • or simply run a report from SNOW and hand it over to someone with a higher pay grade and let them deal with it.

     

    We also use AD / SCCM to deploy packaged software and from what I can see there is no way of syncing AD Groups to Licences in SNOW.

     

    any help / guidance anyone can provide would be appreciated

    Expand Post

  5. SAP data delete

    Maybe anybody knows, how to resolve 2 following things:

    1. How to renew imported information? When I try to import data, SLM make duplicates. I can not find place, where I can change import settings for SAP.

    2. How to delete duplicates from already imported data?

    Already looked import guide, but there is not information about it. 


  6. Simulate SAP costs through contract conversion.

    The new license models from SAP were adapted to On Premise licensing in S4/HANA. This means that there are now only 4 license types that would be relevant for measurement.

    Now we ask ourselves whether the new licensing would be better suited to our situation.

    To answer this question we would like to use SNOW for SAP to simulate the cost changes.

    Since the new license types have different permissions on transactions, the question is whether SNOW already has the possibility to simulate the cost changes for On Premise licensing.

    I am very grateful for your answers and wish you a nice week.

     

    Best Regards

    Julian

    Expand Post

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