1

We have 24 remote locations each with their own subnet range, 10.1.x.1-254. At our HQ, we have 2 subnets to scan.

Previously I had setup 26 separate scans prior to really understanding how SW works.

We use AD and recently made some changes to how we have our main OU organized, so my Inventory Groups are now quite disheveled. ** This was not my doing! **

We have standard IP ranges that we setup at all of our remote locations, so this might make setting up the scans more efficient. Such as Infrastructure & Servers are 10.1.x.1-29, WLAN are10.1.x.40-45, Printers are 10.1.x.30-39.

My question is how would a network scan be best accomplished in this situation? Would it just be more efficient to enable a scan of our main OU container in AD?

Thanks!

1 Spice up
2

Work with remote collectors - one per office/subnet (Collecting Remote Office Inventory using Multiple Spiceworks …).

3

Unfortunately, the one computer at the majority of our remote locations that would be used for this process is already slow and I wouldn’t want to hamper its productivity by installing another database and application/service on it.

4

I installed it on my remote locations conference room machines since our group policy doesn’t allow these to be shut down. Then I ran SW as a service on these, told it to scan once a day at 1:00am and it seems to be working really well.

Our conference room PC’s are not very beefy at all but it handles just fine with the scan running at 1:00am.

-Jay

5

Paul Townsend wrote:

Unfortunately, the one computer at the majority of our remote locations that would be used for this process is already slow and I wouldn’t want to hamper its productivity by installing another database and application/service on it.

As long you use the RC only for scanning (without own helpdesk), it doesn`t matter. The RC would only scan and report the datas back to the central server as a package (and vice versa).

6

After reading the Remote Collector page and its comments, it seems there are a few pieces that aren’t fully implemented, such as remote rescans, pings, etc.

Is there any other way recommended to organize my network scans?

Also, if I were to setup the remote collector, would it benefit me to clear all my Inventory or just let it update what I have?

7

Actually you can rescan items from your main server. I just find the device at the remote site from my main server and choose the rescan from the tools menu and it kicks it off on the remote collector.

As for clearing your inventory, I wouldn’t say it is necessary unless you saw issues.

8

As Jay6111 said, you will get duplicates (in worst case). One detail will differ - scan site.

If SW is not able to update your current inventory with the new (scanned by RCs) you have to delete the old machines scanned by your central server. Also, don`t forget to disable/remove the scan range(s) (covered by RC) at your central server.