Active Scanning

[kinsey]

Is it possible to segment what is scanned via the active scanning feature? I have been piloting this new functionality and it appears that I can scan the entire AD forest, but cannot limit the scope to only certain OUs. We support multiple offices that are segmented by OUs within the same domain. I would love to use this AD scanning feature in conjunction with the login script approach we are currently using, but my preference would be to phase this in one location (or OU) at a time. Any guidance would be greatly appreciated.

Also, is it possible to schedule when these active scans are run?

[Hemoco]

In the config file you also have:
<add key="ConcurrentThreads" value="10" />

This is the amount of simultaneous scans.
All other computers are put in a waitingqueue until a place comes free.
You can change this number according to your hardware.

Some people with dedicated hardware set it to over 100

[kinsey]

Understood. Thanks for the clarification.

Knowing that we can toggle the "Activescanning" value between "0" and "1" to initiate the scan at the schedule we desire, can you please explain how many scans would run concurrently? Does the Lansweeper server query a set number of systems at a time? I just want to make sure that when an active scan is run that we don't have 6,000 clients trying to interface with our Lansweeper server simultaneously. Thanks as always for the feedback.

[kinsey]

Thank you for the quick response.

Can I imply that the intent is to provide OU scanning at a later date or is this not a fair assumption?

We are currently only running lsclient once every seven days in our environment via logon script. Is there a way to throttle active scanning back to a similar schedule?

Also, can you provide a quick overview of how the active scanning process works? Our forest currently contains over 6,000 computer objects and I want to make sure that they are not all being scanned concurrently.

[Hemoco]

kinsey wrote:

Can I imply that the intent is to provide OU scanning at a later date or is this not a fair assumption?

This is indeed not a priority

kinsey wrote:
We are currently only running lsclient once every seven days in our environment via logon script. Is there a way to throttle active scanning back to a similar schedule?
Also, can you provide a quick overview of how the active scanning process works? Our forest currently contains over 6,000 computer objects and I want to make sure that they are not all being scanned concurrently.

They will be scanned at a maximum every 8 hours

[Hemoco]

The ou scanning is currently not implemented.

The schedule is automatic.
When a computer announces itself in active directory the "lastseen" date on the domaincontrollers is changed.
Lansweeper looks when this date changes.

With active scanning a computer is only scanned maximum one time in 8 hours.