1

many of my devices show a ‘last scan’ date of ~90 days ago but an ‘last update’ of today. How can I assure my application inventory for each device is accurate. I am using an agentless scan. Thanks, Dennis

2 Spice ups
2

What changed 90 days ago?

Firewall on clients been updated, new GPO?

Machines from 7/8 to 10?

File and printer sharing needs to be enabled on clients as a start and pings need to resolve too

3

It might be that your full scan is being executed when those devices are powered down. I like to perform an additional scan of all devices that have not been scanned in 30 days to take place during a prime business hour, like 2pm. That usually catches my users that come in late and even the ones that leave a little early.

Settings > Inventory > Device Scanning > Scroll down to Scan Schedules and configure the scan for just the “haven’t been scanned in…” group.

Alternatively, if there is some problem with network communication I would take one of those devices, run the Spiceworks assistant on it, then manually initiate a scan to see if that corrects it.

4

ROD-IT - nothing has changed in the environment that I am aware of.

adamdeich - I performed the additional scan of devices using the group ‘not been scanned in 30 days’ a few hours ago(~1300hrs pst).

Thanks

5

Can your SW server ping a device in the list and get a reply?

If you select a single device in the inventory, click the tools option and rescan, does it find it?

6

ROD-IT, I successfully pinged the device(it is my own laptop), I selected it from the device inventory, choose to ‘rescan’ - the " Last Scan Time" still shows 1-17-2017. Also, I confirmed the credentials(they are my AD admin account) that spiceworks is using to scan.

7

Do you have UAC enabled? Any firewalls, including the default windows one or a third party one like Symantec etc.

8

I think the issue may be spiceworks is using the ip-address(these change as we are dynamic) instead of resolving the device name - can I force it to always resolve the device name instead of the ip address

9

FYI - we are at the latest spiceworks version

10

IP is the only way it works.

If you ping the device by name and note the IP

Then ping -a IP noted, do they match?

11

the device(i.e. my device) has 2 ip addresses listed(wireless and wired) - one of the ip addresses listed is currently(as we use dynamic addresses) belongs to another device. That other device was the one being scanned.

I wonder how others handles their device inventory with dynamic ip addressing

12

They clear out stale DNS records, this is an DNS issue and has nothing to do with DHCP - this is typical, but stale records should be managed y ytour DNS server.
Also you should not have both wired and wireless conencted at the same time, this creates its own issues.

13

ROD-IT - thanks, I ended up removing all my devices and performing a total new scan. Will have our network guys look at our DNS. Thanks

14

Tell them to enable scavenging.

15

got it

16

we are scavenging - have a 7 day threshold

17

If you ping DNSname and get 1.2.3.4

then ping -a 1.2.3.4 and get DNSPC

You have DNS issues, make sure scavenging is enabled on all zones and is actually working, more specifically the rDNS.

Also as I noted above, disable one of your links, having both wired and wireless on will make things difficult for the scanner and the network in general.

18

that was another problem - we were trying to scan both our wired and wireless subnets - I changed to only use/scan our wired subnets.

19

You can scan both subnets, just don’t be on them both at the same time

20

Also, if you have too many devices/a lot - your scans can back up. Ensure your group scan schedules are spread out far enough and are reduced to just what you need. For instance, do your printers really need to be scanned several times a day, or is once or twice enough…

Jackie.