The online status indicator is not influenced by the number of scan requests you make. It is based on a ping request performed from the server hosting your Lansweeper web console to the NetBIOS name (Windows) or IP address (non-Windows) of the asset. This ping request is performed "on demand" when you access the asset's Lansweeper webpage or when you hit the Ping Assets button in asset overviews.
In regards to traffic: one full first time Windows computer scan takes 4MB if you are using an agentless scanning method. Subsequent scans take less data. Scanning non-Windows machines takes very little traffic. By default, Lansweeper uses as much bandwidth as it can get. Best practices for reducing overall bandwidth usage:
- Reduce the number of scanning threads on the scanning server. This can be done through the Lansweeper web console under Configuration\Scanning Setup\Server Options. (You need to restart the Lansweeper service after changing this setting.)
- Perform one full Lansweeper installation and add multiple scanning servers to share the load between servers. Multiple scanning servers are supported by the Ultimate license.
- Use LsPush in a logon script. LsPush scans are only 40 KB for one full scan: http://www.lansweeper.com/kb/how-to-scan-with-LsPush.aspx
- Use QOS on your connections to throttle the bandwidth used by the Lansweeper server. (This is recommended for Lansweeper and other applications.)