Gentlemen, The XML stored in the [ComplianceSavedSearch].[SearchMapping] column indeed is the location that defines the layout of columns in your custom report, as well as additional properties like if a column will to work as a link. Manually editing this XML based on samples taken from existing FNMS reports is not a structured approach though. May I suggest a better solution? The concept for the suggested FNMS reporting library is to use two objects for configuring a report in FNMS: A view that defines the report structure – columns and properties, like if a report column should be available from the ‘Column Chooser’ by default. A stored procedure that actually retrieves the data. After defining these two objects, instead of using the clunky standard FNMS procedure ‘ComplianceCustomViewRegister’, you call a procedure ‘SoSoComplianceCustomViewRegister’ from the library that does all configuration work in the background: EXEC dbo.SoSoComplianceCustomViewRegister @ReportNameUnique = 'FNMS Accounts with their latest activity date' ,@Description = 'All accounts with the date of their last activity.' ,@VersionNo = '1.0' ,@ReportFolderName = 'Sample Training Reports' ,@ViewDefinitionName = '<YourCustomReportDefinitionView>' ,@StoredProcedure = '<YourCustomReportStoredProcedure>' The attachment to this post contains the reporting library including the ‘SoSoComplianceCustomViewRegister’ procedure and all additional modules required. The attachment also includes a sample report that uses the reporting library for retrieving all devices (inventories) that have either a Microsoft SQL Server database or an Oracle Database installed. For documentation, an interactive training module with sample implementations is conveniently provided at the end of the SQL reporting library. If you have a working FNMS test environment, you can load the reporting library into the Microsoft 'SQL Server Management Studio', connect to the [FNMSCompliance] database and work through the examples, creating interesting reports on the fly. And yes, the documentation also covers how to create reports with dynamic links. That is where this whole discussion started after all 😁 . ... View more

Hi Donald, Generally, when using HTTPS on a Beacon running on a newer Windows OS, you will have to switch support for TLS 1.1/.2 on for Windows Server 2008 R2 Servers to allow downloading the policy from the Beacon or for uploading of Inventory data to the Beacon. This is independent if this is a 'Workgroup' server or member of a Windows Domain. See the following discussion for additional information on Windows Server 2008 and other old versions of Windows, please. ... View more

Hi, In case you want to put a little automation into the import of the libraries, you can save the following text in a file on your FNMS Batch Server, name it *.BAT and run it on a schedule using "Task Manager": @ECHO OFF SET FLEXERA-BIN-FOLDER=C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin SET IMPORTPURL=%FLEXERA-BIN-FOLDER%\ImportPURL.exe SET IMPORTRECOGNITION=%FLEXERA-BIN-FOLDER%\MgsImportRecognition.exe SET TEMP-FOLDER=C:\Temp\Libraries echo. ECHO --------- Importing application recognition library ----------- echo. "%IMPORTRECOGNITION%" -ia "%TEMP-FOLDER%\RecognitionAfter82.cab" echo. ECHO --------- Importing Product Use rights libraries ----------- echo. "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-Desktop.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-Adobe.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-IBM.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-Microsoft.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-Oracle.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-SAPPackages.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-Symantec.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\PURL-VMware.cab" "%IMPORTPURL%" -i "%TEMP-FOLDER%\EOSL.cab" In this file, you'll have to: Customize the TEMP-FOLDER path in line #6 in case you are not downloading the *.CAB files to the C:\Temp\Libraries folder. Remove or comment the import statement for *.CAB files in lines #16-#25 in case any of these PURLs are not included in your FNMS license. You can automate the downloading of the libraries in case you have an additional FNMS environment that has an Internet connection. A small VM running SQL Server and FNMS on a single device will be sufficient for this purpose.   ... View more

Hi Chirag, For Windows 10: Generally, yes. As Flexera claims to fully support Windows 10 including all future updates and patches, problems related to the Flexera Agent and a Windows 10 release are highly unlikely. There have been minor issues with the Flexera agent on Windows in the past. However, problems related to the Flexera Agent and a Windows release have always been addressed very quickly. ... View more

Hi Rob, In addition to 'IncludeNetworkDrives', the Flexera Agent has a command line option 'IncludeFileSystemType' that allows scanning of NFS mounts on Unix/Linux. You can combine these command line options like in: -o IncludeNetworkDrives -o IncludeFileSystemType=nfs,ufs(...) For avoiding the potential problems with performance and the amount of file evidence collected by Flexera agents running on Linux that you mentioned, you may want to: Use this option on selected computers only (run the agent from a command line or define options in the 'config.ini' file) and/or Refine the list of folders to be scanned by the Flexera agent using additional 'IncludeDirectory' and 'ExcludeDirectory' command line options. ... View more

I agree with "Captain Kirk"'s comments: Windows 10 Build 19041 - also named "Windows 10 Version 2004" or "20H1" - has been released in May 2020. This is the ninth major Windows 10 update. Major new features of this release are summarized in a Wikipedia article. If you already have Windows 10 Version 1909 installed, Version 2004 is now offered as an optional "Feature Update" when you open the "Windows Update" dialog. Offline installers for upgrading Windows 10 Version 10 Build 1909 to Version 2004 (KB4566782) can be downloaded from Microsoft, too. In the FNMS System Requirements, it is documented that the FNMS Windows agent supports all versions of Windows 7, 8 and 10. The Windows agent is a 32 bit application running both on 32bit and 64bit versions of Windows. It is designed to have as little dependencies on Windows components as possible. Generally, for new Windows builds you should not expect any compatibility issues when using the latest FNMS agent release. To confirm, after upgrading a clean Windows 10 Version 1909 Workstation Enterprise system to Windows 10 Version 2004, I installed and ran the latest Flexera FNMS 2020 R1 Windows agent on the system without any issues. You can find the agent LOG file attached to this contribution. ... View more

Hi dparab27, The installers and database migration scripts for the latest FNMS release can be found in the "Product and License Center" (PLC). As a registered FNMS customer or Flexera partner, below the "Other Resources" menu on this page, you open the PLC directly and browse to the "FlexNet Manager Platform" area. For instructions, use the "Upgrading FlexNet Manager Suite On-Premises" document, please. This document is available for download in PDF format together with a lot of additional documentation in the HelpNet area. Use the menu: "Other Resources > Documentation" for browsing to this page, please. ... View more

Hi msutharh, If the Inventories for these devices can be found in the [FNMSInventory].[Computer] table, you obviously have been able to import inventory data for the devices previously. Are there any NDI file that can be imported using the mgsImport tool succesfully? Which version (and command line options) of the Flexera Agent did you use for creating the latest NDI files where the import fails? Would it be possible to share one of these NDI files for testing, please? ... View more

Hi Stephen, For the shared folder to be configured into the Windows registry, make sure to: Use the Universal Naming Convention (UNC) format (\\servername\folder) for configuring the shares , please. At least the Windows Services account running the FNMS Windows Services on both application servers must have read & write (R/W) access to the shared folder(s). Typically, giving the Windows 'Everyone' user group R/W access to these shared folders works well. Configuring FNMS using a mapped drive (D:\....) for the shared folders instead of an UNC path typically won't work, as the Services Account won't be able to use this setting. ... View more

If you are interested in BitLocker, you can check the following branch in the Windows Registry: HKLM \ Software \ Policies \ Microsoft \ FVE The FVE folder will exist if BitLocker is installed and enabled only. Inside this folder, you find a lot of BitLocker related configuration settings, including a key 'EnableBDEWithNoTPM' that will have a value of '1' if the current device has a 'Trusted Platform Module' chip and a BIOS that allows storing the BitLocker encryption key. When collecting Inventory data using the Flexera agent, you can use the 'IncludeRegistryKey' option for enforcing the collection of configuration data from this part of the Windows registry. ... View more

Hi Stephen, Don't think that your error is related to the file type (Excel instead of CSV). Assuming that your customer is using a configuration where the FNMS application server is split into a FNMS WebUI web application server and a FNMS processing (Batch and Inventory) server, the KB article that you already found is pointing into the right direction. With this configuration, there is a requirement to configure both a "DataImport" as well as a "DataExport" folder in the file system. These two folders must be shared between the two FNMS application servers. You can find additional documentation in the "Installing FlexNet Manager Suite on Premises" document on page #26 and pages #49-51. Typically, these folders are shared on the FNMS processing (Batch and Inventory) server, and the Registry settings are updated manually on the FNMS WebUI server for making the shared folders known to the FNMS application. If you omit this configuration step at installation time, you will run into the error that you observed when you try to import files using standard FNMS import templates from the FNMS WebUI. The 3rd party statement "everything looks ok" most likely is not fully correct for this FNMS environment. ... View more