Credentials error when scanning machine with agent installed

[Firetree]

I've got a server (at least one) that is not on the domain, has Lsagent installed, but when scanned from my on prem Lansweeper server returns a 'No valid credentials found' error.  If the agent is installed, it should not require credentials, right?  

-T

[FrankSc]

Dear, 

That is correct, with an agent, you should not normally receive scanning errors.
If you still get these errors, your asset will still be targeted by an agentless scan, meaning a scanning target or Discovery action (if you use Network Discovery).
An agentless scan runs independently from an agent scan and will still generate errors with no valid credentials. So you mainly have to check your targets to exclude the assets from being scanned agentless.

[Firetree]

Thanks for responding.  When/where is this agent scan scheduled?  I'd like to make sure the info in my assets database is up to date, but the last successful scan date is useless with the invalid credentials issues.

[duster1]

On "Classic" aka on premise lansweeper - it is under Scanning -> Scanning targets

If you scan IP ranges, or "servers" as the asset type - that is likely what is causing it to show in the logs.

[Firetree]

Sorry, i probably didn't phrase that correctly.  When scans run, the machines without the agent get scanned, the ones with agent come back with that credentials error, which is fine.  But at what point do the agents on the server(s) run a scan and report back to lansweeper?  The agent being installed is great but shouldn't it be updating the lansweeper database?

i realize i've taken this conversation on a bit of a drive from my original question

[duster1 · Accepted solution]

Scanning -> LsAgent scanning -> select your configuration tab

If you have more than one group, each group will have its own configuration tab. 

You can set your scan schedule there. 

If you are using lansweeper cloud - do not forget to enable the Relay Service, on the Relay configuration just below the lsagent scanning.
This is also where you get your key that you must pass through during install for lsagent to work with the cloud.

[Firetree]

that's what i needed, thanks Duster!