Chat now with support
Chat mit 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

What does the status of a node or cluster indicate?

As you deploy, enable and disable nodes and clusters, the Configuration Manager gives you feedback. This feedback is visible in the Status column of the Manage Discovery Clusters pane. By default, clusters and nodes are grouped and sorted by Status.

The following table outlines each status of a cluster:

Disabled

The cluster is disabled and no new jobs will be processed. Any jobs currently running when the node was disabled will continue to process until they either complete or are canceled by the user.

Enabled

The cluster has at least one enabled node and is available to process jobs.

The following table outlines each status of a node:

Deploying

The node is currently being installed on the node computer.

Deployment Failed

The node could not be successfully deployed. For information on troubleshooting, see Node Issues .

Enabled

The node is online and available to process jobs.

Disabled

The node is disabled and no new jobs will be processed. If you attempt to disable a node while it is actively processing a task, you will be prompted to either cancel it or wait to disable the node until the task has completed.

Failed to Start

The node is still stopped, as the server was unable to start it.

Failed to Stop

The node is still running, as the server was unable to stop it. It will not accept new tasks from the server.

Faulted

The nodes regularly communicate with the server to confirm their health. A faulted node has not had contact within an acceptable time frame.

Incompatible Version

The node is not the same version of the software as the Enterprise Reporter server to which it is connecting.

Initializing

The node service is currently being configured, and required components are being downloaded to the node.

Removal Failed

The node service could not be deployed (or undeployed) successfully from the node computer.

Starting

The node service is in the process of starting up.

Stopped

The node service has been stopped. It is unavailable to process jobs until it is restarted.

Stopping

The node service is in the process of stopping.

Undeploying

The node service is currently being uninstalled from the node computer.

Upgrading

The node is currently being upgraded on the node computer.

Using the Credential Manager

Credentials are used in different places in Enterprise Reporter. For example, nodes and report schedules both use credentials. The Credential Manager is a central store for accounts and passwords used throughout the system. This makes it easy to keep passwords up to date, and allows you to enter the credential details once, and access them repeatedly.

Accounts are not verified when you add them, and they must already exist in order to be used by Enterprise Reporter. For each account, you can add a description. This is particularly useful for differentiating between similar accounts, such as similarly named service credentials, or your SQL Server® default "sa" accounts. The combination of the account name and the description must be unique.

Credential passwords are encrypted with FIPS 140-2 compliant algorithms and an encryption key that has a user-supplied password. The encryption key is secured in the Windows Credential Manager (not to be confused with the Enterprise Reporter Credential Manager). The encryption key is used to encrypt all passwords that are used in Enterprise Reporter for collections and reporting. Additionally, Enterprise Reporter security groups and roles are used to validate who has access to the encryption key and the key cannot be retrieved without proper authorizations.

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

See also:

2
2
Click Add.
6
3
Click Edit.
6
3
Click Delete.
4

Changing Passwords Using the Credential Manager

When passwords are changed in Active Directory® and Azure Active Directory, they need to 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.

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 hosting the node. If there are jobs currently running on the node, they will be canceled. 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 next to each account that requires a password.

1
On the System | Configuration page, click Manage credentials used by Enterprise Reporter.
3
Select Edit Password.

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 hosting the node. If there are jobs currently running on the node, they will be canceled. To prevent this, either change the credentials during a down time, or cancel the discoveries yourself and restart them once the change takes effect.

1
On the System | Configuration page, click Manage credentials used by Enterprise Reporter.
Verwandte Dokumente