1

I’ve been trying out Spiceworks again after a year long hiatus.

For some reason the server slows to a crawl during scans, making it extremely annoying to work with the interface. This might have something to do with the fact that I’m scanning 6 subnets with around 100-150 client each (around 450 of which are Windows PCs, the rest are ProCurve swithches and a few printers. Now would it be a possible sollution to have a central install that does no scanning, and then separate the scanning on 2-3 remote collectors, I assume this will ease the load on the central site, making it less frustrating to use. Am I correct in this assumption, or should I look for Another sollution?

I can add that running the scans at night is not an option since most if not all machines will be turned off, optimally, to catch all machines at least once a week, I probably need the scans to run at least every 2-3 hours during office hours.

Or should I try to skip the scanning of the Windows Machines and instead install the agent on them? As far as I understand, this will also ease the load on the server…

3 Spice ups
2

Hi,

do not install the agent on the PC’s. The agent should only be used on machines that leave the internal network.

I would try adjusting you scan settings and put a remote collector on each site

Cheers

Ben

3 Spice ups
3

Remote collectors for the win. I do this even if I don’t have a remote site. Just offloading that activity works wonders on the central server.

1 Spice up
4

Well, all my machines are also on the same network (but separated in vlans and subnets). I’m doing the install right now, one central site without any scan jobs, and I’ll start with one remote collector that will be doing all the scanning. If it can’t take the load, I’ll try adding another one. Just need to do some firewalling to let the remote collector talk to all machines on the different subnets/vlans and we’ll se how it goes…

1 Spice up