“Too many LsAgent or LsPush scans”

The Lansweeper software includes two scanning agents, LsAgent and LsPush, that can be used to scan client machines locally. Scanning locally is useful for many reasons. It prevents most scanning errors and, in the case of LsAgent, it allows you to scan the computers of remote workers.

When you install LsAgent or when you set up LsPush, you configure the agent to send data to one of your scan servers or to our cloud relay server. Relay data is also retrieved by a scan server configured by you. While a scan server can handle loads of LsAgent and LsPush data, there may be situations where you end up overloading a server by sending too much agent data to it. The Lansweeper web console may in that case, if your server has less than 1GB or less than 10% of available memory left, show you a warning notification.

There are a few things you can do if a scan server is being overloaded with LsAgent or LsPush data.You can direct some of your scans to a different scan server, or even set up a new server. Alternatively, you can reduce the frequency or scope of your agent scans.

Directing agent scans to a different scan server

One way to decrease the load on a scan server is by directing some of your agent scans to a different server. If you're scanning with LsPush in a logon script, you can easily change the target scan server by modifying the server name in the logon script.

If you're scanning with LsAgent and sending those LsAgent scans directly to scan servers, you can modify the configuration of your LsAgent groups in the Scanning\LsAgent Scanning section of the Lansweeper web console. Here you can select a group of LsAgent assets and, in the group's Configuration tab, link additional scan servers or change the order of the servers by dragging. The LsAgent installations will first try to send data directly to the scan servers specified, in the server order specified. If no server can be reached directly and if you've set up cloud relay access for LsAgent as well, LsAgent will then try to send data to the relay.

LsAgent group linked scanservers

Only one scan server can be configured to retrieve data from LsAgent's cloud relay server. You can configure which scan server that is in the Scanning\Cloud Relay Configuration section of the Lansweeper web console. If the scan server retrieving data from the relay is being overloaded, you may want to consider directing more LsAgent scans directly to scan servers.

Reducing the frequency or scope of your agent scans

Another quick fix to decrease the load on a scan server is by reducing the frequency or scope of your scans. If you're scanning with LsPush in a logon script, you can reduce the number of machines the LsPush policy is applied to or change the scan trigger in your LsPush script.

If you're scanning with LsAgent and sending those LsAgent scans directly to scan servers, you can modify the configuration of your LsAgent groups in the Scanning\LsAgent Scanning section of the Lansweeper web console. Here you can select a group of LsAgent assets and, in the group's Configuration tab, choose a less frequent scanning schedule.

LsAgent scanning schedule

Related Articles

Get Started Right Away

Try Lansweeper for Free