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

Enterprise Reporter 3.5 - 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

Registry Discovery: Optionally refine your scope list with exclusions

Exclusions refine the inclusions you have defined. You can do this optional step in conjunction with inclusions. For more information, see Refining Your Scope with Exclusions .

To explicitly exclude objects from your selected scope
1
Click Add.
- OR-
If you have a text file containing the computers to be selected, click Import
2
Browse to locate the file containing the computers to be imported and select Exclude Computers.
3
Expand the treeview to locate the object you want to exclude.
You can press Ctrl to select multiple objects.
4
Click Exclude.
5
Select the file and click Open to start the import.

Registry Discovery: Select your global scopes

Global scopes are hives or keys that are collected from every computer in the scope. When you run the discovery, Enterprise Reporter uses the scopes you selected in the first two steps to resolve a list of computers that will be targeted. Anything you include or exclude globally is applied to these computers. Use global scopes to:

•
Collect a registry hive on all computers. User specific hives cannot be collected; only available hives are listed.
•
Collect specific registry keys on all computers. If there is a key that you want to collect on many of the computers, it is more efficient to include it globally. If the key is not on all targets, the inclusion will be ignored for those targets.
•
Exclude hives or keys on all computers. You make the same selections outlined above, but choose to exclude them instead of collecting them.
* 
NOTE: A global scope is not valid alone. You must first include a domain, OU, container, computer, hive or key. See Registry Discovery: Include scopes for more information.
* 
NOTE: If you add a global exclusion that conflicts with an explicit inclusion from Step 1, the explicit inclusion will be processed, and the global exclusion will be ignored.
To add a global scope
1
From the Add Global list, choose a hive.
- OR -
From the Add Global list, choose the hive, then type "\" and a key.
For example, select HKEY_LOCAL_MACHINE then type \Software to include all software registry keys on all computers.
- OR -
Type a hive and key.
Because these are going to be collected for all computers in the resolved discovery, you cannot include a computer name in the path. Invalid characters include "|", "[", and "]".
2
Click Include or Exclude.
You can press Enter to add to your list. Enter functions as the last button you clicked - for example, if you have just clicked Include, Enter includes your global scope.

Registry Discovery: Decide what to collect from any computer

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.

 
Table 30. Registry Discovery: Optionally collect information for the following objects
Option
Notes
Performance Cost

Collect values

This option is selected to collect key values. You can disable this option to collect only registry keys and enhance discovery performance.

Medium

Key permissions

 

High

•
Group members

If collecting key permissions, you can enable this option to recursively collect the members of any groups found in your discovery.

High

The following options further refine how collection tasks are handled.When collecting additional attributes, especially ones with a high performance cost, consider enabling this performance option to help improve collection performance.

 
Table 31. Registry Discovery: Performance Options
Performance Option
Notes
Recursion options

 

•
All branches

 

•
Branch depth

Large registry hives can take a while to collect, so you can improve performance by restricting the number of branches using the Branch depth option.

The following options determine how target computers are resolved during discoveries.

 
Table 32. Discovery Resolution Options
Option
Notes
Resolution Options

 

Allow a configurable number of seconds for a target computer to respond to a ping request

Pings target computers at collection time to determine the existence of target computers on the network before processing tasks.

Resolve target computers with disjoint namespaces

Verifies the existence of target computers with disjoint namespaces by using their DNS host names and, if that fails, by using their NetBIOS names.

Step 2b: Choose scopes for your cloud discoveries

In this section, we will explore choosing scopes for each discovery type.

•
Choosing Your Azure Active Directory Scopes
•
Choosing Your Azure Resource Scopes
•
Choosing Your Exchange Online Scopes
•
Choosing Your Microsoft Teams Scopes
•
Choosing Your OneDrive Scopes
•
Choosing Your SharePoint Online Scopes

See also Step 2a. Choose scopes for your on-premises discoveries

 
* 
NOTE: Azure Active Directory, Azure Resource, and OneDrive discoveries are multi-threaded to optimize performance and require an Intel® or AMD 2 GHz multiprocessor with at least two cores.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation