Loading
Skip Feed
  1. Is it possible to install Snow Extender alongside Snow Inventory Server ?

    I’ve got a scenario where the client will be running Snow License Manager on‑premise alongside Snow Atlas for a period of time.

     

    I was considering enabling the File History module in Snow Inventory Server to move processed Snowpacks into a folder that the Snow Extender could pick up and forward to Atlas.

     

    In theory this would allow processing of inventory both on-premise and in the cloud.

    Expand Post

    • Tom Lineen (Flexera Software)

      Hi Dan,

      Yes - you could do something like that.

       

      There are a number of ways to get Snowpacks into both systems for a transition period

      This usually requires running at least one of them on a different port/DNS name during transition.

       

      1) As you suggested you can use the FileHistory option on the Inventory Server. The files created by this module can be forwarded (maybe using a SIM File forwarder) to an Extender

      2) The Extender has a built-in Data forwarder, which can be used to send a copy of each snowpack to the on-prem system.

       

      Once you have completed your transition - you would need to ensure that the forwarding is turned off and that the Extender

      The timing of how you do this is key.

       

      Tom

       

       

       

       

       

       

       

      Expand Post

  2. Our Snow License Manager is currently showing a Critical alert for 18 endpoints. These devices belong to users who are currently on sick leave. please advise on how we can prevent Snow from rom quarantining these devices or suppress the alerts.

  3. liamLittlemore likes this.

  4. Certification of Snow for ServiceNow ITSM Connectors – Australia Release

     

    We are excited to announce that the Snow for ServiceNow CMDB and Catalog connectors have been successfully certified for the latest ServiceNow Australia release.

    Both applications are now available for download on the ServiceNow App Store and are fully compatible with the Australia release, enabling a seamless and fully supported integration experience.

     

    What this means for you

    • Continued alignment with the latest ServiceNow platform updates
    • Ongoing compatibility and support for your integration use cases
    • Confidence in using certified, production-ready applications

     

    Important note

    For customers and partners already using these integration connectors, no action is required. This certification does not introduce any changes or require updates to:

    • Existing Snow for ServiceNow CMDB and Catalog applications
    • Associated connectors configured in Snow Integration Manager. However, it is recommended to be on the latest version of Snow Integration Manager to benefit from the latest updates and patches

     

    Expand Post

    Scott Waugh and Hameed Iqbal like this.

  5. 📢Question Roundup for this week[12th June]: Integration challenges & inventory visibility 

    Hello Everyone,

    It’s been a busy one in the forums, thank you again to everyone who joined our Microsoft 365 Community discussion on we hope you got some valuable insights.

    We also have a number of questions that could benefit from peer responses, if you’ve come across any of the below before please take a second to reply.

    Open questions

    [Flexera One]

    [FlexNet Manager Suite On-Premises]

    [App Broker]

    [Snow License Manager]

    [Snow inventory]

    Thanks so much in advance for taking a look, every reply makes a difference and helps keep the community moving forward 🙏

    Mercedes

     

    Expand Post

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

    • JohnSorensenDK (Flexera Software)

      @CvetStoy​ 

      The Snow inventory agent isn't certified per build version, so all versions supporting Windows 11 would in general support build version 26200 of it. However, the recommendation would be to deploy the latest 26.x version.

       

      I also saw this other thread ... our computers are not reporting in Snow... where the recommendation was to look into the log files, and if you're still struggling and need assistance troubleshooting your issues then you may want to contact Flexera Support.

       

      Thanks,

      John Sorensen

      Expand Post

  7. SLP API Troubleshooting article feedback

    I have feedback on Snow Inventory Server support article https://community.flexera.com/s/article/Optimal-API-endpoint-configuration. In it there is a reference to values that should be present in the SnowInventory and SnowLicenseManager databases for optimal SLM API operation to occur. Following the article, I had our SQL team run these commands first, and they did not help:

     

    EXEC SnowInventory.slm.GetServerAddress;

    EXEC SnowLicenseManager.inv.UpdateServerAddress;

     

    It is unclear in the article that these 2 services are a vital step of the troubleshooting process. I had to restart them in order for the SLM API values appear:

     

    Inventory Server: Snow Inventory Server service

    License Manager Server: Snow Software Inventory Service

     

    Please update or replace this article to help Snow administrators resolve SLM API issues in the future.

    Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
3 Followers
4.35K Posts
3 members are discussing this topic.
Loading
Data Services & Inventory | Flexera