Loading

Snow Integration Connectors

Skip Feed
  1. VMware vSphere 9.0 Compatibility for the VMware vSphere Connector in Snow Integration Manager (SIM)

     

    We are pleased to announce that the VMware vSphere connector in Snow Integration Manager (SIM) has successfully completed end-to-end compatibility testing with VMware vSphere 9.0, including vCenter Server 9.0 and ESXi 9.0.

    The validation confirmed that connector authentication, inventory discovery, and data ingestion continue to work as expected.

     

    What this means for you

    • Continued inventory coverage for VMware vSphere 9.0 environments
    • Compatibility with vCenter Server 9.0 and ESXi 9.0
    • Confidence when upgrading or deploying VMware vSphere 9.0
    • Reduced connector integration and compatibility risk when upgrading your VMware environment

     

    Important note

    VMware vSphere 9.0 compatibility was validated using the existing VMware vSphere connector in Snow Integration Manager (SIM). No specific SIM upgrade, connector update, additional component, or configuration change is required.

    However, we recommend using the latest available version of Snow Integration Manager to benefit from the latest product updates and fixes.

    Expand Post

  2. VMware vSphere 9.0 Compatibility for the VMware vSphere Connector in Snow Integration Manager (SIM)

     

    We are pleased to announce that the VMware vSphere connector in Snow Integration Manager (SIM) has successfully completed end-to-end compatibility testing with VMware vSphere 9.0, including vCenter Server 9.0 and ESXi 9.0.

    The validation confirmed that connector authentication, inventory discovery, and data ingestion continue to work as expected.

     

    What this means for you

     

    • Continued inventory coverage for VMware vSphere 9.0 environments
    • Compatibility with vCenter Server 9.0 and ESXi 9.0
    • Confidence when upgrading or deploying VMware vSphere 9.0
    • Reduced connector integration and compatibility risk when upgrading your VMware environment

     

    Important note

    VMware vSphere 9.0 compatibility was validated using the existing VMware vSphere connector in Snow Integration Manager (SIM). No specific SIM upgrade, connector update, additional component, or configuration change is required.

    However, we recommend using the latest available version of Snow Integration Manager to benefit from the latest product updates and fixes.

    Expand Post

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

  4. Official release of Snow Integration Manager 26.1.0

     

    This release includes:

    • Enhanced Microsoft AD Discovery with configurable aggregation periods, global site name support, and optional discovery without credentials—giving customers more control over data scope, simpler configuration, and improved support for complex AD environments.

     

    • Optimized Microsoft Azure AD Discovery that retrieves only required activity fields—reducing unnecessary data collection, improving performance, and directly addressing customer security and data‑minimization concerns.

     

    • Extended connector compatibility and continuity, including support for BMC Helix ITSM v25.4, SQL Server 2022 & 2025 discovery via SCCM, and updated GitHub Enterprise APIs—ensuring uninterrupted integrations despite upstream API and platform changes.

     

    • Improved validation, accuracy, and reliability across connectors (Intune, Microsoft AD, Nutanix Acropolis)—helping customers avoid configuration errors and ensuring more accurate inventory and compliance data.

     

    • Platform-level updates with adoption of Calendar Versioning for clearer lifecycle and support expectations, plus updated Flexera branding in SIM—aligning SIM with the broader Flexera portfolio and roadmap.

     

    Release information

    Product: Snow Integration Manager

    Release Tier: Minor Release

    Release Version: 26.1.0

    Release Date: 31 March 2026

    Release Availability: GA

    Release Notes: Release Notes

    Product Documentation: SIM DocumentationITSM Documentation

    Distribution method: Installer available for downloads here

     

    Expand Post

    • any progress on the OLVM connector - it's only been 4 years...

  5. Zoom Connector (in Snow License Manager) shows "No Login Activity" for me, but I am using my Zoom account. What is the definition of "No Login Activity"?

    I have Snow License Manager. I also have the Zoom Connector. That connector connects directly into my Zoom online account to track user activity. I like the feature. Recently, I ran a report. It showed certain inactive users. But it also showed my name there. However, I am a regular user of Zoom. I just use Zoom within my Outlook (The Zoom outlook plugin). I do not log in to Zoom.com to create meetings (because I create meetings directly within Outlook). Any one else have experience with the Zoom connector? Also, I did log in to Zoom.com but that was about 45 days ago. So is "No Login Activity" = not used in 30 days?

    Expand Post

    1 of 2
    • Jelle, thanks for the reply. Here is the answer to your question:

       

      If I login to Snow, the Zoom connector shows that "User has no activity".

  6. Oracle VM Connector - questions from Snow R&D

    [Originally posted in 2019]

     

    Hi SnowGlobers,

    for those who would be interested in the Oracle VM Connector, here's a question coming from our R&D: 

     

    "Hi Supporters of this idea, we are just heating up our development machinery on this topic. Who of you would be available to answer some questions, to make sure we are aiming the right direction? 

    Questions like: x86 only, or also Sparc?

    Query the Hypervisor directly, or querying a Management Software instead?

    Would the Management Software be Oracle VM Manager, or something else like OpenStack? 

    Just get in touch with me, using the way you prefer. 

    Thanks in advance,

    @Oliver Berger​ "

     

    So be sure to get in touch with him

    Thanks!

    Expand Post

    1 of 8
    • Hi, has there been any progress on this - any update on a release for this connector for OVM.

    • Hi Kishan, Yes, this is new to 5.17. And I asked Snow for some explanation since for some, the user-defined name was shown while for others the Vcenter host name was? This is what I got back: In SIM 5.14, 5.15 and 5.16, as part of adding support for Oracle licensing and to correctly report and display datacenter/cluster hierarchy, the option of user-defined datacenter names are  removed. Additionally a Snowpack file is generated for each Vcenter host that reports basic information as shown in the below example:   <Client Architecture ="64-bit" HostName ="DNS name of Vcenter" BiosSerialNumber ="vmware-10 11 12 13 " ConfigName ="VMware vSphere_1" ClientType ="SIEDP" Site ="Snow" ClientVersion ="5.17" Manufacturer ="VMware, Inc." Model ="VMware Virtual Platform" HypervisorName ="VMware Virtual Platform" IsVirtual ="1" IsVDI ="1" />   <OperatingSystem Version ="6.7.0" Name ="VMware vCenter Server" BuildNumber ="123456789" Manufacturer ="VMware, Inc." />   When processed by Snow Inventory, the Vcenter server will be reported as a device in Snow Inventory and SLM. This is what we see in the screenshot shared by you. So the issue in your case is with two Vcenters ‘VCenter X’ and ‘Vcenter Y’. These two Vcenters for some reasons (probably incorrect configuration in Domain or something), fail to expose their configured DNS names (highlighted in yellow in above example) in VSphere API endpoints from which the VSphere connector reads their information. So when the connectors don’t find the DNS names for a Vcenter, it retrieves its configured name in VSphere connector GUI as fallback and report it in generated Snowpack file. Since in your case the user-defined names show up, you might have an issue with a DNS configuration too? success, Gert-Jan.
      Expand Post

  7. Trouble-shooting Steps

    Hello All,

    What are the steps that should be followed when trouble shooting a connector that has stopped working.

    My initial thought is this. 

    1. Stop start service/ connector

    2. Restart the server

    3. Check logs for any information.

    4. ? unsure what to do next. 

    I have log files from when the connector was working and when it stopped working. If someone wants to take a look at them I can share them. I would like to be able to troubleshoot/fix these issues without having to file a support ticket every time if possible.  

    Cheers!

    Expand Post

    1 of 2
    • Hi Andrew, I would do as you say but I would turn the logging level to Verbose/All, run the manual aggregation and check the logs first , then, with the error (if any), I would go to the KB articles as Ester says. Based on what I would find there, I would decide if I can investigate further or log a ticket stright with Snow Support. If no error in the log, I would try a restart of the service then of the whole server. If still unsuccessful after that I would ask on the Community by explaining the situation and the steps I have already taken.
      Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
Loading
Snow Integration Connectors | Flexera