Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Enterprise Reporter 3.5.2 - Configuration Manager User Guide

Table of Contents

Product Overview

Key Features of Enterprise Reporter Components of Enterprise Reporter

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 SQL Server Reporting Services (SSRS)

Summarizing the Workflow

Configuring the Configuration Manager

Starting the Configuration Manager Finding answers and getting help 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 Credentials Server Service Credentials

Changing the credentials used by the Enterprise Reporter Server Changing the credentials used by the Enterprise Reporter Server in a Kerberos environment

Using the Credential Manager

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

Setting Up Your First Collection Computers (Nodes)

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

Modifying Your Deployment

Managing Clusters

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

Modifying Node Credentials Modifying the Location of Node Temporary Files Changing a Node to a Different Cluster Removing a Node Why Disable a Node? Stopping a Node Enabling a Node Starting a Node

What does the status of a node or cluster indicate?

Configuring Global Settings

Configuring Change History Configure Logging Credential Manager Database Settings Configuring Email Notifications Registering an Application for Exchange Online Email Delivery

Registering and configuring an application through the Microsoft Azure portal

Managing the Collection of Additional Attributes Configuring IT Security Search Configuring a NAS Host Device Configuring Server Error Notification Managing Tenant Applications Managing Certificates for Tenant Applications Creating Your Own Certificate for Discovery Authentication Managing the Logon Configuration

Customizing the Configuration Manager View

Understanding Discoveries

Defining the Data Collection (Discoveries) Multi-Factor Authentication Discovery Credential Limitations Best Practices for Creating Discoveries Improving the Performance of Your Discoveries

Adding a Node Improving the Performance of a Node

Discovery Permission Requirements

Detailed permissions for Enterprise Reporter discoveries Permissions for Enterprise Reporter discoveries on NAS devices Permissions for Enterprise Reporter tenant applications CM Understanding Discoveries.04.12.html

Creating Discoveries

Step 1. Create the Discovery (Name)

Configuring Tenant Applications for Cloud Discoveries

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 on-premises discoveries

Choosing your Active Directory Scopes

AD Discovery: Include scopes AD Discovery: Optionally refine your scope list with exclusions AD Discovery: Optionally select one or more domain controllers 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: Optionally select a domain controller 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 cloud discoveries

Choosing Your Microsoft Entra ID Scopes

Microsoft Entra ID Discovery: Decide what to collect from the tenant in the discovery

Choosing Your Azure Resource Scopes

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: Decide what to collect from the tenant in the discovery

Choosing Your Microsoft Teams Scopes

Microsoft Teams Discovery: Include Scopes Microsoft Teams Discovery: Decide what to collect from the subscriptions in the discovery

Choosing Your OneDrive Scopes

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

Choosing Your SharePoint Online Scopes

SharePoint Online Discovery: Include Scopes SharePoint Online Discovery: Optionally refine your scope list with exclusions SharePoint Online Discovery: Decide what to collect from the tenant 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 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

Backing up Enterprise Reporter Deploying Enterprise Reporter to another computer after a disaster Checking the Enterprise Reporter configuration after 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 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 Importing a report definition to a category 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

Restoring a connection to the Enterprise Reporter database

If your server has lost its connection to the database, you can still open a console and connect to the server, but functionality will be limited. You will be unable to create discoveries, run reports or modify your configuration. Ensure that the SQL Server hosting the Enterprise Reporter database is running, and that the server can access it.

The Report Manager maintains a direct connection to the SQL Server database, so ensure that the console’s computer can also access the SQL Server.

Troubleshooting Connection Timeouts

As Enterprise Reporter processes your requests, constant communication with the database is required. Depending on your network configuration, your Enterprise Reporter deployment, and the power of your SQL Server host, the solution for timeout issues may vary.

You can fix timeout issues by either increasing the timeout in Enterprise Reporter, or by investigating any systemic or deployment issues. For example, perhaps your SQL Server where the database is hosted is underpowered, or you have located your Enterprise Reporter server physically distant from your SQL Server.

There are the following settings for each timeout configuration:

•

Connection timeout
This is the amount of time given to make the initial connection to the database each time communication is needed. This is less likely to need adjustment. Timeouts are more likely due to SQL Server® or network issues than Enterprise Reporter specific problems. However, if you continually are seeing timeout errors, try increasing this setting.

•

Command timeout
This is the amount of time allowed for the database to process requests. If you are getting timeout error messages during data collection, increase this setting.

There are two types of database timeout settings in the Configuration Manager:

•

Enterprise Reporter Server timeout
You can increase the timeout between the Enterprise Reporter server and the database. If a timeout occurs, you will see a warning dialog box, indicating that this has occurred.

•

Cluster timeout
You can increase the timeout between the nodes in the cluster and the database. This is useful when a collection fails due to a timeout, which is indicated by an error on the discovery task. For information on viewing the error, see Viewing Errors and Error Suppressions . For information on changing the cluster timeout, see Modifying a Cluster .

To change the database timeout settings for the Enterprise Reporter Server

1

Click Configuration.

2

Click Manage database settings.

3

To change the time allowed to establish a connection, modify the Connection Timeout.

4

To change the time allowed to process a database command, modify the Command Timeout.

To change the database timeout settings for a specific cluster

1

Click Manage Discovery Clusters.

2

Select the cluster to update.

3

Click the Cluster Details tab.

4

To change the time allowed to establish a connection, modify the Connection Timeout.

5

To change the time allowed to process a database command, modify the Command Timeout.

Troubleshooting credential change failures

Each credential in the Credential Manager has three parts—an account name, a password, and an optional description—you can change any of them. While most changes are processed smoothly, occasionally issues in the network environment may prevent changes from being applied. When a change fails, you must determine the reason, and manually make the changes.

If you have to manually change a credential on a node, you should ensure that there are no discoveries running or queued before making the change. Change the credentials using the Services console on the host computer, then restart the service. Verify that the node started in the bottom pane of the Manage Discovery Clusters page. Restart any discoveries you canceled.

Once you have changed credentials, review the following:

•

If a node fails to start, ensure the credentials have local administrator access on the node host computer, and check that the credentials you provided are valid.

•

If a discovery fails, ensure that the new credentials have read access on the targets of any discovery. Check the discovery to see if it using the default node credentials or if credentials are specified. Ensure that the credentials you provided are valid.

•

If an cloud discovery fails, (indicating that the tenant cannot be null), ensure that the related tenant application has been reconfigured. For more information, see Configuring Tenant Applications for Cloud Discoveries .

Auditing Enterprise Reporter Activity

User activity from the Configuration Manager, the Reporter Manager console, and Encryption is stored in the Quest Enterprise Reporter Windows Event Log on the machine for the Enterprise Reporter Server. Using this information, you can audit the following user activity for compliance purposes.

Configuration Manager Event Log

The following information is provided in the event log.

Table 55. Configuration Manager Activity in the event log
Event	Event ID	Event Format
User Login (successful)	2000	User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ConfigurationManager
Create Discovery	2002	User <USERNAME> on machine <MACHINENAME> created discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Run Discovery (manual)	2003	User <USERNAME> on machine <MACHINENAME> ran discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Modify Discovery	2004	User <USERNAME> on machine <MACHINENAME> modified discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Delete Discovery	2005	User <USERNAME> on machine <MACHINENAME> deleted discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Create Cluster	2006	User <USERNAME> on machine <MACHINENAME> created cluster '<CLUSTERNAME>' (<CLUSTERID>)
Modify Cluster	2007	User <USERNAME> on machine <MACHINENAME> modified cluster '<CLUSTERNAME>' (<CLUSTERID>)
Delete Cluster	2008	User <USERNAME> on machine <MACHINENAME> deleted cluster '<CLUSTERNAME>' (<CLUSTERID>)
Enable Cluster	2009	User <USERNAME> on machine <MACHINENAME> enabled cluster '<CLUSTERNAME>' (<CLUSTERID>)
Disable Cluster	2010	User <USERNAME> on machine <MACHINENAME> disabled cluster '<CLUSTERNAME>' (<CLUSTERID>)
Add Node To Cluster	2011	User <USERNAME> on machine <MACHINENAME> added node <NODENAME> (<NODEID>) to cluster '<CLUSTERNAME>' (<CLUSTERID>)
Remove Node From Cluster	2012	User <USERNAME> on machine <MACHINENAME> removed node <NODENAME> (<NODEID>) from cluster '<CLUSTERNAME>' (<CLUSTERID>)
Enable Node	2013	User <USERNAME> on machine <MACHINENAME> enabled node <NODENAME> (<NODEID>) on cluster '<CLUSTERNAME>' (<CLUSTERID>)
Disable Node	2014	User <USERNAME> on machine <MACHINENAME> disabled node <NODENAME> (<NODEID>) on cluster '<CLUSTERNAME>' (<CLUSTERID>).

You can interrogate the event log directly for object user activity information. As shown in Table 55, each event is logged with the fully qualified user name of the Enterprise Reporter user who performed the event and the machine name where the event occurred.

Report Manager Event Log

Table 56. Report Manager Activity in the event log
Event	Event ID	Event Format
User Login (successful)	2000	User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ReportManager
Create Report	2015	User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)
Run Report (manual)	2016	User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)
Modify Report	2017	User <USERNAME> on machine <MACHINENAME> modified report '<REPORTNAME>' (<REPORTID>)
Delete Report	2018	User <USERNAME> on machine <MACHINENAME> deleted report '<REPORTNAME>' (<REPORTID>)

Encryption Event Log

Table 57. Encryption Activity in the event log

Security Audit Operation

User <USERNAME> on machine <MACHINENAME> with IP <IPADDRESS> performed <OPERATIONNAME> operation using service contract <SERVICECONTRACTNAME>.

Operations that may be performed are:

•

IsUserInRole - checks the role of the calling user

•

GETIvKey - returns Enterprise Reporter encryption IV key

•

ImportIvKey - sets a new security key

•

GenerateIvKey - generates and sets a new IV key

•

CheckOrUpgradeKey - check the status of the security key and performs an upgrade if possible

•

ResetAllPasswords - resets all passwords

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center