サポートと今すぐチャット
サポートとのチャット

Enterprise Reporter 3.5.1 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises 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 cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Step 2b: Choose scopes for your cloud discoveries

In this section, we will explore choosing scopes for each discovery type.

See also Step 2a. Choose scopes for your on-premises discoveries

Choosing Your Azure Active Directory Scopes

Azure Active Directory discoveries, by default, target the tenant that you specified with the credentials on the Name page in Step 1. Create the Discovery (Name) .

Information about your contacts, users, groups, group members, roles, and application service principals is collected based on the discovery options.

Azure AD Discovery: Decide what to collect from the tenant in the discovery

You can collect a variety of information from the Azure tenant in your discovery. Basic information from the tenant (the tenant name and full LDAP path), subscriptions, licenses, and service plans is always collected.

The following table outlines the additional information that can be collected. Collecting additional information impacts discovery performance. Options with a high performance cost will slow discovery performance more than options with a medium or low performance cost.

Users

Collects basic information for all user accounts.

Medium

If collecting users, you can enable this option to collect additional attributes such as AboutMe, Birthday, HireDate, Interests, MySite, PastProjects, PreferredName, Responsibilities, Schools, and Skills.

High

If collecting users, you can enable this option to collect Multi-Factor Authentication information.

Medium

If collecting users, you can enable this option to collect users flagged for risk.

Medium

If collecting users, you can enable this option to collect user activity data such as such as which licenses are assigned to a user and the dates when a user last used a licensed service.

Low

Groups

Collects basic information for all groups including direct members.

Medium

If collecting groups, you can enable this option to collect additional attributes such as AutoSubscribeNewMembers, and IsSubscribedByMail.

High

Contacts

Collects basic information for all contacts.

Low

Devices

Collects basic information for all devices and their users.

Medium

Roles

Collects basic information for all standard roles including role direct members.

Low

Applications and Service Principals

Collects information for all applications and service principals including the user and group assignments.

High

Choosing Your Azure Resource Scopes

Azure Resource discoveries, by default, target the tenant that you specified with the credentials on the Name page in Step 1. Create the Discovery (Name) . Information about your resources is collected based on the discovery options.

See also:

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択