Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

Changing Account Names Using the Credential Manager

In general, if you want to change an account name, it is recommended that you create a new credential, and delete the old one. However, in the case where you want to replace the credentials in use in a number of places in Enterprise Reporter, the Credential Manager enables you to make a single change and have it be applied across your deployment. For example, if you are provided a new service credential to replace a credential used for a dozen nodes in your environment, you can change the account name on the credential.

If you modify credentials that are used by a discovery node, the node service must be restarted before the changes take effect. Enterprise Reporter will attempt to restart the node. However, if the restart fails, you may need to manually start the service on the computer that hosts the node. If there are jobs currently running on the node, they will be cancelled. To prevent this, either change the credentials during a down time, or cancel the discoveries yourself and restart them once the change takes effect.

Click Authenticate.
Click Sign In.
Click Verify.

Setting Up Your First Collection Computers (Nodes)

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.

Things to Consider Before Creating a Cluster

Make sure you are clear on the following before creating the cluster:

Do you want to use a shared data location?

As data is collected, it is compared to previously collected data on either the SQL Server® or the shared data location, depending on how you configure your cluster. If you have a lightly loaded SQL Server® that is physically close to your nodes, you may find that performance is improved by choosing not to use a shared data location. On the other hand, if network traffic is high and your SQL Server® is under a heavy load or physically distant from the nodes in the cluster, a shared data location will produce faster results.

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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation