downgrade
Skip Feed
Snow Atlas Release Blog — Hameed Iqbal (Flexera Software)
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 PostJoannaJankowska asked a question.
How to limit/reduce cpu use by snow agent scan for Windows ?Snowagent scan consumes a lot of CPU. How to limit or reduse CPU condumption by snowagent scan, that it does not consume more than 7% of CPU ?
1 of 9 - Taz (Flexera Software)
26.1 has some improvements, and like @Andrii Branovskyi has advised amending the process affinity can help .
CvetStoy asked a question.
what snow client version do we need for windows 26200Our computers are not reporting to
Snow
- JohnSorensenDK (Flexera Software)
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
MercedesO (Flexera Software)
📢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]
- Best practices for Datadog license creation and purchase order mapping in Flexera One
- https://community.flexera.com/s/question/0D5PL00000tgW4P0AU/optimal-methods-for-datadog-license-creation-and-po-mapping
- How to integrate Flexera One license availability data into ServiceNow
- https://community.flexera.com/s/question/0D5PL00000tfRj20AE/guidance-on-integrating-flexera-one-license-availability-into-servicenow
[FlexNet Manager Suite On-Premises]
- Resolving Microsoft Office 365 TLS validation errors
- https://community.flexera.com/s/question/0D5PL00000tjyR00AI/microsoft-office-365-is-showing-tls-validation-error-in-task-log-but-test-is-successful
[App Broker]
- App Broker reporting failed deployment via Intune despite successful software installation
- https://community.flexera.com/s/question/0D5PL00000tjkvQ0AQ/deployment-is-coming-through-intune-via-the-app-broker-we-can-see-that-the-software-is-fully-installed-on-the-client-machine-however-the-app-broker-is-still-reporting-it-as-failed
[Snow License Manager]
- Why Adobe Acrobat 2026 Professional subscription users are not uniquely identified in Snow License Manager
- https://community.flexera.com/s/question/0D5PL00000tez3c0AA/why-are-users-of-adobe-acrobat-2026-professional-subscription-not-exclusively-identified-through-snow
- Devices showing inactive and not reporting in Snow
- https://community.flexera.com/s/question/0D5PL00000tddGO0AY/hi-our-computers-are-not-reporting-in-snow-they-are-all-stating-inactive-which-is-due-to-settings-but-not-connecting-to-snow-can-you-assist-please
[Snow inventory]
- Compatible Snow client version requirements for Windows build 26200
- https://community.flexera.com/s/question/0D5PL00000tdUA80AM/what-snow-client-version-do-we-need-for-windows-26200
Thanks so much in advance for taking a look, every reply makes a difference and helps keep the community moving forward 🙏
Mercedes
Expand PostSnow Atlas Release Blog — Hameed Iqbal (Flexera Software)
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 PostSnow Atlas Release Blog — Hameed Iqbal (Flexera Software)
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 Documentation, ITSM Documentation
Distribution method: Installer available for downloads here
Expand PostSamuelBaughan asked a question.
What is the INV_FILE_FILTER exactlyWhat is that SLM SMACC Basic setting exactly about?
The official doc says:
INV_FILE_FILTER: File extension filter for data sources (only applies to Windows OS based files). Defines the type of inventory files that will be transferred to SLM by adding or removing file endings in the comma-separated list.
I see in SLM that files with other extensions are also transferred from INV to SLM (*.tmp, *.dll, *.00, ...). Why are they passed on to SLM? Are the detection rules applied or not to those files with other extensions? What is the use of this filter if it applies only to Windows OS based files? How is it different from the filter <IncludeCriteria> <FileType> in the local snowagent.config?
This thread shows that is does more than what it appears to do: https://community.flexera.com/s/question/0D5PL00000NvxJ90AJ/adding-00-to-the-invfilefilter-setting
Do we still need to add the magical ".00" in this list of extensions?
Expand PostQuestion with a best answer. Best Answer
Your agent can be configured to scan for specific file extensions. It will report all those files to the Inventory server.
But not all files will be transferred over to the SLM server during the Data Update Job, only the ones specified in the INV_FILE_FILTER setting. You would usually want to have the same file extensions in both the agent configuration and the SLM SMACC.
Here is one case where maybe you would have a different list of file extensions: You use another method to report more file extensions but they do not come from your agent. For example, you develop a custom method to scan for specific DLL files on some clients to detect a specific app, but you do not want the Snow agents to scan for all DLLs (there are too many of them on each client). In this case, your agent would not list the DLL extension in its config file, but the SLM SMACC would.
I hope that helps
Expand Post
End of Feed
8 Chatter Feed Items
Skip Feed
- 500 internal server errors on SAM
We see lots of 500 internal server errors using SAM (SaaS).
Authentication takes minutes, getting the (empty) computer search page requires 3 o 4 attempts before it's shown on screen, etc.
Not a PC nor a network problem (happens everywhere).
Opened request to support in the past, got answer "now it works". Wow.
Yet, it still happens every day.
Ideas?
Expand Post - Does not collect data for new servers
In the RN150 server there are 617 IP's verified by the Appliance, in the portal we have data for only one IP, the first one we tested (3 months ago), we validate communications for every one DNS/IP and got a "Connection Failure" result for 5 of them:
- TCP Port 443
- app1.riscnetworks.com (34.192.198.73)
- Backup & Growth (34.192.185.36)
- UDP Port 123
- ntp.riscnetworks.com (3.231.5.12, 18.204.38.15, 52.70.0.210)
The Firewall rules do not have modifications recently and we create new firewall rules for each IP instead DNS, then tested again and got same result.
Could you have some advice or suggestion?
Expand Post - TCP Port 443
- my server has a SNOW agent installed & SIEM We have observed suspicious activity on the Windows Database Servers
my server has a SNOW agent installed & SIEM We have observed suspicious activity on the Windows Database Servers.where we see that the command "for /f "tokens=1,2 delims=\\" %i in ('whoami') do net localgroup "ora_dba" "%i\%j" /ADD” was executed.. We observed use of the 'whoami' command and addition of “nt authority\system” to the "ora_dba" group.
- M365 Doubling Data
Just noticed in both SLM (SPE) and in Atlas (SAM CORE) the M365 module is doubling up subscriptions as the SIM data is including Disabled and Expired subscriptions.
Only way to get round this is if you have the Atlas SaaS module you can select to remove the disabled subs via a filter.
Support have a PRB record for this to be fixed in a new release of the SIM, just no idea when this will be released. So take care people with your M365 data analysis.
Expand Post - PKFail detection - anyone?
Hi Community,
is PKFail a thing which is currently keeping your IT busy?
We`re currently looking into the issue and how to get this information from the device into Snow Atlas / Snow License Manager.
Would like to get some feedback from the field.
Cheers Oli
Expand Post - <ConnectionString> setting in snowserver.config
What is a function of encrypted <ConnectionString> in Snow Inventory snowserver.config? Are they server name, database name, and user credentials stored in encrypted form (found in snowdoc)? When I migrate Inventory to a new server should I preserve it or just configure new settings like db connection?
<Configuration>
<Master>
<License>
<CompanyName>XXX</CompanyName>
<LicenseKey>XXX</LicenseKey>
</License>
<ConnectionString>
<Encrypted>XXXXXXXXXXXXXXXXXXXXX</Encrypted>
</ConnectionString>
Expand Post
End of Feed
8 Chatter Feed Items
