Converse agora com nosso suporte
Chat com o suporte

Enterprise Reporter 3.5.2 - 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 Passwords Using the Credential Manager

When passwords are changed in Active Directory and Microsoft Entra ID, they must be updated everywhere they are in use in Enterprise Reporter. It is possible that the account could be locked if you do not make this change. The Credential Manager makes this easy by providing a central store for accounts. You can change the password and it is updated in all nodes, schedules, discoveries, and so on.

* 
NOTE: You can modify credentials from anywhere you can access the Credential Manager. Be aware when you make a change to a credential, it is applied throughout your deployment, not just in your current context.

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.

Credential passwords are encrypted with FIPS 140-2 compliant algorithms and an encryption key that has a user-supplied password. For further information on creation and management of the Enterprise Reporter encryption key, see Appendix: Encryption Key Manager .

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

To change the password on an 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 password.
2
Select the account, and click Edit.
3
Select Edit Password.
4
Modify the password 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.
5
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 a Microsoft Entra 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 password on a 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 password.
2
Select the account and click Edit.
3
Select Edit Password.
4
Modify the password.
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 changing the password on an Microsoft Entra account, any Enterprise Reporter tenant applications using that account must also be reconfigured. For more information, see To reconfigure application for a tenant .
 

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 Entra 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 Entra 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 a Microsoft Entra 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.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação