This would be an awesome feature if I could count on it. 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. It's main purpose is to allow scanning of systems that leave the corporate network. It's disappointing that LsAgent is not more robust and reliable. Antivirus was initially blamed for the corrupt LsAgent.ini problem, but there is nothing on these systems other than the default Windows Defender. In all cases, the contents were gone, replaced by 279 blank spaces. On several others, I found a corrupt LsAgent.ini file. If I manually start it, the agent starts working. It either failed to start or gracefully exited. I looked in the event log for crashing, but the service did not crash. On some of the computers, the Lansweeper Agent Service is simply not running. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |