I’m currently running version 5.1.67635 in a larger environment 1600 devices and growing as I finish deploying SW into the community. Over the last few weeks when I run the network scan on a new ip range it’ll pick the systems up and correctly classify them but won’t collect the software and config data. If I re-scan the systems individually it’ll pull this info in. I’ve read all the posts I can on this matter and tried the basic steps such as turning off delta’s, setting the scan speed to slow, and turning off incremental scans. I also messed with the data write size chuck with no luck at all. I have noticed that when I run a full scan on a specific range it’ll pickup the software and config data for just one system each time I run the scan.
I’m a little lost and really could use the help on this one since I have a Audit meeting with the executives next week to give them an overview of how things are going. Any help would be much appreciated.
2 Spice ups
Are you using remote collectors with a network of that size? If you are, are all the installations at the same version level?
I’m not using any remote collectors at this time. We plan on using them for the few out of state locations we have but we have pretty big data pipes in between locations locally and didn’t think it was necessary to use remote collectors.
I thought there was a recommendation that on a network of more than 1000 devices, remote collectors would be better. That also depends on your network setup, how often you want to run scans and such.
You might want to contact Spiceworks support directly and ask about the communication problems you see and find out if it has anything to do with running only a single install.
