LSAgent ONLY, and getting errors about No valid credentials found. Check encryption file

[Raymond1]

Hi, we piloted Lansweeper and had the results we wanted. Only dealing with LSAgent deploys at this stage, we have no networks scans at all configured, no AD scans configured, only dealing with LSAgent at this point.

on prem setup and linked to cloud.  We do not have relay configuration setup, LSAgent install is configured for the FQDN of the Lansweeper server only.

When we expanded the deployment of LSAgent to more systems we started seeing scan errors. The error may have been there before but never noticed.

These are all domain joined Windows workstations.

These errors are for each system and appear each hour. it seems like the  Lansweeper server is trying to reach out to the client?

EDIT : Of course once i spend hours on this and then post, i find the answer, i think.

enable "LsAgent Only" under Scanning > LsAgent Scanning > (click your LsAgent group(s)) > Configuration tab to disable agentless scanning for LsAgent assets:

[ErikT]

@Raymond1 

To avoid these scanning errors you can indeed enable "LsAgent Only":
Go to Scanning > LsAgent Scanning, click your LsAgent group(s), then open the Configuration tab and select "LsAgent Only".

Errors should disappear after the next LsAgent scan and won’t return.