サポートと今すぐチャット
サポートとのチャット

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

NTFS Discovery: Include scopes

The scopes you add will determine the computers and specific folders that will be the targets of the discovery when it is run. You can explicitly add domains, OUs, containers, computers, folders, shares, DFS shares, or NAS devices. Domains, OUs and containers can contain many computers, which can significantly increase the time it takes to run the discovery. For more information, see Including Objects in Your Scope .

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 .

1
Click Add.
3
Click Include to add to your selected scopes list.
4
Click OK
1
Click Add.
2
Click Add to Scope | Add DFS share.
4
Click Include to include the DFS share.

NTFS 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 full details, see Refining Your Scope with Exclusions .

1
Click Add.
4
Click Exclude.
5
Select the file and click Open to start the import.
1
Click Add.
3
Click Add.
5
Click Exclude to exclude the DFS share.

NTFS Discovery: Select your global scopes

Global scopes are folders 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 common paths on all computers. For example, if you have included computers from different Windows® Operating Systems, the path to the Windows folder may be different. Instead of having to specifically add the Windows folder, you can choose the global [WINDOWS] scope, and Enterprise Reporter can determine where that folder is located on each computer.

COMMONFILES

The location of the Common Files folder.
Usually C:\Program Files\Common Files

PROGRAMFILES

The location of the Program Files folder.
Usually C:\Program Files

SYSTEM

The location of the Windows System32 folder.
Usually C:\Windows\System32

SYSTEMDRIVE

The drive where the operating system is installed.
Usually C:\

WINDOWS

The location where Windows is installed.

Usually C:\Windows

2
Click Include or Exclude.
3
Optionally select Requirements | Collect only selected shares, folders and DFS shares to suppress the collection of all public shares or volumes.

NTFS Discovery: Decide what to collect from any computer in the discovery

When you run an NTFS discovery, it is resolved to a list of computers and folders. Folders will be accessed using the share path and you must have read access to the share. Accessing folders using the share path is useful if shares are distributed, as in the case for DFS shares or Net App filers where administrative shares are disabled or not available.

The NTFS object that is being shared (for example a folder) is collected, and will be displayed in the report. For example, folders and files on a share called \\NYC_SVR\TrainingMaterials that is physically located on the computer named NYC_SVR in the path C:\HR\NYC\NewHires\TrainingMaterials would be accessed and displayed as \\NYC_SVR\TrainingMaterials.

For all computers in the discovery, you need to decide the starting point for your collection. This combines with your global scopes and recursion level to determine what folders are collected from each computer in the scope.

You must specify how to collect the information from each computer in the discovery. You can collect all available public shares, collect all available volumes, or collect only the selected shares, folders, and DFS shares. The following table outlines these options.

 

Collect all available public shares

The following data is collected:

Medium

 

High

Collect all available volumes

All folders on any computer resolved from the scope are collected, unless:

NOTE: Based on your selected scope, if you are collecting against NAS devices, you have the option to use specified NAS Configurations.

High

Collect only selected shares, folders and DFS shares

This option is displayed when either:

When this option is selected, the NTFS discovery will only collect applicable folders and shares without performing the collection of all public shares and volumes.

Medium

The following table outlines the additional information that can be collected during the discovery. 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.

 

Folder Options

You have options to choose how deep into the tree the discovery will collect data.

 

The default is to collect all folder levels, starting from the included scope.

High

You can collect just the root level by setting the folder depth to 0.

You can choose the number of levels to collect, starting from the included scope, by setting the folder depth as desired. The root is not counted as a recursion level. If you have an excluded scope within an included scope, no folders below the exclusion are collected. In a very complicated nested set of includes and excludes along the same branch, the recursion level is reset with each includes scope.

Medium

File Options

You have options to choose what file information is collected.

 

 

Medium

Option available if collecting files and their basic details.

Requirement: Microsoft Office must be installed on the Enterprise Reporter node computer.

High

Option available if collecting files and their basic details.

High

Permission Options

 

 

 

High

Option available if collecting files and their basic details.

High

Selecting this option reduces the high performance cost of collecting all file permissions

 

Collects the permissions that are Added, Modified, and Removed for a file or folder as compared to the parent.

NOTE: Only the DACL and Owner permissions are collected.

High

You can choose to recursively collect the members of any groups found in the collection of file or folder permissions by selecting this option.

High

Advanced Options

 

 

A collection task is always created for each computer in an NTFS discovery. Selecting this option will create a task per share for each computer to allow tasks to be load balanced using multiple nodes.

 

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

Folder Options

You have options to choose how deep into the tree the discovery will collect data.

The default is to collect all folder levels, starting from the included scope.

You can collect just the root level by setting the folder depth to 0.

You can choose the number of levels to collect, starting from the included scope, by setting the folder depth as desired. The root is not counted as a recursion level. If you have an excluded scope within an included scope, no folders below the exclusion are collected. In a very complicated nested set of includes and excludes along the same branch, the recursion level is reset with each includes scope.

Permission Options

 

Selecting this option reduces the high performance cost of collecting all file permissions.

Advanced Options

 

A collection task is always created for each computer in an NTFS discovery. Selecting this option will create a task per share for each computer to allow tasks to be load balanced using multiple nodes.

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

 

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.

The scopes are now selected and configured. It is a good idea to review your scopes before continuing.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択