Loading

Snow For Service Now

Skip Feed
  1. Official release of Snow Integration Manager 6.13.0

     

    We’re pleased to announce the release of Snow Integration Manager 6.13.0.

    This release focuses on closing critical functionality gaps, strengthening security, and improving data accuracy across key integration connectors.

     

    Here’s a breakdown of the problems we’ve solved - and the value we’re unlocking for our customers.

     

    Red Hat OpenShift Virtualization Integration

    Snow Integration Manager now supports virtualization inventory collection from Red Hat OpenShift environments. Customers gain improved visibility into both standard virtual machines and cluster relationships, enabling better infrastructure insight, stronger license compliance, and support for modern OpenShift-based virtualization platforms.

     

    Secure and Compliant OAuth 2.0 Authentication

    The ServiceNow ITSM and Discovery connectors now support OAuth 2.0 authentication, providing a more secure, token-based connection method. This enhancement aligns with modern enterprise security standards, reduces credential exposure, and simplifies security compliance.

     

    Reliable and Unique Mobile Device Identification

    The Microsoft Intune connector now offers enhanced device identification by allowing the use of DeviceName + SerialNumber for mobile devices and iPads. This ensures more reliable device identification, reduces duplicate records, and improves the overall quality and accuracy of inventory data.

    Release information

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 6.13.0

    Release Date: 2025-12-03

    Release Availability: GA

    Release Notes: Release Notes

    Product Documentation: SIM Documentation, ITSM Documentation

    Distribution method: Installer available for downloads here

    Expand Post

    Max_Schoenhuber likes this.

  2.  Certification of Snow for ServiceNow ITSM Connectors with ServiceNow Zurich Release

     

    We are pleased to announce that Snow for ServiceNow CMDB and Catalog connectors have been successfully certified for the latest ServiceNow Zurich Release.

    Both the CMDB and Catalog applications are now available for download from the ServiceNow App Store, fully compatible with the Zurich Release.

     

    Important Note:

    For customers and partners currently using these integration connectors, this certification does not require any changes or updates to the existing Snow for ServiceNow CMDB and Catalog apps or the associated connectors in Snow Integration Manager.

    Expand Post

    khalid.khan likes this.

  3. Mandatory Migration to OAuth 2.0 for ServiceNow Connectors in SIM

     

    As part of our ongoing commitment to security and compliance, we are introducing OAuth 2.0 authentication support for ServiceNow connectors in SIM 6.13.0, scheduled for RTM on December 3rd.

    This enhancement replaces the existing Basic Authentication mechanism, delivering a more secure and robust integration with ServiceNow APIs.

     

    What’s Changing?

     

    • With the release of SIM 6.13.0, OAuth 2.0 Authentication will be implemented in:
      • Snow for ServiceNow CMDB and Catalog (ITSM) connectors
      • ServiceNow Discovery (SAM) connector
    • OAuth 2.0 Authentication will be the only supported method for these connectors.
    • Basic Authentication will no longer be supported.

     

    Action Required

     

    • After upgrading to SIM 6.13.0, customers and partners with existing integrations of the Snow for ServiceNow CMDB and Catalog and ServiceNow Discovery connectors must update their configuration settings to use OAuth 2.0 authentication.
    • Refer to the respective Connector User Guides for detailed OAuth 2.0 configuration steps which will be published on the RTM date.

     

    FAQs

     

    Q1: What happens if I don’t migrate after upgrading to SIM 6.13.0?

    Your existing ServiceNow connector integrations configured with Basic Authentication will stop working, and inventory or catalog data will no longer sync.

    Q2: How do I get OAuth credentials?

    OAuth credentials (Client ID, Client Secret, Token URL) can be generated in your ServiceNow instance. The detailed configuration steps will be available in the respective Connector User Guides, which will be published on the RTM date.

    Q3: Will there be any downtime during migration?

    No downtime is expected if you follow the migration steps in the connector user guides correctly. We recommend testing in a non-production environment first.

    Q4: Who can I contact for help?

    Reach out to your account manager or contact Flexera Support.

     

    Expand Post

  4. Pushing data back from ServiceNow into SLM

    Hi, does anyone have any advice or experience with the above please?. I've used the Web Configurator to import data into SLM, but I'm looking for two things:

    1) How best to get the data out of ServiceNow (via the API ?)

    2) How best to achieve as-close-as-possible real-time synchronisation of computer asset information (e.g. if an asset state/substate in ServiceNow is flagged as "awaiting disposal", the same status can be reflected via an updated custom field in SLM

     

    Using the ServiceNow API to facilitate a frequent file drop into the Web Configurator polled folder would be a solution but I suspect there is a much better way to do this!

    Expand Post

    1 of 6
    • Hey,

      ​

      I' had this set up with a customer and the only thing I can really recommend is, do not do it - you will probably regret it in a few months 😅. It was configured and worked perfectly until we did an SLM update and then it was broken for 3 years.

      ​

      Snow itself doesn't have anything in place to do this, just Snow > ServiceNow. If you want to feed from ServiceNow to Snow, you need to use a MID Server to import the data into the SQL Server Database and have custom procedures that then transform the data.

      ​

      If you _really_ want to do it, I'd personally go down the Web Configurator way. It's the "supported" solution that is unlikely to break every time you update SLM.

       

      Using the Web Configurator allows you to have a bit less of a delay as well, doing anything other than the Web Configurator will result in a 24 hour delay because of the Data Update Job needing to run for things to sync correctly.

      Expand Post

  5. Is there documentation somewhere to map fields between Snow and ServiceNow?

    Hello, I need a documentation of mapping fields in ServiceNow ITSM connectors. Which columns from the Snow License manager are mapped to which columns in ServiceNow? Is it somewhere in documentation? Unfortunatelly I didn't find something like that in Snow Docs. 


    1 of 3

    • Community Manager (Flexera Software)

      Hi Liam,

      The Snow Catalog and Snow CMDB ServiceNow applications do require a HI account to request from the ServiceNow App store. The 2 applications are not available for ServiceNow Personal Developer instances.

  6. Servicenow cannot see the files sent by SNOW

    We have the Catalog and CMDB applications installed in our Servicenow Instances.

    Since last week, we noticed the SNOW files are not coming into Servicenow Prod instance (Paris Patch 10a). There is nothing under Files waiting for import.

    We recently updated the SNOW applications to 4.1 and the SIM version is 5.34.0

    It is working fine on dev instance(Rome) post update to 4.1

     

    Could you please advise?

     

    Cheers,

    Caren

    Expand Post

    1 of 7
    • Hi, was this ever resolved? We now have a similar issue on 2 instances, but 2 others are working fine

      Also recently updated all servicenow plugins and this seems to be connected....

      Thanks

  7. SNOW to ServiceNow software feed update

    We are using Snow License Manager and using the Snow Integration Manager plugins to integrate SNOW with our ServiceNow CMDB.

    An issue that we are facing is that we seem to be import 300k software instances every night. Is there a way to reduce these software instances, these seem to be happening every night and take some time to process the software import

     

    Is anyone else had any experience with this?

     

     

    Expand Post

    1 of 2
    • We had the same problem for our environment of over 150K systems. We tried all the various tuning but it was still taking a very long time. We ended up breaking our environment down using our Organization structure and only sending a portion of the systems each evening. Thus setting up multiple feeds for different days in order to get our entire enterprise processed. The down side is we do not have the latest information on all systems every day. This is working fine as long as we acknowledge that our data may be a day or two behind.

      Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
Loading
Snow For Service Now | Flexera