1

So how may of you use Remote Collectors?

I am trying to weigh the + and - .

I have a second site that is fairly substantial ( 35 users and about 40 PCs ). Connected via VPN so right now I just scan across the VPN but I would like to limit the traffic across that connection as much as possible.

So…

  1. Will running a remote collector really save me that much bandwidth?

  2. If you are running a remote collector what are some of the “issues” that you have had to deal with? ( duplicate inventory, messed up network map, scan issues, WOL does work, Reporting is not accurate, etc )

  3. Are there benifits other than decreased bandwidth utilization ( i.e. more thorough inventory data, network maps, etc ).

1 Spice up
2

  1. Yes, and the scan doesn’t take nearly as long to perform.

  2. Mainly that there aren’t any real good alerts if a remote collector stops responding for any reason. And that you have to update the remote collector separately from the main SW install. Haven’t had any more duplicate inventory than I normally get, my network map has always been messed up, scan works fine, don’t use WOL, reporting is fine.

  3. Only shorter scan times, which was big for me. My scans were taking a LONG time (14 locations).

3

I use a remote collector and haven’t had any problems with it as of so far.

Yes it will reduce bandwidth since it is only reporting the findings to your main server instead of actually scanning over the network.

As far as I have seen, there are no issues to report, the only problem I have had is with the remote computers being off.

The only thing I have seen was already mentioned with the network map being kind of screwed up, but I do not use that feature anyway.