1

I have tons of machines that are showing up in the not Scanned in 30 days group and I’m trying to figure out why. Many of these are servers that are on 24x7 so there’s no reason they shouldn’t be getting scanned.

One of my Domain Controllers shows:

Last Updated Time: 2016-01-11 @ 08:16 am
Last Scan Time: 2015-09-04 @ 01:00 pm

It was updated a couple hours ago (not sure exactly what that means) but it has been “scanned” since September?

What settings do I need to check to figure this out? We did disable most of the scan schedules but the All Devices still runs every day or two and Resources/Servers run every 15 minutes.

Thanks

3 Spice ups
2

Windows patches, AV, firewalls, IDS/IPS anything like this can cause it to stop being talked to

3

I have 350+ things that are in my >30 days folder. How do I figure out what the problem is for each of them?

Every machine we have gets the same patches, has the same AV, etc…

4

Has anything changed since their last successful scan?

Did you upgrade from an old version to a newer one?

Are scheduled scans still enabled?

If you manually rescan one and give it 15 minutes, does it come back to life?

5

I have upgraded Spiceworks versions as new versions came out if that’s what you’re asking.

Scheduled Scanning is enabled

I just picked one machine and clicked the Wrench and then did Rescan. It’s ben a while since I did that but the Last Scan Time has not changed. Is there a log somewhere I can view to see if it tried and if it had an error?

I noticed that I have a TON of machines who’s last scan date is between 9/4/15 and 9/8/15. Then another big chuck with 9/16/15. After that there are just a few with various dates between then and now.

When I view the details of that server it knows it was rebooted 2 weeks ago and that so it is obviously able to talk to the server to get some data back.

6

DNs not changing the records can be one - if the machines IP has changed but DNS has not updated, the scan will think the machine is offline.

7

Our servers are all static IPs so that shouldn’t be it.

I guess I could just delete the machine(s) and rescan and see if that does anything. hmm.

8

Are all of these devices scanned by the Spiceworks server or do you have remote sites scanning them?

9

Our central server doesn’t do any scanning. I have 3 remote collectors that do the scanning.

10

Can the remote collectors still be seen?

Can they see back to the SW server?

11

Yes. We have 800_ devices (per Spiceworks count) and only 100 of them are not scanning properly. I have a support ticket open so someone is reviewing my logs and things so hopefully they’ll find the problem. :slight_smile: