LS Agent group configuration

[TK_AT_HBK]

Hello,

for win domain controllers we use lsagents.

they kind of get into the system and register themselves in the default lsagent group.

i have set up a new lsagent group.

looking at the UI of the saved lsagent group there is a second tab called configuration.

3 options to configure.....

1 being schedule. so i set up a schedule with my individual name etc.

i expect that the agents being "attached" / moved to my group will pick up the schedule and report accordingly.

it seems that that that group schedule is not honored . it rather seems that the "regular" ip/wmi scan seems to trigger the agent to report back ... looking at the timestamps of "last lsagent scan2 column.

can someone please explain what triggers the agent to report / scan ; are there any priorities when you have competing schedules ?

will an ip/wmi scan realize that there is an LS agent and "skip" that host ? or at least merge those 2 information streams ?

will that ip/wmi scan & existing lsagent combo influence the Alert report " scan issues: wmi access denied" ?

thanks for clarifying

[Obi_1_Cinobi · Accepted solution]

Hello there!

You can change the machine's scanning schedule in the Scanning > LsAgent Scanning section of the Lansweeper web console. Here you can divide machines scanned with LsAgent into groups, configure a scanning schedule for each group and enable/disable/delete LsAgent installations. Keep in mind that the minimum scan interval for LsAgent is 4 hours. If you choose a more frequent schedule, your LsAgent installations will silently default to an interval of 4 hours.

Do keep in mind that if your LsAgent scanned assets are also included in your agentless scanning targets, they will also be scanned by these agentless scanning targets. The LsAgent schedules and the agentless schedules will not take each other into account.

The "Access denied" scanning error that you are seeing on the asset page is not related to LsAgent. The scanning error that you are seeing signifies that the Windows asset is being scanned by a remote scanning target like an IP range scanning target or an Active Directory scanning target. If you want to scan your assets with an agentless scanning target you will need to resolve these scanning errors. 

If you only wish to scan your assets with LsAgent, you will need to make sure that these assets are not included in your agentless scanning targets. And keep in mind that excluding assets from scanning will also exclude them from being scanned by LsAgent.