Loading
  • Public
  • Broadcast OnlyThis group is for broadcast messages. Only group managers can post content.

Technopedia Blog

Skip Feed
  1. NMallikarjun_E (Flexera Software)

    Title: Manufacturer Name Change for NCR Legacy Products from NCR Voyix to NCR Atleos

     

    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.

     

    Summary

    NCR Voyix to NCR Atleos

     

    Proposed change:

    Before 2023, NCR Corporation’s ATM and self-service banking businesses were part of NCR Corporation. In 2023, the business was separated into NCR Atleos and NCR Voyix:

    • NCR Atleos: ATM, self-service banking, payments/network, and related financial technology businesses.
    • NCR Voyix: Digital-commerce business, primarily covering retail, restaurants, POS, and digital banking

    Based on this business-segment separation, the following legacy products are aligned with the ATM, self-service banking, and banking-processing business under NCR Atleos. Hence Flexera plans to update the publisher for the below five products from NCR Voyix (Manufacturer ID : 488145) to NCR Atleos (Manufacturer ID : 2005542294).

    • APTRA Advance NDC
    • APTRA Exchange
    • APTRA Edge
    • ImageMark NCompass
    • WiseIP

    image 2image 1Corresponding product records will be created under NCR Atleos, and all applicable releases and related dependencies will be migrated and aligned accordingly. Following successful migration and validation, the existing product records under NCR Voyix will be deleted.

    Ref:https://www.ncratleos.com/news/ncr-deploys-multivendor-atm-software-in-under-45-days

    https://www.ncratleos.com/news/ncr-completes-inidas-largest-electronic-cheque-truncation-project-npci , https://www.ncratleos.com/about-us/separation-update

    Note: For WiseIP Product, no current product information is available on the vendor’s website or other online sources. As WiseIP is used for banking purposes, we concluded that it should be created under NCR Atleos to maintain alignment between ARL and TNP.

     

    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.

    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 are included in the spreadsheet to help manage downstream processes and organizational reporting

    The spreadsheet “NCR Voyix to NCR Atleos” provides details of the Five selected products for which the manufacturer will be changed from “NCR Voyix” to “NCR Atleos”.

     

    Timeframe: 

    Expected Time to Implementation (ETA): 3rdth Dec to 10th Dec 2026.

     

    Thank you

    Namrata

    Expand Post

  2. NMallikarjun_E (Flexera Software)

    Title: Product Bulletin Retention under HPE and Removal of Duplicate HP Product

     

    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: HP(Tier 1), HPE (Tier 1)

     

    Summary

    Product Bulletin is currently maintained under both HP and HPE, resulting in duplicate Products. Following the 2015 separation of the original Hewlett-Packard company into HP Inc. and Hewlett Packard Enterprise (HPE), the official vendor documentation identifies Product Bulletin under HPE rather than HP

     

    Therefore, Flexera plans to retain Product Bulletin (Product ID: 328705726) under HPE.

    we will remove the existing Product Bulletin lineage under HP and link the former product to the retained Product Bulletin product under HPE. After the implementation and dependencies are moved to the current HPE product, the duplicate Product Bulletin under HP will be deleted.

    Ref:https://h41370.www4.hpe.com/quickspecs/pdfs/HPE_Product_Bulletin_User_Guide.pdf?ver=2

     

    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.

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

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

    The spreadsheet “HP Product Bulletin to HPE Product Bulletin” provides all the software products, releases for which the publisher’s name will be Updated to “HP Product Bulletin” to “HPE Product Bulletin”.

     

    Timeframe: 

    Expected Time to Implementation (ETA):3rd Dec to 10th Dec 2026.

     

    Thank you

    Namrata

    Expand Post

  3. Title: Manufacturer Rename: Elasticsearch to Elastic

    Content Library: Technopedia

    Severity: Level 1 – Tier 1 Manufacturer product and mapping changes

    ETA: November 23, 2026 and November 27, 2026.

    Impacted Publisher/Product: Elasticsearch

     

    SUMMARY OF CHANGE

    Elasticsearch has been renamed to Elastic.

    Through internal quality assessments and in response to customer requests, Flexera identified that the manufacturer Elasticsearch has been renamed to Elastic. As a result, Flexera will update the manufacturer lineage for the affected product releases and mappings, transitioning them from the previous manufacturer name, Elasticsearch, to the new manufacturer name, Elastic.

    For details about the name change, refer to the following announcement:

    https://www.elastic.co/about/press/elasticsearch-changes-name-to-elastic-to-reflect-wide-adoption-beyond-search

     

     

    CUSTOMER IMPACT

    This change affects customers who rely on Technopedia Product IDs, Release IDs, and names. Data previously associated with the old manufacturer will now be linked to the new manufacturer. Customers should review and update any downstream processes and reports within their organization that depend on this data.

    The spreadsheet “ElasticSearch to Elastic” lists all products, releases, and mappings that will move from the old manufacturer (ElasticSearch) to the new manufacturer (Elastic).

     

    ATTACHMENTS

    Please find attached workbooks with mapping details.

     

    NOTE: For any queries or suggested changes on this Notification, please raise a Support ticket with us at https://community.flexera.com/s/support-hub and highlight this article for reference.

     

    Thank you.

    Expand Post

  4. Title:Microsoft Teams Classic v1.0 – Ignore/Irrelevant

     

    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.

    Manufacturer: Microsoft(Tier 1)

     

    Summary

    Microsoft Teams Classic v1.0 evidence to be ignored

    Based on internal quality assessments, Flexera determined that Microsoft Teams Classic v1.0 evidence should be ignored in Technopedia.

    Key Findings:

    ·       Official Microsoft Teams Classic releases use version formats such as 1.6.00.xxxxx and 1.7.00.xxxxx.

    ·       Microsoft’s official Teams version history includes no Teams Classic releases numbered 1.0, 1.00, 1.0.0.0, 1.0.0.1, or 1.0.0.2.

    ·       Versions reported as 1.0 or 1.0.0.x typically originate from:

    ·       Windows provisioning packages

    ·       MSIX/Store package registrations

    ·       Operating system component entries

    ·       Migration components from the Classic-to-New Teams transition

    ·       Inventory and discovery tools may detect these entries, but they do not reflect the actual installed Teams Classic version.

    For versioning details, refer to:

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

    The following mapping rules will apply to discovered Microsoft Teams Classic versions:

    ·       Versions in the 1416/1.x format will map to Microsoft | Teams Classic | 1.0, as this is a valid mapping.

    ·       Versions 1.1 to 1.8 will continue to map to Microsoft | Teams Classic | 1.1 to 1.8, as these are valid per Microsoft guidance.

    ·       Versions 1.0, 1.00, and 1.0.0.x (e.g., 1.0.0.0, 1.0.0.1, 1.0.0.2) will be ignored. These are placeholder or package registration entries, not actual Teams Classic releases.

     

    Impact

    Customers who rely on Technopedia Product IDs, Release IDs, and names will be affected by this change. Data previously associated with the old product will now be marked as Ignore/Irrelevant. Customers should adjust their downstream processes and reports accordingly.

     

    All affected mappings, including Product and Release IDs, that will be updated to Ignore/Irrelevant are listed in the spreadsheet “Microsoft Teams Classic V1.0 To Ignore or Irrelevant”.

     

    Timeframe

    Expected Time to Implementation (ETA): on Nov 23, 2026.

     

    Thank you

     

    Expand Post

  5. Title: Manufacturer Name Standardization-BMC to BMC Helix

     

    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.

    Manufacturer: BMC (Tier 1), BMC Helix(Tier 3)

     

    Summary

    BMC to BMC Helix

    The manufacturer mapping for selected products is being updated from BMC to BMC Helix to reflect their current placement within the BMC Helix product portfolio.

    Hence Flexera is planning to standardize the manufacturer name from BMC to BMC Helix. This change is being initiated with below five products as part of the broader BMC Helix manufacturer name standardization.

    1.Client Management Client.

    2.Knowledge Management Express.

    3.Client Management Console.

    4.Digital Workplace.

    5.Client Management Master.

    As part of this change, the manufacturer BMC Helix (Manufacturer ID: 1988536991) will be replaced with BMC (Manufacturer ID: 4976) for these above products. All associated versions and dependency mappings will be migrated to BMC Helix.

    Once the migration is successfully completed and validated, the corresponding product records currently associated with BMC will be removed.

    Ref:  https://www.helixops.ai/  

    BMC Helix Digital Workplace | BMC Helix

    BMC Client Management - BMC Helix Documentation

    Modifying product categorization attributes - BMC Helix Documentation

     

    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.

    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 are included in the spreadsheet to help manage downstream processes and organizational reporting

    The spreadsheet BMC to BMC Helix provides the complete list of all the software products for which the publisher’s name will be renamed from “BMC” to “BMC Helix”.

     

    Timeframe

    Expected Time to Implementation (ETA): 1st Dec to 4th Dec 2026.

     

    Thank you

    Expand Post

  6. Title: Manufacturer Name Change from Cohesity to Arctera for few products.

     

    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.

    Manufacturer: Cohesity (Tier 3), Arctera (Tier 3)

     

    Summary

    Based on our analysis, the manufacture needs to be updated from Cohesity to Arctera for the following products.

    1) Cohesity | InfoScale | Operations Manager | Managed Host PID-2058849460

    2) Cohesity | InfoScale Availability PID-2058849718

    3) Cohesity | InfoScale Enterprise (InfoScale Enterprise) PID- 2058849725

    4)Cohesity | InfoScale Foundation PID- 2058849744

    5)Cohesity | InfoScale Storage PID- 2058849772

    6)Cohesity | Cluster Server Enterprise Agents PID- 2058848818

    7)Cohesity | File System PID-2058848352

    8)Cohesity | File System Software Developer Kit (VRTSfssdk) PID- 2058848359

    9)Cohesity | License Utilities PID- 2058847181

    10) Cohesity | Perl for VERITAS PID-2058847517

    11)Cohesity | Perl for VERITAS Cluster Server PID- 2058847137

    This is all about to update the manufacturer for the products listed above from Cohesity (which is under Veritas) to Arctera.

    We have also consulted the ARL team, and they are prepared to make the required changes on their end.

    Flexera will migrate all associated products, releases, and mappings from the old manufacturer, Cohesity, to the new manufacturer, Arctera.

    https://www.arctera.com/press-releases/arctera-completes-separation-from-veritas-technologies

     

    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 “Cohesity to Arctera Manufacturer” provides the complete list of software products for which the product name will be renamed from “Cohesity to Arctera”.

     

    Timeframe

    Expected Time to Implementation (ETA): November 18th – 25th,2026.

     

    Thank you

    Expand Post

  7. Title: Manufacturer Name Standardization: Mettler-Toledo International to METTLER TOLEDO

     

    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.

    Manufacturer: Mettler-Toledo International (Tier-3)

     

    Summary

    Mettler-Toledo International to METTLER TOLEDO

    Flexera is planning to Update the manufacturer name from Mettler-Toledo International to METTLER TOLEDO, as METTLER TOLEDO is the globally recognized market name. The duplicate manufacturer Mettler-Toledo International (Manufacturer ID: 8748171) will be replaced with METTLER TOLEDO (Manufacturer ID: 1125706543). All associated Software & Hardware products and dependency mappings will be migrated to METTLER TOLEDO, and the duplicate Mettler-Toledo International manufacturer record will be deleted after the migration is completed.

    Ref: https://www.mt.com/us/en/home.html

     

    Impact

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

    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 spreadsheet Manufacturer Name Standardization: Mettler-Toledo International to METTLER TOLEDO provides the complete list of all the software & hardware products for which the publisher’s name will be renamed from “Mettler-Toledo International” to “METTLER TOLEDO”

     

    Timeframe

    Expected Time to Implementation (ETA): 19th to 26th Nov 2026.

     

    Thank you

    Expand Post

  8. Title: Software Version Order Correction 

     

    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

    Flexera is updating version order information in the Technopedia catalog as part of an ongoing data quality initiative to address sequencing inconsistencies and improve version data accuracy and consistency. Flexera will implement these updates in batches.

    As part of the first batch, Flexera has reviewed approximately 1,962 products covering 88K+ releases and identified 25,636 releases requiring version order corrections.

     

    Impact

    This change may impact customers who rely on Technopedia version information for normalization, reporting, integrations, or downstream processes.

    The attached spreadsheet “Version Order Correction - Product & Release Information.xlsx” contains the list of impacted products corresponding to version order updates.

    Existing Manufacturer IDs, Product IDs, and Release IDs will remain unchanged. Only the Version Order will be updated; Catalog IDs and existing mappings will not be impacted.

     

    Timeframe

    Expected Time to Implementation (ETA): November 16th onwards.

    For detailed implementation dates, please refer to the following report:

    Timeframe for Completion 

    Thank you.

    Expand Post

End of Feed
End of Feed
8 Chatter Feed Items
Loading
Group: Technopedia Blog