• Become a portal pro
• Download
• Print
• My Downloads ()

• Support
• Technical Documentation
• Enterprise Reporter 3.2.1
• Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Table of Contents  

Product Overview

Key Features of Enterprise Reporter Components of Enterprise Reporter 3.2.1

The Configuration Manager

An Overview of the Configuration Manager Clusters Shared Data Locations Nodes Discoveries Role of the Server

The Report Manager The Database Wizard and Database Content Wizard The Encryption Key Manager Knowledge Portal

Enterprise Reporter Architecture Summarizing the Workflow

Configuring the Configuration Manager

Starting the Configuration Manager Finding Answers and Getting Help An Overview of Enterprise Reporter Communications and Credentials Required

Node Credential and Alternate Credential Details for On-Premises Discoveries Detailed Permissions for Enterprise Reporter Discoveries Permissions for Enterprise Reporter Discoveries on NAS Devices Permissions for Enterprise Reporter Tenant Applications

Logged In User Details

Server Service Credential Details

Setting Up Your First Collection Computers

Configuring Clusters and Nodes for Effective Data Collection Things to Consider Before Creating a Cluster Creating Your First Cluster and Node

Modifying your Deployment

When Do You Add a Cluster? Modifying a Cluster Deleting a Cluster Disabling a Cluster What To Do if a Cluster is Disabled Enabling a Cluster Managing Nodes

Modifying Node Credentials Modifying the Location of a Node's Temporary Files Removing a Node Why Disable a Node? Stopping a Node Enabling a Node Starting a Node

Improving the Performance of Your Discoveries

Adding a Node Improving the Performance of a Node

What does the status of a node or cluster indicate? Using the Credential Manager

Changing Passwords Using the Credential Manager Changing Account Names Using the Credential Manager

Changing the Credentials used by the Enterprise Reporter Server Configuring Global Settings

System | Configuration Tips for Customizing the Configuration Manager Views

Global Discovery Settings

Configuring Change History Managing the Collection of Additional Attributes Configuring IT Security Search Configuring a NAS Host Device Configuring Server Error Notification Using the Tenant Application Manager Configuring Email Notifications

Understanding Discoveries

Defining the Data Collection (Discoveries) Best Practices for Creating Discoveries

Creating Discoveries

Step 1. Create the Discovery Step 2. Choose what to include in your discovery (Scopes)

Scopes: An Overview How Scopes Affect Tombstoning Using the Browser to Include and Exclude Scopes Including Objects in Your Scope Importing Computers to Your Scopes Refining Your Scope with Exclusions Filtering in the Browser Using Queries to Define Your Scopes Using Subnets to Define Your Scopes Using Subnet Credentials

Step 2a. Choose scopes for your discoveries

Choosing your Active Directory Scopes

AD Discovery: Include scopes AD Discovery: Optionally refine your scope list with exclusions AD Discovery: Optionally select a domain controller AD Discovery: Decide what to collect from any domain in the discovery

Choosing your Computer Scopes

Computer Discovery: Include scopes Computer Discovery: Optionally refine your scope list with exclusions Computer Discovery: Decide what to collect from any computer in the discovery

Choosing Your Exchange Scopes

Exchange Discovery: Include Scopes Exchange Discovery: Optionally refine your scope list with exclusions Exchange Discovery: Decide what to collect from any server in the discovery

Choosing Your File Storage Analysis Scopes

File Storage Analysis Discovery: Include scopes File Storage Analysis Discovery: Optionally refine your scope list with exclusions File Storage Analysis Discovery: Decide what to collect from any server in the discovery File Storage Analysis Discovery: Configure NAS Host Devices

Choosing Your Microsoft SQL Scopes

MS SQL Discovery: Include scopes MS SQL Discovery: Optionally refine your scope list with exclusions (Scope Exclusions and Global Exclusions)

Choosing Your NTFS Scopes

NTFS Discovery: Best Practices NTFS Discovery: Include scopes NTFS Discovery: Optionally refine your scope list with exclusions NTFS Discovery: Select your global scopes NTFS Discovery: Decide what to collect from any computer in the discovery NTFS Discovery: Configure NAS Host Devices NTFS Discovery: Configure your file collection

Choosing Your Registry Scopes

Registry Discovery: Include scopes Registry Discovery: Optionally refine your scope list with exclusions Registry Discovery: Select your global scopes Registry Discovery: Decide what to collect from any computer

Step 2b: Choose scopes for your Office 365 discoveries

Choosing Your Azure Active Directory Scopes

Azure AD Discovery: Configuring Enterprise Reporter Applications for Azure Azure AD Discovery: Decide what to collect from the tenant in the discovery

Choosing Your Azure Resource Scopes

Azure Resource Discovery: Configuring Enterprise Reporter Applications for Azure Azure Resource Discovery: Include Scopes Azure Resource Discovery: Optionally refine your scope list with exclusions Azure Resource Discovery: Decide what to collect from the subscriptions in the discovery

Choosing Your Exchange Online Scopes

Exchange Online Discovery: Configuring Enterprise Reporter Applications for Azure Exchange Online Discovery: Decide what to collect from the tenant in the discovery

Choosing Your Microsoft Teams Scopes

Microsoft Teams Discovery: Configuring Enterprise Reporter Applications for Azure Microsoft Teams Discovery: Include Scopes Microsoft Teams Discovery: Decide what to collect from the subscriptions in the discovery

Choosing Your OneDrive Scopes

OneDrive Discovery: Configuring Enterprise Reporter Applications for Azure OneDrive Discovery: Include Scopes OneDrive Discovery: Optionally refine your scope list with exclusions OneDrive Discovery: Decide what to collect from the drives in the discovery

Step 3. Schedule your Discovery

Run your discovery once Run your discovery on a daily interval Run your discovery on specified days of the week Run your discovery on a specified day of the month Run Your Schedule Yearly Enabling and Disabling Discovery Schedules

Step 4: Review the summary

Managing Discoveries

How is a Discovery Processed?

Types of Tasks Manually Running a Discovery

Viewing your Discoveries

Navigating the Manage Discoveries Pane Viewing the History of a Discovery What Does the Discovery Status Indicate? Viewing the Tasks for a Finished Discovery Viewing the Tasks for a Processing Discovery What Does the Task Status Indicate? Why is My View Empty? Viewing Errors and Error Suppressions Suppressing Discovery Errors Viewing Statistics Viewing a Cluster's Queue

Working with Discoveries and Tasks

Duplicating a Discovery Modifying a Discovery Canceling a Task or Discovery Deleting a Discovery

Troubleshooting Issues with Enterprise Reporter

Problems Opening the Consoles Troubleshooting Connectivity Issues

Restoring a Connection to the Enterprise Reporter Server Restoring a Connection to the Enterprise Reporter Database

Troubleshooting Connection Timeouts Troubleshooting Credential Change Failures Auditing Enterprise Reporter Activity Resolving Configuration Manager Issues

Node Issues

Node Deployment Issues Dealing with Unassociated Nodes Dealing with Faulted Nodes Problems Deleting a Node Changing the Node Logging Level Changing the Size of the Node Log Files

Scope Enumeration Issues Data Collection Issues

Computer Discovery Errors

Troubleshooting Features in Enterprise Reporter

Exporting Logs from the Configuration Manager Viewing Information About Your Enterprise Reporter Configuration Viewing Errors and Statistics for Tasks

Moving the Enterprise Reporter Database Disaster Recovery

Back Up of Enterprise Reporter How to Deploy Enterprise Reporter to Another Computer After a Disaster Checking the Enterprise Reporter Configuration After a Recovery

Appendix: PowerShell cmdlets

What is Microsoft Windows PowerShell? What are cmdlets? Registering Enterprise Reporter cmdlets Adding the snap-ins automatically to new sessions Enterprise Reporter cmdlets Enabling Enterprise Reporter cmdlets Loading the Enterprise Reporter cmdlets Using cmdlets to manage clusters and nodes

Creating a cluster Creating a node Disabling a node Enabling a node Finding a node by name Piping cmdlets Finding a cluster by name Disabling a cluster Enabling a cluster

Using cmdlets to manage jobs (discoveries)

Getting job information Creating a job Running a job Scheduling a job Deleting a job

Using cmdlets to run reports

Connecting to the server Getting report information Exporting a report definition Generating a report with data

Appendix: Encryption Key Manager

Starting the Encryption Key Manager Generating a Key File Importing a Key File Exporting a Key File Resetting Credentials

Appendix: Log Viewer

Starting the Enterprise Reporter Log Viewer Finding and Opening Log Files Viewing and Searching Log File Entries Filtering Log File Entries

• Viewing Topics 105 - 108 of 233

×

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 .

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 NTFS 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 add a scope using a query, expand the Add to scope menu, select Add scope using a query, and click Add. For more information, see Using Queries to Define Your Scopes .

- 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.

To explicitly include a DFS share (NTFS discoveries only)

1	Click Add.

2	Click Add to Scope | Add DFS share.

3	Type the DFS root path using the fully qualified domain name.

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 .

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.

To explicitly exclude a DFS share (NTFS discoveries only)

1	Click Add.

2	For Add to Scope option, select Add DFS share.

3	Click Add.

4	Type the DFS root path using the fully qualified domain name.

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.

The following table outlines the pre-defined filters available in the global scope selection.

Table 21. Filters in the global scope selection

Filter	Path selected
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

•	Collect specific folders or the contents of specific shares on all computers. If there is a folder that you want to collect on many of the computers, it is more efficient to include it globally. If the folder or share is not on all targets, the inclusion will be ignored for those targets.

•	Exclude common paths, specific folders or the contents of specific shares on all computers. You can 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, NetApp filer, folder or share. See NTFS Discovery: Best Practices for more information.

To add a global scope

1	From the Add Global list, choose the common path.

- OR -

From the Add Global list, choose the common path, then type "\" and a share or folder.

For example, select [WINDOWS] then type \Temp to include or exclude the temp folder on all computers.

- OR -

Type a share or folder.

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.

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.

 

Table 22. NTFS Discovery: How to collect the information from each computer in the discovery

Option	Notes	Performance Cost
Collect all available public shares	The following data is collected: • All folders available through public shares on any computer included in the scope, directly or indirectly • Explicitly added folders • Folders in explicitly added shares, DFS shares, and NetApp filers • All globally included folders • All folders in globally included shares	Medium
• Include hidden shares		High
Collect all available volumes	All folders on any computer resolved from the scope are collected, unless: • they are specifically excluded from the discovery. • specific folders or shares are the only objects included on the computer. In this case, the specified folders or the folders in the specified shares are the only data that will be collected. 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: • both computers and global targets are included in the scope or • explicit shares or folders are included in the scope. 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.

 

Table 23. NTFS Discovery: Optionally collect information for the following objects

Option	Notes	Performance Cost
Folder Options	You have options to choose how deep into the tree the discovery will collect data.
• All folder levels	The default is to collect all folder levels, starting from the included scope.	High
• Folder depth	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.
• Collect files and their basic details like size and attributes		Medium
• Collect advanced file metadata such as author and title	Option available if collecting files and their basic details. Requirement: Microsoft Office must be installed on the Enterprise Reporter node computer.	High
• Calculate duplicate files within the same computer	Option available if collecting files and their basic details.	High
Permission Options
• Collect folder permissions		High
• Collect file permissions	Option available if collecting files and their basic details.	High
• Only collect and store files which have explicitly granted permissions	Selecting this option reduces the high performance cost of collecting all file permissions
• Calculate permission differences between folders and subfolders (and files)	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
• If a group account is found when collecting permissions, recursively collect group members.	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
• Create a task per share for each computer	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.

 

Table 24. NTFS Discovery: Performance Options

Performance Option	Notes
Folder Options	You have options to choose how deep into the tree the discovery will collect data.
• All folder levels	The default is to collect all folder levels, starting from the included scope.
• Folder depth	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
• Only collect and store files which have explicitly granted permissions	Selecting this option reduces the high performance cost of collecting all file permissions.
Advanced Options
• Create a task per share for each computer	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.

 

Table 25. 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.

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

•  Previous
• Viewing Topics 105 - 108 of 233
• Next 

Search this document Search all documents for this product-version Search all documents for this product Search all documents

×

 Welcome to Quest Support

You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center