The ITAM Dispatch
FlexNet Inventory Agent · pick a version range, see what changed
If your last Flexera agent upgrade crossed the desk a while ago, this edition is for you. Use the version range picker above to set the two releases you want to compare. The catch-up matrix and the change list rebuild accordingly. The FlexNet Inventory Agent has shipped … releases since 25.0.0; the rest of this page tells you which of them matter for the range you picked.
The tracked releases aren't bleeding-edge by Flexera marketing standards: no obvious flagship feature, no end-of-life announcement. What is interesting is that the small fixes compose: a Unicode path here, a TLS 1.2 there, a network blip there. Taken one at a time they're nothing, taken together they are the difference between an inventory position you trust at quarter-end and one you re-validate manually.
§1 The Recommendation
Why these are the right releases. In a Windows estate, the Unicode-path crash and the TLS-1.2-on-legacy fix land in 26.1.0, alone worth the upgrade if you have non-English file paths anywhere, or any Windows 2012 R2 boxes still in production. On Unix big-iron, the cache-limit fix in 26.2.0 means full software discovery on SAP estates where you've been tolerating undercounts. On the operations side, the stuck-uploader and stuck-ingestion fixes are the difference between an environment that walks itself off a cliff after a network blip and one that recovers on its own.
Where to hesitate. None of the changes in 25.x–26.4.0 break the 22.2.0 agent–beacon compatibility floor. If you are running an agent newer than your beacon, you stay supported (Flexera warns about the configuration, but doesn't block it). If your beacon is still on a version prior to 25.3.0, the 64-bit conversion is not in the matrix below. It's already past you. Confirm x64 CyberArk Credential Provider and x64 Access Database Engine drivers are installed across your beacon estate before you upgrade further.
§2 Catch-Up Matrix
Every issue × every version in the range you picked. The “why” column tells you what was actually happening to a customer; the version columns trace whether the issue is still with you. The tinted column on the left is the release you are moving from, the tinted column on the right is the release you are moving to.
Loading matrix…
The matrix is a screen view: one column for every release in the range, which does not fit on paper. The same issues, one at a time, with what each one means and where it was fixed, are in the Detail section below.
What each label means
Kind
- FEATURE
- A new capability added to the product. You gain functionality; nothing breaks.
- FIX
- Resolves existing broken behavior. Plan with the next change window.
- ARCH
- Architectural shift. May require driver, dependency, or deployment updates before upgrade.
Matrix states
- Fixed
- The fix shipped in this version or later. You're clear once you upgrade past it.
- Open
- The issue is still unfixed in this version.
- Introduced
- This version is where the change first landed. You have it once you upgrade to this release or later.
- Uncertain
- No changelog data for this issue yet; check Flexera's release notes directly.
- —
- Outside the issue's existence window (typically before it was introduced).
Affects-us labels
- Yes
- Likely affects a typical ITAM shop running this version.
- No
- Unlikely to affect a typical ITAM shop.
- Check
- Depends on configuration, so review it against your environment.
- Maybe
- Situationally; edge cases warrant attention.
⚠ Past caveat, not in the matrix above: the 25.3.0 64-bit Beacon conversion
Released before the versions in range, but still the operationally-most-important event for any beacon estate: FlexNet Inventory Beacon went 64-bit in 25.3.0. If you've already crossed that line, you have x64 CyberArk Credential Provider and x64 Access Database Engine drivers on every beacon host. If you haven't, that migration must happen before any further upgrades. 32-bit downgrades are not supported.
§3 Detail: … range
What changes across the range. The list below holds the issues still open at … and fixed on the way to ….
Loading…
Working towards a change window? The change window plan turns a range like this into an ordered plan: what to prepare first, the order of work, the versions that must not be skipped, and an honest list of what the change does not fix.
§4 Compatibility
— · released —Loading the compatibility facts...
§5 Support and platform lifecycle
Every tracked release line, the platform release it ships with, and the three deadlines Flexera publishes for it. Standard support ends first, then only critical fixes, then nothing. Source: Flexera end-of-life notice.
§6 Security
Two different things, kept apart on purpose. The first is published problems you can point at. The second is the quiet work your upgrade brings you without a changelog line to show for it.
Published problems in the platform you report into
These are not problems in the agent. They are problems in the Flexera platform your agent and beacon report into, published with an identifier, a severity and a fix. Flexera publishes a platform release for every agent release line, so each one can be traced to the version you run. The full catalogue is on the security page.
What your upgrade brings in the libraries
The agent ships with copies of common open-source libraries. Flexera refreshes them in every release to close known security problems in the code running on your machines. It is the quietest work your upgrade brings you.