Flexera Community Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Cloud customers can now share Cognos reports and dashboards with other users.
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
Summary This article applies to FlexNet Manager Suite cloud and on-premises implementations 2019 R2 and later. With FlexNet Manager Suite 2019 R2, new functionality has been added to FlexNet Beacon 14.0.x and later that can be invoked with the use of the SQL file attached to this article in order to reduce FlexNet Beacon engine’s DNS lookups  so that there are limited reads outside a particular FlexNet Beacon’s assigned subnet.  As background, FlexNet Beacon executes DNS read calls when a FlexNet inventory agent requests a policy file, and when a discovery rule runs. There are two settings in the compliance database that control FlexNet Beacon engine’s DNS lookups: BBeaconScopeDiscoveryToBeaconSubnet—The default value is false, meaning the beacon will still go outside of its subnet to do the DNS query. This is the current behavior of FlexNet Manager Suite.  BBeaconDNSCacheRefreshTimeIntervalMinutes—The default is 1440 minutes (24 hours).  The value in this property controls the time span in minutes before it will consider the data stale and thus refresh the values in the DNS cache. If you wish to use the default values shown above, you can skip the following instructions that allow you to set different values in order to take advantage of reducing Flexnet Beacon engine's DNS lookups. The following steps need to be executed on the database server. To reduce FlexNet Beacon engine's DNS lookups: Ensure that you are using FlexNet Beacon 14.0.x or later.  Download the BeaconPolicyUpdate.sql file included in the ATTACHMENTS section of this article. Edit the BeaconPolicyUpdate.sql file: Set the @scopeToBeaconSubnet variable to 'True': set @scopeToBeaconSubnet = 'True' Define the time span in minutes when data should be considered stale and a refresh of the DNS cache should occur (or retain the default 1440 minutes / 24 hours):  set @cacheRefreshtime = 60 Save changes to the BeaconPolicyUpdate.sql file. Run the BeaconPolicyUpdate.sql file against the compliance database. This updates the database with your new values for the settings that control FlexNet Beacon engine’s DNS lookups.  
View full article
This article is for cloud customers experiencing issues with FlexNet Beacon 13.5.x through 13.8.x.
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
Tenant Deletion - Online. This document is targeted to Managed Service Providers (MSPs) of FlexNet Manager Suite and describes how to delete tenants from a multi-tenanted system without disrupting FlexNet Manager Suite online operations. 
View full article
Prerequisites Parent Beacon Installed Parent Beacon initially Configured Child Beacon Installed Configuring Child Beacon to Point to Parent Beacon Get configuration XML Open a FNMS in a web browser, and navigate to Discovery & inventory Select Beacons under Network Select Configure Beacon On the parent beacon box Search for your parent beacon Press Generate a Unique ID Enter the name of the beacon Once completed you need to press Download Configuration button. This will download a XML Import XML to Beacon Copy XML file generated in previous step on to the desktop Go to the child beacon server Open Beacon UI On the Parent connection tab Click Import configuration button Select the XML file from the desktop You will receive a message that there are no credentials specified to connect to the parent Click yes Enter service account username and password Press Test connection
View full article
Symptoms: ARL import (mgsimportrecognition.exe) may fail with the following error: The client and server cannot communicate, because they do not possess a common algorithm Diagnosis: Several versions of .NET framework need additional treatments in the Windows registry when TLS 1.0 is disabled according to the following article. https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions Solution: 1. Open regedit.exe as an Administrator. 2. Change or create values as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions"=dword:00000001 "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions"=dword:00000001 "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 "SchUseStrongCrypto"=dword:00000001  
View full article
Question: Why users cannot see workflows created/submitted by other users in the same company? Answer: By default, users in the same company only can see the workflows created or submitted by themselves.  Follow the steps mentioned below to allow all the users in the same company to see the workflows submitted by other users : Navigate to App_Data folder present inside Workflow Manager Installation  Directory              Ex: C:\ AdminStudio Web Components_2019\wwwroot\App_Data\        2.  Locate 'XMLQuery.xml' file and Open it in a Text Editor        3.  Look for the tag <Query id="WFList_Consumer"> and then the <SqlServerVersion> Tag in it.                Remove the text: AND a.uploadBy = ' {0} '        4. Save XMLQuery.xml file        5. Log in as any user in the same company and now will be able to see the workflows submitted by                  other users in the same company.      
View full article
Many times, the best way to debug a technical problem with the Software Vulnerability Manager Agent scanners is to create a log file that shows what the Agent does and where it fails to submit the scans. The log file is the fastest way to diagnose and evaluate the Agent performance, and the issues that block it.  In the vast of cases, customers prefer to run the SVM Agent under the LocalSystem account as the recommended practice by Flexera goes. However, this makes it harder to debug the Agent manually using manual CMD commands, because as soon as the user opens CMD with their account, the Agent runs under their user's context, and not as it is installed under the LocalSystem account, therefore possibly yielding different test results as it would have generated if the test is ran under LocalSystem.  To go around this problem, you would enable logging for the SVM Agent without using the command line, by appending logging on the fly at the Agent configuration settings at the Windows registry. 
View full article
Why Secunia CVSS score for an advisory is different than the vendor or other sources? This article answers this question and it includes concrete examples of expected use-cases too. 
View full article
Patch for AdminStudio 2019 R2 Summary A patch for AdminStudio 2019 R2 is made available to address a couple of product bugs identified by the AdminStudio product team. This article explains those bugs and how to apply the patch on the affected version of AdminStudio to fix the bugs.   Symptoms Every package imported from the Package Feed Module into AdminStudio’s application catalog was missing the setup file name in the command line value set in ‘Install Command Line’ property. So, there was a need to manually update the value in this property with the setup file name.   The following error is seen while building MSIX projects in AdminStudio Edition of InstallShield (Editor): Error Description: The specified provider is unknown ‘ISMSIX’ Error Code: -9009   Resolution The patch will fix both the issues mentioned above. Please go to the below link to download the patch: https://flexerasoftware.flexnetoperations.com/control/inst/AnonymousDownload?dkey=15101737   How to Apply the Patches: The downloaded AS2019R2_Patch.zip includes two patch installers: Patch#1 AS2019R2_Patch.exe Patch#2 IS2019_Patch.exe To Apply Patch #1: Copy the AS2019R2_Patch.zip to the machine where AdminStudio 2019 R2 is installed Close all the instances of AdminStudio, AdminStudio tools opened. Kill the AdminStudioHost.exe (if it is already running) from the tray icon area on the taskbar. Extract the AS2019R2_Patch.zip Double click on the AS2019R2_Patch.exe | Wait until the patch installation wizard appears | Continue the wizard to apply the patch   To Apply Patch #2: Copy the AS2019R2_Patch.zip to the machine where AdminStudio 2019 R2 is installed Close all the instances of AdminStudio, AdminStudio tools opened. Kill the AdminStudioHost.exe (if it is already running) from the tray icon area on the taskbar. Extract the AS2019R2_Patch.zip Double click on the IS2019_Patch.exe | Wait until the patch installation wizard appears | Continue the wizard to apply the patch Note: These patches can be applied in any order to fix the issues.  
View full article
This article outlines the steps required to perform a swap of your WSUS Self-Signing certificate, or your private code-signing certificate at WSUS, when the old one has expired and you need a new one. 
View full article
You are under Patching menu in SVM2018 and you attempt to connect to your WSUS/SCCM instance using the connection dialog in SVM. The SVM display connection error 0x8007007e and error message "Unable to load DLL "SusNativeCommon.dll" :: The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
View full article
Summary Rejected Issue CVE-2015-2516 within Advisory MS15-098 is not covered by SA66373 Synopsis The issue with the CVE identifier CVE-2015-2516 within the Advisory MS15-098 is rejected due to having a too weak gain considering the exploitation effort and thus this issue is not included within the respective Secunia Advisory SA66373. Discussion Reason for Rating: The application that is affected by the issue is considered a client application and thus the outlined impact of a DoS (Denial of Service) within the proposed exploitation scenario is considered a too weak gain as a user has to consider frequent saves due to security best practices, which limits any loss of data. Additionally, a simple restart of the client application will resolve the DoS situation. Additional Information References: [1] https://technet.microsoft.com/en-us/library/security/ms15-098.aspx [2] http://secunia.com/advisories/66373/
View full article
Summary The problem addressed in this article are some of the issues seen among SVM users, but it might not be the full list of issues due to the nature of the problem. Symptoms Some of the problems discussed here as follows: You are unable to delete standalone users using the Delete controls in the SVM interface. The browser displays an error message as the following. You attempt to create Smart Groups, but none of the new Smart Groups can be saved and you are stuck with an open window which you can only cancel. Cause Local browser caching issues lead to these unpredictable spontaneous local problems. Steps To Reproduce This is difficult to reproduce, but it occurs at browsers which appear to have extensive amount of locally cached data and haven't been cleared recently. Resolution Delete the local browser cache and refresh the page after completion. Workaround Load your account in a different browser and try from there (but clean the other browser cache before opening the app.flexerasoftware.com page) Additional Information This problem only affects the Software Vulnerability Research software by Flexera. If you are still experiencing issues please follow these steps: Open CMD as admin Run certutil -urlcache * >> c:\cookies.txt Open a support case and attach the cookies.txt file
View full article
When attempting to log on with an appropriate username and password to the Software Vulnerability Research software, the SVR returns an error: "Sorry, you are not allowed to access this app."
View full article
Secunia Research can reject software vulnerability reports by other vendors or public sources in the event that the exploitation of the vulnerability as reported by the original public reporters are not realistic, require violation of security best-practices, or the vulnerability exploitation mandatory requires another vulnerability to be exploited first that enable an attack vector for the secondary exploitation.
View full article
If you have decided to set up your SVM On-Prem servers in dual-mode configuration with one server housing Apache, PHP and the SVM configuration, and the other server hosting the SVM database, then you have to assign your database user with the appropriate remote privileges to allow it remote access to the database from the SVM server.  A common configuration makes use of the database root account, but by default accounts on the database will not be enabled for remote login.
View full article