Chat now with support
Chat with 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

What Does the Discovery Status Indicate?

The status of a discovery is largely dependent on the status of the tasks within the discovery. For more information, see What Does the Task Status Indicate? . There are several locations you can view the status of a discovery on the Manage Discoveries page:

•
The Last Run Status column tells you the status of the last completed run of the discovery.
•
If a discovery is currently being processed, the Next Run column indicates its current status.
•
After the first run, when a discovery is running you have access to both the status of the last run and the current run.
•
You can see the status of any completed discovery run when you view the history of a discovery.

The following table outlines the available discovery statuses.

 
Table 31. Discovery Statuses in Configuration Manager
Discovery Status
Description

Pending

The discovery is in the queue, but has not yet started processing. This can be as a result of manual or scheduled run of the discovery.

Processing

Once the first task of a discovery is processed (the resolution task), the discovery goes into a processing state, and remains there until the discovery is canceled or all tasks complete.

Canceled

Indicates that the discovery has been successfully canceled.

Finished

Indicates that all tasks have finished with no errors or errors that did occur were suppressed. The Error Suppressions column will indicate when errors are suppressed for the discovery.

Finished with Failures

Indicates that all tasks have finished, but at least one task failed.

Failed

Indicates that all tasks have finished, but they all failed.

Viewing the Tasks for a Finished Discovery

Viewing the Tasks for a Finished Discovery

Each discovery that has finished at least once has a list of tasks associated with it. Viewing this list is particularly useful if there were errors in your discovery. You can pinpoint exactly which targets are causing errors. The completed tasks are grouped by status, so you can easily see the outcome for each task. For each task, you can also see:

•
The type of task. For more information, see Types of Tasks .
•
The time the task started running.
•
The total time it took to process the task.
•
Errors and statistics for the task. For more information, see Viewing Errors and Error Suppressions and Viewing Statistics .
•
The discovery options that were used during collection.
To view a finished discovery
1
Display the main Manage Discoveries pane.
2
Select the discovery.
3
Click the status link in the Last Result column for the discovery.
The breadcrumb bar indicates the date and time the discovery was submitted for processing.
4
Optionally, hover over any task to display the discovery options that were used during collection.

Viewing the Tasks for a Processing Discovery

If a discovery is currently running, you can view all tasks for that discovery. You can use this view to troubleshoot issues with your discovery, and to cancel a running task. For each task, you can see:

•
A red indicator if errors occurred during the processing of the task.
•
An arrow beside a task if it is currently processing.
•
The status of the task. This indicates whether the task is currently processing, pending, or finished. For more information, see What Does the Task Status Indicate? .
•
The number of errors that occurred during the processing of the task.
•
The time the task started processing.
•
The time it took to process the task, or the current elapsed time.
•
The node to which the task was assigned. A node can be configured to process multiple tasks at once. For more information, see Improving the Performance of Your Discoveries .
•
The current activity on the node. This is a live stream of the work the node is performing, and you can use this to keep track of the progress of the task.
To view tasks for a processing discovery
1
Display the Manage Discovery pane main view.
2
Select the discovery.
3
In the Next Run column for the discovery, click the Processing link.
The breadcrumb bar indicates that you are viewing the processing tasks for the discovery.
You can see all tasks for the discovery, including tasks that have finished processing.

What Does the Task Status Indicate?

The status of the tasks in your discovery give you information about the how your discovery is being processed. You can view the status of a task in both the processing and finished task views of a discovery. By default, tasks are grouped by status. The following table outlines the statuses you may see:

 
Table 32. Task Statuses in Configuration Manager
Task Status
Description

Pending

When a discovery is run, each task has to be assigned to a node. If the node is already running its maximum number of concurrent tasks, the task is Pending. It is in the queue, and will be assigned to a node when one becomes available.

Dispatching

When a node becomes available, the task is sent to it for processing. While this is happening, the task status is Dispatching.

Processing

The task is running on the assigned node

Canceling

The server has received your request to cancel the task, and is communicating this to the node.

Canceled

The task has been canceled.

Finished

The task has successfully completed.

Failed

The task has completed, but was unable to collect all of the data you requested. For more information, see Viewing Errors and Statistics for Tasks .

Rejected

A task is rejected if the same target is already being accessed by a node within the cluster. This can happen when the same discovery is run more than once within a short time.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating