Im new to Spiceworks and had a couple questions!<\/p>\n
Advertisement
When a remote site is setup as a remote collector<\/strong> and reports back to the Central Server.<\/strong><\/p>\n
What is controlled by the Central Server and what is controlled by the Collector?<\/p>\n
\n
\n
What to Scan for? / Scheduled scanning?<\/p>\n<\/li>\n
\n
Which events to track and notify?<\/p>\n<\/li>\n
\n
Authentication for the devices on site?<\/p>\n<\/li>\n<\/ol>\n
What is the advantages to having a Central Server - Remote Collector<\/strong> setup as opposed to have Standalone<\/strong> setups reporting events via SMTP?<\/p>","upvoteCount":2,"answerCount":4,"datePublished":"2018-08-02T00:32:26.000Z","author":{"@type":"Person","name":"michaelkoopmans","url":"https://community.spiceworks.com/u/michaelkoopmans"},"acceptedAnswer":{"@type":"Answer","text":"
The Remote Collector (RC) is traditionally used to scan a remote location locally. You can install it on a machine at a remote site, and it scans the machines and reports back to the Central Server (CS).<\/p>\n
To that end, the RC is in charge of the IP range it discovers (the Your Networks section of the Settings → Inventory → Device Scanning). Any device discovered by the RC is tagged as belonging to that “site” and reported back to the CS.<\/p>\n
Once a device is discovered, the CS is the install that schedules the updates (the Scan Schedules section of the CS Settings → Inventory → Device Scanning). Each scan type in that section updates a specific type of information from machines and is separated by groups in the main Inventory section. For instance, when you enter the Networking group into the All scan category, the CS looks at the devices listed in the Networking group from it’s Inventory, then checks which site that device belongs to. With that information in hand, it then tells the appropriate RCs to scan the devices in that group.<\/p>\n
As for credentials, they all get pulled down from the CS, so you should make sure that the creds that are entered there will work for the remote sites.<\/p>\n
As for why to do it instead of using SNMP traps (which is what I assumed you meant), first, the app doesn’t accept SNMP traps. Second, it helps distribute the network load over WAN link (multiple remote locations being scanned from a single installation can choke WAN end points). Third, depending on your set up, it can also help distribute server load. Because the RCs are doing the scanning, the CS isn’t doing that as well as everything else.<\/p>\n