サポートと今すぐチャット
サポートとのチャット

Enterprise Reporter 3.5 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises 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 cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Improving the Performance of Your Discoveries

When a discovery is run on a cluster, the Enterprise Reporter server assigns work to its nodes. You can add nodes to a cluster at any time. Each node can only belong to one cluster. You can increase the performance of your discoveries by ensuring that nodes are configured to optimize the maximum number of concurrent tasks or by adding new nodes.

Each collection task is assigned to a node, balancing the distribution across the nodes until all the nodes are processing as many tasks as they are able. If no nodes are available to process the task, the task must wait until a node becomes available.

Node performance is based on a combination of memory, processor speed, and network bandwidth. If your network, computer memory, or processor speed are less than you would like, consider adding nodes. If your node is under used, set the maximum concurrent tasks to 0 to optimize node performance instead of adding more nodes. If a node starts to slow down when node performance is already optimized (by setting the maximum concurrent tasks to 0), adding a node will increase performance. For more information, see Nodes and Improving the Performance of a Node .

See also:

Adding a Node

Since a node must belong to a cluster, you must first create a cluster. For more information on creating clusters, see To create your first cluster and node .

If you use credentials that are different than the Enterprise Reporter server credentials, they must be granted access to the database.

5
To use SQL credentials to connect to the database, select Database Credential, then choose SQL Authentication and select the SQL account from the Credential Manager.
6
Optionally, select Specify an alternate credential for Node service deployment, then select the account.
7
Set tasks to be System - managed to optimize performance. For more information, see Nodes and Improving the Performance of a Node .
8
Click Add.
10

Improving the Performance of a Node

It is recommended to set tasks to be System-managed to optimize node performance. CPU load is always used to determine how many concurrent tasks are assigned. You may optionally enter any number greater than 0 to set a Maximum number of tasks that the node can process concurrently.

3
Click Edit Node.
4
Set tasks to be System - managed to optimize performance.
Set the Maximum number of tasks to any number greater than 0 to specify the number of tasks the node can process concurrently and click OK.
5
Once the change is successfully made, click Close in the progress dialog box.

Discovery Permission Requirements

The following sections outline the permission requirements for discoveries.

See also:

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択