1

SW 7 has been giving me some trouble on the Inventory Scan - some of my Workstations are not updating properly.

I’ve got my scan speed set to slow, verbose logging on, collecting all data instead of deltas, etc.

But I keep having devices show up as not having been scanned.

Funny thing is, the same ones are recently updated.

Last Updated Time: = last scan, an hour ago
Last Scan Time: = a month or more.

It’s only on Workstation PCs, and not the same ones each time. Can’t find a pattern.

If I manually rescan them, it clears, and it finds a bunch of new information that happened in the last month. So they’re ‘Updating’, but not getting a proper ‘Scan’.

What gives?

2 Spice ups
2

FWIW, we are seeing that same in our office as well as at clients. I’ve had a bunch of systems with the last scan time of 2015-06-02 @ 05:01 pm but if you look at the device configuration tab, they were last rebooted no to long ago. 14-Sep-2015. I question how that’s possible?

I’ve also had whole subnets fall into the not scanning state, but if you manually launch a scan from the device → Tools → Rescan. The rescan will work no problem and update the last scan time. I haven’t had the time to try to dig into what the problem is yet. But that is as much as I know.

3

Would you mind posting a screenshot showing the entirety of your Network Scan settings page? We’ll need to see your IP ranges at the top, your scan schedules, and the Additional Settings. Please omit the section that displays parts of your Admin credentials.

1 Spice up
4

Here’s a composite.

Scan_Settings.pdf (170 KB)

5

Hey Bartleby,

So, the “last update time” is the last time a device was touched at all. If you manually update the record, or if an up/down scan succeeds, etc., you’ll see this time updated.

The “last scan time” indicates the last time an actual scan was completed.

I’m curious, if you disable all of the scans except for the “all devices” scan under the “all” scan group, do you still see this?

1 Spice up
6

I’ll give it a try for tonight - only running the ‘All Devices’ scan.

But it appears to have actually gotten worse over the weekend. After manually scanning every Workstation individually from Tools>Rescan (saving a few sample items in the 30 days group) on Friday…
23 of 44 devices are today showing that they have not been Scanned since then (again Updated, but not Scanned).

7

No joy with that configuration change. Ran nothing but the All Devices scan last night…and many Workstations are showing that they’re not getting Scanned.

8

Hey Bartleby,

Okay, let’s get some logs over this way and see what’s going on. Hold tight and I’ll shoot over an email!

9

I’m still interested in the outcome of this because I have a server/devices on site that is in the same state.

In my case I setup a second SW server to scan the network, no plugs to heavy changes to the config. Basically we spun up a new server set the scan ranges and let it run. That server is now in the same state in regards to not scanned devices as the primary one we tried to run to ground with Spiceworks support.

Meaning this issue (not scanning) may be more than the unique environment here in our office.

10

This turned out to be the helpful clue:

The difference between the way the automatic scan works and the way the manual scan works is a little complicated. The automatic scan relies on cached information (computers.yaml, kuids.yaml files) to speed things up. When we do a manual scan, we bypass all of that and first try for the hostname of the device and the last IP address we knew it was on. I think we skip doing a ping test too, I think the scanner just tries to connect to that IP right off the bat.

Ended up that there were some devices that weren’t pinging properly, had some DNS anomalies, etc.
That explained why an Automatic scan was having problems, since it start with those functions (a ping, a NDS lookup, etc); Manual scans were bypassing that and going straight to the device, so they worked.

Reviewing & fixing firewall rules, and manually scavenging some DNS records, for the machines that weren’t scanning seems to have got them back on track.

Thanks Peter and Jon!

2 Spice ups
11

Brian,

Thanks for following up on the post!

pnznkqgsrgw4tx0qdpxr.jpg