I’ve had a lot of issues with Spiceworks inventory since the day I began using it (years). For the most part it’s worked but it’s always been a mess. I noticed the other day that some new PC’s I deployed aren’t being picked up in scans. Nothing is there by name or IP. I reset my groups which didn’t help. My synced AD groups are all empty with devices sitting in the default Spiceworks groups. I wouldn’t mind blowing my whole inventory away and starting over but I would lose a lot of relational data like tickets and asset tags. Can anyone give me some advice what to do? Would be great to have a functional and accurate inventory but it’s never been that way, always a perpetual mess.<\/p>","upvoteCount":4,"answerCount":43,"datePublished":"2017-05-01T19:46:28.000Z","author":{"@type":"Person","name":"gregkatz9013","url":"https://community.spiceworks.com/u/gregkatz9013"},"acceptedAnswer":{"@type":"Answer","text":"
Alright, I think I’ve ID’d the issue. A bunch of devices are showing as “hostname exclusions”. Here’s a sample from the log file:<\/p>\n
D[16:36:48.26 c2234c] Host dc02 matches a hostname exclusion, skipping\n...\nD[16:36:48.26 c2234c] Host dc01 matches a hostname exclusion, skipping\n...\nD[16:36:48.28 c2234c] Host wsus matches a hostname exclusion, skipping\n<\/code><\/pre>\n
Advertisement
Now, your exclusion list does have two IP ranges in it (along with a couple of one off IPs):<\/p>\n
{:ID=>4, :Range=>\"10.119.0.1-254\", :Created=>2013-10-03 21:23:40 -0400, :Updated=>2013-10-03 21:23:40 -0400}\n{:ID=>5, :Range=>\"10.120.0.1-254\", :Created=>2013-10-03 21:23:40 -0400, :Updated=>2013-10-03 21:23:40 -0400}\n<\/code><\/pre>\nAre you re-using hostnames on these devices that aren’t working correctly?
\nAre there entries in DNS for hostnames that aren’t scanning in the IP ranges that are being excluded?<\/p>\n
Did you or someone else on the team wipe Inventory in the past? There’s an exclude option when nuking Inventory that can not show up in the Exclusion List, which could be causing this kind of thing as well.<\/p>","upvoteCount":0,"datePublished":"2017-05-03T11:37:46.000Z","url":"https://community.spiceworks.com/t/inventory-issues-new-and-old/577695/32","author":{"@type":"Person","name":"matts","url":"https://community.spiceworks.com/u/matts"}},"suggestedAnswer":[{"@type":"Answer","text":"
I’ve had a lot of issues with Spiceworks inventory since the day I began using it (years). For the most part it’s worked but it’s always been a mess. I noticed the other day that some new PC’s I deployed aren’t being picked up in scans. Nothing is there by name or IP. I reset my groups which didn’t help. My synced AD groups are all empty with devices sitting in the default Spiceworks groups. I wouldn’t mind blowing my whole inventory away and starting over but I would lose a lot of relational data like tickets and asset tags. Can anyone give me some advice what to do? Would be great to have a functional and accurate inventory but it’s never been that way, always a perpetual mess.<\/p>","upvoteCount":4,"datePublished":"2017-05-01T19:46:28.000Z","url":"https://community.spiceworks.com/t/inventory-issues-new-and-old/577695/1","author":{"@type":"Person","name":"gregkatz9013","url":"https://community.spiceworks.com/u/gregkatz9013"}},{"@type":"Answer","text":"
Assuming these are windows devices;<\/p>\n
File and printer sharing and pings need to be enabled<\/p>\n
This will allow SW to see them.<\/p>\n
My BA here covers the rest<\/p>\n