Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

Step 4: Review the summary

For the NTFS Discovery, the final stage of creating a discovery is to review the summary. The summary displays the settings for each of the available options in the discovery. If any of the settings need to be changed, you can go back to the previous pages and make adjustments.

To review the summary of the discovery
1
After creating and configuring the discovery, click Next.
2
Review the settings for each of the available options.
3
If there is a schedule, review when the discovery is scheduled run.
4
Click Finish to accept the settings and finalize the discovery.
- OR -
Click Back to make changes to the settings.

Managing Discoveries

•
How is a Discovery Processed?
•
Viewing your Discoveries
•
Working with Discoveries and Tasks

How is a Discovery Processed?

When a discovery runs, the process is as follows:

•
The server dispatches the resolution task to an available node in the cluster.
•
The resolution task reduces the scope to the smallest possible number of tasks. As the tasks are resolved, they go into the queue and are assigned sequentially to the nodes within the assigned cluster. Nodes can continue to accept tasks until they reach their maximum number of concurrent tasks.
* 
NOTE: A task may be rejected if the target is already being collected by another processing discovery.
•
If no nodes are available to process a task, the discovery is in the queue in a Pending state. When a node becomes available, the discovery will begin processing.
•
If the task is a collection task, data is written to the database, the last collected time for the parent object is updated, and if there are changes to any data, the timestamp is updated. The collector examines existing data and compares it to the new data, and only sends changed information to the database. This keeps network traffic to a minimum.
* 
NOTE: You can see the number of items that have been changed, and therefore updated, in the statistics for the task. For more information, see Viewing Statistics .
•
Once all tasks have been processed, the discovery is finished.
* 
NOTE: For information on configuring nodes, see Creating Your First Cluster and Node and Improving the Performance of Your Discoveries .

See also:

•
Types of Tasks
•
Manually Running a Discovery

Types of Tasks

Each discovery is broken down into tasks for processing. You will see these task types as you manage your discoveries. There are several types of tasks.

 
Table 30. Types of Tasks in Configuration Manager
Task Type
Description

Resolution

Examines your scope and reduces it to the smallest number of targets. For an Microsoft® SQL discovery, a target is a SQL Server®.

Discovery

Displays as the name of the target. A discovery task collects the data from the target and updates the Enterprise Reporter database.

Group Membership

When the collection requires information from other targets, to improve performance the work is performed at the end of the collection. This can prevent the same data from being repeatedly collected.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation