FlexNet Manager 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
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
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
Symptoms: When running a ServiceNow export from FNMS to ServiceNow, you may encounter one or more errors related to connection or secure channel errors such as: ServiceNowConnectionTest.SendTestConnection: Error Checking Connetion to endpoint: api/x_fls_flexera_fnms/integration/fnmstosn System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel. at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at FNMP.ServiceNow.HTTP.ServiceNowRequest.WriteData(HttpWebRequest request, String content) at FNMP.ServiceNow.HTTP.ServiceNowRequest.Post(String content) at FNMP.ServiceNow.HTTP.ServiceNowConnectionTest.SendTestConnection() [2019-09-08 03:01:50] - [DEBUG]: Exiting ServiceNowConnectionTest.SendTestConnection Diagnosis: This has been identified as related to the changes ServiceNow made to disable both both TLS 1.0 and TLS 1.1 [1] This process appears to have been in an instance-by-instance basis so not all customers are experiencing this issue. Solution: See KB article Transport Layer Security (TLS) 1.1 & 1.2 Configuration References: https://hi.service-now.com/kb_view.do?sysparm_article=KB0746078
View full article
Summary It is common for a number of unwanted or old computers and network devices to appear in ManageSoft databases over time. In order to ensure accuracy in numbers shown by reports, it is good practice to implement strategies to clean up these records. This article describes a number of approaches which can be followed to remove such records from the database. The attached zip file includes the text of the article and several helpful installables and procedures. Synopsis It is common for a number of unwanted or old computers and network devices to appear in the ManageSoft databases over time. In order to ensure accuracy in numbers shown by reports, it is good practice to implement strategies to clean up these records. This article describes a number of approaches which can be followed to remove such records from the database. The attached zip file includes the text of the article and several helpful installables and procedures. Discussion Introduction You may want to delete information about a computer or network device for a number of reasons. Some examples include: The computer has been made obsolete or removed from the environment. Inventory (or other) information has not been received from the computer for a long period of time. The device was discovered on the network at some point in the past but has not been seen for a long time. Background In order to understand how to clean up data about computers and network devices, it is important to understand how ManageSoft stores this information. There are two key types of entity that ManageSoft keeps track of:   A ?computer? (recorded in the Computer table in the database) is a piece of hardware such as a desktop, laptop or server. ManageSoft can potentially collect inventory, install packages, collect application usage information and perform other similar operations on computers. Computers are added to the database by a range of operations, including importing an inventory, installation log or other information from a managed device agent, the server side policy merge operation, and when information from a network discovery is imported. A ?network device? (recorded in the NetworkDevice table) is a device that has been found within an environment by ManageSoft discovery processes. Typical discovery processes performed by ManageSoft include IP range scans, enumeration of devices in a WINS browser list (NetBIOS discovery), or discovery based on inventory information that has been received from devices. A computer may be linked to one or more network device records in the database, and a network device may be linked to a computer. This information is stored in the ComputerID field of the NetworkDevice table. Data about computers and network devices stored in the database can be cleaned up independently of each other.   Workaround Procedure The following sections describe various ways to remove computer and network device data from the ManageSoft database. After deleting computer or network device records, be aware of the processes which can cause these records to be recreated in the database. When those processes happen, the records will be created as if the computer had never been known about previously?any previously recorded data for the records will no longer exist. Your ManageSoft database should already be configured to be backed up regularly with appropriate recovery procedures in place. Before deleting any significant amounts of data, it is wise to ensure that a recent backup has occurred successfully in case there is any need to recover lost data.   Computer deletion from Active Directory The typical mechanism by which information about a computer is deleted from ManageSoft is through Active Directory: when a computer account is deleted from (or disabled in) Active Directory, the next server side policy merge process performed by ManageSoft will delete all information about that computer from the ManageSoft database. This is the method of choice by which most cleanup of computer records should be achieved. However it may not be appropriate in all situations. For example: Not all computers that ManageSoft keeps track of and knows about are associated with computer accounts in an Active Directory domain. Not all organizations have a tight obsolescence process which ensures computer accounts in Active Directory are deleted or disabled in a timely manner. In situations such as these, some of the strategies discussed further below can be followed. Operations Portal module for computer deletion The attached DeletePortal.zip file contains a module for the ManageSoft Operations Portal which can be used to delete computer records based on name or date inventory information was last received. The following steps can be used to install and access the module: Uncompress the contents of DeletePortal.zip in to [INSTALLDIR]\Portal\Web\Modules\ ([INSTALLDIR] is the installation directory of ManageSoft, typically c:\Program Files\ManageSoft) on the reporting server. Navigate to http://reporting-server/ManageSoftOP with Internet Explorer. Select the Data Management > Delete Computers menu option. Follow the guidance and interface presented to list and delete appropriate computers by name or inventory age. Computer deletion using direct SQL statements Information about computers can be deleted directly from the database using appropriate SQL statements. These statements can be constructed to select and delete computers according to logic or heuristics you choose. See the ManageSoft System Reference documentation (Ref-System_Reference.pdf) for further information about the ManageSoft database schema. The ManageSoft database contains a stored procedure named DeleteComputer which can be used to delete an individual computer record based on its ComputerID. This procedure can be used as follows: DECLARE @ComputerID INT SET @ComputerID = ID of the computer to be deleted EXEC DeleteComputer @ComputerID ManageSoft 7.8.1 or later databases contain an additional DeleteComputers stored procedure which can be used to delete a set of computers. It is more efficient to delete a set of computers using DeleteComputers than it is to delete them one at a time using DeleteComputer. The DeleteComputers procedure can be used as follows: -- Create a temporary #Computer table containing the -- IDs of the computers to be deleted SELECT ComputerID INTO #Computer FROM Computer WHERE whatever condition you need for deleting computers -- Delete the computers listed in #Computers EXEC DeleteComputers -- Drop the temporary table as we don?t need it any longer DROP TABLE #Computer The attached SQL scripts contain a number of examples using these stored procedures to delete computers based on different heuristics: DeleteComputerByInventoryDate.sql: Deletes computers based on the last date on which hardware inventory was received. Computers whose most recent hardware inventory was received more than 90 days ago are deleted. DeleteComputerByDomain.sql: Deletes computers recorded in a specified domain. A couple of approaches to consider when determining how and when to run a SQL script to perform any cleanup are to: Execute the script manually using an interface such as SQL Query Analyzer. Execute the script automatically on a scheduled basis using a SQL Server Agent job. If you are not familiar with how to do these things, contact your database administrator or see SQL Server Books Online for more information. Network device deletion using direct SQL statements As with computers, network device records can be deleted directly from the ManageSoft database using appropriate SQL statements. No stored procedures are provided to do this; records should be deleted directly from the NetworkDevice table. Be aware of the following constraints when deleting records from the NetworkDevice table: Any records in the ActionApplies table with a DeviceID field value that refers to a record in the NetworkDevice table should be deleted before deleting the NetworkDevice record. Any records in the NetworkDevice table with a DuplicateID field value that refers to another record in the NetworkDevice table should be deleted before deleting the later NetworkDevice record. A typical script to clean up records in the NetworkDevice table looks like the following: USE ManageSoft -- Select network devices to be deleted SELECT DeviceID INTO #NetworkDevice FROM NetworkDevice WHERE whatever condition you need for deleting network devices -- Delete all references and records for the selected devices DELETE FROM ActionApplies WHERE DeviceID IN (SELECT DeviceID FROM #NetworkDevice) DELETE FROM NetworkDevice WHERE DuplicateID IN (SELECT DeviceID FROM #NetworkDevice) DELETE FROM NetworkDevice WHERE DeviceID IN (SELECT DeviceID FROM #NetworkDevice) -- Drop the temporary table as we don?t need it any longer DROP TABLE #NetworkDevice The attached SQL scripts contain a number of examples of scripts to delete network devices based on different heuristics: DeleteNetworkDeviceByLastUpdate.sql: Deletes network device records based on their LastUpdate field; devices that have not been updated for more than 90 days are deleted. The LastUpdate field records the date and time at which a device was last discovered or had any inventory details relevant to discovery change. DeleteNetworkDeviceByDomain.sql: Deletes network device records by the NT/NetBIOS domain they are in.   Related KB Articles How Inventory Manager / FlexNet Manager Suite License Enforcement Works  
View full article
Summary This article explains how Inventory Manager and FlexNet Manager Suite are licensed, and the behaviour of these products when license consumption approaches or exceeds the purchased license entitlements. Synopsis In this article we will explain how Inventory Manager and FlexNet Manager Suite are licensed, and the behaviour of these products when license consumption approaches or exceeds the purchased license entitlements for this product.   Discussion Inventory Manager licensing How license consumption is measured Inventory Manager is licensed per computer/device under management, as determined by there being at least one installation record for that computer in Inventory Manager. Computers that have been discovered by IM but which have no installation records do not count towards license consumption, as they are deemed to not be managed. To calculate license consumption, run the following SQL query on the Inventory Manager database: SELECT COUNT(DISTINCT ComputerID) FROM Installation What happens when a license is breached When license consumption exceeds 80% of the overall license entitlement, a warning is displayed the next time the Inventory Manager Server console is opened. The user can configure the amount of time that should pass before the next warning is shown. When Inventory Manager exceeds its license entitlement, all subsequent attempts to open the administration console are denied. All users are locked out of the administration console until license consumption is reduced to an acceptable level. FlexNet Manager Suite licensing How license consumption is measured FlexNet Manager Suite is licensed per computer. Ignored and discarded computers do not count towards license consumption. For releases 8.2.1 to 8.6, computers linked to retired or disposed assets do not count towards license consumption. For release 9.0 and later, virtual machines without agent inventory do not count towards license consumption. Note that computers require a license regardless of whether they have been imported from IM, SMS or any other inventory source. To calculate license consumption for release 9.0 and later, run the following SQL query on the FlexNet Manager Suite database: SELECT COUNT(*) FROM dbo.ComplianceComputer AS cc LEFT OUTER JOIN dbo.Asset AS a ON a.AssetID = cc.AssetID -- Ignore ignored, placeholder and discarded computers WHERE cc.ComplianceComputerStatusID NOT IN (2, 4, 5) AND -- Ignore computers linked to retired or disposed assets (a.AssetID IS NULL OR a.AssetStatusID NOT IN (4, 5)) AND -- Ignore remote devices cc.ComplianceComputerTypeID <> 4 AND -- Ignore light virtual machines cc.ComplianceComputerInventorySourceTypeID <> 2 To calculate license consumption for servers, run the following SQL query on the FlexNet Manager Suite database: select count(1) from compliancecomputer where OperatingSystem like '%windows%server%' or OperatingSystem like '%linux%' or OperatingSystem like '%Ubuntu%' or OperatingSystem like '%centos%' or OperatingSystem like '%sunos%' or OperatingSystem like '%sun_os%' or OperatingSystem like '%aix%' or OperatingSystem like '%bsd%' or OperatingSystem like 'VMWare ESX%' or OperatingSystem like '%Mac%server%' or OperatingSystem like '%HPUX%' or OperatingSystem like '%HP_UX%' or operatingsystem like '%SuSE%server%' or operatingsystem like '%redhat%server%' or operatingsystem like '%red hat%server%' or operatingsystem like '%RedHatEnterpriseAS%' or operatingsystem like '%RedHatEnterpriseES%' or operatingsystem like '%Red Hat %AS%' -- ADDM evidence or operatingsystem like '%Red Hat %ES%' -- ADDM evidence or operatingsystem like '%RH-EL-%' or operatingsystem like '%RH-ES-%' What happens when a license is breached If you exceed the number of active computers for which FlexNet Manager Suite is licensed, users are given a warning each time the administration console is opened for the next 30 days. If the license breach is not resolved within 30 days, FlexNet Manager Suite subsequently does not allow the addition of any new computers, as follows: The inventory importer does not import any new computers. However, computers already in FlexNet Manager Suite are updated as normal. The administration console does not allow manual creation of a new computer.   Workaround To remove unwanted devices please view R emove unwanted computers and network devices from ManageSoft . Additional Information Note: If you have Inventory Manager and Flexnet Manager Suite installed on the same computer then you need to run each query and the highest of these will be used by the license enforcement to calculate the license count.
View full article
Summary This KB article addresses the error: "The system cannot find the file specified" which is recorded in the recognition.log when running the ARL update. Symptoms Your ARL update fails and you find the following error in the Recognition.log (usually found in C:\Windows\Temp):     Error running command: sqlcmd.exe -S SQL07SZD -d ManageSoft -b -i "C:\Users\svc-mgs\AppData\Local\Temp\Recognition\ARLCreateTables86.sql" -E ******************************************************* ERROR ------------------------------------------------------- System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at ManageSoft.Recognition.Recognition.ExecuteSQLFile(LogWriter log, String filename) at ManageSoft.Recognition.Program.ExecuteSQLFile(LogWriter log, Recognition arl, String sqlDir, String sqlFile) at ManageSoft.Recognition.Program.Main(String[] args) *******************************************************   Cause This error means that either SQLCMD.exe file is missing or is not set in the PATH environment variable.     Resolution Install Microsoft Command Line Utilities which includes the SQLCMD utility.  Older versions of SQL Management Tools includes SQLCMD as part of the install however the newer 18.x versions of SQL Management Tools no longer includes the file making it necessary to install it separately using the Microsoft Command Line Utilities. If the older version of SQL Management Tools is installed and the PATH environment variable is not set automatically (due to User Account Control), the workaround section below contains a method to set the PATH if that is the case.   Workaround If the path for SQLCMD.exe was not set in the PATH variable, use the method below:   Install SQL Command Line Utilities (SQLcmd.exe + bcp.exe) Turn UAC off and then reboot Start cmd as Administrator Add the path of sqlcmd.exe using ?setx PATH <Actual Path to file> ?m? UAC can now be turned back on if required   The PATH should now be set and the ARL update should no longer produce the error covered by this article.   Additional Information The <Actual Path to file> in the Workaround above depends on version, for example on 2008 it is: "C:\Program Files\Microsoft SQL Server\100\Tools\Binn" - the 100 is what shows it is 2008, so make sure that you use the correct folder for your version.
View full article
Summary For secure environments (for example, Oracle servers secured by firewalls), Flexera offers a stand-alone Oracle inventory collection agent that can be deployed on a compatible Windows server. This article explains what you need to know and do to use it. Discussion Discovery and inventory information is a prerequisite to performing license consumption calculations in FlexNet Manager Suite. We recommend that you deploy one or more inventory beacons on your network, and use any of the supported inventory collection methods to collect Oracle inventory. Each inventory beacon collects discovery and inventory information from the devices within its assigned subnet and sends this information to FlexNet Manager Suite. To collect inventory, each inventory beacon requires a network connection to the target Oracle servers within its assigned subnet. In secure environments (for example, Oracle databases secured by firewalls), you may not be able to establish a network connection between each installed inventory beacon and the Oracle servers within its assigned subnet, or you may not be able to install any inventory beacon at all. For such environments, Flexera offers a stand-alone Oracle inventory collection agent that can be deployed on a compatible Windows server. The stand-alone agent collects and saves the Oracle Database inventory information (.ndi files) to a specified location. You can collect hardware inventory (required for Oracle processor-based licenses) through the locally-installed ndtrack or any third-party inventory database. If you do not deploy the agent on an inventory beacon, you will have to transfer the collected data to FlexNet Manager Suite, for performing license consumption calculations. Note: Flexera recommends that you use the stand-alone inventory agent, and not ORATrack, for collecting inventory data on Oracle installations. The stand-alone inventory agent collects hardware information as well as Oracle installation data (whereas ORATrack only collects Oracle data), so it will provide a more comprehensive result. This document describes the installation and operation of the stand-alone Oracle inventory agent. The Oracle Discovery and Inventory chapter of the Systems Reference Guide PDF explains the supported inventory collection methods. Overview The stand-alone Oracle inventory agent has been designed to remotely collect Oracle Database inventory from Oracle servers when you cannot use any of the inventory collection methods recommended by Flexera. You can deploy this agent on any computer with Windows desktop (Windows 7 or higher) or Server (2008 or 2012) edition. After you configure the agent with details of the target Oracle servers, the agent can connect to each Oracle server using the Oracle Data Access Component (ODAC) driver (installed as a part of Oracle client on the computer where the agent is deployed). The agent then uses a pre-configured audit database user to extract Oracle inventory. The collected information is saved to a configured location from where it can be uploaded to FlexNet Manager Suite for license consumption calculations. The following diagram illustrates the process of Oracle inventory collection through the stand-alone Oracle inventory agent. Important: We recommend that you use the stand-alone Oracle inventory agent only for Oracle hosts that have a single Oracle database service running on them. To collect Oracle inventory through the stand-alone Oracle inventory agent, complete the following steps: Verify the prerequisites. See the Prerequisites section below. Deploy the inventory agent. See the Deploying the Agent section below. Configure the inventory agent. See the Configuring the Agent section below. Collect Oracle inventory. See the Collecting Inventory section below. Export the collected inventory to FlexNet Manager Suite. See the Exporting Inventory section below. (Optional) Uninstall the inventory agent. See the Uninstalling the Agent section below. Prerequisites The following are the prerequisites for inventory collection using the stand-alone Oracle inventory agent: On the computer where the agent is to be deployed Windows desktop (Windows 7 or higher) or Server (2008 or 2012) edition Microsoft .NET Framework version 4.0 or later Oracle Client version 11.2xxx (32-bit). It contains the ODAC driver required to connect to Oracle servers. On each target Oracle Database server An audit account with read-only permissions on the Oracle Database for all the tables and views needed for collecting Oracle inventory. One helpful practice is to use the same set of credentials on all servers. You can use a specially designed script to create and configure an audit user (for example, fnmoaudit) on each Oracle server with a password of your choice. To get this script, go to this Knowledge Base article on the Flexera Community. The script is available as an attachment at the bottom of the page. For details about Oracle tables and views required for inventory collection, see the Appendix below. Deploying the Agent The stand-alone Oracle inventory agent is shipped as a zip archive. You can deploy this agent on a computer with a compatible version of Microsoft Windows. Follow these steps to deploy the agent: Create a temporary folder (for example, OracleInventory) on the Windows desktop or any other location. Extract the contents of the Flexera-supplied stand-alone inventory agent file Oracle-Agent.zip into this folder. Using Windows Explorer, create a folder to save the collected inventory information (for example, C:\Inventories\). You should add this path to the OutputDir parameter in the oratrack.ini file. Configuring the Agent To enable the stand-alone Oracle inventory agent to collect inventory from target Oracle databases, register every target Oracle server with the agent, and record the Oracle service name for each Oracle server in the oratrack.ini file. Follow these steps to configure the agent: Ensure that you have both: Installed the compatible ODAC driver on the Windows server where the agent is deployed. Created the audit user on each of the target Oracle servers. Launch the Windows command prompt with the "Run as administrator" option enabled and browse to the OracleInventory folder. Invoke the agent by using the following command. The agent should display a list of available options: ..\OracleInventory> oratrack server Query specified server -a Query all configured servers -l List configured servers and credentials -s Set logon credentials for server -d Delete logon credentials for server When the agent is not being run for the first time, use the following command to list any previously-targeted Oracle servers that are still registered with the agent. oratrack.exe -l If any undesired Oracle servers are registered with the agent, use the following command with the name of the Oracle server whose registration is to be deleted. oratrack.exe -d <server name> where <server name> is the name of the target Oracle server. Use the following command to register a target Oracle server with the stand-alone Oracle inventory agent. The agent will collect inventory only from the Oracle servers registered with it. oratrack.exe -s <server name> where <server name> is the name of the target Oracle server that is to be registered with the agent. The agent prompts you to enter the credentials of the audit user created on this server with the user creation script. For details about how to get the user creation script, see the Prerequisites section above. Enter the credentials for the audit user created on this Oracle server. Repeat step 6 for each of the target Oracle servers. The agent records each server name with its user name and encrypted password in the oratrack.ini file in the OracleInventory folder. To record Oracle service names, open the oratrack.ini from the OracleInventory folder. The file should contain details of every Oracle server registered with the agent. Add the service and port information for each of the registered Oracle servers. The sixth line of the following code shows an example service name for the oracle.example.com Oracle server. [Global] OutputDir=C:\Inventories [oracle.example.com] Username=<user name> Password= ($%^&(^TIJHHDJH Service=<service name> Port=<port num> Note: The oratrack.exe tool encrypts the password automatically, before saving it to the oratrack.ini file. Set the OutputDir parameter to the path where you want the agent to store the collected inventory files. The above code example sets the output directory to C:\Inventories. Use the following command to review the list of Oracle servers registered with the stand-alone agent: oratrack.exe -l Your agent is now ready to collect inventory from target Oracle servers. Warning: We do not recommend using the stand-alone Oracle inventory collection agent with Oracle hosts running multiple Oracle Database services. If you are using the stand-alone Oracle inventory agent to collect inventory from such an Oracle host, you need to: Make sure that the multiple database versions on the host are compatible with the Oracle client version installed on the computer where you are using the Oratrack agent. If the database versions are incompatible with the installed Oracle client version, the agent may not work as expected. Run the tool for every Oracle service on the host, after changing the service name in the oratrack.ini file. Copy the generated inventory (.ndi) file out of the output folder, before you run the tool with the changed service name to save it from being overwritten with the new inventory file. Upload the multiple inventory files to FlexNet Manager Suite. Collecting Inventory When you have registered all target Oracle servers with the stand-alone Oracle inventory agent, you can run the agent to collect Oracle Database inventory from the registered Oracle servers. Follow these steps: Use the following command to run the stand-alone Oracle inventory agent. The agent executes, collects inventory from each of the Oracle servers listed in the oratrack.ini file, and saves the inventory files (.ndi) in the output folder specified in the oratrack.ini file. oratrack.exe -a The agent runs and displays some log messages. Wait until the command execution is over. Navigate to the output folder (C:\Inventories) and verify that an .ndi file exists for each of the target Oracle servers. If the inventory file for a particular Oracle server is missing, you can test its connectivity using the following command: sqlplus fnmoaudit/<password>@<oracle instance> where fnmoaudit is the name of the audit user, <password> is the password for the audit user, and <oracle instance> is the name of the Oracle server. Contact your network administrator to resolve any connection errors. Exporting Inventory The license consumption calculation process of FlexNet Manager Suite requires the collected .ndi files for calculating your Oracle license position. If you have installed FlexNet Beacon software, you can manually transfer the collected inventory (.ndi) files to the Warehouse directory\Incoming\Inventories folder. The inventory beacon uploads the inventory to FlexNet Manager Suite. If you have not installed any inventory beacon, you can use any third-party methods to export the imported inventory to the C:\ProgramData\Flexera Software\Incoming\Inventories folder on the FlexNet Manager Suite server. Some Oracle license calculations (for example, processor-based) are dependent on the hardware information of the host. To get accurate license consumption calculations, FlexNet Manager Suite advises you to gather and upload the hardware inventory of the target Oracle hosts, in addition to the Oracle Database inventory. You can use any third-party inventory system, or any Flexera recommended inventory collection method, to collect hardware inventory from the target Oracle servers. For more information about the inventory collection methods supported by Flexera, see the Oracle Discovery and Inventory chapter in the System Reference Guide PDF. Uninstalling the Agent You can easily uninstall the stand-alone Oracle inventory agent by following these steps: Using Windows Explorer, delete the following folders: OracleInventory — the deployment folder C:\Inventories\ — the output folder. (Optional) Request your Oracle Database administrator to remove the audit user from each of the target Oracle servers. Appendix: Oracle Tables and Views for Oracle Inventory Collection You need to create a database audit account on each of the target Oracle servers to collect Oracle inventory using the stand-alone Oracle inventory agent. The database account must have read-only access to the following tables and views. These tables contain only internal database information, and no user or application data. The database administrator can use a script from Flexera to create a user fnmoaudit on all target Oracle servers. applsys.fnd_app_servers applsys.fnd_application_tl applsys.fnd_nodes applsys.fnd_product_installations applsys.fnd_responsibility applsys.fnd_user apps.fnd_user_resp_groups CONTENT.ODM_DOCUMENT DMSYS.DM$MODEL DMSYS.DM$OBJECT DMSYS.DM$P_MODEL DVSYS.DBA_DV_REALM LBACSYS.LBAC$POLT MDSYS.ALL_SDO_GEOM_METADATA MDSYS.SDO_GEOM_METADATA_TABLE ODM.ODM_MINING_MODEL ODM.ODM_RECORD OLAPSYS.DBA$OLAP_CUBES SYS.DBA_ADVISOR_TASKS SYS.DBA_AWS SYS.DBA_CUBES SYS.DBA_ENCRYPTED_COLUMNS SYS.DBA_FEATURE_USAGE_STATISTICS SYS.DBA_FLASHBACK_ARCHIVE SYS.DBA_FLASHBACK_ARCHIVE_TABLES SYS.DBA_FLASHBACK_ARCHIVE_TS SYS.DBA_INDEXES SYS.DBA_LOB_PARTITIONS SYS.DBA_LOB_SUBPARTITIONS SYS.DBA_LOBS SYS.DBA_MINING_MODELS SYS.DBA_OBJECTS SYS.DBA_RECYCLEBIN SYS.DBA_REGISTRY SYS.DBA_SEGMENTS SYS.DBA_SQL_PROFILES SYS.DBA_SQLSET SYS.DBA_SQLSET_REFERENCES SYS.DBA_TAB_PARTITIONS SYS.DBA_TAB_SUBPARTITIONS SYS.DBA_TABLES SYS.DBA_TABLESPACES SYS.DBA_USERS SYS.DUAL SYS.GV_$INSTANCE SYS.GV_$PARAMETER SYS.REGISTRY$HISTORY SYS.ROLE_SYS_PRIVS SYS.USER_ROLE_PRIVS SYS.USER_SYS_PRIVS SYS.V_$ARCHIVE_DEST_STATUS SYS.V_$BLOCK_CHANGE_TRACKING SYS.V_$CONTAINERS SYS.V_$DATABASE SYS.V_$INSTANCE SYS.V_$LICENSE SYS.V_$OPTION SYS.V_$PARAMETER SYS.V_$SESSION SYS.V_$VERSION SYSMAN.MGMT_$TARGET SYSMAN.MGMT_ADMIN_LICENSES SYSMAN.MGMT_FU_LICENSE_MAP SYSMAN.MGMT_FU_REGISTRATIONS SYSMAN.MGMT_FU_STATISTICS SYSMAN.MGMT_INV_COMPONENT SYSMAN.MGMT_LICENSE_CONFIRMATION SYSMAN.MGMT_LICENSE_DEFINITIONS SYSMAN.MGMT_LICENSES SYSMAN.MGMT_TARGETS SYSMAN.MGMT_VERSIONS
View full article
Summary For secure environments (for example, VMware servers secured by firewalls), Flexera offers a stand-alone VMware inventory collection agent that can be installed on a Windows server. This article explains what you need to know and do to use it. Discussion Discovery and inventory information is a prerequisite to performing license consumption calculations in FlexNet Manager Suite. We recommend that you deploy one or more inventory beacons on your network, and use any of the supported inventory collection methods to collect VMware inventory. Each inventory beacon collects discovery and inventory information from the devices within its assigned subnet and sends this information to FlexNet Manager Suite. To collect inventory, each inventory beacon requires a network connection to the target VMware vCenter or ESX servers within its assigned subnet. In secure environments (for example, VMware servers secured by firewalls), you may not be able to establish a network connection between each installed inventory beacon and the VMware servers within its assigned subnet, or you may not be able to install any inventory beacon at all. For such environments, Flexera offers a stand-alone VMware inventory collection agent that can be installed on a Windows server. Although capable of collecting inventory from individual VMware ESX servers, this agent works more efficiently with VMware vCenter servers, where it collects inventory for all VMware ESX servers registered with the target VMware vCenter server. In a clustered environment, the agent can collect VMware inventory for the entire VMware cluster through the target VMware vCenter server. The stand-alone agent saves the collected VMware inventory information (as .ndi files) to a specified location. You will have to export the collected data to FlexNet Manager Suite for performing license consumption calculations. Overview The stand-alone VMware inventory agent has been designed to remotely collect VMware (ESX or vCenter) inventory when you cannot use any of the inventory collection methods recommended by Flexera. You can deploy this agent on any computer with Windows desktop (Windows 7 or higher) or Server (2008 or 2012) edition. To collect VMware inventory, the agent needs credentials for an account with read access to VMware SDK URL on each of the target VMware servers. When you run the agent after configuring it with the details of the target VMware servers, the agent collects VMware inventory using API calls. The collected information is saved to a configured location from where it can be uploaded to FlexNet Manager Suite for license consumption calculations. The following diagram illustrates the process of VMware inventory collection through the stand-alone VMware Inventory agent: To collect VMware inventory through the stand-alone VMware inventory agent, complete the following steps: Verify the prerequisites. See the Prerequisites section below. Deploy the inventory agent. See the Deploying the Agent section below. Configure the inventory agent. See the Configuring the Agent section below. Collect VMware inventory. See the Collecting Inventory section below. Export the collected inventory to FlexNet Manager Suite. See the Exporting Inventory section below. (Optional) Uninstall the inventory agent. See the Uninstalling the Agent section below. Prerequisites The following are the prerequisites for inventory collection using the stand-alone VMware inventory agent: A VMware vSphere/vCenter/ESXi server, supporting versions from 5.0 to 6.7 inclusive. Note: Inventory is not possible on the free license versions of ESXi. The following software products are required on the server where the agent is to be deployed: Windows desktop (Windows 7 or higher) or Server (2008 or 2012) edition Microsoft .NET Framework version 4.0 or later. Network access to the target VMware vCenter or ESX hosts. An account with read access to the VMware SDK URL is required on each target vCenter or ESX host. Deploying the Agent The stand-alone VMware inventory agent is shipped as a zip archive. Follow these steps to deploy the agent: Create a folder (for example, VMwareInventory) on the Windows desktop or any other location. Extract the contents of the Flexera-supplied stand-alone inventory agent file FNMS-VMware-Scanner.zip into this folder. Using Windows Explorer, create a folder to save the collected inventory information (for example, C:\Inventories\). You should add this path to the OutputDir parameter in the esxquery.ini file. Configuring the Agent To enable the stand-alone VMware inventory agent to collect inventory from target VMware servers, register every target VMware server with the agent, and record the VMware server name in the esxquery.ini file. Follow these steps to configure the agent: On the computer where you deployed the agent, launch the Windows command prompt with the "Run as administrator" option enabled and browse to the VMwareInventory folder. Invoke the agent by using the following command. The agent should display a list of available options: ..\VMwareInventory> esxquery server Query specified server -a Query all configured servers -l List configured servers and credentials -s Set logon credentials for server -d Delete logon credentials for server -c Use existing logon session cookie -f Set VMware license flag for server When the agent is not being run for the first time, use the following command to list any previously-targeted VMware servers that are still registered with the agent: esxquery.exe -l If any undesired VMware servers are registered with the agent, use the following command with the name of the VMware server whose registration is to be deleted: esxquery.exe -d <server name> where <server name> is the VMware server name. Use the following command to register a target VMware server with the stand-alone VMware inventory agent. The agent will collect inventory only from the VMware servers registered with it: esxquery.exe -s <server name> where <server name> is the name of the target VMware server that is to be registered with the agent. The agent prompts you to enter the credentials for this server. Enter the credentials for the account with read access to the VMware SDK URL <https://<server name>/sdk>> created on this VMware server. Repeat step 5 for each of the target VMware servers. The agent records each server name with its username and encrypted password in the esxquery.ini file in the VMwareInventory folder. Set the OutputDir parameter to the path where you want the agent to store the collected inventory files. The following code example sets the output directory to the .\Inventories sub-folder under the VMwareInventory folder. The following code also describes how two VMware servers, server1 and server2 have been recorded in the esxquery.ini file. [Global] OutputDir=.\Inventories [server1] Username=<domain\user name> Password=CtCi3795PXgxC3W8W7gdSg== [server2] Username=<domain\user name> Password=EEfoiY3pmz0xC3W8W7gdSg== The esxquery.exe tool encrypts the password automatically, before saving it to the esxquery.ini file. Use the following command to review the list of VMware servers registered with the stand-alone agent: esxquery.exe -l Your agent is now ready to collect inventory from the target VMware servers. Collecting Inventory When you have registered all target VMware servers with the stand-alone VMware inventory agent, you can run the agent to collect VMware inventory from the registered VMware servers. Follow these steps: Use the following command to run the stand-alone VMware inventory agent. The agent executes, collects inventory from each of the servers listed in the esxquery.ini file, and saves the inventory files (.ndi) in the output folder specified in the esxquery.ini file. esxquery.exe -a The agent runs and displays inventory success messages. The following code shows an example output: C:\Flexera\VCenter Query>esxquery.exe -a servername: found VMware vCenter Server v4.1.0 servername: inventory generated successfully Using Windows Explorer, navigate to the output folder (C:\VMwareInventory\Inventories). You should see an .ndi file for each of the target ESX servers. Each .ndi file contains inventory for a target ESX server, as well as all of the virtual machines registered with it. Note: The stand-alone VMware inventory agent also collects inventory for the virtual machines that were switched off during the inventory collection process. Exporting Inventory The license consumption calculation process of FlexNet Manager Suite requires the collected .ndi files for calculating your VMware license position. If you have installed FlexNet Beacon, you can manually transfer the collected inventory (.ndi) files to the Incoming\Inventories folder. The FlexNet Beacon uploads the inventory to FlexNet Manager Suite. If you have not installed any inventory beacons, you can use any third-party methods to export the imported inventory to the "C:\ProgramData\Flexera Software\Incoming\Inventories" folder on the FlexNet Manager Suite server. Uninstalling the Agent You can easily uninstall the stand-alone VMware inventory tool by deleting the: Deployment folder (VMwareInventory) Output folder (Inventories). Appendix: API Calls for VMware Inventory Collection The stand-alone VMware inventory agent connects to the VMware SDK URL (https://<servername>/sdk) on each target VMware server. This connection requires an account with read access to the SDK URL. Once a connection is established with the target VMware server, the agent makes the following API calls through the SDK: API name Description GetServiceContent A single call is made to this API to retrieve the ServiceInstance to enable further queries. RetrieveProperties: Host Information A single call is made against the root folder to return information about each host server with the following attributes: ComputeResource.host ClusterComputeResource.host Datacenter.hostFolder Datacenter.vmFolder Folder.childEntity RetrieveProperties: VM Information A call is made against each returned HostSystem to obtain the following attributes for each virtual machine that exists on the host: HostSystem.parent ComputeResource.resourcePool ResourcePool.resourcePool ResourcePool.vm
View full article
How you can remove FlexNet inventory beacons from incorrectly consuming PVU licenses.
View full article
Summary FlexNet Manager Suite contains data about Oracle installations. Some of this data can be extracted and provided to people from Oracle License Management Services (Oracle LMS), who can analyse that data for you to assist with the status of your Oracle license consumption. This article provides guidance on how to override the following Oracle LMS information: Database edition License metrics (when multiple Oracle license metrics are in use within the enterprise) Oracle installation environment usage (when other than production) Discussion Database Edition Note: This refers to the database server edition used for licensing the server (not to be confused with the installed edition); for example, a DB SE installation covered by DB SE1 license. Exported Oracle LMS ORCL_OVERVIEW data from FlexNet Manager Suite includes the installed Oracle edition. Where an installed Oracle Database edition is different from the licensed Oracle edition used within the FlexNet Manager Suite, Flexera recommends updating the Oracle Database edition value within LMS ORCL_OVERVIEW. You should manually update the value of the Oracle Database edition that is installed on the server with the edition recorded in the license. You can update the licensed Oracle database edition by following these steps: Extract the exported Oracle LMS data from FlexNet Manager Suite. (Refer to the Oracle Instances topic in the online help for FlexNet Manager Suite for instructions.) Find the record for the particular Oracle Database server, and in the ORCL_OVERVIEW.csv file, update the DATABASE EDITION with the appropriate licensed edition; for example: Oracle Database Standard Edition One (SE1) Oracle Database Standard Edition (SE) Oracle Database Enterprise Edition (EE) License Metric The license metric value within an exported LMS ORCL_OVERVIEW file comes from the license type used within FlexNet Manager Suite to license an Oracle Database installation. Where multiple license metrics (for example, Oracle Named User Plus and Oracle Processor) are used to license Oracle Database installations within FlexNet Manager Suite, Flexera recommends using allocations or restrictions with such Oracle installation servers. You can apply allocations to Oracle Database licenses by following these steps: Open the license properties. On the Consumption tab, search for, and select, the required installation of Oracle Database. Use the Allocate button to choose the kind of allocation to make for the selected installation. Similarly, restrictions may be applied in the Restrictions tab of the license properties; or you may prefer to use the Group assignment tab to manage license priorities. Environment Usage By default, all inventory devices are listed for production use. Where Oracle is installed in an environment other than production (for example, “Test”), Flexera recommends updating the inventory device role, which automatically adjusts the license consumption within FlexNet Manager Suite, as well as updating the files exported for delivery to Oracle License Management Services. You can adjust the inventory device role by following these steps: Go to Discovery & Inventory > Oracle Instances. Select the Oracle server to open the inventory device properties. On the General tab, select the appropriate device role value (for example, Test) to update the default Production device role. Save the updated properties. Reconcile. (Either wait for an overnight reconcile, or if you have Administrator access, reconcile immediately. Note: Restrict the reconcile to Oracle only by deselecting Reconcile all publishers.) Perform an Oracle LMS data export. (Refer to the Oracle Instances topic in the online help for FlexNet Manager Suite for instructions.) ORCL_OVERVIEW will now reflect the updated environment usage for that Oracle server.
View full article
Summary Information about FlexNet Manager Suite 2019 R1 FlexNet Manager Suite 2019 R1 Release: March, 2019 Prior Release Later Release FNMS 2018 R2 -     Release Notes for FlexNet Manager Suite 2019 R1 are available in the following languages: FlexNet Manager Release Notes (English) FlexNet Manager Versionshinweise (Deutsch) Notes de publication FlexNet Manager (Español) Notes de publication FlexNet Manager (Français) FlexNet Manager リリースノート (日本語) These provide information relating to new features, significant changes, resolved issues, installation process and compatibility with other products.   Additional Information You can also download the following reports and updates from the Flexera Software Product and License Center: Reports Known Issues for FlexNet Manager Suite 2019 R1 Provides the current listing of issues relating to this release of FlexNet Manager Suite. This list may include issues resolved in any future release.   Hotfix Releases FlexNet Manager Suite Update 2019R1-05 Investigating and resolving application recognition issues is easier than ever thanks to the new  Evidence  tab which lists the evidence discovered for a selected inventory device. After applying this update when you see a listing for an application which you don't think is installed, or if you can't find an application which you know is installed, you can view the evidence used to recognize the applications on that device. Using this new evidence view enables you to identify and then determine the best way to resolve any discrepancies. FlexNet Manager Suite Hotfix 2019R1-04 Addresses an issue when processing purchases from the License Recommendations page. Any entries that recommend changing the licenses settings 'User multiplier infrequent' and/or 'User multiplier external', will fail to be applied. FlexNet Manager Suite Hotfix 2019R1-03 Fixes an issue when running a publisher specific reconciliation set to Oracle, the calculated licenses for IBM applications may be reset to zero. FlexNet Manager Suite Hotfix 2019R1-02 This hotfix resolves an issue when there is exemption set for any device role on the Use Rights & Rules tab of an Oracle licence, Oracle Instances consuming from this license are not shown in the Oracle Server Worksheet. FlexNet Manager Suite Hotfix 2019R1-01 This hotfix resolves the issue where the IBM PVU License Consumption report may show duplicate rows when multiple titles assigned to the same license are installed on the same inventory device.   Accessing the Product and License Center Ensure that you are logged into the Flexera Community From the top page of the Flexera Community, open FLEXNET MANAGER. Select Download Products and Licenses under the PRODUCT RESOURCES section. Choose the LET’S GO! Button under the group of products that includes FlexNet Manager Platform. Once the Product and License Center page has loaded, find and select FlexNet Manager Platform under Your Downloads. Under the Latest Version tab, you would typically see either the cloud or on-premises edition of FlexNet Manager Suite. Older versions of the on-premise edition reside under the Previous Versions tab. Click on your product. A list of available files to download will be presented. This will include a file similar to either: Known issues for FlexNet Manager Suite Cloud Edition Known Issues for FlexNet Manager Suite 2019 R1 Click on the presented file to download the report.
View full article
Synopsis FlexNet Manager Suite 2018 R2 Release: September, 2018 Prior Release Later Release FNMS 2018 R1 FNMS 2019 R1   Discussion Release Notes for FlexNet Manager Suite 2018 R2 FlexNet Manager Release Notes (English) Notes de publication FlexNet Manager (Français) FlexNet Manager Versionshinweise (Deutsch) FlexNet Manager リリースノート (日本語) FlexNet Manager Notas de la versión (Español) Provides information relating to new features, significant changes, resolved issues, installation process and compatibility with other products. Known Issues identified in FlexNet Manager Suite 2018 R2 Provides the current listing of issues relating to this release of FlexNet Manager Suite. This list may include issues resolved in any future release. Additional Information You can download the following updates from the Flexera Software Product and License Center: Hotfix & Update Releases These updates have been released for FlexNet Manager Suite 2018 R2. FlexNet Manager Suite Update 2018R2-06 Investigating and resolving application recognition issues is easier than ever thanks to the new  Evidence  tab which lists the evidence discovered for a selected inventory device. After applying this update when you see a listing for an application which you don't think is installed, or if you can't find an application which you know is installed, you can view the evidence used to recognize the applications on that device. Using this new evidence view enables you to identify and then determine the best way to resolve any discrepancies. FlexNet Manager Suite Hotfix 2018R2-05 Addresses an issue when processing purchases from the License Recommendations page. Any entries that recommend changing the licenses settings 'User multiplier infrequent' and/or 'User multiplier external', will fail to be applied. FlexNet Manager Suite Hotfix 2018R2-04 FlexNet Manager Suite contains a license update engine that generates proposals to remove applications from licenses when the content license definitions indicate a given application should not be present on a license. Without applying his hotfix, accepting these recommendations will appear to be successful, however the application will not be removed from the license. FlexNet Manager Suite Hotfix 2018R2-03 Fixes an issue when running a publisher specific reconciliation set to Oracle, the calculated licenses for IBM applications may be reset to zero. IBM applications may be reset to zero. FlexNet Manager Suite Hotfix 2018R2-02 Fixes an issue where FlexNet Manager Suite may not update a ServiceNow instance name change. FlexNet Manager Suite Hotfix 2018R2-01 While using a proxy server, the Inventory Beacon will fail to get the account details for an Amazon Web Services inventory import. FlexNet Manager Suite Update 2018R2-01 (cloud) or FlexNet Manager Suite Update 2018R2-01 (on-premises) FlexNet Manager Suite has updated its ServiceNow integration application (FlexNet Manager Suite for Enterprises) to v4.0. This version has been certified by ServiceNow.
View full article
Summary Information about FlexNet Manager Suite 2018 R1 Synopsis FlexNet Manager Suite 2018 R1 Release: March, 2018 Prior Release Later Release FNMS 2017 R3 FNMS 2018 R2   Discussion Release Notes for FlexNet Manager Suite 2018 R1 FlexNet Manager Release Notes (English) Notes de publication FlexNet Manager (Français) FlexNet Manager Versionshinweise (Deutsch) FlexNet Managerリリースノート (日本語) Provides information relating to new features, significant changes, resolved issues, installation process and compatibility with other products. Known Issues identified in FlexNet Manager Suite 2018 R1 Provides the current listing of issues relating to this release of FlexNet Manager Suite. This list may include issues resolved in any future release. Additional Information You can download the following updates from the Flexera Software Product and License Center: Hotfix Releases These Hotfix updates have been released for On-Premises installations of FlexNet Manager Suite 2018 R1 FlexNet Manager Suite Update 2018R1-09 Investigating and resolving application recognition issues is easier than ever thanks to the new  Evidence  tab which lists the evidence discovered for a selected inventory device. After applying this update when you see a listing for an application which you don't think is installed, or if you can't find an application which you know is installed, you can view the evidence used to recognize the applications on that device. Using this new evidence view enables you to identify and then determine the best way to resolve any discrepancies. FlexNet Manager Suite Hotfix 2018R1-08 Addresses an issue when processing purchases from the License Recommendations page. Any entries that recommend changing the licenses settings 'User multiplier infrequent' and/or 'User multiplier external', will fail to be applied. FlexNet Manager Suite Hotfix 2018R1-07 FlexNet Manager Suite contains a license update engine that generates proposals to remove applications from licenses when the content license definitions indicate a given application should not be present on a license. Without applying his hotfix, accepting these recommendations will appear to be successful, however the application will not be removed from the license. FlexNet Manager Suite Hotfix 2018R1-06 This hotfix addresses a vulnerability with the version of Cognos that is used for Flexera Analytics 2018 R1. When you apply this hotfix, your version of Flexera Analytics is upgraded from 2018 R1 to 2018 R2. FlexNet Manager Suite Hotfix 2018R1-05 This hotfix addresses an issue where Custom property values can be lost after making changes if Custom properties that have the same value are cleared when using multi-edit on another custom property OR when changing the asset type of the asset through the business adapter. FlexNet Manager Suite Hotfix 2018R1-04 This hotfix addresses an issue where software licenses associated with Microsoft Office 365 applications erroneously clear the Publisher and Version fields of the license. Additionally, the hotfix fixes the erroneous records in the database. FlexNet Manager Suite Hotfix 2018R1-03b This hotfix addresses two issues relating to Microsoft Server/Management Core licenses where the core count may be incorrectly calculated under specific conditions. FlexNet Manager Suite Hotfix 2018R1-02 This hotfix enhances inventory collection on Oracle Database servers, improves inventory scheduling, and repairs issues affected installation or upgrade of FlexNet inventory agent on various specific platforms. The Knowledge Base article is available here. FlexNet Manager Suite Hotfix 2018R1-01 This hotfix affects the Microsoft Office 365 adapter which will fail to execute on a FlexNet Beacon that has not been upgraded for FlexNet Manager Suite 2018 R1 Other Releases Data Platform connector for FlexNet Manager Suite 2018 R1 This Data Platform connector will import normalized inventory data from Data Platform v5 (formerly from BDNA, and now from Flexera).
View full article
Summary This article describes what to do when the test connection from a beacon to the FlexNet Manager Suite server fails with the following message: The connection to FNMP succeeded, but the server did not respond to the test correctly. Synopsis The following error when is reported when attempting to test the connection to a beacon's parent in the beacon UI: The following error may also be shown in the uploader.log on the beacon: [9/05/2017 3:24:08 PM (N, 0)] {8704} Error 0xE05001F4: 500 Internal Server Error [9/05/2017 3:24:08 PM (N, 0)] {8704} Error 0xE050044D: Failed to create remote directory /ManageSoftRL [9/05/2017 3:24:08 PM (N, 0)] {8704} Error 0xE0690099: Specified remote directory is invalid, or could not be created [9/05/2017 3:24:08 PM (G, 0)] {8704} ERROR: Remote directory is invalid [9/05/2017 3:24:08 PM (G, 0)] {8704} Upload failed due to a server side issue. This server may be retried during this upload session. [9/05/2017 3:24:08 PM (G, 0)] {8704} Ignoring failover locations for upload on an inventory beacon [9/05/2017 3:24:08 PM (G, 0)] {8704} WARNING: FlexNet Manager Platform has failed to upload a file to all configured upload servers; aborting attempt to upload these file(s) [9/05/2017 3:24:08 PM (G, 0)] {8704} Upload directory is 'C:\ProgramData\Flexera Software\Incoming\Logs'   Discussion 1) Launch IIS manager and open the "Authentication" properties for the "ManageSoftRL" virtual directory. 2) Confirm if anonymous authentication is enabled. If the error shown below is reported when you try to open the "Authentication" properties, take a look at the following KB article: Error when attempting to open Authentication Properties on IIS
View full article
Summary The IAtrack tool is not part of any of the FlexNet Manager Suite products. This tool provides additional capabilities and is delivered "as is". No official support from Flexera should be expected. Discussion IAtrack: Supplemental inventory import utility. IATrack is a standalone Windows Console Application that can be used to gather supplemental inventory for various products like Hyperion, WebLogic, O365, Cognos, DB2, Siebel etc. Please refer to the User Manual included in the package zip for usage instructions and other details. Download IATrack. New in this version: WebLogic edition recognition based on WLST(WebLogic Scripting Tool) script. DB2 recognition based on db2licm(DB2 License Manager) command output. Siebel Inventory updates. Creation of Inventory file with a custom name. O365 Inventory performance optimization and other fixes. Fix to handle multiple encryptions of IATrack configuration file. Hyperion enhancement to include AD users when external AD users are provisioned. Bug fixes. Please refer the User Manual and Readme documents in the package zip files for details about its capabilities, usage and limitations, etc. *****Disclaimer: IATrack is a standalone utility that provides access to some early stage inventory technology developed by the Flexera Content Research Lab. It is a research tool used by Flexera to investigate and try out various techniques for gathering inventory related to particular applications of interest. Capabilities provided by IATrack are considered experimental in nature, and may not meet your particular need or objective. You should only use IATrack as directed by somebody from Flexera.***** Additional Information Again, please note that this tool is not part of FlexNet Manager Suite. No Flexera Software maintenance contracts apply, and Support will be provided on a reasonable effort basis only with no guarantees provided for any fixes. For any questions or issues related to this tool, the Flexera Support team can be contacted and the support Engineers will try to address any request to the best of their knowledge; if unsuccessful, they will forward the request to the Flexera Software team that developed this tool.
View full article
Summary This Knowledge Base article will explain what are the correct steps to stop/kill a running batch process if required in FlexNet Manager Suite 2014 R2 and later versions. Synopsis For version 2015+, we introduced the BatchProcessTask.exe & BatchProcessTaskConsole.exe command line which can be used to run batch process individually (for details how to use this command line, please see KB: (000018340) To stop/kill a running batch process for v2015+ , please follow the below steps: BatchProcessTaskConsole list-tasks to find the <task ID> BatchProcessTaskConsole fail-task -m <task ID> To stop/kill a running batch process for v2014 R2, 2014 R3, (since we didn't have BatchProcessTaskConsole.exe in those version), please follow the below steps: 1 . Run attached SQL Script SELECT statement to find the 'right' Batch Process, we need know the type of process is running 2. Kill the corresponding task executable file from Windows Task manager, eg: ComplianceReader.exe (for Compliance Inventory Import) ; MgsImportRecognition.exe (for content library download/import) 3. Run 'Deletion statement' to cleanup the 'stale' Batch process from the database, (to make sure system is back to sync) Discussion For version 2014 R2+, the step 3 mentioned above to clean up the database entry of a killed process is required to run. A running process is killed, but the product WEBUI may showing the status still running without a clean up on the database (table: BatchProcessExecution) A reported issue was found in 2014 R2 , the root cause is due to the killed batch process is still appearing in the DB, so UI is hanging , for details please see 'Additional Information' session. Related KB Articles 000018340 -- How to use BatchProcessTask.exe/BatchProcessTaskConsole.exe command line in Flexnet Manager Platform v2015+ On Premise Additional Information The specific customer reported case is License Reconcile page is always showing running so the issue is customer is no longer able to run a manual reconcile from the UI, but in reality the import.log and schedule task are both showing the process is not running. The root cause is due to a hanging process in the 'BatchProcessExecution' table , once the hanging entry is deleted from the database, UI is back to original status.
View full article