My Spiceworks is up to date.

On a couple of systems Spiceworks is unable to scan. They are Windows systems, domain joined. I can use the same AD account that Spiceworks is configured to use to query WMI via PowerShell.

Going to one of the systems in the inventory and selecting rescan, selecting WMI, and re-entering the credentials displays:

“Yep! Worked. We’re rescanning this device now…”

However, it still doesn’t populate the device entry.

Any logs I could look thru to troubleshoot this further?

1 Spice up

Add one of the non scanning devices as their own scan range either by IP or DNS name, once this scans the rest should too - no idea why this works but I’ve seen it a few times, if it works you can remove the individual item again

I gave it a try, didn’t work in my case. Then I went and deleted it from the inventory and re-scanned the single IP range again and it failed to scan again.

is file and printer sharing enabled on the device?

I ran a GP Results from the GPMC and it shows enabled.

I then remoted in via powershell and ran ‘netsh adv show cur’ to verify that the machine is on the domain profile.

When you ran it as a single scan on an individual device, what did it say once scanned?

Are the devices running a different AV, IDS or IPS software than the others?

The devices DNS matches its reverse?

There were stale records in the reverse zone. Scavenging was enabled, so I’m not sure why old records were stuck. Removing them manually fixed the issue.

Thank you very much.

1 Spice up

Boo for stale records