Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Product Overview 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
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 Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Step 1. Create the Discovery

When you are creating a discovery, it is important to consider what cluster will be running the discovery. A discovery can only belong to one cluster. When you run the discovery, the collection is performed by the nodes in the cluster.

By default for on-premises collection, the credentials used to access the targets and read the data are those provided when creating the node. If required, you can specify alternate credentials during the creation of your on-premises discovery. For more information, see Node Credential and Alternate Credential Details for On-Premises Discoveries .

Select an existing discovery on the Manage Discoveries pane and click Duplicate to create an exact copy. Click OK to confirm that you want to duplicate the selected discoveries and edit the copy to meet your needs. For more information, see Modifying a Discovery .
For Azure, Exchange Online, Microsoft Teams, and OneDrive discoveries, click Add to use the Credential Manager and select (or Add) an Office 365 administrator account within the target tenant that does not have multi-factor authentication enabled and click OK. For more information, see Using the Credential Manager .
Optionally, click Remove to delete an invalid or unwanted account.
7
Click Next to continue to the Scope page.

Step 2. Choose what to include in your discovery (Scopes)

In this section, we will explore what targets (scopes) you can define for each discovery.

See also:

Scopes: An Overview

Scopes define the targets of the discovery. Scope options vary depending on the type of discovery you are creating. When you are choosing scopes for on-premises collection, the node credentials or alternate credentials you specify on the Name page of the Create Discovery wizard determine the available targets. If you are using default node credentials, only targets that the logged in user can access are shown. If you provided alternate credentials when you created the discovery, those credentials are used to enumerate your scopes. For more information, see Node Credential and Alternate Credential Details for On-Premises Discoveries .

Some discovery types have additional options to collect related information that adds value to your reports. For example, if an NTFS discovery encounters AD groups in the security settings on an object, you can collect and report on the nested members of the groups. The data is collected for all scopes in the discovery and will add time to your discovery, so take this into consideration when selecting this option.

You may be able to enable this in a subset of your discoveries. For example, if you have six different discoveries with varying schedules that could potentially collect the same group members, you could enable it in only the discovery that is scheduled once a week, assuming that is sufficient to meet your reporting needs. In this way, performance is maximized, and reports have the data they need. It does not matter what discovery type is used to collect the data, as long as you are sure the data will be complete. Results are available for any report that includes the field.

How Scopes Affect Tombstoning

The concept of tombstoning refers to the process of comparing the objects found in previous collections with those found in current collections and subsequently marking objects that are no longer found in the current collection as tombstoned in the database. Tombstoned objects in the database will not be shown in library reports.

Enterprise Reporter makes the best assumptions it can based on what is collected. For some discovery types such as Computer, SQL Server, and Registry, use caution when changing collection options between collection runs on the same target (same computer). If these options are changed, objects that are not found in resulting collections will be marked as tombstoned in the database.

For example:

Other discovery types such as Active Directory, NTFS, Azure Active Directory, Azure Resource, and Microsoft Teams allow for collection of different object types from the same target without tombstoning the objects.

For example:

The following table describes how each discovery type works with tombstoning.

Active Directory

Domain

No

Azure Active Directory

Tenant

No

Azure Resource

Tenant

No

Computer

Computer

Yes

Exchange

Organization

No

Exchange Online

Tenant

No

File Storage Analysis

Computer

Not applicable - collects historical snapshots

Microsoft SQL

Microsoft SQL Server

Yes

Microsoft Teams

Tenant

No

NTFS

Share

Yes

OneDrive

Drive

No

Registry

Computer

Yes

*Yes indicates that objects will be tombstoned when subsequent collections run on the same target with different collection options.

Note: All discovery types have a root object that is not tombstoned by Enterprise Reporter. For example, in Computer, File Storage Analysis, MS SQl, NTFS, and Registry discoveries, the computer is the root object, so computers will never be tombstoned.

Documents connexes