1

Hello everyone,

I’m in charge of deploying spiceworks to do the inventory of our network that consists in 15 branch offices.

I’ve read the documentation and don’t know if I should use the agent on all client computers or setup a network scan.

Our installation will be hosted on one of the branch Offices and would scan via WAN all the others. In the past we’ve tried spiceworks but for some reason it mixed up some devices, for example one computer scanned after some time it mixed up with another one that’s why I was thinking in an agent based deployment.

Any sugestions you can give?

4 Spice ups
2

Just like you we have 17 branches that we manage. We’ve been doing network scan for a while and only had minor issues. Not really sure what the biggest benefits are between the two.

3

If all offices are connected do not install the agent on the remote computers. You can improve performance if you install SW collectors in each location.

1 Spice up
4

That won’t be an option because we don’t have any server deployed on the branch offices that can have spiceworks installed.

5

Agents are designed for laptops and machines off the network, the report back via a public URL.

They have a limit of about 120 device before you start to see problems.

All your networks should be connected by VPN so have internal subnets, so long as you can route to them, you should be able to scan them using the default method.

1 Spice up
6

You do not need a full blown server on a remote site to do this. Pretty much any decently spec’d small PC will do the job.

7

I’m just going to throw this out there, but Spiceworks v8 will be more agent focused. So if you want to go that way, it’s in line with what we’re doing going forward.

That being said, that many agents on version 7.5 might be problematic. Remote Collectors is likely a better way to go for now. Just make sure you’ve got squeaky clean DNS entries for the scan to work with (as that’s likely what was happening before).