→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Susan_A
Lansweeper Alumni

TL;DR-Sweepy-Icon (1).png
This page describes how to resolve the issue of an overloaded scan server caused by too many LsAgent of LsPush scans. 


When you install LsAgent or set up LsPush, you can configure the agent to send data to one of your scan servers. A scan server configured by you can also retrieve relay data. While scan servers can handle many LsAgent and LsPush data, it's possible to overload a server with too much agent data.

If your server has less than 1 GB or less than 10% of available memory, the Lansweeper web console might display a warning notification.

To resolve this issue, you can:

Direct agent scans to a different scan server

LsPush

If you've integrated LsPush with a logon script, change the scan target in the logon script. Follow the instructions in How to use the LsPush scanning agent in a group policy, but update the scan server you set in Step 4.

LsAgent

If you're sending LsAgent scans directly to scan servers:

  1. In the Lansweeper web console, go to Scanning >LsAgent scanning.
  2. Select a group of LsAgent assets, then Configuration. Next, either:

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.

procedure-linking-scanning-servers-to-lsagent-group.jpg

LsAgent cloud 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 > Relay Configuration section of the Lansweeper web console.

If the scan server retrieving data from the relay is overloaded, consider diverting more LsAgent scans directly to scan servers.

Reduce the frequency or scope of your agent scans

LsPush

If you've integrated LsPush with a logon script, change the scan target in the logon script. Follow the instructions in How to use the LsPush scanning agent in a group policy, but reduce the number of machines the LsPush policy is applied to or change the scan trigger in your LsPush script.

LsAgent

If you're sending LsAgent scans directly to scan servers:

  1. In the Lansweeper web console, go to Scanning >LsAgent scanning.
  2. Select a group of LsAgent assets, then Configuration.
  3. Adjust the Scan schedule so that scans are run less frequently.

procedure-changing-lsagent-schedule.jpg


Was this post helpful? Select Yes or No below.
Did you have a similar issue and a different solution? Share your work in the comments and help your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions or Community Forum.

If you can't find what you're looking for, create a post in our Community Forum.


Was this article helpful? Yes No
No ratings

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now
Version history
Last update:
‎12-18-2023 04:57 PM
Updated by: