outlines the process of using the console to configure and perform data collections.
You must configure at least one cluster. A cluster is a logical collection of one or more computers (nodes) on which discoveries are executed. A discovery must be assigned to a cluster. A cluster can access an optional shared data location for discovery data. This reduces network traffic, and the processing load on the server.
For more information, see , and .
Each discovery cluster can have an optional shared data location that is used by each of the cluster’s nodes. Data collected from discoveries is stored in this shared data location, and then added to the SQL database maintained by the Enterprise Reporter server for report generation. When new data is discovered, it is compared to the data currently held in the Enterprise Reporter database. The difference between the existing data in the database and the new data from the discovery is added.
A shared data location may only be used by nodes within its assigned cluster. Since the Enterprise Reporter server receives only the difference between previously collected data and new data, the shared data locations cannot be shared among clusters.
NOTE: Not all discovery types utilize the shared data location. For example, Active Directory, Exchange, NTFS, Azure Active Directory, and Office 365 discoveries do not use the shared data location to optimize on the number of collection tasks generated to collect the data in a more efficient manner.
Ensure the optional shared data location is secured as it contains temporary files of collected data. For more information, see .
A node is a computer assigned to a cluster and is responsible for processing discoveries. A node may only be assigned to a single cluster. A discovery consists of one or more tasks, each of which collects information from a target. A node may collect data from more than one target and may process more than one discovery simultaneously. The maximum concurrent tasks of each node defaults to 0 to allow the node to determine how many tasks it will process based on the available CPU. This setting allows the node to process discoveries with optimal performance. For more information, see , , and .