We have several Agents in the Console that have the same IP, Mac address, Host name, and Windows UUID. But the Agent and Console IDs are different. We believe this is happening every time the Agent updates. The Problem is the “Last Scan date” is today, but looking at each duplicate separately one has scan history of today (2-22-23) and one has scan history Stopping 125 days ago (10-20-22).
This is causing a lot of Duplicates and Having a dynamic group for last scanned >60 days ago doesn’t work as it halfway correlates the two and shows both as scanned today (even though the history on that asset shows different)
1 Like
i have seen this in our console as well.
Annoying to detect and deal with because as you say, the “Last Scan Date” always shows as today even if the actual scan date was months ago.
Support Was able to confirm what I found
“That definitely seems like that is where its coming from. It seems like they know they are the same asset and updating the last scan as if its one but two different assets. There is times where it looks at its history in the backend of when it got imported and if the agent id was different or there was something different it wont change it in the backend and it wont retroactive correlate even though the new data of the asset suggest otherwise. That is the reason why the assets would need to be deleted and allowed to be imported again to start from a clean sleight.”
The only Issue I’m still working on is the Dynamic group wont pull anything due to it thinking it was scanned today
Hi, I’m also seeing duplicate assets in environment. Was there any fix provided?
I think this conversation is mostly going back to data retention settings from the administration page. If you’re retaining all data then you may have multiple asset_ids for the same asset. If one of those assets has not been scanned in over 120 days then a data retention setting of 2 months should wipe those out of your database.
I’m seeing duplicate assets again starting last week. Has anyone else seen this problem come back recently?
I too see duplicates, and the insite Support rep has suggested that Agent Category is at fault.
I can see the duplicate assets all have the same respective UUID’s but they have different addresses and different Agent ID’s. From what I have seen here the answer would be to delete all the Assets and let them be rediscovered or is there another way to resolve this issue?
Thanks
We had this issue and followed through with a support case. The recommendation was to upgrade agents to version 4.0.7.26. Since we have had ~most of our assets on that version, the number of duplicates have went back to zero. Seems there was a duplication issue on prior agent versions. Hope this helps.
We’ve been on 4.0.7.26 since it became available. Once it has created a new copy of an agent, the old one seems to be ignored. Out of roughly 80 agents, we had a three or four duplicates shows up while using this version. (I’m uncertain on the number as we have removed the originals once we were certain that IVM would not start updating information on the originals again.)