Community FAQ
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
dffe
Engaged Sweeper
I have been trying for some time now to get the Active Scanner to work correctly, but it still bugs me.

I can see when I restart the service do it scan ~400 PCs.

Restarted the service around 14:30 yesterday - my Test PC X was scanned.
Logging in and out and rebooting PC X didnt make LanSweeper scan it again that day.
This morning did it got scan on my first logon, but not afterwards when I try to log in and out.

So is there some time between the Active Scan wanna scan a PC? We need it to scan on every logon as we have users switching PCs several times on a daily bacis and want to use LanSweeper to locate the users.

Is there some parameters/settings I need to set or is there an error somewhere in my setup?

Need more info? Just ask 🙂

Kind Regards


4 REPLIES 4
5Type
Engaged Sweeper
I guess you could script your Lansweeper service to stop and start.

Create a .bat file
net stop <service> <---- stop desired services
net start <service> <---- start desired services


Then you could use windows Scheduled Task to make it run every x amount of minutes. (Note: you need to create a dayly task and save it then you re-open the task and go into the advanced scheduling to set it X amount of minutes.)
Hemoco
Lansweeper Alumni
Even if lsclient fails to scan the login history of the user will always be send so that should solve your problem.
Hemoco
Lansweeper Alumni
Active scanning only scans a computer at maximum once every 8 hours.
If you want faster logon tracking I suggest to use lsclient in combination with the active scanning.
dffe
Engaged Sweeper
Lansweeper wrote:
Active scanning only scans a computer at maximum once every 8 hours.
If you want faster logon tracking I suggest to use lsclient in combination with the active scanning.


We have been trying to use the LSclient together with active scanning, but LSClient often fails to scan.

My theory is that when in the GPO/login-script does it often try to contact the LS-server before the computer is fully started up and something blocks the communication between the Client and server (most likely our McAffee). Active Scanning doesnt seems to have this issue when it is working outside the 8 hour frame, so we wanna use this (ofc).

Is there no way to set it up to scan every time, with timelimit before it wanna scan again)? If it isnt there, then can you add it to the "Wish-list of features" 🙂