The LsAgent installations will first try to send data directly to the scan servers specified, in the server order specified. 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. 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. 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. One way to decrease the load on a scan server is by directing some of your agent scans to a different server. Directing agent scans to a different scan server Alternatively, you can reduce the frequency or scope of your agent scans. 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. 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. 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. Relay data is also retrieved by a scan server configured by you.
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. It prevents most scanning errors and, in the case of LsAgent, it allows you to scan the computers of remote workers. Scanning locally is useful for many reasons. The Lansweeper software includes two scanning agents, LsAgent and LsPush, that can be used to scan client machines locally.
0 kommentar(er)
