![]() ![]() consultant, I have numerous small clients (mostly 1 to 10 employees each). 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. On this screen, enter the information for your Central Spiceworks server. The following is a screenshot of the setup process for the Remote Agent. ![]() Spiceworks can be installed on any computer or inside a Virtual Machine. Remote Agent a small app that you install on a laptop (for instance) that will scan that single machine and send that data back to your Central Spiceworks install. ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |