Loading

Snow Integration Connectors

Skip Feed
  1. 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...

  2. 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".

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

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

  5. VMware connector not inventorying all VM

    Hello Snower's,

     

    We noticed that our VMware connector is not retrieving all the possible information from the VCenters (even if configured to look for shutdown vms or templates). I've confirmed that something is wrong because the logs of the collection are really missing some VMs and if I use VMware PoweCli (running in Snow Server as well) I can actually get more VMs and the corresponding license keys.

     

    Is someone aware of this issue? How to troubleshoot it? Is it possible to rebuild the information that is collected from each VCenter?

    I deleted the configuration and added it again (login details) but no luck. I have the VMware connector configured with around 20 central vCenters. I've tried a forced aggregation besides the daily schedule but still d'ont get all the VMs.

     

    Thanks.

    Expand Post

    1 of 3
    • Solution: Making sure that the vcenters ESX are well configured in terms of name and hostnames. If the hostnames are not unique or wrong it may lead that no ALL ESX be seen by the connector.

  6. Snow Integration Manager - Dropbox Connector

    Hi All,

    Has anyone out there successfully configured the Dropbox Connector?

    I am interested in the Dropbox API settings within the Dropbox Dev portal, outside of what is supplied within the Snow Integration Manager - Dropbox Connector Guide.

    Look forward to chatting.

    Regards

    ShazBerry

    Expand Post

    1 of 6
    • Yes I have a ticket open with Support as we couldn't get the connector to work at all. Came up with an authentication error. It's been logged as a defect and I'm waiting for a fix. I've asked for an ETA, but nothing to date. Interesting that they would provide you with a beta version to test and haven't mentioned that to me. I will update my ticket and ask if I can use it too? Thanks  Adam

  7. Dynamics 365 Active Users
      Updated Hi All, I believe O365 connector still only retrieves usage information from O365 Admin Portal for Office family products.  Please excuse and correct me if I am wrong. Are there plans for Snow product teams to build Dynamics 365 Subscription Active User and usage information into the O365 connector now that Microsoft has deprecated (love that word) the app called Microsoft Dynamics 365 - Organisational Insights and replaced with analytics via the Power Platform Admin Centre? NB All data is available within a single source now rather than requiring an additional App installed on the Admin Portal. https://docs.microsoft.com/en-us/power-platform/admin/analytics-common-data-service As suggested by ‌ I have copied this over to Ideas with same Title.  Please respond here . Cheers Shaz ‌ ‌ ‌ ‌
    Expand Post

    • Nathan Stevens (Flexera Software)

      Hi ‌, its best to register this on the ‌ where the "new idea" can be reviewed and discussed in that forum. If there is enough interest from the community the R&D team can pick this up and scope it out based on customer feedback. 

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
30 Posts
2 members are discussing this topic.
Loading
Snow Integration Connectors | Flexera