premium version and active scanning

[wsaxon]

We are evaluating the Premium version of this product, and have enabled Active scanning of one domain with 2 OU filters.

There should be 31 machines found, but Lansweeper is only finding 22 machines after well over 24 hours. Triggering a scan with lstrigger on a machine still does not make it show up.

Lansweeper did find 2 machines with WMI problems that prevented full scans, so I expect machines to show up regardless of whether a scan can complete or not.

How can we tell if there are specific errors preventing a scan? What would cause a machine to not be found/scanned automatically by Lansweeper?

[wsaxon]

Lansweeper wrote:

wsaxon wrote:
It seems to me that a machine that does not participate in a domain authentication event would not be picked up at all. Is this true?

All machines do this (if they belong to a domain) to exchange kerberos tokens

Only if they need to authenticate someone. Are you checking for particular authentication events in the event logs on the domain controllers? We seem to be able to trigger discovery by logging in to machines which are not being picked up.

The 'scan entire OU now' will be very good, as long as there is a way to remove garbage or retired machines from the list.

[Hemoco]

When lansweeper first starts it looks for all computers seen by the domaincontrollers in the last 4 hours, it then repeats this process every 15 minutes.

So your first scan you might miss some computers, but after 24 hours you should get them all (if they are in the network)

Do you have any errors in the errorlog.txt file?

lstrigger only works for computers already in the database.