Enterprise Reporter 3.5.1 - Configuration Manager User Guide


	NOTE: If you make changes to Azure applications outside of Enterprise Reporter (for example, if you remove permissions or delete applications), Enterprise Reporter does not receive these updates. Use the Reconfigure link beside an application to recreate the application and grant consent to the application permissions again.

To open the Tenant Application Manager from a cloud discovery

On the Names page, click Configure beside the tenant name to open the Tenant Application Manager.

To add a tenant

Click Add.

Enter the name of the tenant where Enterprise Reporter applications will be created.

Click OK.

To delete a tenant

Select the name of the tenant to be deleted.

Click Delete.

Click Yes to confirm that discoveries for any tenant that you delete will be unable to collect data

The tenant and the Enterprise Reporter applications for this tenant are removed.

To edit administrator credentials for the tenant application

Open the Tenant Application Manager. For more information, see To open the Tenant Application Manager .

Click Configure or Reconfigure next to the application.

Complete the Microsoft wizard that guides you through registering the application and consenting to application permissions using credentials that have administrative access to create Enterprise Reporter applications on the tenant.

If multi-factor authentication has been configured for this account, you will be prompted to complete the verification steps to complete the authentication process.

Once consent is complete, the Tenant Application Manager will display a Reconfigure link next to the application.

To configure applications for a tenant

Open the Tenant Application Manager. For more information, see To open the Tenant Application Manager .

Click Configure next to the application.

Complete the Microsoft wizard that guides you through registering the application and consenting to application permissions using credentials with administrative access to create Enterprise Reporter applications on the tenant.

If multi-factor authentication has been configured for this account, you will be prompted to complete the verification steps to complete the authentication process.

Once the consent is complete, the Tenant Application Manager will display a Reconfigure link next to the application.


	NOTE: For more information, see Permissions for Enterprise Reporter tenant applications .

To reconfigure application for a tenant

Open the Tenant Application Manager. For more information, see To open the Tenant Application Manager .

Click Reconfigure next to the application.

If multi-factor authentication has been configured for this account, you are prompted to finish the verification steps and complete the authentication process.

Once the consent is complete, the Tenant Application Manager will display a Reconfigure link next to the application.


	NOTE: For more information, see Permissions for Enterprise Reporter tenant applications .

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 the following sections:

•

Scopes: An Overview

•

How Scopes Affect Tombstoning

•

Using the Browser to Include and Exclude Scopes

•

Including Objects in Your Scope

•

Importing Computers to Your Scopes

•

Refining Your Scope with Exclusions

•

Filtering in the Browser

•

Using Queries to Define Your Scopes

•

Using Subnets to Define Your Scopes

•

Using Subnet Credentials

Scopes: An Overview

Scopes define the targets of the discovery. Options vary depending on the type of discovery you are creating. When you choose scopes for on-premises collections, 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 the 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.

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.

Some discovery types have additional options to collect related information that adds value to your reports. For example, if an NTFS discovery encounters Active Directory 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 on-premises 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, SharePoint Online 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.

For the SharePoint Online discovery type, all site collections that are part of the include list are stored in the database while other previously collected site collections are not tombstoned. All site collections that are part of the exclude list are tombstoned while all other site collections are collected.

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

Table 26. 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
SharePoint Online	Tenant	No

*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.

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.5.1 - Configuration Manager User Guide

Configuring Tenant Applications for Cloud Discoveries

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

Scopes: An Overview

How Scopes Affect Tombstoning

Bitte wählen Sie Ihr Produkt aus: