Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding Answers and Getting Help An Overview of Enterprise Reporter Communications and Credentials Required Logged In User Details Setting Up Your First Collection Computers Modifying your Deployment Improving the Performance of Your Discoveries What does the status of a node or cluster indicate? Using the Credential Manager Changing the Credentials used by the Enterprise Reporter Server Configuring Global Settings Global Discovery Settings
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your 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 Office 365 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

Logged In User Details

The following table outlines the use of the logged in user credentials, and how to properly configure your environment to ensure successful data collection:

 

Configuration Manager

Enterprise Reporter Server

Must be a member of the Reporter_Discovery_Admins group in order to log in to the console.

Configuration Manager will send configuration and set up requests to the server.

Configuration is dependent on your deployment’s security group setup. See the System | Information page to determine the type of security in place.
For more information, see Configuring the Database and Security Groups in the Quest Enterprise Reporter Installation and Deployment Guide in the Technical Documentation. 

For more information, see Configuring the Database and Security Groups.

Configuration Manager

Targets

Must be able to enumerate the targets during scope selection, unless alternate credentials are provided for the discovery.

All domains with which the credentials have a forest or domain level trust will be enumerated.

On each target, grant the user read access.

See also:

Server Service Credential Details

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:

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 Quest Enterprise Reporter 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.

Setting Up Your First Collection Computers

Before you can collect and report on data, you must set up the computers that will perform the collections. The minimum deployment is a single cluster with a single node, with the node residing on the same computer as the Enterprise Reporter server.

See also:

Configuring Clusters and Nodes for Effective Data Collection

A cluster is a logical grouping of the physical computers (nodes) that will be collecting the data. Each physical computer in a cluster is a node, and each node may belong to only one cluster. You will be assigning collection jobs to a cluster, and the collection tasks are then spread across the nodes. To help make collections more scalable, all of the computers in the cluster share a data store, where the results of a data collection are stored. Clusters provide scalability and performance benefits—you can have as few or as many clusters as your network demands.

Figure 4 outlines a three cluster implementation of Enterprise Reporter. The server and database are located in New York, with clusters in three other cities. Each cluster contains 3 nodes.

Documents connexes