Chat now with support
Chat with 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

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.

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

Click Configuration.
Click Manage database settings.
Click Manage Discovery Clusters.
Click the Cluster Details tab.

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:

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.

The following information is provided in the event log.

User Login (successful)


User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ConfigurationManager

Create Discovery


User <USERNAME> on machine <MACHINENAME> created discovery '<DISCOVERYNAME>' (<DISCOVERYID>)

Run Discovery (manual)


User <USERNAME> on machine <MACHINENAME> ran discovery '<DISCOVERYNAME>' (<DISCOVERYID>)

Modify Discovery


User <USERNAME> on machine <MACHINENAME> modified discovery '<DISCOVERYNAME>' (<DISCOVERYID>)

Delete Discovery


User <USERNAME> on machine <MACHINENAME> deleted discovery '<DISCOVERYNAME>' (<DISCOVERYID>)

Create Cluster


User <USERNAME> on machine <MACHINENAME> created cluster '<CLUSTERNAME>' (<CLUSTERID>)

Modify Cluster


User <USERNAME> on machine <MACHINENAME> modified cluster '<CLUSTERNAME>' (<CLUSTERID>)

Delete Cluster


User <USERNAME> on machine <MACHINENAME> deleted cluster '<CLUSTERNAME>' (<CLUSTERID>)

Enable Cluster


User <USERNAME> on machine <MACHINENAME> enabled cluster '<CLUSTERNAME>' (<CLUSTERID>)

Disable Cluster


User <USERNAME> on machine <MACHINENAME> disabled cluster '<CLUSTERNAME>' (<CLUSTERID>)

Add Node To Cluster


User <USERNAME> on machine <MACHINENAME> added node <NODENAME> (<NODEID>) to cluster '<CLUSTERNAME>' (<CLUSTERID>)

Remove Node From Cluster


User <USERNAME> on machine <MACHINENAME> removed node <NODENAME> (<NODEID>) from cluster '<CLUSTERNAME>' (<CLUSTERID>)

Enable Node


User <USERNAME> on machine <MACHINENAME> enabled node <NODENAME> (<NODEID>) on cluster '<CLUSTERNAME>' (<CLUSTERID>)

Disable Node


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


User Login (successful)


User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ReportManager

Create Report


User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)

Run Report (manual)


User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)

Modify Report


User <USERNAME> on machine <MACHINENAME> modified report '<REPORTNAME>' (<REPORTID>)

Delete Report


User <USERNAME> on machine <MACHINENAME> deleted report '<REPORTNAME>' (<REPORTID>)


Security Audit Operation


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

Operations that may be performed are:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating