Just to update on the issue that computers where still on screen... and it resonates with multiple customer situations I have seen: there was a duplicated inventory source (the beacon reading inventory data from the FNMS Inventory database) and this was causing sticky data. Technically, if a beacon (or any inventory source) imports data into FNMS, it will create a "ComplianceConnectionID". If you have old connection or duplivcated ones, you may get incredibly painful "merging" issues with old evidences causing false positives... check on https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Inventory-Gap-Analysis-custom-reports-VMs-from-vCenter-Oracle/ta-p/211848 for the "merged devices" report. To delete a connection, go to admin/Data Input (first screenshot), Inventory imports, open the detail, delete the connection (second screenshot).           ... View more

The service now inventory adapter was released to on-prem and cloud customers in the 2020R2 release. https://community.flexera.com/t5/FlexNet-Manager-Blog/ServiceNow-Inventory-Connector-in-FlexNet-Manager-Suite-2020-R2/ba-p/168980 This release required no additional licensing to my knowledge, unless you see an increase in active devices counts which would require FNMS licensing. The inventory adapter requires you install and configure the Flexera Integration on a ServiceNow mid-server.  This is available on the ServiceNow app store.  Assuming you just want ServiceNow device inventory imported into FNMS (One-way), from there you will just need to setup the powershell inventory adapter on your Flexera Beacon to have the service now data come into FNMS inventory. Hopefully I understood your question fully. 😉 ... View more

@winvarma - No, a newly installed agent does not gather inventory until the next scheduled event.  For example, if the Inventory Settings Page has your inventory schedule set to run every Saturday, then if you successfully install an agent on Monday, it does not perform the first inventory until Saturday. ... View more

It looks to me the test connection logic is inconsistent with the actual automation so I wouldn't imagine it is having a problem. Likely because the Get-IAMUser call is made to validate credentials. ... View more

I wanted to touch base to see if there was any further progress with this issue?  I too am seeing this problem sporadically across the enterprise with the 2020 R1 agent. ... View more

I am using the following database query as part of a compliance process to prove ADDM computers are in FNMS --Verify ADDM Computers are in FNMS inventory, expect results for AIX LPARs and VIO(AIX) machines as these are assigned a --different Serial number in FNMS than is discovered by ADDM to avoid duplication of serial numbers SELECT * FROM [AddmStaging].[dbo].[Host_ci] LEFT JOIN [FNMS].[dbo].[ComplianceComputer_MT] as Comp ON [AddmStaging].[dbo].[Host_ci].Serial = Comp.SerialNo WHERE [AddmStaging].[dbo].[Host_ci].Serial IS NOT NULL AND Comp.SerialNo is NULL ... View more

Yes, changing the instance name of a SQL Server instance would require similar changes to database server configuration details in the registry and database tables as when a database is moved from one FlexNet Manager Suite instance to another. ... View more

We've now added an Adobe best practice guide.   As you might expect, to meet the constant evolution of our industry, our best practice guides are often updated, so I'd recommend that those who have used them subscribe and/or revisit them to see if there's new content. ... View more