Enterprise Reporter 3.2.1 - Configuration Manager User Guide

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 .

Select the type of discovery. On the Name page of the Create Discovery wizard, type a unique name for your discovery.

Provide an optional description that outlines the data you collect with this discovery.

Select the assigned cluster.

Your change history status is indicated. For more information, see Best Practices for Creating Discoveries .


	NOTE: A cluster with a red icon is currently disabled. Your discovery cannot be run until you resolve the issue with your cluster.

For all discoveries except Azure, Exchange Online, Microsoft Teams, and OneDrive, select Use default node credentials to target computers that the logged in user can access.

For access to additional targets, use alternate credentials and choose an account from the Credential Manager. For more information, see Using the Credential Manager .

- OR -

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 .

If any warnings or messages are displayed, review them and click OK to continue.

Optionally, click Remove to delete an invalid or unwanted account.

Optionally, repeat these steps to add additional accounts that can be used to access the same target tenant for this discovery. Specifying additional accounts helps optimize the discovery by collecting tenant information in a more efficient manner.

For all discoveries except Active Directory, Azure, Exchange Online, Microsoft Teams, My SQL, and OneDrive, choose whether to ping computers in the discovery, and how long to allow for a response. (NTFS, computer, Exchange, File Storage Analysis, and Registry discoveries do not ping by default).

This sets the amount of time given to confirm a computer’s existence prior to attempting to collect data. Leave this option disabled if it is not possible to ping the computers in the discovery.

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.

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 .


	TIP: It is recommended that you only include a target (computer) in a single discovery for each type.


	NOTE: Use care when changing credentials. Credentials must have read access to all targets of the discovery, or tasks will fail. If this is not possible for all targets in one large discovery, break the discovery into smaller discoveries.


	NOTE: When choosing scopes for Azure Active Directory, Azure Resource, Exchange Online, Microsoft Teams, and OneDrive, the credential provided on the Name page of the Create Discovery wizard provides the default tenant name. If the tenant name is different than the credentials provided, the tenant name can be edited and specified. The tenant name is then used to enumerate scopes.

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:

•

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, 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:

•

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

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen

Bitte w&auml;hlen Sie Ihr Produkt aus:

Damit wir Ihnen besser helfen können, geben Sie den Grund Ihres Chats an:

Empfohlene Lösungen für Ihr Problem

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Step 1. Create the Discovery

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

Scopes: An Overview

How Scopes Affect Tombstoning

Bitte wählen Sie Ihr Produkt aus: