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

Enterprise Reporter 3.2.2 - Configuration Manager User Guide

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

Registry Discovery: Include scopes

You can specifically add domains, OUs, containers, computers, hives and keys. For full information on using the browser to add scopes, see Using the Browser to Include and Exclude Scopes .

You can create scopes using a dynamic query, which is resolved when the discovery is run. This gives you the flexibility to describe the computers you want to target. For more information, see Using Queries to Define Your Scopes .

* 
NOTE: Use caution when creating your queries. Ensure that the resulting set of targets is not too large for a single discovery. As well, query results should not include computers included in another discovery of the same type. If a target is in more than one discovery of a particular type, rejected tasks will appear. For more information, see Data Collection Issues .
To explicitly include objects in your Registry scope
1
Click Add.
- OR-
If you have a text file containing the computers to be selected, click Import and follow the steps as outlined in Importing Computers to Your Scopes .
2
In the treeview, locate the desired object and select it.
To select multiple objects, press Ctrl during selection.
For more information, see Filtering in the Browser .
- OR -
To include a scope using a subnet, expand the Add to scope menu, select Add Subnet, and click Add. For more information, see Using Subnets to Define Your Scopes .
3
Click Include to add to your selected scopes list.
4
Click OK. 
* 
NOTE: When you add a domain, its child domains are not included - each domain must be explicitly added. When you add an OU or container, all children are included.

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 and follow the steps as outlined in Importing Computers to Your Scopes .
2
Expand the treeview to locate the object you want to exclude.
You can press Ctrl to select multiple objects.
3
Click Exclude. 

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 20. 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 21. 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 22. 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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation