Chat now with support
Chat mit Support

Enterprise Reporter 3.5.1 - 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

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.

To change the account
1
On the Configuration page, click Manage credentials.
It is recommended that you make these changes while no discoveries are running or waiting to be run before changing the account
2
Select the account, and click Edit.
3
Modify the account and click OK.
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.
4
Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.
When changing the password on an Microsoft 365 Azure account, any Enterprise Reporter tenant applications using that account must also be reconfigured. For more information, see To reconfigure application for a tenant .
 
To change the multi-factor authenticated account
1
On the Configuration page, click Manage credentials.
It is recommended that you make these changes while no discoveries are running or waiting to be run before changing the account.
2
Select the account and click Edit.
3
Modify the account.
4
Click Authenticate.
5
On the Microsoft Azure authentication screen, if the account has multi-factor authentication enabled, type the account name and password.
 
* 
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
Click Sign In.
7
Enter the verification code sent to the account.
8
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.
9
Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.
When changing the password on an Microsoft 365 Azure account, any Enterprise Reporter tenant applications using that account must also be reconfigured. For more information, see To reconfigure application for a tenant .
 

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
•
Things to Consider Before Creating a Cluster
•
Creating Your First Cluster and Node

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.

Figure 4. A typical enterprise deployment of Enterprise Reporter
* 
TIP: To maximize performance, and minimize network traffic, clusters should be physically close to the computers hosting the data you are collecting.
* 
NOTE: To collect data, you need to create a cluster — even if you are only planning to use a single computer to perform the collections.

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.

•
If you are using one, where is the shared data location?
Create the shared folder, and give read and write access to the credentials you will be using for the nodes. As long as it is accessible, the shared data location can be located on any computer in your environment. Be cautious and ensure that the location is secured while it is accessible as it contains temporary files of collected data. For maximum benefit, locate the data source physically close to the nodes in the cluster.
* 
NOTE: Not all discovery types utilize the shared data location. For example, Active Directory, For example, Active Directory, Azure Active Directory, Exchange, and NTFS discoveries do not use the shared data location to optimize on the number of collection tasks generated to collect the data in a more efficient manner.
•
What are the first nodes that you want to add?
A cluster is not functional until you add a node and enable it. The node computer is the computer that will resolve the targets of the collection, and perform the actual collection. You can add as many nodes as you want during the initial creation of a cluster.
•
How many tasks do you want to run at the same time on each node?
Discoveries are executed as tasks on the nodes of the assigned cluster. To maximize the performance of a node, you can limit the number of tasks that can run concurrently. The default setting of zero to allow the node to determine how many concurrent tasks it will process is a good place to start; you can later experiment with limiting this number to improve performance. For more information, see Improving the Performance of a Node .
•
What credentials are you going to use?
Discoveries are performed by a service that runs on the node computer. The credentials used by the node must have read and write access to the Enterprise Reporter database, and have the read permissions to access the targets, and collect the necessary data, and permission to write to the shared data location. You can optionally choose to use SQL credentials for the database connection. For more information, see Node Credential and Alternate Credential Details for On-Premises Discoveries .
* 
NOTE: If you use credentials that are different than the Enterprise Reporter server credentials, they must be granted access to the database.

For more information, see “Configuring the Database and Security Groups” in the Installation and Deployment Guide.

* 
NOTE: These credentials are also used to access the target computers during a discovery, unless alternate credentials are specified for a discovery. For more information, see Step 1. Create the Discovery (Name) .
 
•
Access to Admin$ on the node host
To ensure the success of node deployment, the node installation files are copied into Admin$ (\\computername\admin$). The service account must have read and write access to this share. Once the node has been successfully installed, you can remove this access if required.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen