FlexNet Manager Update: Application Recognition Library 2996 and Service Life Data Pack 841 are available

What's new in this release?

• Count of new applications added:

• Publishers renamed as listed below:

• Classification updated for Microsoft 365Companions from Commercial to Component. Refer to the following for more details: Feed Detail

Current Library Totals:

• Number of applications in ARL:  315,424 across 18,648 publishers.
• Number of commercial applications with service life dates:  99,326
• Number of evidence recognition rules: 3,597,550
  • Installer evidence rules:  2,376,640
  • File evidence rules:   1,217,162
  • WMI evidence rules: 1,727
  • Application suite evidence rules: 2,021

Details of changes in the ARL

You can inspect changes made in this ARL release as per the following links:

• List of new applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewApplicationsARL2996
• List of new versions of applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewVersionsARL2996
• List of new publishers added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewPublishersARL2996
• List of applications updated in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=UpdatedApplicationsARL2996
• List of Applications deleted in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=DeletedApplicationsARL2996

Updating library data

FlexNet Manager Cloud: These updates will be installed before Monday, 2nd November 2026

FlexNet Manager On-premises: This library release will be applied to your FlexNet Manager according to the schedule settings and processes configured for your instance. If your environment requires you to download and update library data manually, see the following article for guidance: Downloading the FlexNet Manager Suite Content Libraries manually.

You can inspect currently installed library versions using the FlexNet Manager Menu > System Health > System Health Dashboard menu option.

Upcoming ARL and Service Life Data Pack updates: We nominally expect the next ARL and Service Life Data Pack updates to be published on or around Friday, November 6th, 2026

Reporting issues with ARL and SLDP updates

Should you have any FlexNet Manager library data issues, please submit a case by logging in to the Flexera Community and selecting the Get Support > Open new case menu option.

We are interested in feedback on these announcements. If you have any questions or suggestions for improvements, please comment below. 

We trust you will find this update helpful and look forward to continually improving your application recognition results.

- Team Content

FlexNet Manager Update – SKU, PURL & Bundle updates - Release #587

The SKU, Product Use Rights Libraries (PURL) and Bundles libraries, used by FlexNet Manager Suite, have been updated. For on premise customers the SKU/PURL/Bundles libraries have been published and are now available.

Customers of Flexera One IT Asset Management (ITAM) will have this update applied by the Recognition Data Import task and will be available on Monday, November 2nd, 2026, in your time zone.

What's new in this release?

• 155 new SKUs have been added to the SKU library. The following table provides an overview of the number of SKUs with respect to publisher: 
•  More than 130 SKUs are mapped to their respective applications.
• SKUs missing PURL templates and existing mapping were refreshed which covered more than 6,997 SKUs. Details on the number of SKUs covered across each publisher:
• 25 new custom FLX SKUs - 1 Atlassian SKU and 24 SKUs for Tier 3 publishers have been created and released to supplement Flexera One SaaS Manager workflow for the respective products and cater to customer requests. SKUs details are available in the attached spreadsheet 'CustomFlexeraSKUsForOctober2026.xlsx'.
• Updated Publisher from "McAfee" to "Trellix" for Mvision related products across the SKU Library to align with vendor documentation.
• Expanded the PUR library by adding six new publishers: Acoustic, Trellix, Docker, Nexthink, VanDyke Software, and Screaming Frog.
• Added 'Trellix' and 'NEXThink' as new publishers in the bundle library.
• Refreshed 10 bundles by adding/removing applications and SKUs as per latest vendor literature.
•  26 New Bundles published for October release, mapping 182 SKUs.
• Library information is as follows:

o  Total number of SKUs in the library is 2,227,456 across 2,554 publishers.

o  Total number of PURL templates is 7,924 across 94 publishers.

o  Total number of published Bundles is 5,144 across 41 publishers.

How do I report issues with SKU/PURL/Bundles Library updates?

Should you have any issues related to SKU/PURL/Bundles processing with FlexNet Manager, please contact Flexera Support. Visit Contact-Flexera-Support for more details.

The regular schedule for SKU/PURL/Bundles updates

We expect the next update to the PURL, SKU & Bundles Library to be available on Friday, November 27th, 2026. The libraries are available as soon as published and are updated weekly via the Recognition Data Import task, or as otherwise reflected in your local configuration. Customers of Flexera One IT Asset Management (ITAM)  will have this update applied by Monday, November 30th, 2026, in your time zone.

Downloading the SKU/PURL Libraries Manually

The SKU/PURL library updates can be downloaded from the Flexera Product and Licensing Center (PLC 2.0).

For full details on how to install content library files once they have been downloaded, see the "Manual Updates of Library Data" topic in the Installing FlexNet Manager Suite On-Premises PDF applicable to your version of FlexNet Manager Suite.

To locate this PDF, go to the Flexera Product Documentation website and select your FlexNet Manager Suite version from the VERSION drop down list. The file will now be listed and available for you to download.

Monthly updates are our minimum commitment. We may also provide additional updates from time to time based on customer demand. We will continue to send email alerts to announce each update.

Regards,

Team Content

ARL Content Change: Microsoft OneDrive classification and product consolidation

Content Library : ARL

Severity: Level 1. Tier1 Product Classification update

Impacted Publisher/Product: Microsoft OneDrive and OneDrive for Business

Expected Implementation: ARL release scheduled 6th Nov 2026

SUMMARY OF CHANGE

In the upcoming ARL update, Microsoft OneDrive releases will be classified as Commercial instead of Freeware, and OneDrive for Business 2022 will be consolidated into OneDrive 22. Microsoft uses the same OneDrive sync client and version numbers across personal and business environments, so this change will provide more consistent recognition and reporting. Refer : Microsoft OneDrive Sync Release Notes

DETAILS OF CHANGE

·      Classification update: OneDrive applications currently classified as Freeware will be changed to Commercial for all the versions present in ARL.

·      Product consolidation: OneDrive for Business 2022 will be merged into OneDrive 22. Existing recognition data for OneDrive for Business 2022 will map to OneDrive 22 after the update.

·      Reason for change: This update will make OneDrive product recognition and reporting more consistent across customer environments.

·      Recognition handling: Installations currently recognized as OneDrive for Business 2022 will be reported as OneDrive 22 after the update.

Records retained without change: The following records will not change:-

• legacy and pre-release on-premises versions, including OneDrive for Business 2016, 2019, 3.0, and 2013 Preview
• OneDrive for Office 365 products and plans
• OneDrive Mobile versions 2 through 6 and
• OneDrive Online for the Microsoft 365 SaaS application.

The table below lists each affected ARL record and its planned change

CUSTOMER IMPACT

·      Classification and reporting: The affected OneDrive releases will appear as Commercial instead of Freeware after customers receive the updated content library.

·      Normalization and recognition: Installations currently recognized as OneDrive for Business 2022 will appear as OneDrive 22 after the consolidation.

·      Existing records: OneDrive for Business 2022 records will move to OneDrive 22, and affected OneDrive applications will change from Freeware to Commercial. Products listed under “Records retained without change” are not affected.

·      License and entitlement: This update affects product classification and recognition only. It does not change license entitlements.

RECOMMENDED CUSTOMER ACTION

No customer configuration changes are required. After receiving the updated content library, customers should review reports, filters, dashboards, and integrations that rely on the classification and the OneDrive for Business 2022 product name.

For questions or suggestions about the listed OneDrive changes, please raise a support case with us and reference this content change notification for review. Thank you!

Understanding Oracle Java Evidence Processing and Recognition in the ARL

Oracle Java recognition can be complex because a Java installation may generate multiple types of software evidence. The same device may report file evidence for Java executables, installer evidence for JDK or JRE packages, and evidence created by another Oracle product that includes an embedded Java runtime.

The Application Recognition Library, or ARL, evaluates the available evidence to identify the applicable Java product, version, publisher and commercial classification while reducing duplicate or false-positive recognition.

This article explains the main evidence-processing principles used for Oracle Java.

Types of Java evidence

1) File evidence

File evidence is collected from Java executable files and their associated metadata. The primary executable patterns considered for Oracle Java recognition are:

• java.exe
• javaw.exe

The ARL assesses attributes such as:

• File and product version
• Product name
• File description
• Company or publisher
• Installation path

The java.exe executable may be present in both JDK and JRE installations. Therefore, an executable alone may confirm the presence of Java without always proving whether the installation is a standalone JDK, a standalone JRE, or Java embedded within another product.

The FlexNet Inventory Agent can also collect detailed file metadata when Oracle Java scanning is enabled, including the installation path, product name, publisher, Java version and related properties.

 2) Installer evidence

Installer evidence may be generated by:

• Native Java installers
• MSI or package-manager installations
• FlexNet Inventory Agent Java inspection
• Oracle Universal Installer, or OUI
• Another software product containing an embedded Java runtime

Installer evidence reported with the raw evidence type Java is collected after the FlexNet Inventory Agent locates a Java executable and runs supported Java version commands. Consequently, this evidence normally has corresponding Java executable file evidence

How the ARL determines the Java product

Java Platform

When the available file metadata identifies Java or Java Platform but does not reliably distinguish JDK from JRE, the evidence may be associated with Java Platform.

This provides visibility that Java is present while avoiding an unsupported assertion that the executable represents a separate JDK or JRE installation.

 Java Development Kit

Evidence is evaluated for JDK recognition when reliable attributes identify terms such as:

• JDK
• Java Development Kit
• JDK-specific product metadata

Beginning with Oracle JDK 11, Oracle no longer offers separate JRE or Server JRE downloads. Runtime capabilities are provided as part of the JDK distribution

 Java Runtime Environment

Evidence may be associated with JRE when reliable metadata identifies:

• JRE
• Java Runtime Environment
• A supported JRE installer pattern

JRE-specific mapping is generally applicable to Java 10 and earlier, subject to the evidence containing sufficient product and publisher information.

Publisher validation

Java is also distributed or repackaged by vendors other than Oracle. To reduce incorrect attribution:

• Evidence is mapped to Oracle Java only when the available publisher or file metadata supports Oracle attribution.
• Evidence clearly identifying IBM, SAP, Red Hat, BellSoft or another Java distributor should not be automatically attributed to Oracle.
• Evidence without reliable publisher or company information may be ignored or left unrecognised when the vendor cannot be established with sufficient confidence.
• Version patterns known to be associated with repackaged Java distributions are reviewed separately rather than automatically mapped to Oracle.

The current ARL guidance records that Java evidence without publisher or company information is ignored, and that certain repackaged version patterns require special handling.

This validation is important because identical or similar Java executable names may be used across different Java distributions.

Handling Oracle Universal Installer (OUI) Evidence

Oracle Universal Installer (OUI) evidence may be generated when Java components are installed as part of other Oracle products. As a result, the presence of OUI evidence does not necessarily indicate that Oracle Java was installed as a standalone product.

Examples of Oracle Java-related OUI evidence patterns include:

• Oracle.JDK
• Oracle.JRE
• Oracle.JDK Enterprise
• Oracle.JRE Enterprise

For example, Oracle.JDK and Oracle.JRE with evidence type OUI have been identified as patterns that can originate from Oracle product installations rather than an independent Java installation. To reduce false-positive Oracle Java recognition, Oracle Java evidence with evidence type OUI will be ignored in ARL.

Why is OUI evidence ignored?

Ignoring Oracle Java OUI evidence helps:

• Reduce false-positive recognition of Oracle JDK and JRE.
• Avoid recognising Java as a standalone installation based solely on evidence generated by another Oracle product.
• Ensure Oracle Java recognition is based on stronger evidence associated with the actual Java installation.

 Evidence that may be ignored

Java evidence may be ignored when it does not provide sufficient confidence for reliable recognition. Examples include:

• Evidence with no publisher or company information.
• Files that cannot be validated as Java product evidence.
• Known repackaged or vendor-specific patterns that must not be attributed to Oracle.
• Generic Oracle component evidence that does not establish a standalone Java installation.
• OUI patterns known to be generated by another Oracle product.
• Supporting executables that do not independently prove installation of the Java product.

Ignoring evidence means that the record is not used to recognise an ARL application. It does not remove the raw inventory evidence collected from the device.

What customers may see

As Java recognition rules are refined, customers may observe:

• A Java application being associated with a more appropriate publisher.
• Evidence moving between public and commercial Java applications after build-level validation.
• Duplicate JDK or JRE recognition being suppressed by precedence.
• OUI-based false-positive recognition being removed.
• Previously unrecognised Java evidence becoming recognised after ARL enrichment.
• Evidence remaining unrecognised when the publisher or product cannot be determined reliably.

Changes in recognised installation counts do not necessarily mean that software was installed or removed. They may result from improvements to evidence mapping, classification or application precedence.

Recommended customer actions

Customers investigating an Oracle Java recognition result should review:

• Application Transparency to identify the evidence contributing to recognition.
• The file path, publisher, product name, file version and evidence type.
• Whether both file and installer evidence exist for the same installation.
• Whether the Java runtime is standalone or embedded within another product.
• The latest ARL version available in their environment.

If evidence appears to be incorrectly mapped, submit a Flexera Support case with:

• The recognised application name and Flexera application ID.
• Exported installer and file evidence.
• The relevant device inventory or NDI file.
• The Java installation path.
• Output from java -version or equivalent vendor information, where available.
• Details showing whether Java was installed independently or supplied with another product.

This information enables Flexera to distinguish a content-mapping issue from incomplete, stale or ambiguous inventory data.

Important note : ARL recognition provides software inventory and normalization information. It does not determine whether an organization requires an Oracle Java licence or establish its contractual obligations. Customers should assess recognized installations against their applicable Oracle agreements and obtain appropriate licensing guidance where necessary.

FlexNet Manager Update: Application Recognition Library 2995 and Service Life Data Pack 840 are available

What's new in this release?

• Count of new applications added:
• Publishers renamed as list below:
• Microsoft SQL Sever 2025 bug fix - reference the following for more details: https://community.flexera.com/s/feed/0D5PL00000zsfG90AI
• BigFix Client recognition improvements.

Current Library Totals:

• Number of applications in ARL:  315,223 across 18,639 publishers.
• Number of commercial applications with service life dates:  99,327
• Number of evidence recognition rules: 3,592,804
  • Installer evidence rules:  2,373,935
  • File evidence rules:   1,215,121
  • WMI evidence rules: 1,727
  • Application suite evidence rules: 2,021

Details of changes in the ARL

You can inspect changes made in this ARL release as per the following links:

• List of new applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewApplicationsARL2995
• List of new versions of applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewVersionsARL2995
• List of new publishers added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewPublishersARL2995
• List of applications updated in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=UpdatedApplicationsARL2995
• List of Applications deleted in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=DeletedApplicationsARL2995
• List of applications Updated/Inserted with EOL in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=ListofApplicationswithServiceLifeDataPack840

Updating library data

FlexNet Manager Cloud: These updates will be installed before Monday, 26th October 2026

FlexNet Manager On-premises: This library release will be applied to your FlexNet Manager according to the schedule settings and processes configured for your instance. If your environment requires you to download and update library data manually, see the following article for guidance: Downloading the FlexNet Manager Suite Content Libraries manually.

You can inspect currently installed library versions using the FlexNet Manager Menu > System Health > System Health Dashboard menu option.

Upcoming ARL and Service Life Data Pack updates: We nominally expect the next ARL and Service Life Data Pack updates to be published on or around Friday, October 30th, 2026

Reporting issues with ARL and SLDP updates

Should you have any FlexNet Manager library data issues, please submit a case by logging in to the Flexera Community and selecting the Get Support > Open new case menu option.

We are interested in feedback on these announcements. If you have any questions or suggestions for improvements, please comment below. 

We trust you will find this update helpful and look forward to continually improving your application recognition results.

- Team Content

ARL Content Change: Classification Update for Microsoft 365Companions

Content Library : ARL

Severity: Level 3. Tier1 Product Classification update

Impacted Publisher/Product: Microsoft 365Companions

Expected Implementation: ARL release scheduled 02nd Nov 2026

SUMMARY OF CHANGE

Classification update for Microsoft 365Companions from Commercial to Component.

Microsoft documents Microsoft 365Companions as a suite of taskbar-integrated apps—People, Files, and Calendar—that works with Microsoft 365 services. The apps are intended for organizational use and rely on Exchange Online and SharePoint (OneDrive) Online. Users must have an eligible commercial Microsoft 365 license that includes both services. Microsoft 365Companions is not marketed as a separately purchasable standalone offering. Its use depends on the underlying licensed Microsoft 365 services.

DETAILS OF CHANGE

Flexera is updating the ARL classification from Commercial to Component to more accurately represent Microsoft’s documented product structure, licensing prerequisites, and service dependencies.

This change applies only to the classification of the product. All existing metadata, evidence linking, and product relationships will be retained. 

CUSTOMER IMPACT

After the update, customers will see the affected Microsoft 365Companions products classified as Component instead of Commercial in the ARL.

Customers may observe the new classification in:

• Custom reports and dashboards
• ARL exports
• Integrations that consume ARL classification data
• Automated workflows that use Product Classification as a filter

This ARL update aligns the product classification with Microsoft’s documented product structure, licensing prerequisites, and service dependencies.

RECOMMENDED CUSTOMER ACTION

Customers should review any custom reports, dashboards, ARL exports, integrations, or automated workflows that use the Classification or Product Classification attribute. No deployment or inventory changes are required solely because of this ARL update.

References:

Microsoft 365 companion apps overview

Get started with Microsoft 365 companions

For any additional queries or suggestions, please feel free to raise a support case with us, and we will be happy to review them. Thank you!

ARL Content Change: Microsoft SQL Server 2025 Application Recognition Bug Fix Update

Summary : We identified an issue affecting the recognition of Microsoft SQL Server 2025 applications, where multiple SQL Server 2025 editions may be recognized on a device instead of only the edition that is installed.

Issue : Following the addition of new WMI evidence for SQL Server 2025 applications in the previous content release (Build #2994, 19th October 2026), we identified that a setting required to consolidate application recognition from WMI evidence was not enabled.

As a result, the recognition criteria were broader than intended, which could cause multiple SQL Server 2025 editions to be recognized on the same device.

Resolution : We have enabled the required setting for the affected SQL Server 2025 applications. This correction will be included in the content release scheduled for 26 October 2026.

Following this update, recognition will be consolidated so that only the appropriate installed SQL Server 2025 application and edition is recognized.

Customer Impact : After applying the content release scheduled for 26 October 2026, customers should see corrected recognition behavior for the affected Microsoft SQL Server 2025 applications.

No additional customer action is required beyond applying the updated content release.

Thank you!

FlexNet Manager Update: Application Recognition Library 2994 and Service Life Data Pack 839 are available

What's new in this release?

• Count of new applications added:
• Broadcom product name update from Automic Automation Intelligence to Automation Analytics & Intelligence (AAI)

Current Library Totals:

• Number of applications in ARL:  314,887 across 18,627 publishers.
• Number of commercial applications with service life dates: 98,994
• Number of evidence recognition rules: 3,581,003
  • Installer evidence rules: 2,365,119
  • File evidence rules:   1,212,136
  • WMI evidence rules: 1,727
  • Application suite evidence rules: 2,021

Details of changes in the ARL

You can inspect changes made in this ARL release as per the following links:

• List of new applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewApplicationsARL2994
• List of new versions of applications added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewVersionsARL2994
• List of new publishers added: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=NewPublishersARL2994
• List of applications updated in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=UpdatedApplicationsARL2994
• List of Applications deleted in the release: https://flexera-esd.flexnetoperations.com/flexnet/operations/WebContent?fileID=DeletedApplicationsARL2994

Updating library data

FlexNet Manager Cloud: These updates will be installed before Monday, 19th October 2026

FlexNet Manager On-premises: This library release will be applied to your FlexNet Manager according to the schedule settings and processes configured for your instance. If your environment requires you to download and update library data manually, see the following article for guidance: Downloading the FlexNet Manager Suite Content Libraries manually.

You can inspect currently installed library versions using the FlexNet Manager Menu > System Health > System Health Dashboard menu option.

Upcoming ARL and Service Life Data Pack updates: We nominally expect the next ARL and Service Life Data Pack updates to be published on or around Friday, October 23rd, 2026

Reporting issues with ARL and SLDP updates

Should you have any FlexNet Manager library data issues, please submit a case by logging in to the Flexera Community and selecting the Get Support > Open new case menu option.

We are interested in feedback on these announcements. If you have any questions or suggestions for improvements, please comment below. 

We trust you will find this update helpful and look forward to continually improving your application recognition results.

- Team Content