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

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

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

Managing Nodes

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

• Viewing Topics 25 - 28 of 249

×

Server Service Credentials

Server service credentials are provided during the installation of the server. The following table outlines the use of the service account credentials, and how to properly configure your environment to ensure successful data collection:

 

Table 12. Server Service Credentials in Configuration Manager

From	To	Permission Details	Configuration
Enterprise Reporter Server	Enterprise Reporter Database	Must be in the local administrators group for the service to start properly. Must be able to read and write to the database. If the server is configured to use SQL authentication, the SQL credentials will be used to access the database, not the service account.	Configured automatically during installation. If you change the service credentials for the Quest Enterprise Reporter Server service, you need to ensure that a SQL login exists for that account, and create one if none exists. The login must be added to the database roles. For more information, see Configuring the Database and Security Groups in the Installation and Deployment Guide in the Technical Documentation. For more information, see Configuring the Database and Security Groups.
Enterprise Reporter Server	Discovery Node	Must be in the local administrators group for the server service to fully function. Must be in the group Reporter_Discovery_Nodes for the service to fully function. Must be able to write to the Admin$ share to deploy the node. Controls the actions of the node.	On the node host, grant the service account local administrator rights.

Changing the credentials used by the Enterprise Reporter Server

The credentials used to run the Quest Enterprise Reporter server service on the host computer are not stored in the Credential Manager. To change these credentials—either to a different account or to update the password—perform the following steps:

1	Open the Configuration Manager.

2	Stop any currently running discoveries. It is important to wait until all discoveries have finished cancelling to ensure data integrity.

For more information, see Canceling a Task or Discovery .

3	Disable all nodes in each cluster.

For more information, see Why Disable a Node? .

CAUTION: At this point, you may want to inform your reporting users that they will lose connection to the Enterprise Reporter server and they may lose work if they have not saved their latest changes.

4	Close the Configuration Manager.

5	On the computer that hosts the server, use the Services console to stop the service.

6	Modify the properties of the Quest Enterprise Reporter Server service to use the new credentials. See your Microsoft documentation for details.

7	Restart the service.

8	Open the Enterprise Reporter Encryption Key Manager and import the encryption key from the backup file. You must provide the user-supplied password that was used to create the backup file.

For more information, see Importing a key file .

9	Open the Configuration Manager and enable the nodes.

For more information, see Enabling a Node .

10	Restart any discoveries you canceled.

For more information, see Manually Running a Discovery .

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

The credentials used to run the Quest Enterprise Reporter server service on the host computer are not stored in the Credential Manager. To change the account to either UPN (userPrincipalName) or SPN (servicePrincipalName) required by Kerberos perform the following steps.

NOTE: The following instructions apply to both the ReporterServer.exe.config and ConfigurationManager.exe.config files.

To change the account to either UPN or SPN required by Kerberos:

1	Locate and edit the relevant config file; C:\Program Files\Quest\Enterprise Reporter\ConfigurationManager for the ConfigurationManager.exe.config file and C:\Program Files\Quest\Enterprise Reporter\ReportManager for the ReporterServer.exe.config file.

2	Locate the identity element under the <system.serviceModel><Client><endpoint> elements.

3	Enter the UPN or SPN required by Kerberos, by replacing the empty string value.

For example:

<system.serviceModel>

<client>

<endpoint address="net.tcp://localhost:7738/Quest.Reporter.Core.Server.Host/StartupManager" behaviorConfiguration="ClientBehavior" binding="netTcpBinding" bindingConfiguration="NetTCPPortSharing" contract="StartupManagerService.IStartupManager" name="NetTcpBinding_IStartupManager">

<identity>

<userPrincipalName value="erserverserviceaccountuser@Domain(FQDN)" />

</identity>

</endpoint>

or

<system.serviceModel>

<client>

<endpoint address="net.tcp://localhost:7738/Quest.Reporter.Core.Server.Host/StartupManager" behaviorConfiguration="ClientBehavior" binding="netTcpBinding" bindingConfiguration="NetTCPPortSharing" contract="StartupManagerService.IStartupManager" name="NetTcpBinding_IStartupManager">

<identity>

<servicePrincipalName value="net.tcp/ERSVR.your-domain:your-port" />

</identity>

</endpoint>

4	Update all endpoint identities (21 total) in the configuration file with either UPN or SPN from

<endpoint address="net.tcp://localhost:7738/Quest.Reporter.Core.Server.Host/StartupManager"

down to and including:

<endpoint address="net.tcp://localhost:7738/Quest.Reporter.Core.Server.Host/FileTransferManager"

5	Save the file.

6	Stop and re-start the services.

Using the Credential Manager

Credentials are used in different places in Enterprise Reporter. For example, nodes and report schedules both use credentials. The Credential Manager is a central store for accounts and passwords used throughout the system. This makes it easy to keep passwords current, and allows you to enter the credential details once and access them repeatedly.

 

NOTE: Cloud discoveries now support multi-factor authentication. The Microsoft 365 discovery credentials must be authenticated by Microsoft through the Credential Manager. NOTE: Credentials added in the Report Manager are only available to the user who added them while accounts added in the Configuration Manager are available to all Configuration Manager users on the same Enterprise Reporter server.

Accounts are not verified when you add them and they must already exist to be used by Enterprise Reporter. For each account, you can add a description. This is useful for differentiating between similar accounts, such as similarly named service credentials, or your SQL Server default "sa" accounts. The combination of the account name and the description must be unique.

Accounts with multi-factor authentication enabled must be authenticated by Microsoft through the Credential Manager.

Credential passwords are encrypted with FIPS 140-2 compliant algorithms and an encryption key that has a user-supplied password. The encryption key is secured in the Windows Credential Manager (not to be confused with the Enterprise Reporter Credential Manager). The encryption key is used to encrypt all passwords that are used in Enterprise Reporter for collections and reporting. Additionally, Enterprise Reporter security groups and roles are used to validate who has access to the encryption key and the key cannot be retrieved without proper authorizations.

The Credential Manager will display a red key icon beside each account that requires a password.

See also:

•	Changing Passwords Using the Credential Manager

•	Changing Account Names Using the Credential Manager

To open the Credential Manager

•	On the Configuration page, go to Credential Manager and click Manage credentials.

- OR -

Click the ellipsis anywhere credentials are required.

To use a credential from the Credential Manager

1	Select the account from the list.

2

Click OK.

To add a credential for use in the system

1	Open the Credential Manager.

2	Click Add.

3	Type the account name.

You can enter any account that you want to use in Enterprise Reporter, including Windows accounts, SQL Server accounts, and Microsoft Entra accounts.

 

NOTE: If you are entering credentials in the Configuration Manager, remember that other users may have entered the same credential, so if necessary, verify that you are adding a unique account.

If this is an Microsoft Entra-enabled account, select the Microsoft Entra Credential option. Once selected, click Authenticate to login and authenticate the account through Microsoft.

4	Type the password for the account.

5	Optionally, type a description.

The combination of the account name and the description must be unique.

6

Click OK.

To add a multi-factor authenticated credential

1	Open the Credential Manager.

2	Click Add.

3	Enter the account user name and password.

 

NOTE:   • The combination of the account name and the description must be unique. • For a multi-factor authenticated Microsoft Entra credential, ensure to select the Microsoft Entra Credential option. Once selected the credential will be authenticated through Microsoft.

4	Optionally, enter a description.

5	Click Authenticate.

6	On the Microsoft Entra authentication screen, enter the account name.

7	Click Next.

 

NOTE: When entering credentials in the Configuration Manager, verify that no other users have used the same credential and that the account you are adding is unique.

8	Enter the password for the account.

9	Click Sign In.

10	Enter the verification code sent to the account.

11	Click Verify.

The Credential Manager authenticates the account for discovery usage and changes the account information on any applicable discoveries.

A progress dialog box appears.

 

NOTE: The Credential Manager displays a Last Authenticated On date, which indicates when the credential was authenticated through the Microsoft authentication process as a multi-factor authenticated credential. If there is no date, then the credential was not authenticated.

12	Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.

When you change the password for a Microsoft Entra account, any Enterprise Reporter tenant applications that use that account must also be reconfigured. For more information, see To reconfigure application for a tenant .

 

To edit a credential

1	Open the Credential Manager.

2	Select an account.

3	Click Edit.

4	Optionally, modify the password by selecting Edit Password.

5	Make all changes.

6

Click OK.

7	When you change the password for a Microsoft Entra account, any Enterprise Reporter tenant applications that use that account must also be reconfigured. For more information, see To reconfigure application for a tenant .

To edit a multi-factor authenticated credential

1	Open the Credential Manager.

2	Select an account.

3	Click Edit.

4	Modify the account.

5	Click Authenticate.

6	On the Microsoft Entra authentication screen, enter the account name.

7	Click Next.

 

NOTE: When entering credentials in the Configuration Manager, verify that no other users have used the same credential and that the account you are adding is unique.

8	Enter the password for the account.

9	Click Sign In.

10	Enter the verification code sent to the account.

11	Click Verify.

The Credential Manager authenticates the account for discovery usage and changes the account information on any applicable discoveries.

A progress dialog box appears.

 

NOTE: The Credential Manager displays a Last Authenticated On date, which indicates when the credential was authenticated through the Microsoft authentication process as a multi-factor authenticated credential. If there is no date, then the credential was not authenticated.

12	Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.

When you change the password for a Microsoft Entra account, any Enterprise Reporter tenant applications that use that account must also be reconfigured. For more information, see To reconfigure application for a tenant .

 

To alter an account to be multi-factor authentication enabled

1	Open the Credential Manager.

2	Select the account to authenticate.

3	Click Authenticate.

4	On the Microsoft Entra authentication screen, enter the account name.

5	Click Next.

 

NOTE: When entering credentials in the Configuration Manager, verify that no other users have used the same credential and that the account you are adding is unique.

6	Enter the password for the account.

7	Click Sign In.

8	Enter the verification code sent to the account.

9	Click Verify.

The Credential Manager authenticates the account for discovery usage and changes the account information on any applicable discoveries.

A progress dialog box appears.

 

NOTE: The Credential Manager displays a Last Authenticated On date, which indicates when the credential was authenticated through the Microsoft authentication process as a multi-factor authenticated credential. If there is no date, then the credential was not authenticated.

10	Verify that your changes were processed. If any errors occur, you must troubleshoot the issue and manually make any changes.

When you change the password for a Microsoft Entra account, any Enterprise Reporter tenant applications that use that account must also be reconfigured. For more information, see To reconfigure application for a tenant .

 

To delete a credential

1	Open the Credential Manager.

2	Select an account from the list.

You can only delete accounts that are not currently in use.

3	Click Delete.

4

Click OK.

•  Previous
• Viewing Topics 25 - 28 of 249
• 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. Terms of Use Privacy Cookie Preference Center