I'm envisioning setting up the central server in my lab (100/20 mbps internet) and having the Remote Agent run on all subscribing client's hardware. I've been reading that my approach isn't 'proper' - that I should have a Remote Site at the client perform agentless collection then send results to the Central Server (me) - fine if the client has a server (workgroup or domain) that's guaranteed to be up and can run a SW site. However, for my serverless clients (lost), I'm not too keen on assigning a random user computer to perform the agentless scan as I never know if any particular computer will be up. My feeling is that by using Remote Agents exclusively, each computer will contact the Central Server directly.Ģ. If so, is there a white paper describing best practices for what I want to do?ģ.
Any idea how much traffic a remote agent generates per scan?įor Remote Collectors (or any Spiceworks Help Desk install), don't get hung up on the word 'server' when it comes to installation. Spiceworks can be installed on any computer or inside a Virtual Machine.
The key is the computer should be on and running when the other computers at the location are on and running, so it can get the information from the other computers and send it to your Central Installation.
