Chat now with support
Chat with Support

Enterprise Reporter 3.2.2 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Collect Only the Data Needed

When you configure a discovery, you choose both the scope of the discovery, and what you want to collect from each target. If you know what the data is going to be used for, you can collect only the needed data. If you are not sure, and performance is an issue, consider collecting a minimal set of data, and then wait for requests for more data before extending the discovery.

When scoping your discovery, consider:

Once you have carefully selected your scopes, consider what you need to collect from each target. The following table outlines the collection options for each type of discovery:

Active Directory®

Azure Active Directory

Azure Resource

Computer

Exchange

Exchange Online

File Storage Analysis

Microsoft SQL

Group members — either Active Directory® or computer users who are members of any groups discovered in the collection. You can also get this information through Active Directory® and Computer discoveries. For more information, see Optimize Nested Group Membership Collection .

MS Teams

NTFS

Note: Group members of any groups discovered in the collection - either Active Directory® or computer users who are members of any groups discovered in the collection. You can also get this information by through Active Directory® and Computer discoveries. For more information, see Optimize Nested Group Membership Collection .

OneDrive

Registry

Plan Discovery and Reporting Schedules

Enterprise Reporter reports on previously collected data. It is important to coordinate the discovery schedules with your reporting schedules, to ensure that the data meets the requirements of the users.

As your deployment grows in complexity, you may find value in coordinating the schedules for your discoveries in a cluster. Things to consider:

Optimize Nested Group Membership Collection

Depending on the reports that will be run, you may need to collect data to show nested group memberships. It is more efficient to collect to group members through Active Directory® discoveries than using the nested group membership options in individual discoveries of other types. This also helps avoid collecting the same accounts in multiple discoveries. The recommended practice for collecting nested group members is to:

NOTE: If you are not running Active Directory® or Exchange® discoveries, you will need to include the nested group members in NTFS, Registry or MS SQL discoveries.

Optimize Nested Group Membership Collection for Azure and Office 365 Discoveries

Depending on the reports that will be run, you may need to collect data to show nested group memberships. It is more efficient to collect group members through the Azure Active Directory discoveries than using the nested group membership option on the Azure Resource, Exchange Online, or OneDrive discovery.This also helps to avoid collecting the same accounts in multiple discoveries.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating