Title

Standardization of Ghostscript Product Name with Edition Classification (GPL, AFPL, ESP)

Class 2

Moderate updates, which bring significant changes in the customer's environment and potentially adverse impact on some customers' environments, had they not been anticipated and necessary adjustments made beforehand

Summary

Flexera will update all releases and mappings from products “GPL Ghostscript, AFPL Ghostscript, ESP Ghostscript” to the single product “Ghostscript” under different editions ‘GPL, GPL Lite, AFPL, and ESP’.

Previously, Products such as GPL Ghostscript, AFPL Ghostscript, and ESP Ghostscript were maintained as separate products.

However, these labels represent different licensing terms of the same underlying product—Ghostscript—not distinct products themselves.

Hence, we are capturing dependencies under the editions (GPL, GPL Lite, AFPL, and ESP).

Reference link: https://ghostscript.com/

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. 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 attached spreadsheet provides a complete list of software products and releases impacted by the product name change from “GPL Ghostscript, AFPL Ghostscript, ESP Ghostscript” to Ghostscript(GPL, GPL lite, AFPL, ESP) including detailed information for each updated product.

Timeframe

Expected Time to Implementation (ETA):  June 16th 2026.

Thank you.

Title

Mapping correction within Technopedia for Lakeside Software Systems Management Agent evidence

Class 3

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

Summary

Flexera will correct all evidence related to the Systems Management Agent. Previously, this evidence was mapped to the SysTrack product, which represents the main application. However, based on a detailed analysis, it was determined that this evidence corresponds to the SysTrack Agent product rather than the main application.

Since the agent component is a separate application from the main SysTrack product, the evidence should be mapped accordingly. As a result, the mappings are now being updated to associate this evidence with the SysTrack Agent product instead of the main application.

Reference link: https://documentation.lakesidesoftware.com/docs/agent-installers

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID mapping on the Microsoft SharePoint data. This change will require customers to manage downstream processes and reporting within their organizations.

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 attached Spreadsheet Proposed Sample List provides a list of all software mappings. “Lakeside Software Systems Management Agent” will be updated to “Lakeside Software Systrack Agent” Product. This includes the new release details for the updated mappings.

Timeframe

Expected Time to Implementation (ETA):  June 16th 2026.

Thank you.

Title

Mapping correction within Technopedia for Google Drive 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) require all customers to make the necessary adjustments in advance.

Summary

Flexera will correct evidence related to Google Drive, Backup and Sync, and Drive File Stream based on product evolution and version patterns.

Initially, Google Drive transitioned into Backup and Sync. During the same timeline, Drive File Stream was also introduced as a separate product. At that stage:

-> Google Drive evidence was effectively represented as Backup and Sync.

-> Drive File Stream existed independently for enterprise use cases.

Later, Google merged Backup and Sync and Drive File Stream into a unified product called Google Drive for Desktop.

Based on detailed analysis of version patterns:

Evidence with version patterns up to version 44 that align with Google Drive or Backup and Sync usage will continue to be maintained as Backup and Sync.

-> Evidence that specifically matches Drive File Stream patterns up to version 44 will continue to be maintained as Drive File Stream.

-> From version 45.0 onwards, where product overlap and consolidation occurred, all evidence will be mapped to Google Drive for Desktop (latest product).

-> Evidence with null, blank, unknown, invalid discovered versions, build-level information will be mapped at the product level to Google Drive for Desktop, to ensure consistent and future-aligned classification.

Reference links:

https://en.wikipedia.org/wiki/Google_Drive

https://knowledge.workspace.google.com/admin/drive/google-drive-for-desktop-release-notes

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. 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 attached spreadsheet “Proposed Sample List “provides a complete list of Backup and Sync, Drive File Stream, and Drive for Desktop, including detailed information for each updated product.

Timeframe

Expected Time to Implementation (ETA):  June 23rd 2026.

Thank you.

Title

Mapping correction within Technopedia for Microsoft Outlook for Windows 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) require all customers to make the necessary adjustments in advance.

Summary

Flexera will rectify all evidence related to Microsoft Outlook and Outlook for Windows with version pattern 1.2024.618.200 and 1.2025.213.300. Previously, this evidence was mapped to Microsoft Outlook.

In 2022, Microsoft introduced a new version of Outlook called Outlook for Windows (new Outlook). The Outlook remains active and is not discontinued.

Based on detailed analysis, it has been identified that version patterns follow formats such as 1. year.x (e.g., 1.2025.x) and extended numeric build patterns (e.g., 20250116064.16) are associated with Outlook for Windows (new Outlook). Earlier, this evidence was not consistently distinguished from the classic Outlook version, resulting in incorrect mappings. To ensure accurate product classification, all evidence that matches these version patterns will now be mapped to Outlook for Windows rather than Microsoft Outlook (Classic). The mappings are being updated accordingly to maintain correct product association.

Reference links:

https://learn.microsoft.com/en-us/officeupdates/release-notes-outlook-new#january-28-2025

https://apps.microsoft.com/detail/9nrx63209r7b?hl=en-US&gl=US

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID mapping on the Microsoft SharePoint data. This change will require customers to manage downstream processes and reporting within their organizations.

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 attached spreadsheet Proposed Sample list contains “Microsoft Outlook for windows “ and Microsoft Outlook “provides some lists of all software mappings that will be updated for “Microsoft outlook for windows”.

Timeframe

Expected Time to Implementation (ETA):  June 23rd 2026.

Thank you.

Title

Mapping Changes- Microsoft .Net Runtime to Microsoft .Net Desktop Runtime

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 Mappings of the discovered data Microsoft Windows Desktop Runtime from product name “Microsoft .Net Runtime to Microsoft .Net Desktop Runtime” to align with the vendor naming convention.

Reference Link: https://dotnet.microsoft.com/en-us/download/dotnet/10.0

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:

->      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 two weeks.

->   Accordingly, the New Mappings are included in the spreadsheet to help manage downstream processes and organizational reporting.

The attached spreadsheet provides the complete list of all the AR Mappings for which the product name will be updated from “Microsoft .Net Runtime to Microsoft .Net Desktop Runtime”. This includes the new mapping details for the updated product name.

Timeframe

Expected Time to Implementation (ETA):  June 24th 2026.

Thank you.

Title:

Product update- McAfee Data Exchange Layer (DXL) to Trellix Data Exchange Layer (DXL)

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, Components, and Mappings from “McAfee Data Exchange Layer (DXL) to Trellix Data Exchange Layer (DXL)” to align with the vendor naming convention. With respect to Add/Remove Mappings, evidence is mapped to the Data Exchange Layer Client, and this will be appropriately mapped to the Trellix Data Exchange Layer.

Ref Link: https://www.bytes.co.uk/info/industry/introducing-trellix-mcafee-rebrand

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. For this case, it will be two weeks.

->     Accordingly, the New Release IDs and mappings are included in the spreadsheet to help manage downstream processes and organizational reporting.

The attached spreadsheet provides the complete list of all software products, releases, and AR Mappings impacted by the Manufacturer name from “McAfee Data Exchange Layer (DXL) to the Trellix Data Exchange Layer (DXL). This includes the new mapping details for the updated product name.

Timeframe

Expected Time to Implementation (ETA):  June 24th 2026.

Thank you.

Title: Adobe Acrobat Versioning Updates

Class 3

Customers should be prepared and take action.

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

Summary

->   Versioning will follow major. Minor granularity will be used moving forward (for example: 24.001, 24.002, 24.003, 24.004, 24.005, 25.001, 26.001), and mapping activities will also align with the same version granularity.

-> The versioning changes are being made because multiple date variations can be observed on the website for different Adobe Acrobat releases. Due to these variations, mapping broadly under 24.x (continuous) would not provide the required granularity. Therefore, versions such as 24.0.01 and 24.0.02 are being maintained separately to ensure more accurate version mapping and evidence alignment. Based on this, we have decided to update the Adobe Acrobat versioning structure accordingly.

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names. 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.

The attached spreadsheet provides the details.

Timeframe

Expected Time to Implementation (ETA):  June 8th to 26th

Thank you.

Title: Manufacture Name Update -  Veritas to Cohesity

Class 3

Customers should be prepared and take actions

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

Summary

Based on our analysis, the manufacturer needs to be updated from Veritas to Cohesity. All Veritas products and releases should be moved under Cohesity.

Flexera will also migrate all associated products, releases, and mappings from the former manufacturer, Veritas, to the new manufacturer, Cohesity.

Ref Link: Cohesity Becomes World’s Largest Data Protection Software Provider After Completing Combination with Veritas’ Enterprise Data Protection Business

These changes are being implemented to ensure alignment across both ARL and Technopedia (TNP) environments and to avoid any mapping issues.

Impact

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

The spreadsheet “Veritas to Cohesity“ provides the complete list of software products for which the product name will be renamed from “Veritas to Cohesity”

Timeframe

Expected Time to Implementation (ETA):  June 22nd to 26th

Thank you.