It is still happening in my company, i get ini files empty and services stopped.
Even restarting service does nothing most of the time, this is boring to troubleshoot.
A new lsagent version more stable would be appreciated as my company is running lsagent only to get computers information. We have stopped using global credential a few months ago and i already have more than 300 computers not sending scan...
Hi @Unlucky ,
Have you verified you're running a recent version of Lansweeper (>= 10.5.2.1) and LsAgent (>= 10.4.2.0)? Those versions should no longer have issues with corrupt in files.
If you do have that version or higher, could you contact our support department and share the lsagent error log to resolve this issue?
If you run the report "LsAgent: Not seen in the last 7 days", and then the "Ping Assets" action, do you find any computers online? If the agent is working correctly, you shouldn't. But I have on multiple occasions.
I've encountered two different problems. On some of the computers, the Lansweeper Agent Service is simply not running. I looked in the event log for crashing, but the service did not crash. It either failed to start or gracefully exited. If I manually start it, the agent starts working.
On several others, I found a corrupt LsAgent.ini file. In all cases, the contents were gone, replaced by 279 blank spaces.
I sent both issues into support. Antivirus was initially blamed for the corrupt LsAgent.ini problem, but there is nothing on these systems other than the default Windows Defender.
It's disappointing that LsAgent is not more robust and reliable. It's main purpose is to allow scanning of systems that leave the corporate network. I was able to fix the systems I found when I checked the "LsAgent: Not seen in the last 7 days" report, but I don't know how many systems are out in the wild that are forever broken. This would be an awesome feature if I could count on it.