@raaron1 - If your client has ILMT on SQL Server, then they could arrange to backup the ILMT database and restore a copy of it on a SQL Server that a beacon can connect to.  The backup/restore process could be done on a periodic basis. I am not a DB2 expert, but I assume the same process could be performed with the DB2 database. ... View more

@winvarma - For the Microsoft Remote Desktop CAL, you typically grant a user access to remote desktops through an Active Directory security group.  Any User Accounts in those groups have access to a Remote Desktop and need a CAL.  With such an arrangement, you can create a Business Adapter to connect to AD and extract the User Accounts within those specific Security Groups and allocate them to your RDS User CAL License to generate consumption. In regard to your Windows Server External Connector, there is the following description of this license on the following Microsoft Site:  https://www.microsoft.com/en-us/licensing/product-licensing/client-access-license An EC license assigned to a server permits access by any number of external users, as long as that access is for the benefit of the licensee and not the external user. Each physical server that external users access requires only one EC license regardless of the number of software instances running. An "instance" is an installed copy of software. So, this should be managed within FNMS as a simple Device license.  You would need to allocate each Windows Server to this license that has services being accessed by an "external" user, which would typically be servers that support a public website.  FNMS would count the number of allocate servers and compare this count against the number of purchases. The last 3 items are all Office 365 services, and should be managed by FNMS when you connect to your Office 365 Portal with the FNMS Office 365 connector.  Or, you connect to your Office 365 Portal using Flexera SaaS Manager and integrate SaaS Manager with FNMS. ... View more

@clugo1 - The new REST API is only for FNMS Cloud.  For FNMS On-Premises, you have full access to all of the data at the SQL layer.  The FlexNet Manager database schema is fully documented and you can get assistance if needed from the Community with your SQL Scripts if you should chose to use that method to extract data. ... View more

@marcog - The main Business Adapter Studio application can be launched with Command Line parameters, specifying the name of the XML file you have created.  You can then use Windows Task Scheduler to set up your business adapter to run on a scheduled basis. Additional information can be found in the Flexera Business Adapter Guide and look in Chapter 2 for the command line interface: https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/WebHelp/PDF%20Documents/On-Prem/UsingFlexNetBusinessAdapters.pdf   ... View more

Look in the TRACKER.LOG file on one of these devices.  Make sure that Inventory is being generated and that the NDI Inventory File is being successfully uploaded to a Beacon. ... View more

@dparab27  - At the present time, calculating Named User/Application User license consumption for Oracle Middleware Products is a combination of using Technology, People and Process. Technology - FlexNet Manager is able to identify the servers where your Middleware products are installed and also take into account any product bundling rules.  The Product Use Right libraries also know the correct "minimum user" rules to apply for each product.  For example, a minimum of 10 users are required for each core. People and Process - The ability to automatically capture the list of users with access to Middleware products is not something that is currently available within FlexNet Manager (or any other tool).  However, Flexera continues to research this topic and does have some experimental technology, as John has stated.  Therefore, you need to work with the System Administrators of your middleware products to get lists/counts of users with access to each middleware product.  Once you have the total user count, you can go to the Consumption tab of the license within FlexNet Manager. There is a field called "Non-Inventoried Users".  In this field, enter the total number of users that has been captured from your administrators or whatever process you have used to get this information. Technology - During the next License Reconciliation, FlexNet Manager will look at the hardware attributes of all the servers where the middleware product is installed and then calculated the Minimum User rule.  It will compare this to the number of Non-Inventoried Users and whichever number of greater will be used as the license consumption. People and Process - Option 2 - You can use internal techniques that may be available to export the actual users with access to a Middleware Product via an Administrator Console or other method.  Once you have this User List, you can import this list of users against the FlexNet Manager license with a Business Adapter.  FlexNet Manager during a reconcile will count the number of users against the Minimum User calculation and use whichever number is higher. ... View more

@gavin_mouat - If you are using the FlexNet Agent, then there is no real benefit to import from ADDM in terms of inventory. The one benefit to import from both sources of data would be to cover the scenario where you have a server that has been inventoried by BMC Discovery that has not been inventory by the FlexNet Agent.  In this scenario, you will still get the inventory from such a device that does not have the FlexNet Agent. ... View more

@winvarma  - You can also reduce the size of the LOG files by updating the Properties of the database.  Go to the Options and set the Recovery Mode to "Simple" rather than "Full". ... View more

Have you considered setting up a DNS ALIAS? ... View more

@Ralph_Crowley  - Can you provide more context around the "known issue" with vCenter 6.5 having duplicate serial numbers for ESX Hosts?  I have not really encountered/seen this.   ... View more

@junaid_vengadan - Thank you for the update and happy to hear that you got the SSO working for Cognos Analytics. ... View more

@jackyjoy123  Starting with FNMS 2019 R2, the Mac Agent install package is signed and also 64-bit.  With this updated install package, the requirement to disable Gatekeeper was removed. In addition, the FNMS 2020 R2 Mac agent has full support for the new Big Sur OS X operating system (Mac OS X 11.0), as well as support for the new ARM hardware platform. ... View more

@junaid_vengadan - The authentication to Cognos is built into FlexNet Manager as part of the installation.  Authentication to Cognos is directly from FlexNet Manager.  In other words, you cannot log directly into Cognos outside of FlexNet.  Therefore, integration with OKTA is not needed for Cognos. You must first log into FlexNet Manager using OKTA, and once you are logged into Cognos, your security roles within FlexNet Manager indicate if you can connect/log into Cognos. ... View more

@ACallisto  Markward is correct.  The FlexNet Agent has 0 dependancies on Java. Kirk ... View more