Change Title Adding Virtual models to Virtual subcategories Class 3 Customers should be prepared and take actions Change Summary In Technopedia, we do not have any virtual models under Hardware Virtual categories. To fill this gap, we are planning to include at least one virtual model ID for a few products under virtual categories.   Additionally, we are going to revisit the mappings in Hardware discovery data from product level to model level mapping when applicable. Impact This change will impact customers who have relied upon Hardware discovered data mappings, especially on virtual machines.   In the attached file, we have included a list of Virtual model IDs along with the corresponding category and product details. When Customers should expect these changes on 9 th March 2022 ... View more

UPDATE (May 9, 2022 09:15PM UTC): The work to capture Software Collection  and Base Package separately under Red Hat has been completed. Please refer to the latest attachment (Red Hat SW Collection and Base Package Report.xlsx) to get the complete details on all Release ID's along with the lifecycle dates that have been updated in Technopedia Change Title   Red Hat components from “Base Package” vs. “Software Collection” to be captured differently in Technopedia   Class 1   Customers should be prepared and take actions                 Change Summary   Context: Red hat packages are available as either software collection s or base package. The software collections allow users to concurrently install multiple versions of the same software components on their syste m. Currently, we have not differentiated these products in Technopedia.      This notification is to announce the intention to differentiate Red Hat components as software collection and base package in product and release tables in Technopedia . To apply these changes, we will be i mplementing below changes in Technopedia :     Software Collections:   N ew product will be added under Red Hat software collection with the prefix “rh- “ in the product name. Based on package version details in RHEL versions, we are creating releases along with lifecycle details for new products.   Examples:   Manufacturer    Old product name   New Product Name    Version    End of Life   Notes    Red Hat    ruby   rh- R uby    2.4    Apr 2020      Red Hat    ruby   rh- R uby   2.6    May 2022    New product name will be created as this package version is supported in RHEL 7     Discovered evidence data with “rh-xxxx” will be re-mapped to the above software collection products.     Base Packages:   We are going to differentiate the base packages by keeping their product names without any prefix. For the existing Technopedia products without this ‘rh-’ prefix in the name field, we are going to classify them as base package and will update their EOL dates in the way as mentioned below. Based on the discovered evidence data, we are going to capture version details as below, Examples :     ruby-2.0.0.648-38. el7 .x86_64   ruby-1.8.7.352-3. el6 .x86_64     The versions and EOL for these base packages will be captured in Technopedia as follows:     Manufacturer    Product Name    Version    EOL    Notes    Red Hat    ruby    1.8   11/30/2020    Following EOL for RHEL 6    Red Hat   ruby   2.0   6/30/2024   Following EOL for RHEL 7      Discovered evidence data will be mapped based on above scenarios.   Impact   This change will impact customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped data to these packages. They will be reviewed and updated.   The attached excel file  " RedHat_ProposedChanges.xlsx” provides an example of proposed changes.    When   Customers should expect these changes on April 1st 2022.   Completed on May 9, 2022. ... View more

  Change Title Microsoft Office for Mac 16/16.x Version Changes (Latest) Class 2 Customers should be aware and be prepared Change Summary Starting with the 16.17 release in September 2018, the release notes of Office for Mac apply to Office 2019 for Mac and the Microsoft 365 subscription version. [5] Starting with the 16.54 release, this information also applies to Office 2021 for Mac. [1] Microsoft Office for Mac version 16.x have three different license terms: Microsoft 365 subscription license, 2019 license and 2021 license. Versions 16.x with Microsoft 365 subscription, 2019 license and 2021 license share the same version history but with different lifecycle.[2] 2019 license will be end of life as 10/10/2023.[4] 2021 license will be end of life as 10/13/2026.[6] However, Microsoft 365 subscription always keeps the applications in support and up-to-date. [3] Microsoft 365 for Mac, Office 2019 for Mac and Office 2021 for Mac use the same application and file names, but the license information would not display in normalize discovered data. To accommodate the above changes, Flexera is going to update the Microsoft Office for Mac and its components version 16.x in the Data Platform. For Office for Mac, we are going to create a new separate product Microsoft 365 for Mac, and capture those 16.x version under version group 365 for the Microsoft 365 subscription. For the component products, for example Excel for Mac, we are going to change the existed version group 16 and version 16.x to version group 365 and version 16.x (365) for the Microsoft 365 subscription, to distinguish from the 2019 license and 2021 license. Product Version Group Version End of Life Obsolete 365 for Mac 365 16.54 12/31/2999 12/31/2999 365 for Mac 365 16.17 12/31/2999 12/31/2999 Office for Mac 2021 16.54 (2021) 10/13/2026 10/13/2026 Office for Mac 2019 16.54 (2019) 10/10/2023 10/10/2023 Office for Mac 2019 16.17 (2019) 10/10/2023 10/10/2023 Excel for Mac 365 16.54 (365) 12/31/2999 12/31/2999 Excel for Mac 365 16.17 (365) 12/31/2999 12/31/2999 Excel for Mac 2021 16.54 (2021) 10/13/2026 10/13/2026 Excel for Mac 2019 16.54 (2019) 10/10/2023 10/10/2023 Excel for Mac 2019 16.17 (2019) 10/10/2023 10/10/2023   The components of Microsoft Office for Mac will follow the same changes as Excel for Mac in the example, the components are as follow. Microsoft Excel for Mac Microsoft Word for Mac Microsoft PowerPoint for Mac Microsoft Outlook for Mac Microsoft OneNote for Mac All mappings will be reviewed and updated. Impact This change will impact customers who rely on Technopedia Product ID/Release ID & Names and discovered previously mapped data to Microsoft Office for Mac version group 16 and version 16.x. They will be reviewed and updated. The attached spreadsheet provides the full list of all releases in scope for this review that will be created. When Customers should expect these changes to have been completed starting from January 11, 2022 to January 17, 2022. Reference [1] https://docs.microsoft.com/en-us/officeupdates/release-notes-office-for-mac [2] https://support.microsoft.com/en-us/office/microsoft-office-and-the-mac-app-store-ad2293a8-f5aa-4652-ae3f-83dda906d748 [3] https://docs.microsoft.com/en-us/lifecycle/products/microsoft-365-apps [4] https://docs.microsoft.com/en-us/lifecycle/products/microsoft-office-2019-for-mac [5] http://web.archive.org/web/20190617064626/https://docs.microsoft.com/en-us/officeupdates/release-notes-office-for-mac [6] https://docs.microsoft.com/en-us/lifecycle/products/office-2021   ... View more

This KB article describes the steps on how to raise requests for Content Services.  Requests for data and content maintenance on the data Libraries are handled by the Content Support & Operations teams and involves (but is not limited to) the following activities: Requests for the addition of new Vendors, Products and Versions not currently in the catalogue Requests for maintenance of existing content following Vendor announcement of product changes, including divesture, merger or retirement Requests for SKU/PURL maintenance including linking to Products in the catalogue Maintenance of discovered application evidence and mapping to Product and Versions Maintenance of market enriched data such as Lifecycle dates, Open-Source attributes, and Vulnerabilities, etc.   Requests for Content Services are made as follows: Navigate to the Support Portal on the Community here Select ‘Flexera Community’ if not already selected in the ‘Community’ picklist   Select ‘Content Requests’ from the ‘Product’ Picklist.  This applies to all customers irrespective if you are a FlexNet Manager, Technopedia, or IT Visibility customer     Select ‘Library’ from the ‘Version’ Picklist for which maintenance is required.  For example, Technopedia customers requiring Content Services for Product, Version and/or Evidence mapping would pick Technopedia.  FlexNet customers requiring similar would select ARL     Enter the requirements for Library maintenance in the ‘Description’ field   Severity will default to ‘Low’.  Increase the Severity as per the urgency of your request.  This will ensure that your requests will be addressed in the correct order compared to other requests for Content Services that you may have open   Note that for ‘Critical’ and ‘High’ severity requests we would like to understand more about the impact to your organization so that we can respond accordingly    If required, you may add up to 10 attachments into the ‘Drag and drop’ area.  We encourage customers to aggregate similar requests into one ask so as to reduce the administration overhead to tracking requests to closure     ... View more

This KB article describes the steps on how to raise requests for Content Services.  Requests for data and content maintenance on the data Libraries are handled by the Content Support & Operations teams and involves (but is not limited to) the following activities: Requests for the addition of new Vendors, Products and Versions not currently in the catalogue Requests for maintenance of existing content following Vendor announcement of product changes, including divesture, merger or retirement Requests for SKU/PURL maintenance including linking to Products in the catalogue Maintenance of discovered application evidence and mapping to Product and Versions Maintenance of market enriched data such as Lifecycle dates, Open-Source attributes, and Vulnerabilities, etc.   Requests for Content Services are made as follows: Navigate to the Support Portal on the Community here Select ‘Flexera Community’ if not already selected in the ‘Community’ picklist   Select ‘Content Requests’ from the ‘Product’ Picklist.  This applies to all customers irrespective if you are a FlexNet Manager, Technopedia, or IT Visibility customer     Select ‘Library’ from the ‘Version’ Picklist for which maintenance is required.  For example, Technopedia customers requiring Content Services for Product, Version and/or Evidence mapping would pick Technopedia.  FlexNet customers requiring similar would select ARL     Enter the requirements for Library maintenance in the ‘Description’ field      Severity will default to ‘Low’.  Increase the Severity as per the urgency of your request.  This will ensure that your requests will be addressed in the correct order compared to other requests for Content Services that you may have open   Note that for ‘Critical’ and ‘High’ severity requests we would like to understand more about the impact to your organization so that we can respond accordingly    If required, you may add up to 10 attachments into the ‘Drag and drop’ area.  We encourage customers to aggregate similar requests into one ask so as to reduce the administration overhead to tracking requests to closure     ... View more