1

I have several dozen one-pc remote sites, and many travelling users. Is it necessary to have SW loaded on each machine as a remote site?
What is a good way that I can pull the inventory of those remote machines?
What kind of scenarios could I try?
I am already using SW as a remote collector, collecting from sites that have 2 -3 or even more PCs in an office, but each of those sites have a domain controller, so it was an easy fit… these places I have that only have one PC in the office, was not sure…
I wondered if I went the hamachi route, hub and spoke, with each machine polled through that vpn connection, or something similar… all of the sites have high-speed, always on internet connections, but was really unsure of the best route to take…
Any guidance will be appreciated!
Thanks!

3 Spice ups
2

Hello, MonarchAndy,

The best way is via Remote Collectors, as you said. For traveling users you can use “stand-alone”.

http://community.spiceworks.com/how_to/show/178

3

Seriously? Each machine will be its’ own remote collector? That looks like it will be a mess, especially in the remote sites configuration page on the central server…

Any other ideas?

4

We’re an MSP and have a few situations like that you describe, we are one of those who use Spiceworks Agent (a.k.a. Stand-Alone Data Collector) - Spiceworks …

There are a number of different ways to deploy and use it, including ones like this: Setting up computer scan (stand alone data collector) on user …

We use a few different ways, most of them relying on the local creation of a YAML file they send to use and we use to update the local inventory record. You can also do this for computers with no internet acces for whatever reason.

Just remeber this (Agents ‘stand-alone’) use of Spiceworks is unsupported by Spiceworks and you will generally need to look for help if you need it from those of in the community who use this method.

This is also worth a look: Spiceworks Stand-Alone Data Collector