04-26-2022 10:19 AM
03-01-2024 08:00 PM
I ran into similar issues a while back. I deleted a lot of 'unidentified' entries from the LsAgent assets page. I discovered that, at least in some cases, the agent did eventually check in but that initiated an uninstall of the agent from that asset. It was not always successful, and when it wasn't it left the agent in a very messy state.
I also had a deployment package in place to install the agent where it was not installed, and I did see instances (based on the agent install logs on the endpoints) where the asset appeared to go through several uninstall/install cycles before we ended up with a manageable asset again. It wasn't pretty, and in some cases I had to manually intervene to cleanup the agent directory on the endpoint before the agent would reinstall.
I heartily endorse opening a support case on this item if you show solid examples. And if you get more details on how this works (or should work), please share!
02-28-2024 05:03 AM
02-27-2024 07:12 PM
Facing exactly the same problem. This behaviour of the LsAgent scanning is terrible and did suprise me in a negative way.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now