Chat now with support
Chat mit Support

Enterprise Reporter 3.2.2 - Configuration Manager User Guide

Product Overview Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your Office 365 discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Configuring the Configuration Manager
Starting the Configuration Manager Finding Answers and Getting Help An Overview of Enterprise Reporter Communications and Credentials Required Logged In User Details Setting Up Your First Collection Computers Modifying your Deployment Improving the Performance of Your Discoveries What does the status of a node or cluster indicate? Using the Credential Manager Changing the Credentials used by the Enterprise Reporter Server Configuring Global Settings Global Discovery Settings
Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

An Overview of the Configuration Manager

Figure 1 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 Configuring Clusters and Nodes for Effective Data Collection , and When Do You Add a Cluster? .

Technical Documentation.

Shared Data Locations

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.

Ensure the optional shared data location is secured as it contains temporary files of collected data. For more information, see Things to Consider Before Creating a Cluster . Technical Documentation.



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 Clusters , Discoveries , and Improving the Performance of a Node .

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen