The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.
Dear Comunity,
Durin this year, we have been experiencing some strange situations. We have currently upgraded into FNMS 2019 R2 on Premise.
Before those upgrades we were able to delete devices from UI with success, and if the device wouldnt report back again, then it wouldnt reappear into the UI, which tu us, it seemed to be working as intented. Please do note that back in previous versions we also had the AD connecter stablished as per default, meanwhile there was NO AD management (which means no disabled devices and records back from 2015 till present).
However lately we have been trying to deleted over 5 times the inventories that we do not want to have in the UI, and after every single reconciliation the inventory would report back with the last inventory date that the device reported, but with the created date as in the day that was re-created after the reconcile.
Please do note that we do not have any third party connector, we run only the Agent Inventory and the default AD connector.
Any thoughts on where the problem is?
‎Mar 31, 2020 10:41 AM
@andresdarquea - Here is another thread on the Community on this same topic. If your only source of inventory is the FlexNet Manager Agent, then to permanently delete this from FNMS (assuming the agent is not reporting inventory), then you must delete the device from both of these views. If you only delete from the Active Inventory view, it will come back after the next import:
1) Active Inventory
2) All Discovered Devices.
Also since you have FNMS On-Premises, there are some references to Stored Procedures in the FNMSInventory database that you can run to delete inventory that way.
https://community.flexera.com/t5/FlexNet-Manager-Forum/Deleting-old-inventory-records/td-p/99395
‎Mar 31, 2020 02:54 PM
Thanks for the quick reply, I would like to inform you that I have performed the advised steps, however it turns out that after deleting all of the inventory and all of the discovered devices then executed the reconcile, once the reconcile was done, all of the devices were there again. everything like if almost nothing got deleted.
In addition to the thread suggested, I am guessing that the AD section where it is mentioned that devices get deleted from UI IF within the AD they are deleted or marked as disabled, that doesnt mean that the inventories cant be deleted manually right? To be more detailed on my question:
There is no AD manager, so nobody sets up disabled or clears the AD. But what i would do is the device no longer reports, so i just go ahead an removed it from the UI. Back in previous versions I was able to perform such action without the inventory being re-created..
Any other advice or step I could take on this problem am having?
‎Mar 31, 2020 05:25 PM
Option B is to simply go to Active Inventory and change the status of the Inventory Device from Active to Ignored.
When an inventory device is set to a status of Ignored:
1) Any software installed on that device will be ignored by Software License Reconciliation/Consumption
2) The inventory device will not be counted by your FlexNet Manager License
You may also want to look into some of the SQL Scripting mentioned in the other Community Thread.
‎Mar 31, 2020 05:36 PM
Dear kclausen,
Thanks once again for the reply, but wouldnt you call this bug? From the Flexera perspective has this been raised as a concern to the technical team? if so, when are we expecting to have a fix for it.
As for the B suggestion, I understadn what you mean about it, but isnt there a reason on why there is an ignore button an a delete button? both as quite specific towards their purpose.
As for the SQL recommendation, I would need to ask to the team to review the SQL Server proposal, however.. if am forced to go into the SQL Server option rather than the UI, then something is definitely wrong between what the UI does and the SQL Server reconciliation (Inventory DB and Compliance DB)
Are there any other steps that we could take?
Like I said, I would like to thank you for your fast replies but so far both suggestions arent telling me that FlexNet 2019 R2 is working as intended.
Kind Regards,
Wolfgang D.
‎Mar 31, 2020 05:43 PM
Any suggestions to this Bug... would be great, or at least some rfix patch release date-..
‎Apr 01, 2020 04:53 PM
I would recommend you open a support case to track it, if you believe that you've found a 'bug'.
Thanks,
‎Apr 14, 2020 04:26 AM
‎Mar 31, 2020 05:37 PM