Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Table 7. Statuses of a Cluster in Configuration Manager
Status	Meaning
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:

Table 8. Statuses of a Node in Configuration Manager
Status	Meaning
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.


	NOTE: Credentials added in the Report Manager are only available to the user who added them, while accounts added in the Configuration Manager are available to all Configuration Manager users on the same Enterprise Reporter server.

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.

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.


	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 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.

To change the password on an account used by Enterprise Reporter

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

Select the account, and click Edit.

Select Edit Password.

Modify the password and click OK.

A progress dialog box appears.

Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.