Tchater maintenant avec le support
Tchattez avec un ingénieur du 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:

•
If you add OUs and Domains as your scope in an NTFS, computer or registry discovery, all relevant objects within these containers will be collected. This has the advantage of capturing changes within the containers, but the disadvantage of potentially collecting information that is of little interest. You may want to break up large discoveries into smaller, more focused discoveries.
•
Ensure that each target computer is in only one discovery of each type. For example, a computer can be in a Computer discovery and an NTFS discovery, but not in two different NTFS discoveries.
•
Collect only the files, folders, and registry keys that you know are required for your reporting users.

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:

Table 28. Collection Options For Each Type Of Discovery
Discovery Type
Collection Options

Active Directory®
•
Users
•
Token groups count
•
Domain controller last logon
•
Remote desktop information for domain users
•
Photographs for domain users
•
Groups and Members
•
Members from foreign domains
•
Nested groups and their members from foreign domains
•
Computers (Active Directory® objects)
•
Domain Controllers
•
Permissions
•
Contacts
•
Trusts
•
Sites
•
Deleted objects
•
Service Accounts
•
Active Roles Virtual Attributes

Azure Active Directory
•
Users
•
Additional attributes from Office 365
•
Multi-factor authentication attributes
•
Users flagged for risk
•
Contacts
•
Devices
•
Groups
•
Additional attributes from Office 365‘
•
Roles
•
Applications and Service Principals

Azure Resource
•
Subscriptions (all or specific)
•
Resources
•
Virtual machines
•
Disks
•
Networking
•
Storage Accounts
•
Access control
•
Nested group members

Computer
•
Printers
•
Shares
•
Volumes
•
Accounts
•
Installed Software
•
Microsoft Store Applications
•
Hotfixes
•
Policies
•
Services
•
Event Log Configuration
•
Extended WMI Entities
•
Nested group members

Exchange
•
Mailboxes
•
Mailbox subfolders
•
Mailbox delegates
•
Include system delegates
•
Mail-Enabled Users
•
Mail Contacts
•
Public Folders
•
System public folders
•
Distribution Groups
•
Permissions
•
Mailbox AD permissions
•
Mailbox Exchange permissions
•
Mailbox folder permissions
•
Public folder permissions
•
Optionally, only explicit permissions
•
Nested group members

Exchange Online
•
Mailboxes
•
Mailbox delegates
•
Mailbox statistics
•
Mailbox folders
•
Public Folders
•
System Public Folders
•
Mail-Enabled Users
•
Mail Contacts
•
Distribution Groups
•
Group members
•
Dynamic group members
•
Permissions
•
Mailbox folder permissions
•
Optionally, only explicit permissions
•
Nested group members

File Storage Analysis
•
Shares
•
Hidden Shares
•
Home Directories
•
Collect NAS using Configuration
•
If unable to collect volumes then collect shares as volumes
•
Files
•
Folders
•
Follow Directory Symbolic Links
•
Owners

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
•
Channels
•
Files and Folders
•
Applications

NTFS
•
How to collect the information:
•
Collect all available public shares
•
Include hidden hares
•
Collect all available volumes
•
Based on your selected scope, if you are collecting against NAS devices, do you want to use specified NAS Configurations?
•
Yes
•
No
•
Collect only selected shares, folders and DFS shares. Collection of all public shares or volumes will not occur.
•
Folder options:
•
All folder levels
•
Folder depth— determines how far into the folder structure to collect data
•
File options:
•
Collect files and their basic details like size and attributes
•
Collect advanced file metadata such as author and title
•
Calculate duplicate files within the same computer
•
Permission options:
•
Folder permissions - these should only be collected if needed by your reporting users
•
File permissions - these should only be collected if needed by your reporting users
•
Only collect and store files which have explicitly granted permissions
•
Calculate permissions differences between folders, subfolders, and files.
•
If a group account is found when collecting permissions, recursively collect group members.
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 .
•
Advanced options:
•
Create a task per share for each computer - a collection task is created for each computer in the NTFS discovery. You can select this option to enable additional load balancing between nodes.

OneDrive
•
Drives
•
All drives
•
Selected drives
•
Folders
•
Files
•
Permissions
•
Nested group members
•
Configuration Settings

Registry
•
Registry values
•
Permissions and group members
•
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 .
•
Recursion level — determines how far into the registry structure to collect data.

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:

•
Run your discoveries or scheduled reports at times when network traffic is low.
•
Take into account the number of nodes in relation to the number of tasks that will be processed by discoveries. You should only schedule discoveries simultaneously if your deployment is capable of processing them.
•
Evaluate the time it takes to run a discovery using the history view for a discovery. This can be very useful when you are trying to get the freshest data possible for a scheduled report—you can schedule to start as late as possible while still providing data for the necessary reports. You can also use this understanding to better coordinate the schedules of your discoveries to avoid overloading your nodes.

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:

•
Collect accounts from each domain of interest (one discovery per domain, and be sure to include all other data that you need from that domain). This results in the groups and members in the domain being collected once.
•
If a domain has groups with members from other domains for which you do not have separate discoveries, you should collect foreign group members to ensure complete data.
•
Do not collect group members in NTFS, Registry, or MS SQL discoveries, if you will have all the information needed for reporting from the Active Directory® or Exchange® discoveries.
* 
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.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation