‎05-30-2024 09:43 PM - edited ‎05-30-2024 09:47 PM
We are having issues with some remote assets not showing up from LsAgent. I'm trying to narrow down what the reason could be, but had some questions regarding when LsAgent actually scans and sends information from a laptop.
The problem is likely with laptops that are not using the VPN when on a public/private network or connected to a company network. We get Asset Radar assets to show up just fine. We do not (or at least I do not) have access to the LsAgent logs from remote computers without first finding which asset is not reporting, contacting the user to set up a remote session, and then manually grabbing the logs. This would take some time seeing how it's around 400 assets not reporting based upon our employee count vs what's reporting in Lansweeper as actively scanned.
‎05-31-2024 03:16 PM
LsAgent runs based on the configured schedule, and it starts to count from the moment it first run. For example, if the computer has been off for for 10 hours, the last LSAgent scan was 1 hour before shutdown, and it is configured to run every 4 hours, the next scan will be 1 hour after start up.
For troubleshooting the other LsAgent issues, we recommend opening a support case with our Support engineers, that kind of troubleshooting usually requires sharing logs.
Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now