Tchater maintenant avec le support

Obtenir une aide instantanée
Terminer l’enregistrement

Se connecter

Demander les tarifs

Contacter le service des ventes

Enterprise Reporter 3.2.2 - Installation and Deployment Guide

Parcourir le contenu

Product Overview

Introducing Quest™ Enterprise Reporter Key Features of Enterprise Reporter Enterprise Reporter Components

Enterprise Reporter Architecture

Installation Considerations for Enterprise Reporter

Before You Install Enterprise Reporter Reporter Server and Database Considerations

Failover Recovery using SQL Clusters

System Requirements 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 Minimum Permissions for Initially Installing Enterprise Reporter Port Requirements Firewall Requirements

Database Requirements

Configuring the Database and Security Groups

Installing and Configuring Enterprise Reporter

Installing Enterprise Reporter

Installing the Components

Installing and Configuring Individual Components

Installing and Configuring the Configuration Manager Installing and Configuring the Report Manager Installing and Configuring the Database Wizard Installing and Configuring the Log Viewer Installing and Configuring the Encryption Key Manager Creating a Database Prior to Enterprise Reporter Server Installation Installing and Configuring IT Security Search

Upgrading Enterprise Reporter

Preparing to Upgrade Enterprise Reporter Upgrading Enterprise Reporter Components Upgrading Enterprise Reporter Nodes Upgrading Manually-Configured Enterprise Reporter Nodes After Upgrading Enterprise Reporter

Licensing Enterprise Reporter

Activating or Updating Your License

Security Groups in Enterprise Reporter Role Based Security in Enterprise Reporter Managing Your Database Using the Database Wizard

Using the Database Wizard to Create or Connect a Database Upgrading a Database Deleting a Database Changing the Security Mode Changing the Connection to the Enterprise Reporter Database Performing Database Maintenance

Managing Your Enterprise Reporter Deployment

Optimizing Enterprise Reporter Enterprise Reporter Server and Database Considerations

Failover Recovery using SQL Clusters

Cluster Deployment Considerations

Consider the Data to Collect Before Deploying Nodes Fine Tune Each Cluster and Node Optimize Node Setup Plan Credential Use

Logged In User Details Understanding Credentials Using Scenarios

Effectively Deploy Remote Nodes

Deploying a Node to a Trusted Domain

Optimize Data Transfer

Discovery Considerations

Divide Discovery Targets According to Cluster Structure Collect Only the Data Needed Plan Discovery and Reporting Schedules Optimize Nested Group Membership Collection Optimize Nested Group Membership Collection for Azure and Office 365 Discoveries

Troubleshooting Issues with Enterprise Reporter

Troubleshooting Installation Issues

Connecting to a SQL Server® Issues with Multi-Domain Controller Environments

Problems Opening the Consoles Database Configuration Issues 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 Resolving Issues in the Configuration Manager

Node Deployment Issues Dealing with Unassociated Nodes Problems Deleting a Node Creating a Node Debug Log File

Data Collection Issues

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: Database Content Wizard

Software Requirements Starting and Configuring the Enterprise Reporter Database Content Wizard Transferring an Enterprise Reporter Database Backing Up an Enterprise Reporter Database Restoring an Enterprise Reporter Database Cleaning an Enterprise Reporter Database Merging Two Enterprise Reporter Databases Running Custom Enterprise Reporter Scripts

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

Problems Opening the Consoles

Database Configuration Issues

Troubleshooting Connectivity Issues

Each console maintains connections to the Enterprise Reporter server and to the SQL Server® database that stores Enterprise Reporter data. A loss of either connection causes problems. Figure 12 outlines the connections between the components and the server and database.

Figure 12. Connections between components and the server and database.

Topics:

•

Restoring a Connection to the Enterprise Reporter Server

•

Restoring a Connection to the Enterprise Reporter Database

Restoring a Connection to the Enterprise Reporter Server

There are a number of reasons why a Enterprise Reporter server may be down. When a console loses its connection to the server, it becomes unusable and must be restarted. All users connected to the Enterprise Reporter server are affected. You should check the following connections:

•

Ensure that the computer hosting the server is turned on and running properly.

•

Ensure that the Enterprise Reporter server service is running. If necessary, restart it using the Services console.

•

Ensure that you can reach the host computer over your network.

•

Ensure that the server host computer meets the minimum system requirements.

If the server has gone down and been restored since you last logged in, then the next time you connect, you will be informed that the server went down. If you are the main Enterprise Reporter administrator, this allows you to be aware that your server has had issues. Intermittent failures over time may be due to instability in your network, problems on the server’s host computer, or your SQL Server® deployment.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation

© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center