The following table details the FlexNet Manager Suite product version number that corresponds to each agent and beacon release number. Release number Product version 19.2.x 2022 R2.2 19.1.x 2022 R2.1 19.0.x 2022 R2 18.7.x 2022 R1.7 18.6.x 2022 R1.6 18.5.x 2022 R1.5 18.4.x 2022 R1.4 18.3.x 2022 R1.3 18.2.x 2022 R1.2 18.1.x 2022 R1.1 18.0.x 2022 R1 17.4.x 2021 R1.4 17.3.x 2021 R1.3 17.2.x 2021 R1.2 17.1.x 2021 R1.1 17.0.x 2021 R1 16.5.x 2020 R2.5 16.3.x 2020 R2.3 16.2.x 2020 R2.2 16.1.x 2020 R2.1 16.0.x 2020 R2 15.2.x 2020 R1.2 15.1.x 2020 R1.1 15.0.x 2020 R1 14.3.x 2019 R2.3 14.2.x 2019 R2.2 14.1.x 2019 R2.1 14.0.x 2019 R2 13.8.x 2019 R1.6 13.7.x 2019 R1.5 13.6.x 2019 R1.4 13.5.x 2019 R1.3 13.4.x 2019 R1.2 13.3.x 2019 R1.1 13.2.x 2019 R1 13.1.x 2018 R2 13.0.x 2018 R1 12.4.x 2017 R3 12.3.x 2017 R2 12.2.x 2017 R1 12.1.x 2016 R1 SP1 12.0.x 2016 R1 11.5.x 2015 R2 SP5 11.4.x 2015 R2 SP4 11.3.x 2015 R2 SP3 11.2.x 2015 R2 SP2 11.1.x 2015 R2 SP1 11.0.x 2015 R2 10.3.x 2015 10.2.x 2014 R3 10.1.x 2014 R2 10.0.x 2014 9.23.x 9.2.3 9.2.x 9.2   The 'x' values shown here release numbers may vary depending on any installed hotfixes. Product version and release number details appear on the FlexNet Manager Suite License page in the web UI. ... View more

Summary Here is the instructions for checking / changing the datawarehouse connection Synopsis For updating the DataWarehouse connection in the ComplianceConnection table, there is no interface to edit the connection details. Discussion This can safely updated directly, since it uses integrated authentication. To update the connection details use the following queries (this is for single tenant on-premises installation): For updating both DB server and the DB name update ComplianceConnection set Server = '<servername>', DatabaseName='<dbname>' where SourceType='FNMPDataWarehouse' or For updating only the DB sever name update ComplianceConnection set Server = '<servername>' where SourceType='FNMPDataWarehouse' or For updating the DB name update ComplianceConnection set DatabaseName='<dbname>' where SourceType='FNMPDataWarehouse' Registry The following registry key also needs to be modified "HKLM\Software\Wow6432node\Managesoft Corp\Managesoft\Reporter\CurrentVersion" and update the connection string in the registry key "FNMPDWDatabaseConnectionString" Update the references in Cognos. This can be edited through Cognos administration (i.e. as a web admin in Cognos Connection/Administration). Additional Information There is a bug - FNMS-25922 : Unable to Configure FNMPDataWarehouse DB connection details from UI ... View more

Summary Instructions for batch removing asset records from the FNMS database Synopsis Instructions for batch removing asset records from the FNMS database. Discussion Before carrying out these steps, ensure you have taken a full back of your database If you have a list of assets you which to remove, run the following SQL script on your FNMS Compliance Database: drop table #asset SELECT * INTO #Asset FROM [FNMSCompliance].[dbo].[Asset] where ShortDescription in ('Asset1''Asset2','Asset3') exec dbo.AssetRemoveBatch *Note: Add the asset names to the 'where ShortDescription in ('Asset1''Asset2','Asset3') ' line. This will delete all the assets specified. Related KB Articles Salesforce: 00822366 ... View more

Summary How can the beacon SAP system configurations be backed up on beacons? Synopsis You may wish to take a backup of your SAP configuration after spending time configuring them on a beacon. Discussion Normally, settings from a previous installation would persist when upgrading the beacon. There are three configuration files from beacon under: \ProgramData\Flexera Software\Beacon -ActiveSAPSystemLandscapes.xml -SAPSystemLandscape.xml -config.xml These can be copied and restored if required. ... View more

Synopsis In order to filter accounts for Oracle Instances, please filter them by 'Oracle service names'. Discussion When gathering Oracle inventory, FNMS connects via Oracle Listener. In this case, the device name is actually an oracle listener. Oracle listener can be configured to then connect to one or many Oracle Service Services. To connect to each service, FNMS uses the usernames/passwords stored in the password store. In other words, username/password created/configured are tied to an Oracle Service, not to an Oracle Listener, hence we recommend that the usernames/passwords in the password store are filtered by Oracle services. When Listeners change, no changes are required in the password stores. Note:Whenever a new instance is created, a username/password needs to be created/updated for FNMP to perform inventory gathering. So the Oracle DBA needs to do this and pass this information to FNMS administrator which then updates the password stores. ... View more

Summary This article describes the agent upgrade reboot requirement Question If our agents are upgraded via policy (the recommended method), a reboot should not be required. This is due to the use of relaunch.exe which shuts down services before the msi is upgraded. If upgrading via other means, a reboot is likely to be required. ... View more

Summary This guide provides an explanation of a stored procedure that can be used to automate operator account creation Synopsis Before carrying out the following steps, please ensure you take a full back of your database. SP GroupExAddGroupMembership can be used for adding an operator to a role. Example Usage -- Add given group member that is not in a group of the given type to a group of the given type ? i.e. assumes that group member is not already in a group of this type exec dbo.GroupExAddGroupMembership @GroupID=7,@TargetID=2,@TargetType=N'ComplianceOperator',@GroupTypeID=5 ... View more

Summary XenDesktop discovery: Installation and access requirements Synopsis The beacon must be installed and must be able to directly communicate with the XenDesktop broker. The XenDesktop broker must allow remotely signed PowerShell scripts to be run. See Knowledge Base  Article - Set up Remote Powershell for XenDesktop discovery https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Set-up-Remote-Powershell-for-XenDesktop-discovery/ta-p/5892 You can check to see the execution policy on the XenDesktop broker server by opening a PowerShell window on it and running Get-ExecutionPolicy Ensure the policy is either RemoteSigned, AllSigned, or Unrestricted (not recommended). If it is Restricted, run the following command to set it RemoteSigned Set-ExecutionPolicy RemoteSigned Ensure the server running the beacon also has a similar PowerShell execution policy so it can run the required PowerShell commands to communicate with the XenDesktop broker. Ensure the password store on the beacon has an entry for the XenDesktop server. Troubleshooting Look at the beacon logs for errors relating to XenDesktop discovery %PROGRAMDATA%\Flexera Software\Compliance\Logging\BeaconEngine Turn on tracing by modifying <INSTALL DIR>\Flexera Software\Inventory Beacon\etdp.trace and enabling the Scheduling/RemoteExecution tracing option ... View more

Summary How to specify a path or paths for the inventory agent to scan for evidence Synopsis In order to specify a directory for ndtrack to scan, use the following switch -o IncludeDirectory=<specify path> Example: ndtrack -t machine -o IncludeDirectory=/ehc/fs1/softs/SOFT1 If you want to include multiple paths, separate each one with a semi colon Example: ndtrack -t machine -o IncludeDirectory=/ehc;/Var Additional Information See the Preferences for Managed Devices guide (attached to this KB article) for further information about the inventory agent. ... View more

Summary Error 0x80092013: The revocation function was unable to check revocation because the revocation server was offline. Symptoms Uploads from zero-touch inventory won't work over HTTPS even when using the command switches CheckCertificateRevocation=False -o CheckServerCertificate=False The following error is displayed: [11/2/2015 12:00:08 PM (N, 0)] {4348} Error 0x80092013: The revocation function was unable to check revocation because the revocation server was offline. [11/2/2015 12:00:08 PM (N, 0)] {4348} Error 0xE050044D: Failed to create remote directory /ManageSoftRL [11/2/2015 12:00:08 PM (N, 0)] {4348} Error 0xE0690099: Specified remote directory is invalid, or could not be created [11/2/2015 12:00:08 PM (G, 0)] {4348} ERROR: Remote directory is invalid [11/2/2015 12:00:08 PM (G, 0)] {4348} WARNING: FlexNet Manager Platform has failed to upload a file to all configured upload servers; aborting attempt to upload these file(s) [11/2/2015 12:00:08 PM (G, 0)] {4348} Uploading finished Cause Internet Explorer is incorrectly configured to use a proxy server. Resolution Change the following registry keys on the server: - HKEY_Users\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings - should be empty - HKEY_Users\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ProxyEnable - value 0 All keys in "HKEY_Users\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\" related to proxy, should not be present. If they are - delete them or disable. ... View more

Summary The following error may occur when running a reconcile. This article contains a description of the issue and possible resolutions. "Error: The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions." Symptoms You may see the following error message displayed in the Importer log: 2018-01-16 05:42:34,348 [INFO ] Failed to execute Writer 'DeleteUnrequiredInstalledFileEvidence' from file E:\FNMSProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\FileEvidence.xml, at step line 13 Error: The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. 2018-01-16 05:42:34,348 [INFO ] All retries have been attempted for Writer 'DeleteUnrequiredInstalledFileEvidence' 2018-01-16 05:42:34,363 [ERROR] System.Data.SqlClient.SqlException (0x80131904): The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.? Cause Possible causes of this issue: A reconcile was running and changing DB data at the same time a Web UI user changed the same table. For example when the license reconcile is running and updating licenses, if a user was to save a license this can stop the reconcile as the lock will be held by the Web UI user. On-premise only: Database settings are not set correctly according to the product specifications, for example if a database is set to a FULL recovery model instead of SIMPLE. To confirm the settings use the following query: SELECT * FROM sys.dm_exec_requests CROSS APPLY sys.dm_exec_sql_text(sql_handle) SELECT * FROM sys.sysprocesses WHERE open_tran = 1 SELECT * FROM sys.databases DBCC SQLPERF(logspace) SQL Server memory allocation has not been configured to have enough resources. SQL Server affected by a known bug in certain versions (see the Microsoft link in the Additional info section below). Resolution Firstly, re-run the reconcile and confirm if the issue can be reproduced. It may be advisable to run this when the system is expected to be idle and to change the scheduled job as necessary. If the issue reoccurs it will need further investigation by engineering. For Cloud customers, there can be limited troubleshooting beyond attempting to re-run a reconcile - so contact support for assistance if still continuing issues. To adjust the database settings (for recovery model, etc): Open SQL Server Management Studio and connect to the relevant instance. Right-click the DB and click Properties. Click the Options tab. To adjust SQL Server memory allocation: Open SQL Server Management Studio and connect to the relevant instance. In Object Explorer, right-click a server and select Properties. Click the Memory node. Under Server Memory Options, enter the same amount that you want for Minimum server memory and Maximum server memory. Use the default settings to allow SQL Server to change its memory requirements dynamically based on available system resources. It is recommended to set a max server memory as detailed above. Additional Information Effects of min and max server memory: https://technet.microsoft.com/en-us/library/ms180797(v=sql.105).aspx FIX: Performance problems occur when database lock activity increases in SQL Server: https://support.microsoft.com/en-in/help/2926217/fix-performance-problems-occur-when-database-lock-activity-increases-i ... View more

Summary All agents installed are not able to refresh their policy Symptoms From a deployed beacon, the following error is found in the BeaconISS log file : 2018-02-15 08:29:48,856 [mmon.BeaconPolicyCache] [ERROR] Could not load policy file from disk. System.IO.IOException: The process cannot access the file 'C:\ProgramData\Flexera Software\Beacon\BeaconPolicy.xml' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at Flexera.Beacon.Common.BeaconPolicyCache.LoadBeaconPolicyFromDisk() As consequence, new agents are not reporting to the App Server. Cause If you get the System.IO.IOException: The file exists error, it's probably because your C:/Windows/Temp folder is absolutely full with temporary files. In fact, if you have more than 65535 files in your temp folder, the method GetTempFileName will throw this error. Resolution To resolve this, just remove all temporary files in C:/Windows/Temp. It might take some time, but it will solve the problem. After clearing files from c:\windows\temp and restarting the beacon engine service, then agents should be able to update their policy. ... View more

Summary VMWare License Keys are masked in FNMS Synopsis The license keys for application, which we are getting from vCenter in "VMWare Inventory" module are masked for "read only access" credentials and Full keys are visible while using privileged credentials. Discussion Flexera's advice is that you use a VMWare Administrator account and so it is likely this is caused by a security blockage from the VMWare server. Please see the below except from the online help relating to this: Using Password Manager When Collecting Specialized Inventory Inventory type: VMware infrastructure Server type: VMware vCenter or VMware ESX servers For each inventory beacon managing the target servers, add the credentials of the vCenter administrator to the Password Manager. Select Account on VMware VirtualCenter from the Account type drop-down to inventory a VMware vCenter Server, or select Account on VMware ESX server to inventory a VMware ESXi Server. For more information on VMware inventory, see VMware Device and Infrastructure Inventory. Tip: Best practice is to take inventory of a VMware vCenter Server rather than individually targeting multiple VMware ESXi Servers being managed by it. When you inventory a VMware vCenter Server, the inventory beacon also inventories all the VMware ESXi Servers being managed by the vCenter Server. http://<FNMS Server>/Suite/Help/webhelp/index.html#tasks/PwdStore_VMwareInfrastructure.html Workaround Use a VMWare Administrator account for VMWare Inventory collection. ... View more

Summary What steps are required to add new columns to custom views in the FNMS Cloud? Synopsis This will be possible if you provide Flexera support with the specific changes required based on the guidelines of section 1 'Adding Custom Properties', page 12 of the FNMS System Reference Guide. See the attached the FNMS System Reference Guide ('FNMSSystemReferencePDF.pdf'). Discussion Adding Custom Properties It is possible to add properties to underlying database objects, and have these custom properties displayed in the web interface. If you have an on-premises implementation, with your own database, you can implement the changes yourself, following the guidelines in this chapter. If you use a cloud-based implementation, you can use these chapters to create a detailed specification of your requirements, and then submit a change request to your support contact from Flexera (or your third-party managed service provider) to implement your specified changes on your behalf. Custom Properties With a little technical effort, you can customize the properties of many objects presented in FlexNet Manager Suite. The complexities of managing software licenses within your corporate processes inevitably means you will want additional fields to record data specific to your enterprise. This section explains how you can specify additional properties for various objects that are displayed in the property sheets and your custom reports within FlexNet Manager Suite. Tip: Since the 2015 R2 SP1 release of FlexNet Manager Suite, it is no longer necessary to download a SQL stored procedure to enhance the database for custom properties. This functionality is now built in to the database as installed. The broad overview of the process is: 1. Plan your custom property, including its control type, and where it should appear in the properties of its parent object. 2. In Microsoft SQL Server Management Studio, execute specific SQL procedures to declare your customization in a "top down" manner. For example, if you want an extra field in a new section of an entirely new tab of properties, you must first declare the tab, then the section, and then the field. Objects are positioned relative to others that already exist in the database. In running the procedures, you must also refer to all objects and properties by their internal names, or by numerical mappings. Those names and mappings are included below, in Internal Property Names for Applications and the following similar topics. 3. Customizations are available immediately after the SQL procedure is run, so you can review the results immediate in the web interface for FlexNet Manager Suite. You can also immediately commence storing data in your new custom field through the web interface, as the database has been updated to store your data. 4. While the compliance database and the web interface are updated immediately, the data model for the Business Adapter Studio installed on your inventory beacon(s) is updated by a scheduled task running overnight. This means either waiting until next day before importing values with a business adapter to your new custom field; or you can trigger an immediate update as described in Triggering Immediate Update of the BAS Data Model. Tip: In general, customizations you make to the user interface and database are preserved through product upgrades. The one exception is the rare case where a product upgrade removes the 'anchor', the object used for positioning your custom control. In this case, both the anchor and your custom control disappear (although the data entered through the control is preserved and is still available in your customer reports). You can remedy this rare case by re-declaring the missing custom control relative to a new anchor. This restores your customization in the web interface, with full access to the previously-recorded data values. Limitations In the web interface, a custom property is displayed in the property sheet of your chosen object, and it is automatically available in the report builder for inclusion in custom reports. However, the custom property is not available in the following: ? Standard, factory-supplied reports ? Grids in management views ? Search fields, including within property sheets. As well, custom properties are always editable in property sheets (they cannot be made read-only in that context), and you cannot provide any validation to check data entered into the custom control. In declaring internal names for your custom properties, you should adopt a stringent naming convention that starts with your own company name-space (a consistent abbreviation for your enterprise name, such as AE for Acme Enterprises). You'll next find it convenient to name the object type that you are adding (such as Asset). Finally, add the individual name of the property. Separate each of these naming elements with an underscore. Use only characters in the following ranges: a-z, A-Z, 0-9, and underscore (_). (Specifically do not use a dot or dash.) A valid example name is: AE_Asset_ChargeBackValue Warning: Do not use a naming convention that starts with the database object name and uses a dot as a separator. This combination produces obscure errors. Starting with your own name space makes it safe, and using an underscore separator also makes it safe. ... View more

Summary No inventory gathering on device 'Device_Name' because the discovery did not find the server type Symptoms The following FlexNet Manager Suite On-Premises error can be seen in the VMWareInventory.log files: No inventory gathering on device 'Device_Name' because the discovery did not find the server type.   Cause This is a known issue when the Inventory Beacon is not able to verify that the VMware vCenter/Host Server has an SDK open on the target port. The VMware vCenter/Host inventory scan goes through three processes when it is targeted: STEP 1: Discover the device information, IP to Host resolution, Host to IP resolution, and its open ports while scanning the provided list STEP 2: Discovering the existence of a VMware SDK using the IP Address STEP 3: Taking inventory of the vCenter/Host using credentials from the Inventory Beacon's Password Store, targeting by IP Address The above error refers to the failure of Step 2. The best way to test if the Inventory Beacon Server has access to the VMware vCenter/Host is through a Web Browser with the following link, while having any Internet Proxies disabled (vimService.wsdl is case sensitive!): https://IPAddress:PortNumber/sdk/vimService.wsdl (e.g. https://10.1.10.101:443/sdk/vimService.wsdl) . If you get an xml-formatted page or a login screen, then the test passed. If you get a "page not found" error, try the following to make sure it's not a firewall issue which this link should ask you for a login if it passed the firewall:  https://IPAddress:PortNumber/mob (e.g. https://10.1.10.101:443/mob) Possible causes are as following, sequenced by the most common: A firewall is blocking the port between the vCenter/Host and the Inventory Beacon Server (above browser tests will both fail) The target vCenter/Host does not have a SDK enabled/fully-enabled (above SDK browser test will fail) The Local_Machine registry keys have forced policy to use an Internet Proxy, which would apply to the Inventory Beacon since it by default runs as the Local System account (above browser tests might succeed) The current mgsipcan (Flexera's port scan tool) reported 443 as "filtered" not "open" which prevented inventory to proceed. (above browser tests will succeed).   Resolution This can be resolved by identifying which of the 4 common causes and contacting the proper internal department (e.g. Network Security, Firewall Team). If the issue is not due to the first three issues, then it could be due to cause #4. This can be resolved by downloading the attached MGSIPScan.zip to the inventory beacon server and unzip it to the following directory: Program Files (x86)\Flexera Software\Inventory Beacon\RemoteExecution\MgsIPScan\ - overwriting the current contents. ... View more