Service Pack 3.2 is available for FlexNet Manager for Engineering Applications 2021 R1. This service pack addresses issues with user access and the Organizational Structures page. IMPORTANT: Follow the prerequisites before proceeding with the install instructions. You will need to uninstall the previous service packs before installing the new service pack. The previous service packs are included in Service Pack 3.2. Service Pack 3.2 can be accessed via the Flexera Product and License Center. Install instructions and further details are available at the links below. FlexNet Manager for Engineering Applications 2021 R1 Service Pack 3.2 Release Notes  FlexNet Manager for Engineering Applications 2021 R1 Product Documentation Resolved Issues Service Pack 3.2 will resolve the issues listed in the table below. Issue Number Description IOK-993333 When any user with a role other than Super Admin User logs in after a user with the Super Admin User permission has already logged in, user permissions for both sessions are changed to the most recent logged-in user permission. IOK-1013484 Under Licenses, the Edit link does not display for users who are assigned the License Admin and License Server Admin roles, therefore preventing these users from editing the license file. IOK-1012186 The Create New Org Structure and Import buttons are missing from the Organizational Structures page. IOK-1010918 Tabs freeze when clicking the Organization Structures link under the Reporting tab.   ... View more

After applying the latest service pack (SP1) to your FlexNet Manager for Engineering Applications 2022 R1 install, you may be redirected to a URL using HTTPS when trying to access the web interface. Once you’ve installed Service Pack 1, a redirect variable in one of the configuration files automatically redirects to HTTPS. The site will be blocked as untrusted if you do not have HTTPS/SSL configured. Solution To remove the automatic redirect to HTTPS, follow these steps on both the Admin server and Reporting server. Navigate to the following directories and locate a file named standalone-full.xml.template . <Install Directory>\FLEXnet\manager\admin\patches\installed\jboss\config\ <Install Directory>\reporting\patches\installed\jboss\config\ Open the file in an editor such as Windows Notepad. Search for the following lines and remove them, then save the file. On line 612:  <filter-ref name="http-to-https" predicate="equals(%p,@{flexnet.port}@)"/> On line 629:   <rewrite name="http-to-https" target="https://@{flexnet.host}@:@{https.port}@%U" redirect="true"/> Open a Command Prompt/Windows Terminal window as an administrator. Go to the install directory and run the command: flexnet site make . <Install Directory>\FLEXnet\manager\admin\ <Install Directory\FLEXnet\manager\reporting\ Start the Admin and Reporting services. You should now be able to access the web interface using HTTP.   ... View more

Vendor daemons may not display under the license server due to case sensitivity in the configuration of the license server. Using both upper and lowercase characters in the server string can cause it to be read inaccurately. For example, "Server Hostname HostIdentifier port" wouldn't be read accurately because it uses both upper and lowercase letters. This issue can occur for a single license server or a triad setup. It may show the vendor daemon for some of the servers in the triad setup, but not all. How to fix this issue Replace "Server" with "SERVER" in the license files of your license server(s). Replace in all three servers if using a triad. Navigate to the Configure and Manage Server page under Servers tab > License Manager Summary. Select Reread All.      4. Navigate to Servers tab > License Manager Summary and select Update Status for the license server. ... View more

Heap size is important when building an environment, as it will dictate the amount of memory available for FlexNet Manager for Engineering Applications. For example, if your server has 50 GB of RAM, you can limit FlexNet Manager for Engineering Applications to only use 16 GB by configuring the heap size. The cause of many performance issues with FlexNet Manager for Engineering Applications is a lack of resources as the environment grows larger. As your environment grows, the number of resources required to keep the application performing at an optimal level will increase. Increasing the heap size can resolve most slowness/performance issues. RAM requirements  We recommend a minimum of 16 GB of RAM for each the Admin and Reporting servers. These specifications are based on a small environment. The larger the environment, the more resources you will need. Factors that will affect RAM requirements: The number of agents/license servers/vendors  The amount/size of .RL files imported into FlexNet Manager for Engineering Applications  Users' usage of the application, specifically the reporting functionality  The size of your database  Increase/decrease the heap size  Option 1 1. Stop the Admin and Reporting services and ensure no associated processes are open in the task manager. 2. Open a command prompt as an administrator and go to the installation directory: <Installation Directory>\FLEXnet\manager\admin\  <Installation Directory>\FLEXnet\manager\reporting\  3. Run the following command:  flexnet site  4. In the configurator, go to step 2 of 6, then change the Initial Heap Size and Maximum Heap Size to your desired values. Note: The initial heap size cannot be the same as the maximum heap size. If you're lowering the maximum heap size, the initial heap size value must be lower than the maximum. 5. Click Next until the final step, then select Finish. This process will rebuild the configuration files with the reduced heap size.   Option 2 1. Stop the Admin and Reporting services and ensure no associated processes are open in the task manager   2. Navigate to the following directory and open the site.properties file in notepad: <Installation Directory>\FLEXnet\manager\admin\config  <Installation Directory>\FLEXnet\manager\reporting\config  3. Modify the maximum and initial heap sizes to the desired values. flexnet.heap.maximum=32768  flexnet.heap.initial=16384 Note: The initial heap size cannot be the same as the maximum heap size. If you're lowering the maximum heap size, the initial heap size value must be lower than the maximum.   4. Open a command prompt as an administrator. Go to the installation directory and run the below command to rebuild the configuration files. flexnet site make ... View more

After applying FlexNet Manager for Engineering Applications 2021 Service Pack 2, if Log4j 1.2.17 still shows up on vulnerability scans, the Log4j 1.2.17 files have not been deleted and remain on the server as legacy files. You may see the files remaining in the following directories: <Install Directory>\FLEXnet\manager\admin\release\platform\webapps\flexnet\WEB-INF\lib <Install Directory>\FLEXnet\manager\reporting\release\platform\webapps\flexnet\WEB-INF\lib Remove Log4j 1.2.17 files After applying Service Pack 2, if you still have Log4j 1.2.17 files appearing on your system, it is safe to delete them, as they are no longer used by the application. Note: After Service Pack 2 is installed, the Log4j 1.2.17 files will not regenerate if you run either 'flexnet site' or 'flexnet site make.'   ... View more

A recent security vulnerability had been identified in SpringFramework (CVE-2022-22965) as highlighted in the previous post by our product management team https://community.flexera.com/t5/Community-Notices/Security-Advisory-Assessment-of-Flexera-s-products-exposure-to/ba-p/230099#FNMEA We are happy to inform you that a service pack has now been released to update the Spring Framework version that is being used by FNMEA, the download for service pack 3 will be available to you through your community/product & license center account. Please be aware if you currently have either of the previous two service packs installed in your environment you will need to uninstall these patches first using the 'flexnet patch uninstall' command, within the zip file is a pdf file with the installation instructions, please review these before proceeding with the install.   Resolved Issues; FNMEA-15709 Fix Spring vulnerability (CVE-2022-22965)   If you have any issues accessing the downloads or applying the service pack please reach out to support for assistance. ... View more

In the release of FlexNet Manager for Engineering Applications 2021 R1, there were two issues identified with some of the classic reports and with the OpenSSL version. A service pack has now been provided to address these and can be accessed through your Product & License center accounts, please see information about the service pack below. It is recommended if you are currently using FNMEA 2021 R1 to apply this service pack to resolve the issues listed below; Service Pack Highlights: • A complete existing kavachart component replaced by JFREE chart to display professional quality charts which is compatible with OpenJDK. • An open SSL library upgraded from 1.1.0 into 2.1.0 version   Resolved Issues; IOJ-2204891 Classic reports (HWM,PUD,SBC,UES,UOT) should be generated IOJ-2237707 Upgrade Openssl version from 1.1.0 into 2.1. ... View more

Summary Your beacon may fail to gather inventory from some Oracle VM Manager (OVMM) servers. This article describes a possible cause of this due to TLS configuration incompatibilities. Cause OVMM versions 3.4.5 and later can only communicate using TLS 1.2. OVMM versions 3.4.4 and earlier can only communicate using TLS 1.0 and TLS 1.1. FlexNet beacons cannot dynamically choose between TLS protocols based on the OVMM server versions. Solution If your OVMM servers are running version 3.4.5 or later you will need to configure your beacon to communicate over TLS 1.2. If TLS 1.0 and 1.1 are still enabled the communication wouldn't work correctly and inventory would fail. If you have more than one version of OVMM on your environment you will have a situation where you have one or more servers that require communication using TLS 1.2, and other servers that require TLS 1.0 or 1.1 for communication. An approach here is to setup a two beacons: One beacon is configured to use TLS 1.2, and with OVMM inventory rules targeting OVMM servers running 3.4.5 and later. The other beacon is configured to use TLS 1.0 and 1.1, with inventory rules targeting OVMM servers running 3.4.4 and earlier. With this setup your inventory for both environments should come in correctly. See also Transport Layer Security (TLS) 1.1 & 1.2 Configuration ... View more

Summary   You have a device which used to have Oracle DB installed on it but has now been uninstalled however this is still being reflected in FNMS as being installed.   Cause   There will be left over evidence somewhere on the device which is still reporting in, this could be a registry key or a single xml file, if these are picked up it would identify these installations.   Troubleshooting   Check the tracker log on the device and look for the following entries, if any of these entries exist then there is still evidence remaining on the device reporting this in.   [14/06/2020 05:19:33 (G, 0)] {10456} The file 'C:\Program Files\Oracle\Inventory\ContentsXML\comps.xml' has been detected as a possible package registry [14/06/2020 05:19:33 (G, 0)] {10456} The file 'C:\Program Files\Oracle\Inventory\ContentsXML\inventory.xml' has been detected as a possible package registry   Solution   First steps will be to check the locations in the comps.xml and inventory.xml where evidence is being reported from, the evidence could be brought in by a single xml file in one of the locations listed in the file, once these files are removed after the next import we should expect the application to no longer be reported in.   However there are occasions were even after removing the files or even the folder path that is being shown in the xml files the application still reports in showing the same file locations, in these cases there is most likely a reg key that still exists in the registry, running a trace with the following options edited in the etcp.trace file should allow you to find the information for the installations.   #+Configuring #+Inventory/Packaging/OracleUniversalInstaller #+Inventory/Oracle ... View more

Symptoms: When you are trying to add new user groups within your FlexNet Manager for Engineering Applications WebUI after clicking the 'Add Group' button there is 'Next' button on the following screen to allow you to go through and complete the task and add the new group. Diagnosis: -Within the FNMEA WebUI if you go Admin > Users > Show Groups -Click on the 'Add Group' button -Choose the Domain that you would like to add the group from and click 'Next' -On the next page there will be no 'Next' button to finish adding the group Solution: A hot fix has been developed which once added to your application will resolve this issue, please be aware this hot fix is for FlexNet Manager for Engineering Applications 2019 R2, if this hot fix may not be fully compatible with older versions, if you are running an older version of FNMEA please reach out to support who can check for a back ported version Please see zip file attached for the hot fix, before applying please read the ReadMe.txt file carefully and follow the instructions provided in that file. Ticket reference number: IOJ-1865316 ... View more