Converse agora com nosso suporte
Chat com o suporte

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

Choosing Your Microsoft Teams 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 . You can edit the name of the tenant if it is different from the credentials specified. Information about your resources is collected based on the discovery options.

See also:

Microsoft Teams Discovery: Configuring Enterprise Reporter Applications for Azure

You must register the applications used by Enterprise Reporter in your Azure environment. You can complete this process using the System | Configuration | Tenant Application Management option in the main menu before you create discoveries.

If the Enterprise Reporter Azure and Teams applications have not yet been registered in your Azure environment, the Microsoft Teams Scopes page of the discovery will display a warning message above the Azure Tenant name at the top of the screen. If you have already configured the required tenant application and it indicates the option to Reconfigure, nothing further is necessary.

1
On the Microsoft Teams discovery Scopes page, click Configure next to the tenant name to open the Tenant Application Manager.
1
Click Add.
3
2
Click Delete.
3
Click Yes to confirm that discoveries for any tenant that you delete will be unable to collect data
2
Click Configure or Reconfigure next to the application.
2
Click Configure next to the application.
2
Click Reconfigure next to the application.

Microsoft Teams Discovery: Include Scopes

Microsoft Teams discoveries, by default, target the Azure tenant that you specified with the credentials on the Name page in Step 1. Create the Discovery . You can edit the name of the Azure tenant if it is different from the credentials specified. Information about your teams, channels, owners, applications, tabs, files, and folders is collected based on the discovery options.

Microsoft Teams Discovery: Decide what to collect from the subscriptions in the discovery

Basic information from the tenant (the tenant name and full LDAP path) 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.

 

Channels

 

Medium

Applications

 

Medium

Files and Folders

 

Medium

Tabs

 

Low

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação