Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Multi-Factor Authentication Discovery Credential Limitations

Microsoft 365 discoveries support both Multi-Factor Authentication enabled and disabled credentials. However, using Multi-Factor Authentication enabled credentials on Microsoft 365 discoveries can result in an incomplete collection that omits one or more of the following objects and attributes.

Azure Active Directory

No Risky users and Azure Active Directory extended attributes

Azure Resources

Fails with no data returned

Exchange Online

All Exchange Online Permissions, Mailbox Folders, Mailbox Statistics, Public Folders, Dynamic Groups and Members

Microsoft Teams

No files and folders (drives)

SharePoint Online

Fails with no data returned

One Drive

Fails with no data returned

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 18, the scoped tenant will resolve to a single collection task for the tenant. This means that if you want to use 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 five object types (users, groups, contacts, roles, and service principals) that can be collected so a maximum of five nodes can be used at one time.
For OneDrive discoveries, as shown in Table 18, 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 as in Azure AD discoveries. This means that if you want to use 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

SharePoint Online

20,000 Site Collections (25,000 sites including 5000 sub-sites)

1

1

N/A

2 hours

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

Improving the Performance of Your Discoveries

When a discovery is run on a cluster, the Enterprise Reporter server assigns work to its nodes. You can add nodes to a cluster at any time. Each node can only belong to one cluster. You can increase the performance of your discoveries by ensuring that nodes are configured to optimize the maximum number of concurrent tasks or by adding new nodes.

Each collection task is assigned to a node, balancing the distribution across the nodes until all the nodes are processing as many tasks as they are able. If no nodes are available to process the task, the task must wait until a node becomes available.

Node performance is based on a combination of memory, processor speed, and network bandwidth. If your network, computer memory, or processor speed are less than you would like, consider adding nodes. If your node is under used, set the maximum concurrent tasks to 0 to optimize node performance instead of adding more nodes. If a node starts to slow down when node performance is already optimized (by setting the maximum concurrent tasks to 0), adding a node will increase performance. For more information, see Nodes and Improving the Performance of a Node .

See also:

Adding a Node

Since a node must belong to a cluster, you must first create a cluster. For more information on creating clusters, see To create your first cluster and node .

If you use credentials that are different than the Enterprise Reporter server credentials, they must be granted access to the database.

5
To use SQL credentials to connect to the database, select Database Credential, then choose SQL Authentication and select the SQL account from the Credential Manager.
6
Optionally, select Specify an alternate credential for Node service deployment, then select the account.
7
Set tasks to be System - managed to optimize performance. For more information, see Nodes and Improving the Performance of a Node .
8
Click Add.
10
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation