Too many LsAgent or LsPush scans

[Susan_A]

The Lansweeper software includes two scanning agents, LsAgent and LsPush, that can scan client machines locally.

Scanning locally is helpful for many reasons. It prevents most scanning errors and, in the case of LsAgent, allows you to scan the computers of remote workers. When you install LsAgent or set up LsPush, you can configure the agent to send data to one of your scan servers or our cloud relay server.
A scan server configured by you also retrieves relay data. Scan servers can handle a lot of LsAgent and LsPush data. Nevertheless, you may overload a server by sending too much agent data.
If your server has less than 1GB or less than 10% of available memory left, the Lansweeper web console may show you a warning notification.

This article explains two methods to solve this issue: redirecting scans to a different or new server, and reducing the frequency or scope of your agent scans.

Directing agent scans to a different scan 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. You can select a group of LsAgent assets and link additional scan servers or change the order of the servers by dragging in the Configuration tab. The LsAgent installations will first try to send data directly to the scan servers in the order specified. If no server can be reached directly, and cloud relay access has been set up for LsAgent, LsAgent will try to send data to the relay.

Only one scan server can be configured to retrieve data from LsAgent's cloud relay server. You can configure which scan server 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 diverting more LsAgent scans directly to scan servers.

Reducing the frequency or scope of your agent 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. You can select a group of LsAgent assets and choose a less frequent scanning schedule in the Configuration tab.