Thanks for the solution. I'm wondering anyway if there is a way to do it for a single target server from FNSM UI. I'm telling this since I have 900 servers with 300 false positive. I cannot go one by one to modify the comps file. Is there another way to do it? Thanks ... View more

@jjensen @mfranz   Thanks for your input , i have also verified the same . the behavior is same as explained under this topic.   ... View more

Very good to hear, thank you for following up with your solution! ... View more

No problem, happy to help. It's easy to miss when there's so much documentation to keep track of. Have a good day yourself sir 🙂 ... View more

thanks!  That helps! ... View more

To add onto @adrian_ritz1's comment - if ICMP is indeed disabled within your network, then the following KB may be of some use to you: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-allow-beacon-network-scans-in-a-network-with-ICMP/ta-p/150060 HTH, Joseph ... View more

The FlexNet Agent and FlexNet Inventory Beacons are installed in your network. Agents communicate with a beacon over Port 80, but can be configured to communicate over Port 443.  Agents initiate all communication to the beacon using HTTPS PUT and HTTPS GET Inventory Beacons communicate to the FlexNet Manager Cloud using HTTPS using TLS 1.2 encryption.  Inventory Beacons initiate all communication to the Cloud using HTTPS PUT and HTTPS GET ... View more

Thanks @jjensen  for the query to identify how the reconciliation is triggered. it was helpful. ... View more

Hello @scott_thornhill, The data extraction carried out by the M365 adapter is controlled by the Logic.ps1 PowerShell script, available at C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\Microsoft 365 on your beacon server by default. If you open that file within a text editor, and search for '$Sku', then you will notice that there is a 'local SKU library' within that file. For each plan SKU pulled from your M365 tenant, one of two things can happen: 1) The SKU is recognised within the '$Sku' local SKU library. In this case, the license will have whichever name is associated to that SKU. For example, SKU "MIDSIZEPACK" will result in a license name of "<M365 Tenant> Office 365 Midsize Business" 2) The SKU is not recognised within the '$Sku' local SKU library. In this case, the license name will take the following format: "<M365 Tenant> <Raw SKU>" In the scenario you have described, perhaps #2 is happening - is the raw SKU name = "_ENTERPRISE_PLAN1"? Regarding your second query - if you have access to the Compliance database, you can carry out the following steps to view all licenses directly imported from the O365 connector: 1) Run the following query to obtain the relevant ComplianceConnectionID for the O365 connection: SELECT * FROM ComplianceConnection 2) Once you have the necessary ComplianceConnectionID, run the following query, again against compliance: SELECT * FROM ImportedSoftwareLicense WHERE ComplianceConnectionID = <ComplianceConnectionID> ...replacing the placeholder as necessary. Alternatively, navigate to License Compliance -> All Licenses in the Web UI, and run a search against the Name column for your M365 tenant name - 'DYN365'. HTH, Joseph ... View more

Great i will try it and update this! Thanks ... View more