Title: Standardizing Microsoft Windows and Windows Server Product Modeling in Technopedia

Class1 Customer Action Recommended

Major updates that introduce new or modify existing content to change the behavior of existing product features or deprecate any existing content (along with the associated product features), which may require customers to make necessary adjustments beforehand.

Overview

To better align Technopedia with Microsoft's product strategy and maintain consistency across Flexera content catalogs, we are updating how Microsoft Windows and Windows Server products are represented in Technopedia.

Historically, major Windows and Windows Server versions were modeled as separate products. Example- Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, etc. As Microsoft continues to evolve these offerings under broader product families, this approach may create challenges for customers managing upgrades, migrations, reporting, and normalization consistency.

Technopedia will now adopt a standardized product model where supported Windows and Windows Server versions are represented under a single product hierarchy while preserving release-level granularity.

Key Benefit - This change establishes a vendor-aligned and catalog-consistent model for Microsoft Windows and Windows Server products while preserving detailed release-level visibility and improving long-term maintainability across Technopedia. 

Scope of change

• Windows - Windows 10, Windows 11 and all future Windows releases
• Windows Server - Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025 and all future Windows Server releases
• All Windows and Windows Server versions released prior to the versions listed above will continue to remain unchanged in Technopedia. 

What is Changing?

Microsoft Windows

Windows 10 and Windows 11 product records will be aligned to a single Microsoft Windows product (Product ID 950963). Existing releases, mappings, and recognized software data will be migrated to the consolidated product structure while retaining detailed release identification.

Microsoft Windows Server

Windows Server 2016, 2019, 2022, and 2025 product records will be aligned to a single Microsoft Windows Server product (Product ID 50896947). Calendar-year-based product names will be represented through version groups and releases rather than separate products.

Release Representation

To preserve release-level precision, releases will use a standardized naming approach based on: Internal Version + Build Number + Microsoft Release Designation . Example-

• Windows: 10.0.10240 (1507)
• Windows Server: 10.0.14393 (1607) under Version Group 2016

Current vs. Future Catalog Structure

Current catalog model: 

 

Future catalog model:

Catalog transformation example for Windows :

Catalog transformation example for Windows Server :

Evidence and Mapping Changes

Existing normalized mappings and recognized application data will be remapped to the newly curated release structure. Customers may observe updates to Product IDs, Release IDs, Product names, Release names, Normalization results.

Windows mapping example:

Windows Server mapping example:

Additional Data Quality Improvements

As part of these updates, we are also addressing a small number of catalog inconsistencies:

Windows

• Consolidation of Windows 10 LTSB and non-LTSB blank-version releases for builds 1507, 1607, 1809.
• Removal of Windows 11 early-build releases intended for Microsoft’s early testing purposes.
• Removal of duplicate Windows 11 releases using non-standard internal version numbering.

Windows Server

• Exclusion of MultiPoint Premium Edition releases that have no dependent catalog or mapping data.
• Lifecycle data alignment across supported release channels Semi-Annual channel (SAC), Annual Channel (AC), and Long-Term Servicing Channel (LTSC) 

Impact to Customers

This change affects both Catalog representation and Normalized evidence mappings.

Customers should review any integrations, reports, automations, or operational processes that refers to:

• Windows 10, Windows 11 Product IDs
• Windows Server 2016/2019/2022/2025 Product IDs
• Associated Release IDs
• Product or release names

Customer Actions

We recommend that customers:

• Review dependencies on Windows and Windows Server Product IDs and Release IDs.
• Validate reports, dashboards, and downstream integrations after deployment.
• Update any custom logic or automation that references retired product identifiers.
• Verify normalization results in environments that consume Technopedia content.

Attached are two detailed spreadsheets with current vs future information for Windows and Windows Server updates.

Timeline & Support

Planned release window is August 17–21, 2026. Customers should complete validation activities after the deployment window to ensure dependent processes continue operating as expected.

In case of any queries, please raise a support case.

Title:

Correcting inconsistencies within Technopedia for Microsoft ASP.NET Core evidence

Class 1

Major updates that introduce new content to support new product features/capabilities, modify existing content to change the behavior of existing product features/capabilities, or deprecate any existing content (along with the associated product features/capabilities), which require all customers to make necessary adjustments beforehand

Summary

We are rectifying the inconsistencies for Microsoft ASP.NET Core evidence

Previously, this evidence was mapped to Microsoft ASP.NET Core in Technopedia, but Microsoft ASP.NET Core does not have a separate standalone installer for development. Instead, it comes with ASP.NET Core Runtime, ASP.NET Core Hosting Bundle, and .NET SDK (which includes ASP.NET Core components).

 So we have decided to capture this evidence under the ‘ASP.NET Core Runtime’ product.

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names, or who previously discovered data mapped to the old product, which will be mapped to the new product. The change requires the customer to manage downstream processes and reporting in their organization.

Note:

·      As part of the new CCN process, releases with the updated name have already been created in Technopedia.

·      The migration of discovered data mappings will occur after 1, 2, or 4 weeks, depending on the CCN type. For this case, it will be one week.

·      Accordingly, the new release IDs are included in the spreadsheet to help manage downstream processes and organizational reporting

The new changes will have an impact on both the catalog and evidence mapping levels, as there will be updates/deletions at the existing catalog level that directly impact the existing normalized Mappings.

The details of these Sample evidence, products, and releases are provided in the attachment.

Timeline

The expected Time for Implementation (ETA) is August, 6th 2026.

Thank you.

Title

Correcting inconsistencies within Technopedia for Figma Agent installer evidence

Class 3

Minor updates as a result of "Business-As-Usual (BAU)" activities, which historically cause no adverse impact on customers' environments except for coverage increases.

Summary

We had an inconsistency in the recognition of the “Figma Agent,” which will now be unmapped in Technopedia discovery. 

Currently, Installer evidence for “Figma Agent” was recognized as the product “Figma” (PID: 511203667). Figma Agent is a background helper service that enables local machine integrations (such as local fonts and file access) for the desktop application and should be considered a supporting component within the Figma ecosystem. It does not have a distinct installation that can be identified independently, which informed our decision to mark this as irrelevant in Technopedia.

Along with ignoring Figma Agent discovery, we are also implementing the following changes:

Figma is the primary collaborative design platform, while Figma Desktop is its native Windows/macOS client and not a separate product. The desktop application provides the same functionality as the web version and connects to the same Figma service. Desktop version numbers represent releases of the installed client only and do not indicate a separate product or licensing model. Therefore, Figma should be treated as the parent product. We are maintaining only Figma (PID: 511203667), with both web and desktop versions maintained under the same application, and removing the product Figma Desktop (PID : 1326583853), as it's simply an access client for the Figma platform.

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names, or previously discovered data mapped to the old manufacturer will be mapped to the new manufacturer. The change requires the customer to manage downstream processes and reporting in their organization.

Timeframe

The expected Time for Implementation(ETA) is between July 27th and 30th.

Thank you.

Title: Oracle Product Name Changes – Four Products Renamed

Class 2- Minor Update

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Manufacturer: Oracle (Tier1)

Summary

As part of the Oracle product portfolio review,the following Oracle products will be renamed to their corresponding WebCenter product names:

OLD PID:Content Server(PID 1265233)

NEW PID:WebCenter Content Server(PID 863569648)

OLD PID:Imaging and Process Management(PID 1265141)

NEW PID:WebCenter Imaging (PID38570848)

OLD PID:Universal Records Management(PID 1265103)

NEW PID:WebCenter Content: Records(PID 44962566)

OLD PID:Desktop Integration Suite(PID 1288872)

NEW PID:WebCenter Content: Desktop(PID915543629)

To ensure consistency and avoid mapping discrepancies, Flexera will migrate all associated releases, mappings, and related data from the legacy products to the corresponding new products.

This update reflects Oracle's current product naming conventions and product lineage as documented in Oracle WebCenter Content documentation: Oracle WebCenter Content Installation and Configuration

Impact

This change will impact on customers who rely on Technopedia Product ID/Release ID & Names or previously discovered data mapped to the old manufacturer will be mapped to the new manufacturer. The change needs the customer to manage downstream processes and reporting in their organization.

The spreadsheet “Oracle 4 products rename changes” provides the complete list of software products for which the product name will be renamed.

Timeframe: 

Expected Time to Implementation (ETA): August 3, 2026 – August 7, 2026

Thank you

Title: Microsoft Teams Classic – Lifecycle Date Update and EOL Clarification

Class 2- Moderate updates

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Manufacturer: Microsoft (Tier1)

Change Summary

As part of a review of Microsoft Teams Classic lifecycle information, a discrepancy was identified between Microsoft's published end-of-availability guidance and subsequent product releases.

Based on Microsoft’s official lifecycle guidance, support for the Classic Teams client ended on July 1, 2024. Microsoft also states that the end of availability for the Classic Teams client began on July 1, 2025, meaning the client should no longer be available after that date.

Reference: https://learn.microsoft.com/en-us/lifecycle/products/microsoft-teams

https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability#:~:text=As%20of%20July%201%2C%202025,client%20is%20no%20longer%20available

Observed Discrepancy

Despite the published end-of-availability guidance, Microsoft released Microsoft Teams Classic version 1.8 in August 2025. This appears inconsistent with the previously stated lifecycle timeline and creates uncertainty about how lifecycle dates should be applied to later Classic Teams releases.

Reference: https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning

Problem Statement

Because the vendor documentation contains conflicting information, it is unclear which lifecycle guidance should be followed for Microsoft Teams Classic. This creates uncertainty in determining the correct EOL dates and applying lifecycle status consistently across Classic Teams releases.

Action Taken

To address the conflicting vendor statements, Flexera will apply the following approach in Technopedia:

• Microsoft Teams Classic versions up to 1.7 will have an EOL date of July 1, 2025.
• Microsoft Teams Classic version 1.8.x and later will be marked as (Date not published by vendor). since no EOL date has been publicly published by Microsoft and the last known patch release (1.8.00.21151) was released on 08/06/2025, we have decided to update the EOL status for version 1.8.x as "Date Not Published by Vendor". As a result, the EOL date will be displayed as blank to customers.

This approach aligns with the currently published vendor documentation while accounting for the discrepancy between Microsoft’s lifecycle announcements and the later release of version 1.8.

Flexera will update the EOL dates in Technopedia based on the approach outlined above.

Impact

Customers using Technopedia lifecycle data for compliance, reporting, or asset management may observe updated EOL information for Microsoft Teams Classic releases. Versions up to 1.7 will reflect the published end-of-availability date, while newer 1.8.x releases will be marked as Not available with date not published by vendor exception.

This change is intended to align Technopedia with currently available Microsoft documentation while accounting for the conflicting lifecycle information.

The spreadsheet Microsoft Teams Classic provides the complete list of all the versions for which the EOL will be changed.

Timeframe

Expected Time to Implementation (ETA): July 28th to 31st July.

Thank you

Title: Deletion of IBM MQ and maintaining IBM MQ Server

Class 2- Minor Update

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Manufacturer: IBM (Tier1)

Summary

As part of an ongoing Technopedia (TNP) product portfolio review and customer-requested data quality improvements, the IBM MQ product entry will be deleted from the catalog, while IBM MQ Server will continue to be maintained as the active and supported product. This change removes redundant or less relevant catalog content and ensures that IBM MQ-related inventory is consistently represented under the appropriate IBM MQ Server product entry. The update improves catalog accuracy, reduces ambiguity, and provides a clearer product structure for inventory management and reporting.

And the mapping will be followed as below:

IBM MQ Client → when Client component is explicitly identified.

IBM MQ Server → default component when component information is missing or unspecified.

https://www.ibm.com/docs/en/was/9.0.5?topic=settings-mq-server

Impact

This change will affect customers who rely on Technopedia Product IDs, Release IDs, product names, and existing mappings associated with IBM | MQ. Following implementation, all existing mappings currently linked to IBM | MQ will be migrated to IBM | MQ | Server. As a result, customers should review and validate any downstream processes, integrations, reporting, or custom references that depend on the existing product structure.

The attached spreadsheet, "IBM MQ To IBM MQ Server", provides the complete list of impacted products, releases, and mappings that will be transitioned from IBM | MQ to IBM | MQ | Server as part of this change.

Timeframe: 

Expected Time to Implementation (ETA): July 27th, 2026 to July 30th, 2026.

Thank you

Title

Removal of "Advanced Security Option (ASO)" String and Standardization to Advanced Security

Class 2

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Summary

Flexera will update all releases and mappings from Oracle Database Advanced Security (Advanced Security Option, ASO) to Advanced Security. The additional text "(Advanced Security Option, ASO)" is being removed from the product name because it is an alternate name for the same Oracle product and does not indicate a separate offering.

Previously, the product was maintained as Advanced Security (Advanced Security Option, ASO). To standardize product naming and align with market terminology, the product will now be maintained as Advanced Security

Reference: https://docs.oracle.com/en/database/oracle/oracle-database/19/jjdbc/client-side-security.html#GUID-45DF369A-3C7E-4D4F-8432-B8A44961DC58

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names, or previously discovered data mapped to the old product will be mapped to the new product. The change requires the customer to manage downstream processes and reporting in their organization.

Note:

->  As part of the new CCN process, releases with the updated name have already been created in Technopedia.

-> The migration of discovered data mappings will occur after 1, 2, or 4 weeks, depending on the CCN type. In this case, it will be one week.

-> Accordingly, the new release IDs are included in the spreadsheet to help manage downstream processes and organizational reporting

The attached spreadsheet provides a complete list of software products and releases impacted by the product name change from “Oracle Database Advanced Security (Advanced Security Option, ASO) to Advanced Security including detailed information for each updated product.

Timeframe

Expected Time to Implementation (ETA):  July 14th, 2026.

Thank you.

Title

Technopedia Release Lifecycle Dates Update

Class 2

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Summary

Flexera is updating Release Lifecycle dates for 118 releases in Technopedia. The details are mentioned in the attached spreadsheet.

Impact

This change will impact Technopedia customers (including Flexera One, IT Visibility, and Data Platform customers) who rely on Lifecycle dates to manage their EOL and EOS/OBS programs, and customers who rely on Technopedia Product ID/Release ID & Names and have previously mapped data to these Releases.

Timeframe

Expected Time to Implementation (ETA):  July 13th, 2026.

Thank you.