Chat now with support
Chat mit Support

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Product Overview 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
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 Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Understanding Discoveries

Defining the Data Collection (Discoveries)

Once you have configured a cluster, you can begin setting up discoveries. Discoveries define the targets from which you will be collecting data. Enterprise Reporter uses a "collect all" model. After you run a discovery, you can run reports that include the data you have collected. For more information on reporting, see the Quest Enterprise Reporter Report Manager User Guide in the Technical Documentation. 

Enterprise Reporter includes the following types of on-premises discoveries:

Active Directory

Collects information about your domains and Active Directory® objects within the domains, such as users, groups, sites and trusts.

Computer

Collects information specific to a computer, such as printers, shares and security policies.

Exchange

Collects information about your Exchange organization and permission information about your organization's mailboxes, stores, public folders, contacts, groups, and group members.

File Storage Analysis

Collects information about your network’s file storage capacity and usage.

Microsoft SQL

Collects information about your Microsoft® SQL Servers®.

NTFS

Collects information about your NTFS structure— files, folders, and permissions.

Registry

Collects registry keys and values from available registry hives.

 

Enterprise Reporter includes the following types of Office 355™ discoveries:

Azure Active Directory

Collects information about your Office 365™ tenant information about your Azure™ users and groups.

Azure Resource

Collects information about your Azure subscriptions.

Exchange Online

Collects information about your Office 365™ tenant and permission information about your Exchange Online™ mailboxes, public folders, contacts, groups (static, dynamic, and unified) and group members.

Microsoft Teams

Collects information about your Microsoft Teams.

OneDrive

Collects information about your Office 365™ tenant and permission information about your OneDrive® files and folders for licensed OneDrive users.

Best Practices for Creating Discoveries

To get the best performance, and meet the needs of your reporting users, there are a number of things you should consider.

Active Directory

100,000 users

1

40 minutes

Active Directory

500,000 users, groups, and computers (includes 10 million group members)

2

11 hours

Computer

200 computers

12

25 minutes

File Storage Analysis

1 server with 1 million files and folders

1

2 hours 25 minutes

Exchange

1,000 mailboxes and 15,000 mailbox folders

1

40 minutes

Exchange

10,000 mailboxes with permissions

1

1 hour 20 minutes

NTFS

5 million files and folders with permissions

6

5 hours 50 minutes

NTFS

31 million files and folders with permissions

10

20 hours

Note: All collection times are affected by hardware specifications and network activity.
For Azure discoveries, as show in Table 12, the scoped tenant will resolve to a single collection task for the tenant. This means that if you want to utilize more nodes for the collection of a single tenant, you should create a discovery by object type for optimal performance. For Azure discoveries, there are 5 object types (users, groups, contacts, roles, and service principals) that can be collected so a maximum of 5 nodes can be used at one time.
For OneDrive discoveries, as shown in Table 12, the scoped tenant will resolve to a single collection task for the tenant, but the discovery will be tombstoned based on the drives, not the object type like Azure AD discoveries. This means that if you want to utilize more nodes for the collection of a single tenant, you must create a discovery for each drive or group of drives. For example, if your tenant has 10 drives, you can create 10 discoveries so a maximum of 10 nodes can be used at the same time.

Azure AD

30,000

1

2

N/A

30 minutes

Azure AD

300,000

1

1

N/A

5.5 hours

Azure Resource

7 subscriptions with 7,000 resources

1

3

N/A

30 minutes

Exchange Online

1,000 mailboxes

1

1

N/A

8 minutes

Exchange Online

1,000 mailboxes with permissions and delegates

1

1

N/A

3 hours
59 minutes

Exchange Online

1,000 mailboxes with folders

1

1

N/A

1 hour
12 minutes

Exchange Online

1,000 mailboxes with folders

1

3

N/A

24 minutes

Exchange Online

5,000 mailboxes

1

1

N/A

15 minutes

Exchange Online

5,000 mailboxes with permissions

1

1

N/A

4 hours
35 minutes

Microsoft Teams

1,000 teams with 10,000 files and folders

1

1

N/A

1 hour
30 minutes

Microsoft Teams

1,000 teams with 200,000 files and folders

1

1

N/A

5 hours

OneDrive

Drives: 1
Files/Folders: 400,000

1

11

10

17 hours

OneDrive

Drives: 5
Files/Folders: 20,000

1

5

10

1

OneDrive

Drives: 100
Files/Folders: 500,000

1

11

10

21 hours

Note: All collection times are affected by hardware specifications and network activity.

Creating Discoveries

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

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen