立即与支持人员聊天
与支持团队交流

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

Creating Discoveries

•
Step 1. Create the Discovery
•
Step 2. Choose what to include in your discovery (Scopes)
•
Step 2a. Choose scopes for your discoveries
•
Step 2b: Choose scopes for your Office 365 discoveries
•
Step 3. Schedule your Discovery
•
Step 4: Review the summary

There are several steps for creating a discovery. A wizard guides you through the process, which varies slightly depending on the type of discovery.

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 .

* 
TIP: It is recommended that you assign the discovery to the cluster closest to the data.
To create a discovery
1
On the Manage Discoveries pane, click New Discovery.
- OR -
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 .
2
Select the type of discovery. On the Name page of the Create Discovery wizard, type a unique name for your discovery.
3
Provide an optional description that outlines the data you collect with this discovery.
4
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.
5
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 and click OK. For more information, see Using the Credential Manager .
 
* 
NOTE: Office 365 discoveries support Multi-Factor Authentication enabled and disabled credentials.
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.
6
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.
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
•
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. 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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级