Flexera Status:
All Systems Operational- SNOW is showing "Missing installation for user" To Assigned Users even thou they have the Programm installed on their Computers/Devices?
Pre-release notification: Edit of multiple agreements (standard fields) in SAM on Snow Atlas
Release summary:
We are excited to introduce Edit of multiple agreements (standard fields) in SAM on Snow Atlas. This enhancement enables you to update multiple agreements in a single operation, directly from the Agreements list, eliminating repetitive manual updates and reducing reliance on APIs or technical support.
· Release date: June 18, 2026
· Product domain: SAM on Snow Atlas
· Release availability: Early Access (EA)
What is included?
- Multi-editing capability: Select and update up to 1,000 agreements of the same type in one action.
- Standard field updates: Modify key agreement attributes across multiple records simultaneously.
- Smart field behavior: Fields with identical values are pre-filled, while differing values remain empty for selective updates.
- In-app experience: Perform all updates directly from the Agreements list without APIs, imports or external tools.
- Permission consistency: Uses existing edit permissions with no additional configuration required.
Why it matters?
- Removes repetitive work: Eliminates the need to update agreements one by one.
- Saves significant time: Multi-editing that previously took time can now be completed in seconds.
- Improves data consistency: Apply changes across multiple agreements simultaneously, reducing the risk of errors.
- Reduces technical dependency: Enables users to perform multi-editing without relying on APIs, imports, or technical teams.
- Frees up time for strategic work: Allows teams to focus on higher-value activities such as compliance, optimization, and vendor management.
Note
- Support for editing custom fields on agreements is currently in development and will be delivered in a future iteration.
- Our teams are actively working on expanding this capability as part of ongoing improvements to multi-editing.
Expand Post
cterbeck asked a question.
Why are users of Adobe Acrobat 2026 Professional Subscription not exclusively identified through Snow?Why are users of Adobe Acrobat 2026 Professional Subscription not exclusively identified through Snow? All authorized users have an Adobe Acrobat 2026 Professional Subscription. However, non‑authorized users who are using Adobe Acrobat 2017 are also listed. Why can’t Snow distinguish between them?
Expand Post
Hi,
It depends where you look and how you get the data.
There are 2 ways you can get the list of users:
- The Adobe Cloud Connector
- I do not use this connector (see the documentation on how to set up if necessary), but if it works a bit like the Microsoft 365 connector, then it will connect to the cloud portal and pull a list of all users and probably also usage information. This list should only show official users belonging to your Adobe "tenant".
- The standard application detection and metering
- This will list all users how have been inventoried as using any application including Adobe Acrobat 2017. This is regardless of whether they used it on an inventoried computer, inventoried VM or inventoried RDS or VDI environment.
Can you confirm which scenario you are having?
Expand Post- The Adobe Cloud Connector

CvetStoy asked a question.
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
Can you post the content of the log file on one of those failing computers?
The default folder to find this log file is
C:\Program Files\Snow Software\Inventory\Agent
Make sure to remove any sensitive info before posting!
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 Post
Snow 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 Post
Snow Atlas Release Blog — Gabriel Carvalho (Flexera Software)
Official release of Snow Inventory Agent for Linux 26.1.1
We are pleased to announce the release of the Snow Inventory Agent for Linux 26.1.1.
Release Date: 2026-06-10
This release includes:
- Cloud Instance Id
- Java_Home detection with environment variables
- Binary security enhancement
- Agent Unique ID Improvements
- Removal of 32 bit installer
- Fix HTTP headers content type
- Performance improvements for Oracle scanners
- Command elevation improvements
- Fix for folder transversal when the name overlap
- Third-party libraries updated
Customer Impact:
- The agent now adds the Cloud Instance Id as part of the main inventory in the snowpack.
- It is now included under the <SystemIdentifier> tag inside the inv3x.xml file.
- It is now possible to use environment variables in the env.java_home system setting.
- The agent security has been enhanced by enabling additional binary hardening protections.
- The agent now collects the MachineID property, which is generated by the operating system during installation. This should improve the unique id generation, preventing different computers from merging into a single one.
- From this release onwards, no 32 bit versions of the agent will be provided.
- The agent now set its HTTP headers to content-type: "application/octet-stream".
- This improvement fixes communication issues when Web Application Firewall (WAF) is in use.
- CPU usage and scan times have been reduced when collecting Oracle inventory data, helping minimize impact during full filesystem scans (for example, C:\* or /*).
- Corrected an issue where the agent would discard entries in the include criteria if the name of the folder contained the name of another folder entry.
- Example: In a situation where the agent is supposed to scan C:\temp and C:\temp2, the agent would discard C:\temp2, as its name was partially contained in the previous C:\temp entry.
- The agent has been enhanced to read sudo permissions with (ALL : ALL) NOPASSWD. Previously, it was limited to (ALL) NOPASSWD and (root) NOPASSWD.
- The curl, libxml2, zlib, nemtrif/utfcpp, openssl, repo, cryptopp and sqlite3 third-party libraries used by the agent have been updated for increased security
Product Documentation: Agent Documentation
Please find more about the content of this release in the Release Notes.
Expand Post
Snow Atlas Release Blog — Gabriel Carvalho (Flexera Software)
Official release of Snow Inventory Agent for Windows 26.1.1
We are pleased to announce the release of the Snow Inventory Agent for Windows 26.1.1.
Release Date: 2026-06-10
This release includes:
- Java_Home detection with environment variables
- Legacy webmetering deprecation
- Removal of 32 bit installer
- Performance improvements for Oracle scanners
- Fix for folder transversal when the name overlap
- Web Metering Improvements
- Third-party libraries updated
Customer Impact:
- It is now possible to use environment variables in the env.java_home system setting.
- The feature"legacy_webmetering" used by the agent to collect SaaS application usage before the introduction of the browser extensions, has been deprecated.
- The system setting <Setting key="legacy_webmetering.is_enabled" value="true"/> will no longer have any effect from this version of the agent and onwards.
- From this release onwards, no 32 bit versions of the agent will be provided.
- CPU usage and scan times have been reduced when collecting Oracle inventory data, helping minimize impact during full filesystem scans (for example, C:\* or /*).
- Corrected an issue where the agent would discard entries in the include criteria if the name of the folder contained the name of another folder entry.
- Example: In a situation where the agent is supposed to scan C:\temp and C:\temp2, the agent would discard C:\temp2, as its name was partially contained in the previous C:\temp entry.
- The web metering module now runs as an independent service (SnowWebMetering). This controls a local read-only API used for the extension communication.
- This enhancement brings extended privacy and security to web metering, by only writing to disk information that has already been matched against either the Allow List or Crules file, and brings back the support to Apple Safari browser.
- New troubleshooting commands are included in this release, facilitating support of this feature.
- NOTE: This new web metering version requires the use of the new Flexera Web Metering browser extension. Previous versions of the Snow Web Application Metering extensions will not work.
- The curl, libxml2, zlib, nemtrif/utfcpp, openssl, repo, cryptopp and sqlite3 third-party libraries used by the agent have been updated for increased security
Product Documentation: Agent Documentation
Please find more about the content of this release in the Release Notes.
Expand Post
- Has anyone had success configuring Custom Connectors ?
if you have had success, for what applications? - I have set up WDesk, Workiva & no new data is populating in SaaS Management - the advice is that this is a limitation for the Workiva application - so interested to hear of success with other applications?
Expand Post - I have an app that references the native windows file IsInet32.dll but I want to use the linux equivalent of this file libhasp_linux_x86_64.so so that I could deploy my app to linux distribution.
I have an app that references the native windows file IsInet32.dll but I want to use the linux equivalent of this file libhasp_linux_x86_64.so so that I could deploy my app to linux distribution.
I've search the net even AI chatgpt but forwarded me to this site. Is there a way to download the SDK that should contain the said file libhasp_linux_x86_64.so?
Expand Post - We have recently migrated SLM to a new SQL server. This used to exist on the same server as SNOW Automation Platform. Now they are on different servers, SNOWAP cannot connect to SLM for the application import. can they exist on 2 separate servers?
We have recently migrated SLM to a new SQL server. This used to exist on the same server as SNOW Automation Platform. Now they are on different servers, SNOWAP cannot connect to SLM for the application import. They are now on two different servers but the workflow for application import fails. If anyone has any advice on this that would be great
Expand Post - How do i securely configure an on-prem OCP environment as 'connected' to enable Snow Atlas Container visibility?
We recently upgraded to Snow Atlas one driver being the ability to enable containers visibility. Unfortunately, Snow Atlas does not support 'disconnected OCP' clusters for containers visibility. I would be glad to learn from anyone with an on-prem OCP environment that is connected to the internet securely and containers visibility is configured and working well. How do you securely configure a connected OCP environment to enable this visibility?
Expand Post