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

•
For a Computer collection, if you collect shares and services for a particular computer in one collection and then run another collection for the same computer but just select shares, all the services will be marked as tombstoned and only shares will be updated.

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:

•
For an Active Directory collection, if you collect users and groups for a particular domain in one collection and then run another collection for the domain computers for the same domain, the users and groups from the previous collection will not be tombstoned.
•
For a OneDrive collection, if you collect a drive from a particular tenant in one collection and then run another collection for a different drive from the same tenant, the previous drive will not be tombstoned.

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

Table 7. How each discovery type works with tombstoning
Discovery Type
Root Object
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:

•
there are several options that are applied to every object in a discovery, such as global scopes and discovery options.
•
it makes it easier to understand what you are collecting.
•
you are more likely to meet the needs of your reporting users by providing consistent data.
* 
NOTE: The account you are logged in as is used to enumerate the scopes. If you are not seeing the expected objects in your browser, check your permission level.

See also:

•
Including Objects in Your Scope
•
Importing Computers to Your Scopes
•
Refining Your Scope with Exclusions
•
Filtering in the Browser

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.

* 
TIP: It is strongly recommended that each target is included in only one discovery. Including a target in differently-configured discoveries can result in data loss. If you add individual targets, ensure that they have not already been implicitly included in another discovery by way of a domain, OU, or container.

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

•
Specific computers: You can drill into domains, OUs and containers and select individual computers. All options in the scope are applied to each selected computer, including global scopes.
•
Folders and shares: You can drill into a computer and select folders and shares. All relevant options in the scope are applied.
* 
NOTE: If you select competing scopes, collection options define what will be collected. If you are collecting public shares and include a computer and a specific share, only the selected share will be collected. If you are collecting public shares and include a computer and a specific volume, both the volume and all public shares will be collected.
•
Registry hives and keys: You can drill into a computer and select specific hives and keys. Because the local registry hives are not available for collection, they are not available to select. When you include a specific hive or key, Enterprise Reporter interprets this to mean that is all you want to collect from the host computer; global scopes will not be applied.
•
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:

•
Step 2a. Choose scopes for your discoveries
•
Step 2b: Choose scopes for your Office 365 discoveries

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:

•
Computer
•
File Storage Analysis
•
Microsoft® SQL
•
NTFS
•
Registry

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:

\\computer1.domain.com
\\192.168.10.25
computer3.domain.com

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

To import computers to your scopes
1
On the scopes page, click the Import button.
2
Select Include Computers.
- OR -
Select Exclude Computers.
3
Browse to locate the file containing the computers to be imported.
4
Select the file and click Open to start the import.
5
Review the import progress and results messages and click OK when complete.
* 
NOTE: Any computer that is not successfully imported will be indicated by a red dot next to its name with an error description in the Message column.
6
Successfully imported computers will be visible in the Selected Scopes pane.
7
Optionally, fix any errors in the text file and repeat steps 1 through 5 until all computers are imported.
* 
NOTE: There is no need to remove previously imported computers from the text file as only unique computer names will be loaded during subsequent imports.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen