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

Including Objects in Your Scope

A valid discovery requires that you include at least one object. You can explicitly include high-level objects—domains, OUs and containers. This implicitly adds all computers in the selected object. For some discovery types, you can include objects using a query for more flexibility. For more information, see Using Queries to Define Your Scopes .

When you run the discovery Enterprise Reporter resolves the high level object to a list of targets, or in the case of an AD discovery, to a list of domains. These can be useful because if the contents of the container change, so do the targets of the discovery. Once Enterprise Reporter resolves this list, the other options in the scope can be applied.

* 
TIP: It is strongly recommended that each target is included in only one discovery. Including a target in differently-configured discoveries can result in data loss. If you add individual targets, ensure that they have not already been implicitly included in another discovery by way of a domain, OU, or container.

Depending on the discovery type, you may also be able to select:

•
Specific computers: You can drill into domains, OUs and containers and select individual computers. All options in the scope are applied to each selected computer, including global scopes.
•
Folders and shares: You can drill into a computer and select folders and shares. All relevant options in the scope are applied.
* 
NOTE: If you select competing scopes, collection options define what will be collected. If you are collecting public shares and include a computer and a specific share, only the selected share will be collected. If you are collecting public shares and include a computer and a specific volume, both the volume and all public shares will be collected.
•
Registry hives and keys: You can drill into a computer and select specific hives and keys. Because the local registry hives are not available for collection, they are not available to select. When you include a specific hive or key, Enterprise Reporter interprets this to mean that is all you want to collect from the host computer; global scopes will not be applied.
•
DFS Shares: A published Windows® Server DFS share can be added like any other share, from the System\Dfs-Configuration container within a domain. You can use the Browse dialog box to manually add all other DFS shares.

For more details on including objects in your scopes for each discovery type, see also:

•
Step 2a. Choose scopes for your on-premises discoveries
•
Step 2b: Choose scopes for your cloud discoveries

Importing Computers to Your Scopes

On the Scopes page, instead of using the Add button to add one computer at a time, you import multiple computers to be included (or excluded) from collection for the following types of discoveries:

•
Computer
•
File Storage Analysis
•
Microsoft SQL
•
NTFS
•
Registry

You can import from any text file containing a list of the fully qualified computer name (or IP addresses) of the computers to be targeted with one computer per line, as in the following example:

\\computer1.domain.com
\\192.168.10.25
computer3.domain.com

Only unique computer names free of invalid characters will be imported.

To import computers to your scopes
1
On the scopes page, click the Import button.
2
Select Include Computers.
- OR -
Select Exclude Computers.
3
Browse to locate the file containing the computers to be imported.
4
Select the file and click Open to start the import.
5
Review the import progress and results messages and click OK when complete.
* 
NOTE: Any computer that is not successfully imported will be indicated by a red dot beside its name with an error description in the Message column.
6
Successfully imported computers will be visible in the Selected Scopes pane.
7
Optionally, fix any errors in the text file and repeat steps 1 through 5 until all computers are imported.
* 
NOTE: There is no need to remove previously imported computers from the text file as only unique computer names will be loaded during subsequent imports.

Refining Your Scope with Exclusions

This step can be done in conjunction with the inclusions. Exclusions refine your scope further. Use the browser, a query, or the Import option to exclude scopes. For more information, see Importing Computers to Your Scopes .

For example, you can add a computer, but exclude a specific folder; or add a domain and exclude a specific OU. The following rules are used to process your exclusions:

•
If you add an exclusion without the inclusion of a parent, it has no meaning and will be ignored. As long as the exclusion can be traced up the AD tree to a parent object, the exclusion can be processed.
•
If you explicitly exclude a folder or share, that data will not be available for reporting.
•
You should not collect the same shares or volumes in multiple discoveries as data loss can occur.
•
When selecting a domain, OU or container as a target to collect, a whole computer can be excluded from the discovery.
•
For an Active Directory discovery, excluded objects are processed after included objects. Any OU or container that is included below an excluded one in the AD structure will not be included, as the exclude will take precedence.

Filtering in the Browser

It can be difficult to find the objects you are looking for when you are selecting your scope. To address this, you can use filtering in the browser. Filtering starts from your selected location, and is applied one level down. For example, if you filter at the domain level, the filter is applied to the first level containers. You remove filters one at a time, starting with the last filter you applied.

To apply a filter
1
Expand the tree, and then select your starting point.
You must expand the first level of the selected node in order for the filter to work.
2
In the Apply filter to box, type your search string.
3
Click Apply Filter.
* 
NOTE: You can also right-click any node on the tree and choose Filter.
To remove a filter
1
Click Undo Filter to remove the last filter applied.
The details of the filter you will remove are displayed in the "Last Filter applied to" box.
2
Repeat if needed to remove other filters.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation