Last IP Scan Times Not Matching Scan Triggered

[laurin1]

I'm confused as to how this is supposed to work. We have an IP Scan that runs every night at midnight. However, this morning we are noticing that some assets were not updated at midnight. Looking at the scan times, I see this for a sample asset:

Last Seen: 10/24/2013 00:03:54
Last IP Range Scan: 10/24/2013 00:03:37
Scan Last Triggered: 10/23/2013 09:44:09
services 6 10/23/2013 09:44:28 0.80

I think that Scan Last Triggered was a manual scan, but why did it not rescan at 00:03?

[laurin1]

I had no idea that page even existed. Geez. Ok, so I'm curious. The documentation states:

"To avoid unnecessary network traffic during non-agent based scanning, not all Windows computer
data is rescanned all the time. Each scan item runs on its own schedule."

Is it the intent that if we certain machines (like all the servers) scanned, every item, every time, that we should use lspush.exe instead of setting all of these to zero?

[Hemoco · Accepted solution]

Please review the information on page 82 and beyond of our online documentation: http://www.lansweeper.com/documentation.pdf
Most scanning methods respect the wait times found under Configuration/Scanning Setup/Item Wait Time.

[Hemoco]

We're not sure we're understanding your question. The specified machine WAS scanned at midnight by IP Address Range Scanning. Note the following timestamp:

Last IP Range Scan: 10/24/2013 00:03:37

[laurin1]

Lansweeper wrote:
We're not sure we're understanding your question. The specified machine WAS scanned at midnight by IP Address Range Scanning. Note the following timestamp:

Last IP Range Scan: 10/24/2013 00:03:37

But, as the examples I gave show, nothing was actually scanned (none of the "categories" were updated) at that time, they all show roughly the same value as Last Scan Triggered.