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.