The ITAM Dispatch
Inventory Beacon · pick a version range, see what changed
The Inventory Beacon has … releases in this edition's range. The range picker above lets you set the two releases you want to compare. The catch-up matrix and the change list rebuild accordingly. The hardest version to skip past is 25.3.0: it's the 64-bit conversion, and you cannot stay on a 32-bit beacon after that.
The tracked releases are heavy on fixes (Oracle audit, concurrent discovery, dangling ndupload processes) and lighter on features. The notable features are operational: HTTPS+basic auth on self-hosted web servers, configurable certificate verification for package signature validation, full TLS 1.3 support, SBOM upload support. None of them are marketing flags. All of them are real quality-of-life upgrades for any customer who runs their own infrastructure.
§1 The Recommendation
Why these are the right releases. If you're past the 25.3.0 64-bit conversion, you've already cleared the architectural hurdle. Everything since has been operational fixes and quality-of-life features. The 26.x releases close the Oracle audit gap, fix concurrent-discovery unreliability, and make policy file generation work cleanly on first-deploy beacons. Older still, 24.2.0 brought HTTPS+basic auth to self-hosted beacons (long-requested by Snow Atlas migrators), 24.3.0 fixed the multiple-discovery-task concurrency bug, and 23.5.0 closed a real security finding around beacon file permissions.
Where to hesitate. The 22.2.0 agent-beacon compatibility floor still applies. If you're upgrading a multi-beacon estate and any beacon is below 22.2.0, no beacon in that estate can self-upgrade past legacy versions until all are above 22.2.0. The 24.2.0 removal of legacy package retrieval (PackageRetrieve.exe) is the trigger that makes this hard.
§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.
⚠ The 25.3.0 64-bit Beacon conversion is in the matrix above, and it's the operationally-most-important event in this window.
If you've already crossed it, you have x64 CyberArk Credential Provider and x64 Access Database Engine drivers on every beacon host. If you haven't, the 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 — · 64-bit since 25.3.0Loading 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 beacon. 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 beacon 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 beacon ships with copies of common open-source libraries, fewer of them than the agent. Flexera refreshes them release by release to close known security problems in the code running on your beacon hosts. It is the quietest work your upgrade brings you.