@AamerSharif  based on the resolved issues. Is there any plan to integrate fix for IOJ-2198658 into the on-prem O365 adapter. Some times we run into this issue when gathering a huge amount of data from O365. IOJ-2198658 Integration: Other When the Microsoft 365 adapter runs more than an hour to collect the usage information, the import fails with an error - access token has expired   Best, Dennis ... View more

Hi @Favari0105 ,   take a look at this post, which covers the same topic. https://community.flexera.com/t5/FlexNet-Manager-Forum/Batch-license-allocation/m-p/106352#M1504   Best, Dennis ... View more

Hi @sushant_narula  The appropriate settings and permissions are all in place. It really only fails at the connection to the FNMS database as in the screenshot of @carlos_quiros  and is due to a problem with TLS1.2, which can be solved by an adjustment via the "Settings Tab" in Cognos. Although the problems and approaches may be different, the community would greatly appreciate your solution so that others with the problem can get to a solution faster. Thanks and regards, Dennis ... View more

Hy @carlos_quiros  @WheresThePizza  could you please share the solution how to get the "settings tab" back to cognos. I'm running into the same problem and as already discussed and would like to change the dispatcher settings to connect to the ContentStore DB.   Thanks and Best, Dennis ... View more

Hi @rwiltshire  I would recommend a tiered approach to beacons. If possible, then operate a central beacon within the GCP and all agents report their data to it. The central GCP beacon is then connected to your DMZ or intranet beacon via only one necessary firewall rule. A normal configuration. When it comes to agent deployment, I think it depends on how dynamic your environment is. If VMs are only active for a short time and then deleted again, then the results of the inventory may be wrong and have an impact on your balance. Here I would recommend a solution like the AWS/Azure Connector. On the one hand, the inventories are determined by the agent (agent in the template incl. first start after deployment) and, on the other hand, the infrastructure data (status of the VMs, similar to the vCenter Adapter) is determined. Based on this information, inventories that are no longer in the structure are cleaned up. You can find more information about the procedure in the documentation. https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/InvAdapConn/index.html#adapters/Azure/topics/Azure-AgentInventoryExInst.html Terminated instances are a special case. 1.Before termination, the running instance may have had an inventory device record (provided that it was reporting inventory). 2. When you terminate the instance, Microsoft Azure keeps the terminated instance visible through the API for about an hour, and if you have implemented your Azure PowerShell connector on an inventory beacon with the default 30 minute schedule, the termination is imported through the connector, and the record in the CloudServiceInstance table is updated with the terminated status. (This record, with its terminated status, is visible in the Cloud Service Provider Inventory page, if you set the filters on that page appropriately.) 3. At the next full inventory import (by default, overnight, immediately before the license compliance calculations), any inventory device record linked to a terminated instance is deleted, because you do not want terminated instances consuming from your licenses. 4. Of course, the terminated instance no longer reports inventory; but its previously-recorded inventory is still in the inventory database (and in normal processes is not cleaned up for a while). Although the next full import (typically the next night) normally imports records from the inventory database, for terminated instances this is prevented by the terminated flag in the CloudServiceInstance table. This prevents the deleted inventory device record from reappearing.   Best, Dennis ... View more

Hi @Vishal  I would say yes, because the agent uses the ping only to prioritize the possible beacons (https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/NetSel-SuppliedAlgors.html). If the ping fails, the beacon will only get a lower priority, but will still be used. Decisive is only whether the agent can reach/resolve the URL "https://Server-FQDN/ManageSoftRL". Just try it and post the logs in case of problems (C:\Windows\Temp\ManageSoft) Best, Dennis ... View more

Hi @bmaudlin  could you please post some log file of a fresh installed agent running into this issue? C:\Windows\Temp\ManageSoft ... (Installation.log, upload.log) an your mgssetup.ini.   Thanks and Best, Dennis ... View more

Hi @rclark0  detailed information for Unix and Windows can be found here: https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/tasks/FA3-CustomUNIXSetup.html https://docs.flexera.com/FlexNetManagerSuite2020R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/tasks/FA3-CustomSetupIni.html   If you miss any information, let us know and we'll answer your questions in this post. Best, Dennis ... View more