Scanning part 2

[paprita]

After few hours the scanning slow down.
Now, every polling the system scan max 1 PC or no one at all (Concurrent Threads = 50).
In my network there are more than 15.000 PC and the DB contain less than 6.000 PC.
Why?
What's happen?

[Hemoco]

This means only 3000 clients contacted the domain controllers last 2 hours.

Second/third, ... round only new found workstations are scanned so this is normal that the queue decreases.

Even if you leave your workstation on it will still contact the domain controllers (about once every 4-8 hours)

[paprita]

Lansweeper wrote:
This means only 3000 clients contacted the domain controllers last 2 hours.

Even if you leave your workstation on it will still contact the domain controllers (about once every 4-8 hours)

OK ... :-)))

[paprita]

The detailed situation is: when scanning reach 3.000 PC (more or less) number of scanning for each poll decrease drastically ... I've already tried this situation two or three times ... if I stop the system and start again, it go again to maximum speed until it reach 3.000 ...

What the reason?
How can I do if I would leave my system on for 24/7/365 ?

Edit: we posted almost at the same time; I've read your answer and now all is quite clear ... :-)))

[Hemoco]

How active scanning works:

When you start the service is checks all domaincontrollers in the selected domains and queries for computers logged on in the last 2 hours and add then to the scanning queue.
After this the following step is repeated with a 10 min break.
Check all domaincontrollers again for computers logged on since the last time
...

After this just set it and forget it, when new workstations come in the network they will be found.

Each workstation is only scanned maximum once every 8 hours.