1

OK. Dumb question time, or I am just really bad at searching for the right answer in the history here.

I understand that scheduled scans run off the schedule set on the Central Server, even for the remote sites.

So, just to clarify, if i set XYZ type scan to run every day at noon, and it will be executed on a remote site because of the groups included in the scan, does the scan occur on the remote site at noon on the central site or noon on the remote site?

1 Spice up
2

Hey Rob,

Not a dumb question! This is a point of confusion for a lot of folks. Let’s see if I can clarify…

The group (scheduled) scan schedules are handed out from the central server. The remote collector runs the scan and hands the data over to the central server.

So, in your case, the scan would occur at noon on the remote collector.

Does that make sense?

3

I think it does. So the central server is used to create the schedules but it passes the info to each remote collector and the clock is ticking on the remote collector. Is that accurate?

Since my Central Server is in Chicago, CST remote collectors in Chicago suburbs, upstate Wisconsin, Oklahoma, Cedar Park TX, and a motley group of remote collectors in Bangalore, Singapore, Taipei, Tokyo, Beijing, London, Munich, and Eura, Finland, it is important I have a clear grasp of the timing.

Thanks

4

Hey Rob,

You’re welcome!

I’m going to throw another layer in there for you. While the central server hands out the sheduled group scans, you’ll still want to add the IP ranges directly on your remote collectors.

Why? The remote collectors handle the “discover” scans directly. Those are the scans controlled by the IP ranges and not the “schedules” section.

Does that make sense too? That’s the part that’s a little tricky.

5

Yeah. That I had already figured out. Just working through partitioning hardware into different custom groups to control the detailed inventory scanning and distribute it across the WAN connections and the site-to-site VPN connections.

Thanks again

1 Spice up