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

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, NTFS, 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, 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, and Registry discoveries, the computer is the root object, so computers will never be tombstoned.

Using the Browser to Include and Exclude Scopes

The browser is designed to allow you to drill into the acceptable objects for a given discovery type. Although the browser may vary slightly between discoveries, the basic use of it is consistent.

Your discovery should contain objects for which you want to collect similar data because:

See also:

Including Objects in Your Scope

A valid discovery requires that you include at least one object. You can explicitly include high-level objects—domains, OUs and containers. This implicitly adds all computers in the selected object. For some discovery types, you can include objects using a query for more flexibility. For more information, see Using Queries to Define Your Scopes .

When you run the discovery Enterprise Reporter resolves the high level object to a list of targets, or in the case of an AD discovery, to a list of domains. These can be useful because if the contents of the container change, so do the targets of the discovery. Once Enterprise Reporter resolves this list, the other options in the scope can be applied.

Depending on the discovery type, you may also be able to select:

DFS Shares: A published Windows® Server DFS share can be added like any other share, from the System\Dfs-Configuration container within a domain. You can use the Browse dialog box to manually add all other DFS shares.

For more details on including objects in your scopes for each discovery type, see also:

Importing Computers to Your Scopes

On the scopes page, instead of using the Add button to add one computer at a time, you may choose to import multiple computers to be included or excluded from collection for the following types of discoveries:

Microsoft® SQL

You may import from any text file containing a list of the fully qualified computer name (or IP addresses) of the computers to be targeted with one computer per line, as in the following example:

Only unique computer names free of invalid characters will be imported.

2
Select Include Computers.
Select Exclude Computers.
4
Select the file and click Open to start the import.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation