Loading

ITSM & Automation

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


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

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

     

     


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


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


  7. How to Configure the AWS Discovery connector without creating an IAM role .

    I am seeking assistance from the community on configuring the AWS Discovery connector without creating an IAM role. Due to privacy concerns at my organization, I am unable to use an Access Key or Secret Access Key. Any guidance on how to achieve this would be greatly appreciated.


  8. I just wanted to ask if there is an established or standardized script to start / stop the SLM or Inventory services for an on premise installation.

    We occasionally see cases where not every service restarts after the reboot from Windows patching. Right now we RDP to the server and start these services. We'd like to monitor for this condition and automate a script to restart any Snow services that have not restarted. We can create this script (PowerShell) but are just wondering if there is already something like this available (if not officially endorsed or supported)


    1 of 4
    • Hi,

      You can use the following attached files to better monitor your Snow services.

      referenced .exe files can be downloaded from https://learn.microsoft.com/en-us/sysinternals/downloads/pstools.

      Note: manually run the 2 .exe files and accept the EULA before using the .cmd file

      change the $logpath in RestartService.ps1 to the folder of your choice, try to use folder without <space>

      change the filepath in tsMonitorSnowServices.cmd to the folder of your choice, try to use folder without <space>

      Add extra services to SnowMonServices.txt by adding services' name and associated .exe.

      Remove services from monitoring by deleting the entry or insert colon : in front of the entry.

      Using Task Scheduler to schedule tsMonitorSnowServices.cmd - hourly, daily etc... as deem required.

      For testing purpose - stop Snow service(s) and run tsMonitorSnowServices.cmd from cmd prompt where the files reside.

       

      Expand Post
      • Unknown file type
        The file is no longer available.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
Loading
ITSM & Automation | Flexera