Data Platform Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Knowledge Base Categories
Microsoft is planning to release a patch to the LDAP to increase the security. Here are the links about the update. https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV190023   FLEXERA DATA PLATFORM and USER CONOLE should support it. It is recommended to use SSL with AD  as suggested by Microsoft
View full article
Default Report Changes in 5.5.26: Some out of the box reports are now hidden by default starting v 5.5.26 Reason: We have added some enhanced additional reports in v 5.5.26. Not all old reports maybe required by each customer and hence these are disabled by default. If needed customers can show these Hidden reports based on their use case. Steps to show Hidden Reports: Explained below is the definition of BDNA_A_REPORTS view. The list of report names in the first CASE WHEN clause is the list of reports to hide in 5.5.26. In order to show the reports, comment out or remove the line of report name in the list, and run the scripts to re-create BDNA_A_REPORTS view. (This is SQL server version, Oracle is similar to this)   DROP VIEW BDNA_A_REPORTS;   CREATE VIEW BDNA_A_REPORTS AS SELECT   CASE     WHEN REPORT_NAME IN ('Hardware Entitlement Dashboard',     'Operating System Summary',     'OS Distribution by Family',     'OS Distribution by Manufacturer and Name',     'Purchase Order Normalization',     'Server Software Windows 32Bit Readiness',     'Server Software Windows 32Bit Status',     'Server Software Windows 64Bit Readiness',     'Server Software Windows 64Bit Status',     'Software Asset Management',     'Software Compliance Dashboard',     'Software Entitlement',     'Top Licensable Server Software',     'Top Licensable Server Software with CPU Counts',     'Top Licensable Software for Workstations and Laptops',     'Top Software Manufacturers with Licensable Indicator',     'Top Software Products',     'Win Server CPU Compatibility',     'Win Server Hardware Readiness',     'Win Server HDD Compatibility',     'Win Server RAM Compatibility',     'Windows Desktop Migration Software Readiness',     'Windows Server Hardware Readiness',     'Windows Server Migration Software Readiness',     'Hardware Entitlement'        ) THEN            CASE         WHEN (SELECT COUNT(*) FROM BDNA_CP) > 0         THEN 'HIDE'       END     WHEN REPORT_PATH NOT LIKE '%pricing.template%'     AND REPORT_PATH NOT LIKE '%lifecycle.template%'     AND REPORT_PATH NOT LIKE '%UserReports%xdash'   THEN     BDNA_A_CUBES.DISPLAY_OPTION     WHEN REPORT_PATH LIKE '%pricing.template%' THEN       CASE         WHEN (SELECT 1 FROM BDNA_CP WHERE CP_NAME = 'HW SW Pricing' AND  IS_SUBSCRIBED = 'Y') > 0 AND BDNA_A_CUBES.DISPLAY_OPTION = 'SHOW'         THEN 'SHOW' ELSE 'HIDE'       END     WHEN REPORT_PATH LIKE '%lifecycle.template%' THEN       CASE         WHEN (SELECT 1 FROM BDNA_CP WHERE CP_NAME = 'Lifecycle And Support' AND  IS_SUBSCRIBED = 'Y') > 0  AND BDNA_A_CUBES.DISPLAY_OPTION = 'SHOW'         THEN 'SHOW' ELSE 'HIDE'       END     WHEN REPORT_PATH LIKE '%UserReports%xdash'       THEN 'SHOW' ELSE 'HIDE'   END   DISPLAY_OPTION,   BDNA_A_CUBES.CUBE_WEIGHT,   BDNA_A_REPORTS$.* FROM BDNA_A_REPORTS$ LEFT JOIN BDNA_A_CUBES ON BDNA_A_CUBES.CUBE_NAME = BDNA_A_REPORTS$.REPORT_CUBE ;
View full article
Manufacturer Harris has been renamed to L3Harris Technologies   In 2019, Harris and L3 combined complementary strengths in a merger of equals to form L3Harris Technologies, Inc. Please see full story: https://www.l3harris.com/who-we-are/our-history Technopedia has reflected this change based on our research findings.  We have integrated Harris's products and releases under L3Harris Technologies. Now Harris has been marked as 'inactive' and 'L3Harris Technologies' has been upgraded to a Tier-2 manufacturer.   Please refer to the attachment provided to show the changes that we have implemented. - L3Harris Technologies Product List.xlsx    
View full article
Summary This article provides the Technopedia manufacturer Tier 1 and Tier 2 list. Synopsis Technopedia list of Tier 1 and Tier 2 manufacturers as of Dec 2019.   Discussion Tier 1: 65 manufacturers Tier 2: 92 manufacturers Tier 1/2: 157 manufacturers Tier Manufacturer Manufacturer ID 1 Acer America 4323 1 Adobe Systems 4382 1 Agilent Technologies 4432 1 Amazon.com 14938863 1 Apache Software Foundation, The 9121 1 Apple 4611 1 AT&T 4731 1 Avaya 4808 1 BlackBerry 8323 1 BMC Software 4976 1 Broadcom 1054842 1 Canon 5084 1 Cisco Systems 5220 1 Citrix Systems 5224 1 Dell 5616 1 Eastman Kodak Company 1336411 1 Electronic Arts 5834 1 Dell EMC 442549405 1 Fujitsu 6245 1 Gateway 6278 1 GE Healthcare 900459 1 Google 594348 1 Hewlett Packard Enterprise 213050000 1 HP 213049949 1 Hitachi 6469 1 Honeywell International 13756 1 IBM 6517 1 Intel 6720 1 Intuit 6798 1 Juniper Networks 6904 1 Lenovo Group 7053 1 LG Electronics 993468 1 Lockheed Martin 13790 1 McAfee 7256 1 McKesson 1071907 1 Micro Focus International 7343 1 Microsoft 7365 1 Motorola Solutions 7463 1 Mozilla Foundation 593620 1 NEC 488193 1 NetApp 7602 1 Nokia 7672 1 Nortel Networks 7678 1 Oracle 7835 1 QUALCOMM 8198 1 Quest Software 301696601 1 Ricoh Americas 8355 1 salesforce.com 8433 1 Samsung Group 16547 1 SAP 8458 1 Seagate Technology 8514 1 Sharp Electronics 16549 1 Siemens 8594 1 Sony 964465 1 SUSE 8903 1 Symantec 8918 1 Texas Instruments 16556 1 Veritas Technologies 45100653 1 ViewSonic 9506 1 VMware 9569 1 Western Digital 9662 1 WinRAR 475460 1 Xerox 9754 1 Yahoo! 900655 2 3M Health Information Systems 4268 2 Agfa-Gevaert 1071973 2 Akamai Technologies 594205 2 Altera 4514 2 Amdocs 4537 2 AOL 921624 2 APC by Schneider Electric 957065 2 ASUSTeK Computer 16485 2 Autodesk 4785 2 AVG Technologies 1389544 2 Avid Technology 4819 2 Brother Industries 5028 2 Cadence Design Systems 5053 2 Check Point Software Technologies 5182 2 CIENA 5202 2 Compuware 5352 2 Corel 5423 2 Dassault Systemes 5546 2 D-Link 5709 2 EarthLink 1061902 2 Emerson Electric 593596 2 Empirix 5888 2 Epson America 5975 2 Extreme Networks 6078 2 F5 Networks 6087 2 FIS 6124 2 Fiserv 1061843 2 FileMaker 6129 2 Flexera 537527008 2 Forcepoint 181194354 2 Fuji Xerox 6240 2 Garmin 6275 2 General Dynamics 13746 2 General Electric Company 13748 2 Giga-Byte Technology 16513 2 H&R Block 899442 2 Harmonic 6425 2 Hexagon 64840491 2 Hitachi Data Systems 957074 2 Huawei Technologies 6489 2 InFocus 6625 2 Informatica 6634 2 Itron 6861 2 Ivanti 322240358 2 KONICA MINOLTA HOLDINGS 957069 2 Konica Minolta Printing Solutions U.S.A. 6981 2 Koninklijke Philips Electronics 944382 2 Kyocera Document Solutions 7001 2 L3Harris Technologies 983336725 2 LexisNexis Group 13849 2 Lexmark International 7061 2 Logitech International 7116 2 Marvell Technology Group 1061456 2 MathWorks, The 9145 2 Medtronic 900439 2 MicroStrategy 7367 2 Minitab 7397 2 National Instruments 7518 2 NCR 488145 2 NETGEAR 7573 2 Nuance Communications 7711 2 OpenText 7796 2 Panasonic Corporation of North America 7900 2 Pitney Bowes 8020 2 Polycom 8068 2 PTC 7915 2 Quark 8210 2 Red Hat 8282 2 Riverbed Technology 8371 2 Sage Group, The 9156 2 SanDisk 8449 2 SAS Institute 8465 2 SolarWinds 1407434 2 Sony Mobile Communications 8734 2 Software AG 13873 2 SuperLogix Software 804520 2 SS&C Technologies 8789 2 Synopsys 8945 2 Tableau Software 8973 2 TechSmith 9030 2 Tektronix 16555 2 Telefonaktiebolaget LM Ericsson 5993 2 Teradata 9099 2 TIBCO Software 9183 2 Toshiba America 9227 2 Trend Micro 9272 2 Unisys 16561 2 VeriSign 9452 2 Viavi Solutions 64840491 2 VIZIO 29377866 2 Zoom Telephonics 9827
View full article
Broadcom Inc. Completes Acquisition of CA Technologies On  Nov. 5, 2018, Broadcom Inc. announced that it has completed its acquisition of CA Technologies (NASDAQ: CA) ("CA").  https://www.broadcom.com/company/news/financial-releases/2375294 Technopedia has reflected this change based on our research findings.  We have integrated related CA Technologies's products and releases under Broadcom. We have compiled a complete list to show the changes that we have made. Please refer to the file attached to this article.
View full article
Microsoft Features on Demand   Features on Demand (FODs) are Windows feature packages that can be added at any time to Windows 10 or Windows Server 2019. They are distributed as .cab files on the Feature on Demand ISO and you can use Deployment Image Servicing & Management (DISM) to add a FOD to a Windows image. There are 2 types of Features on Demand   FOD's without satellite packages: Comprise features with all language resources packaged into the same package. These FODs are distributed as a single .cab file. FODs with satellite packages: Language-neutral FODs that have language and/or architecture resources in separate packages (satellites). These FODs are distributed as a set of several .cab files, but are installed by specifying a single 'capability name'.   Some FODs come preinstalled with Windows 10 or Windows Server 2019. You can also add additional FODs to support additional hardware features or enable certain use cases. The following Features on Demand come preinstalled, and have no satellite packages Internet Explorer 11 Math Recognizer OneSync OpenSSH Client Quick Assist   The following FODs are not preinstalled but are recommended to be preinstalled to enable certain scenarios .NET Framework Mixed Reality Retail Demo Experience RDX Server Core App Compatibility   The following FODs are not preinstalled Accessibility Braille OneCore Developer Mode Graphics DirectX WebDriver MSIX Packaging Tool Driver RAS Connection Manager Administration Kit (CMAK) OpenSSH Server Enterprise Cloud Print / Mopria Cloud Service Remote server administration tools (RSAT) Windows Storage Management XPS Viewer   Discovery and Normalization of FOD   FOD Products will still continue to be captured into Technopedia along with Support Policies and Lifecycle dates as long as Microsoft still allows the Products to be downloaded separately.  For example RSAT can be downloaded separately from  the official website here https://www.microsoft.com/en-au/download/details.aspx?id=45520 and will show up in ‘Uninstall or change a program’.  Note from the screenshot below this is where we could see the ‘Publisher’, ‘Name’ and ‘Version’ data which is typical for what we discover for Add/Remove evidences.   However, if the Product is downloaded as a FOD and installed using DISM then it only shows up in the ‘Turn Windows Features On or Off’ list.  In this scenario, currently it is not possible to discover the ‘Publisher’, ‘Name’ and ‘Version’ data evidence, since DSIM requires Administrator privileges, and extractors do not have the capability to run Command line arguments since the versioning of RSAT is not available for Discovery when installed and activated as a FOD, it is not possible to capture lifecycle EOL/Obsolete dates.     In certain circumstances, customers discovered data will present a FOD along with the OS installed e.g.       Note that the versioning of the FOD is not available from Discovery.  To accommodate this, Technopedia will capture FOD titles, when they meet the S/W eligibility criteria with Versions based on the specific OS in which it is known to be installed an activated. The FOD lifecycle dates will piggyback on the lifecycle dates of that Windows OS version as well. For example, RSAT would be captured as follows:  
View full article
Symptoms: 1. Configure Data Platform Wizard  is failing on the Import configuration step. 2. error message in setup.log - "Login failed for User 'BDNA_PUBLISH'" 3. You will see below info in setup.log INFO FIPS policy setting: Enabled. Diagnosis: 1. Double check if FIPS has enabled In Control Panel, click Administrative Tools, and then double-click Local Security Policy. In Security Settings, expand Local Policies, and then click Security Options. Under Policy in the right pane, double check if System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing is enabled   2. Can login directly using SQL management studio with both the BDNA and BDNA_Publish user  3. User are listed as db_own on respective databases.    Solution: This is an known issue, and has been addressed in 5.5.24. This happens because the new encryption algorithm is not compatible with the local FIPS security policy. Here are two workarounds to resolve this issue Workaround 1: The temporary workaround is to disable the FIPS, then you should be okay to enable it as soon as the BDNA app upgrades to 5.5.24.   Workaround 2: A. Instructions to fix the Data Platform Install error 1. Connect to Data Platform server, and download the attached patch to the server 2. Please make sure Data Platform Configuration Wizard windows is closed and the Data Platform service is stopped. 3. Run CMD as Administrator 4. enter to "..\Data Platform\Bin" 5. run below command line to apply the patch to Data Platform server Updater.exe /File="PATH-TO-PATCHSET\5.5.22_BDNA31912_DLLS.zip" Note, if you see any warning while performing the command line to apply the patch, please reboot the server and try it again.   B. Instructions to fix the User Console Install error 1. Login to User Console Server 2. Please make sure that Data Platform service is up. 3. Please make sure that the User Console Configure Wizard is closed, and the user console service is stopped 4. Run CMD as Administrator 5. Run below command line to apply the patch to user console server cd D:\Program Files\BDNA\User Console\Bin Updater.exe" /FILE="PATH-TO-THE-PATCH-FILE\5.5.22_Analyze_BDNA31912_NBIDLLS.zip" 5. If still see any warn or error message while applying the patch, please reboot the User Console server and try it again  
View full article
Threat: A link is functional over an insecure, HTTP connection. No redirection to HTTPS occurs. Impact: Data sent over a non-HTTPS connection is unencrypted and vulnerable to network sniffing attacks that can expose sensitive or confidential information. This includes non-secure cookies and other potentially sensitive data contained in HTTP headers. Even if no sensitive data is transmitted, man-in-the-middle (MITM) attacks are possible over non-HTTPS connections. An attacker who exploits MITM can intercept and change the conversation between the client (e.g., web browser, mobile device, etc.) and the server. Solution: The security vulnerability can be fixed by disabling HTTP and enabling HTTPS on IIS settings only. Flexera cannot directly modify the existing IIS host settings, since the users may have some other applications deployed on the same IIS. The below is a manual instruction to update the settings to remediate the insecure vulnerability.   Open IIS settings on Data Platform and User Console respectively Browse to the web site where Data Platform or User Console is installed to, the default is "Default Web Site" Open "Bindings" in Action panel Remove HTTP bindings from the list and keep HTTPS only. Re-run Data Platform and User Console Configure Wizard to update the website protocol from HTTP to HTTPS.  
View full article
Threat: The web application is possibly vulnerable to a "slow HTTP POST" Denial of Service (DoS) attack. This is an application-level DoS that consumes server resources by maintaining open connections for an extended period of time by slowly sending traffic to the server. If the server maintains too many connections open at once, then it may not be able to respond to new, legitimate connections. Unlike bandwidth-consumption DoS attacks, the "slow" attack does not require a large amount of traffic to be sent to the server – only that the client is able to maintain open connections for several minutes at a time. The attack holds server connections open by sending properly crafted HTTP POST headers that contain a Content-Length header with a large value to inform the web server how much of data to expect. After the HTTP POST headers are fully sent, the HTTP POST message body is sent at slow speeds to prolong the completion of the connection and lock up server resources. By waiting for the complete request body, the server is helping clients with slow or intermittent connections to complete requests, but is also exposing itself to abuse. Impact: All other services remain intact but the web server itself becomes inaccessible. Solution: The security vulnerability can be fixed by updating the Limits settings for the web site. For some customers, they have some web applications installed on the same web site, Flexera cannot update the settings for the whole web site. Please follow the below instructions to limit the size of the acceptable request to User Console to remediate the Slow HTTP Post vulnerability. Steps: Open IIS settings Browse to the web site where User Console is installed to, the default is "Default Web Site" On the Actions panel, click "Limits" Set Connection time-out to 30 Check "Limit number of connections" and set the value to 1024. Click OK Run iisreset.exe to restart IIS service and take effect.
View full article
Under normal circumstances during the course of content research (e.g. Publisher, Product, Release or Model, Support and Life cycle Dates), the Content Team will endeavor to capture the publicly available external URL as a reference to validate the information that has been captured into Technopedia.  For a small number of these data points, the reference has been provided either by the customer or the vendor directly (in the form of documentation, screenshot, or any other artifacts that cannot be accessed publicly), and as such there is no external URL reference that we are able to share. Please follow up with Flexera Support should you need more information on the information that has been captured. 
View full article
Symptoms: BDNA upgrade has succeeded on applying 5.5.22_DLLS.zip file, but failed at applying User Console patch - 5.5.22_Analyze_NBIDLLS.zip file. Diagnosis: 1. Check logs if 5.5.22_DLLS.zip has been applied successfully.   2. Check the version of bms.common.dll in both Data Platform/bin and User Console/bin folder. The version is expected to be different due to the upgrade failure.   3. User Console cannot be connected in Admin UI   Solution: 1. Please DON'T re-run User Console Config Wizard when this error occurs   2. Please make sure "FIPS" is disabled on the local security policy group   3. Follow the below steps to manfully apply the patch set - 5.5.22_Analyze_NBIDLLS.zip   1. Connect to User Console Server, and run CMD as administrator 2. Enter to ‘the-patch-to\User Console\Bin’ 2. Run command line Updater.exe /file="Path-to\Use Console\tmp\ 5.5.22_Analyze_NBIDLLS.zip"   4. When #2 completes without errors, then go to admin UI to activate User Console (you may want to check if User Console UI works first, if see license related error, please file a new case for a new analyze license)   5. Connect to BDNA database and run below query to waive the patch set - 5.5.22_Analyze_NBIDLLS.zip out from RED BANNER in Admin UI   1. For SQL setup update nbf_sys_files set status='NONE' where file_name like '5.5.22_Analyze_NBIDLLS%'; 2. For Oracle setup update nbf_sys_files set status='NONE' where file_name like '5.5.22_Analyze_NBIDLLS%'; commit;   7. Go to Admin UI and re-apply the remaining patches.
View full article
Issue: Unable to Start User Console Service while running User console Config Wizard. The startup time exceeds the default timeout and fails with error: ERROR BDNA.NormalizeBI.Setup.SetupException: BDNA User Console service startup failed. ERROR Install failed.   Resolution: You can increase the timeout by adding an additional parameter OnlineTimeout in the  NBI.configuration.config to customize service startup timeout. The file is located at: <User Console Install directory>/conf/ NBI.configuration.config  Example of how the file looks like when this parameter is added: <Configuration> <NBIApplication> <ValueDict> <key> <string> OnlineTimeout </string> </key> <value> <string>12 00 </string> </value> </ValueDict> If the above parameter is missing in NBI.configuration.config file, or the value is negative number, the default value (300) is used. NOTE : This value is in seconds. After the above parameter is added the custom value 1200 seconds = 20 minutes is used. There is a logging message in UX.log which shows the effective change. Steps: 1)Make the above changes in NBI.configuration.config file and save this file. 2)Restart the User console service. 3)Rerun the User Console configuration wizard.   NOTE : This is supported on version 5.5.10 and above.  
View full article
Symptoms: 1. Error in Admin UI : Get an error  - "An exception occurred during a WebClient request" during catalog sync. 2. Error in BDNA.log: 2019-11-08 16:50:18,346 0 INFO Downloading file from Technopedia Update Services... 2019-11-08 17:01:40,961 0 ERROR System.Net.WebException: An exception occurred during a WebClient request. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) — End of inner exception stack trace — at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.WebClient.DownloadBitsState.RetrieveBytes(Int32& bytesRetrieved) at System.Net.WebClient.DownloadBits(WebRequest request, Stream writeStream, CompletionDelegate completionDelegate, AsyncOperation asyncOp)   3. When trying with offline sync option, will see the server cannot download the catalog package error Diagnosis: This issue is due to the content package that is going to be downloaded is too big. Solution: 1. Login to Admin UI 2. Go to Technopedia -> Setting page 3. Then uncheck "Automatic software updates" checkbox 4. Start catalog sync 5. When catalog sync is done, you can check "Automatic software updates" and re-run catalog sync to get the new patches accordingly.
View full article
Scenario: Fresh Data platform install for version 5.5.22 Data Platform configuration wizard fails on Create BDNA Schema. Error occurred when executing mssql_CreateDatabase.sql Error in setup.log: ERROR Read script file error: Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: MODIFY FILE failed. Specified size is less than or equal to current size. Cause: The script uses the ALTER DATABASE with MODIFY FILE command  which can only make a file size bigger. If a smaller size is encountered the above error is caused. a)If "BDNA" and "BDNA_PUBLISH" already exists with a default size greater than what is specified in the script, this can give the above error. b)If the model database in SQL server is set to a size greater than what is specified in the script, this can give the above error. Resolution: 1)If its a fresh install - Drop existing "BDNA" and "BDNA_PUBLISH" database. 2)Close the config wizard if still opened. 3)In file explorer browse to C:\Program Files\BDNA\Data Platform\Database\SQLServer\Script or the equivalent location in your system. 4)Open the file mssql_CreateDatabase in edit mode and find the following code: Original Code snippet: "ALTER DATABASE [${BMS_CATALOG_NAME}] MODIFY FILE(Name = ${BMS_CATALOG_NAME}, SIZE =5GB , FILEGROWTH=200MB); ALTER DATABASE [${BMS_CATALOG_NAME}] MODIFY FILE(Name = ${BMS_CATALOG_NAME}_LOG, SIZE =50MB , FILEGROWTH=50MB); " Now replace or edit the above code to match the below: ALTER DATABASE [${BMS_CATALOG_NAME}] MODIFY FILE(Name = ${BMS_CATALOG_NAME}, SIZE =350MB , FILEGROWTH=350MB); ALTER DATABASE [${BMS_CATALOG_NAME}] MODIFY FILE(Name = ${BMS_CATALOG_NAME}_LOG, SIZE =250MB , FILEGROWTH=250MB);   5)Validate the Model database size. The modeldev and modellog size should be less than what is being used in the script. If it is not, you may either decrease the initial size in the model database or increase the size in the mssql_CreateDatabase.sql script.
View full article
The Normalize gap-fill process refers to the process of reviewing 'Unknown' entries from the Normalize result and turning them into 'Known' entries (either 'Mapped' or 'Irrelevant'). The following article outlines Flexera Resolution goals for gap-fill.  Definitions Data Source: An operational IT tool which collects hardware and software data to be normalized Unmatched Data: Hardware and software data from a Data Source that is not successfully normalized by Flexera Normalize, excluding custom software and hardware Gap-fill: Process by which customer submits Unmatched Data from a Data Source and Flexera provides normalized result back to Flexera Normalize Resolution Goals Flexera will provide Gap-fill for all Unmatched Data from customer's Data Source for Tier 1 and Tier 2 vendors as specified in Technopedia Catalog within 30 days Flexera will provide Gap-fill for any Unmatched Data from a customer's Data Source for any Tier 3 vendor with more than twenty (20) installations of a single product within 30 days For large submissions of initial Unmatched Data, Flexera will provide an estimate for Gap-fill within 3 business days. (Customer must submit a support incident to request this estimate.) Related Articles Normalize for Purchase Orders Gap-fill Resolution Goals Normalize Gap-Fill process (page 135)
View full article
Data Platform Lifecycle Timeline Application Version General Availability End of Standard Lifecycle End of Extended Lifecycle Lifecycle as of Today Data Platform Discover 7.7.2 2016-11-09 N/A N/A Full Support Data Platform/ User Console 5.5 2017-11-01 N/A N/A Full Support Data Platform/ User Console 5.4 2017-07-27 2018-07-31 2018-11-30 No Support Data Platform/ User Console 5.3 2017-03-30 2018-03-31 2018-07-31 No Support Data Platform/ User Console 5.2 2016-11-23 2017-11-30 2018-03-31 No Support Data Platform/ User Console 5.1 2016-05-17 2017-07-31 2017-11-30 No Support Data Platform/ User Console 5.0 2015-11-12 2017-03-31 2017-07-31 No Support Normalize/ Analyze 4.3 2015-02-12 2016-12-12 2017-06-12 No Support Normalize/ Analyze 4.2 2014-08-26 2016-02-25 2016-08-25 No Support Normalize/ Analyze 4.1 2013-12-21 2015-07-25 2016-01-25 No Support The date format used is YYYY-MM-DD Versions not listed should be assumed as past extended lifecycle.   Read a complete description of the   Flexera lifecycle and end-of-life policy.  
View full article
The attached spreadsheet lists details for each IT Data Source (i.e. Extractor) used by Normalize. The information provided includes: Source Database (DB) Attribute Categories Collected Attributes
View full article
HCL Technologies acquires select IBM software products Technopedia has made changes accordingly. Related products and mappings under IBM (mfr id: 6517) have been migrated to HCL Technologies (mfr id:  55039103 ). We have compiled a complete list of software products displaying lineage and relationships affected by this acquisition. Please refer to the file attached to this article. - HCL Technologies software list Source: https://www.hcltech.com/press-releases/press-releases-business/hcl-technologies-announces-close-acquisition-select-ibm
View full article
Issue: Interactive reports created before v5.5.22 which contained a filter on column  'HW EOL DATE (calc)' or 'SW EOL DATE (calc)', cannot be opened on v5.5.22 Error:  Date string syntax "xx/xx/xxxx" is invalid Cause: Following columns were in string type before 5.5.22, but were changed to be Date type in 5.5.22: 1. HW EOL DATE (calc) 2. SW EOL DATE (calc) Workaround: This issue can be manually fixed with following steps. 1. Open the old report. 2. Close the pop up error. 3. Edit the filter, as the screenshot below: 4. After editing the filter, the report can be open. Then save the report again in order to save the edition, so that it can be open with any errors next time. 
View full article
Summary This article describes the Technopedia lifecycle standards and process. Synopsis Product lifecycle in Technopedia has standards to follow certain stages -- from the inception of the product to the last stage where the product becomes obsolete. These standards allow users to compare lifecycle stages for products across different vendors.   Discussion Here are the definition of various dates/stages in Lifecycle: SOFTWARE: - General Availability: Date the product is generally available through official vendor distributions - End of Life (EOL): Last date that full support for product is provided by the vendor. Partial support is still available. - End of Support (EOS) or Obsolete: Last date that any support is provided by the vendor. The only support available after this date, if applicable, is self-help online support. HARDWARE: - Introduction: Date the hardware was introduced/announced - General Availability: Date the hardware was available for sale - Last Availability: Last date the hardware is available for purchase from the vendor - End of Support (EOS) or Obsolete: Date when any form of support from the vendor ceases to exist   Translation Rules from String to Date Fields Whenever a date is captured in Technopedia, it is always captured verbatim as published by the vendor. For example, when a date is captured as 'Spring 2016', or 'Q3 2016', they are captured exactly like that in the 'String' field of Lifecycle dates. These string fields are then translated to follow the date format (MM/DD/YYYY) in the 'Date' field of Lifecycle dates. For the same examples, the 'Date' fields will contain '04/01/2016' and '07/01/2016' respectively. This practice is consistently applied across all the lifecycle stages above. There are also cases where Flexera could not find an actual date, even after an extensive research. In this case, Flexera puts 'Not Available' in the string field and provides a more specific reason in an 'Exception' field. Here are the possible values for the exception reasons: - Date not published by vendor - Support policy is not defined by vendor - Exact date unknown (a date range is provided) - Contract-based support only (no specific date) - Open-source support only (no specific date) - Limited, self-help support only (no specific date) - Date in the past (exact date unknown) - To be determined - Other   Some of those exception reasons will translate 'Not Available' in the string field into an actual date or null in the date fields, as shown in the following table:   Exception Generic: Date Translation Software: General Availability Software: End of Life Software: End of Support or Obsolete Hardware: Introduction Hardware: General Availability Hardware: Last Availability Hardware: End of Support or Obsolete Date not published by vendor (null) (null) (null) (null) (null) (null) (null) (null) Support policy not defined by vendor (null) (null) (null) (null) (null) (null) (null) (null) Exact date unknown, a date range is provided (null) (min date) (max date) (max date) (min date) (min date) (max date) (max date) Contract-based support only, no specific date(s) (null) (null) (null) (null) (null) (null) (null) (null) Open-source support only, no specific date(s) (null) (null) (null) (null) (null) (null) (null) (null) Limited, self-help support only, no specific date(s) (null) (null) (null) (null) (null) (null) (null) (null) Date in the past, exact date unknown 1/1/1900 1/1/1900 1/1/1900 (ONLY if General Availability Date is 'null' or '1/1/1900') 1/1/1900 (ONLY if General Availability or End of Life Date is 'null' or '1/1/1900') 1/1/1900 1/1/1900 (ONLY if Date Introduced is 'null' or '1/1/1900') 1/1/1900 (ONLY if Date Introduced or Date Available is 'null' or '1/1/1900') 1/1/1900 (ONLY if Date Introduced or Date Available or Last Availability Date is 'null' or '1/1/1900') To be determined 12/31/2999 (null) 12/31/2999 (ONLY if Obsolete Date is 'null' or '12/31/2999') 12/31/2999 (null) 12/31/2999 (ONLY if Last Availability Date or Last Support Date is 'null' or '12/31/2999') 12/31/2999 (ONLY if Last Support Date is 'null' or '12/31/2999') 12/31/2999 Other (null) (null) (null) (null) (null) (null) (null) (null)   Additional Flag and Date Rules 'Desupported' flag Indicates whether a software release or hardware model has been desupported. This flag is set in the Technopedia Content and is not calculated in the Technopedia Synch done on premise. This is the same as having Exception = 'Date in the past, exact date unknown' under 'End of Support or Obsolete Date' field. Whenever a software release or a hardware model has the Desupported flag = yes, then those dates are translated following the same exception value rules. Some actual date values are also translated automatically whether the Exception flag is set or not: 'TBD': 12/31/2999 'Ongoing': 12/31/2999 Date = null (empty, blank, not populated) indicates that research has not been done on this particular entry yet, and gap-fill is needed. For hardware dates, when either 'Introduction Date' or 'General Availability Date' is not available, the date from one field is duplicated to the other field. For example, if the 'Introduction Date' is empty, it is populated with the same date as in 'General Availability Date'.   Product Version EOL Date Rules The BDNA Content process captures the EOL date for a Minor Version only if it is different from the Major Version. This is indicated by the IS_MAJOR attribute on the Software Release table. If IS_MAJOR indicates 'yes', it's a Major Version. If the EOL date is the same for Versions indicated as Major and Minor, Technopedia only shows EOL Date for the Major Version. There may be some historical entries where Technopedia captured the EOL for a Minor Version even if it is the same as the Major Version, but this is not a cause for concern since BDNA follows the practice of only mapping customer data to major version (unless the lifecycle date for the minor version is different). Why do some EOL Dates look different for the same product? This is probably because a Service Pack or Subversion exists that has different EOL dates. To check the differences, add the PATCHLEVEL field from the Software Release table and VERSION and SUBVERSION fields from the Software Version table to your query to review and compare the detail.   Calculated Lifecycle Data Platform 5.x introduced a new Calculated Lifecycle available that is available with the Lifecycle Content Pack. The Lifecycle Option calculates whether software or hardware is supported based on an Industry Average calculated from Technopedia product published dates. The Is_Supported Flag is calculated in the Technopedia Synch process and indicates yes or no when the actual End of Support field is missing from Technopedia. Based on research from Technopedia, the industry average for end of life is 47 months, with support for the past seven version increments. This is 3 years 10 months, and 20 days For Hardware, the average is 99 months. This is 8 years 2 months, and 13 days. If EOL Date or Obsolete Date are found, Technopedia uses those dates. If EOL Date and Obsolete Date are Null, Technopedia uses the GA Date and does the calculation based on the Technopedia Lifecycle defaults or custom selections. If GA Date is null, Technopedia uses the SW Version to determine if it is supported based on Max Version - Version Order = Delta. If this Delta is greater than or equal to the Industry Average Version Increments, it updates Is_Supported to ?no?. In the Technopedia Catalog Settings, you have the option to accept the defaults or select Custom to change the Number of Months and Version Increments that a Software Release is supported. These settings are used when you schedule the next Technopedia Catalog Synch.   The Calculated Lifecycle attributes can be viewed on the User Console Technopedia Detail Page with the Lifecycle and Support content. The calculation is done on premise when Technopedia synch is run from the Data Platform .  
View full article