지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Enabling a Cluster

If you have disabled a cluster, you must enable it before the cluster can do any work. When you enable a cluster, it enables all nodes in the cluster. This action makes the cluster available for collections.

To enable a cluster
1
In the Manage Discovery Clusters pane, select the cluster.
2
Click Enable Cluster.

Managing Nodes

You might want to change the credentials your node is using or change the location of a node’s temporary files. Occasionally, nodes may need to be disabled or stopped to perform regular system maintenance, or as part of troubleshooting your Enterprise Reporter deployment. You can move a node from one cluster to another or remove it completely if needed.

See also:

•
Modifying Node Credentials
•
Modifying the Location of Node Temporary Files
•
Removing a Node
•
Why Disable a Node?
•
Starting a Node
•
Enabling a Node
•
Starting a Node

Modifying Node Credentials

You can modify the node credentials using the Configuration Manager. The node account must be a member of the group Reporter_Discovery_Nodes.To ensure that your change goes smoothly, the new credentials should be permissioned as outlined in Node Credential and Alternate Credential Details for On-Premises Discoveries .

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.

Occasionally a credential change fails.For example, credentials can fail when the node host computer is not available on the network or has a firewall configured, or because you have provided invalid credentials. In this case, the node indicates that it failed to start in the bottom pane of the Manage Discovery Clusters view.

Nodes can potentially lock an Active Directory password, so remember to change the password on the node whenever you update the password on the node’s account. If you are performing a password update on credentials, see Changing Passwords Using the Credential Manager for more information.

You can manually restart the service using the Services console on the remote computer. For more information, see Troubleshooting credential change failures .

To modify the credentials a node uses
1
Select Manage Discovery Clusters, and click the cluster containing the node.
It is recommended that you cancel any running discoveries before changing your password.
2
In the bottom pane, select the Discovery Nodes tab.
3
Select the node, and click Edit Node.
•
To modify the service credential, select a user account from the Credential Manager.
•
To modify the credential that is used to connect to the Enterprise Reporter database:
a
Click Database Credential.
b
Select the type of authentication.
If you are using SQL Server authentication, select a SQL account from the Credential Manager.
If you are using Windows authentication to connect to the database, you must use the same account as the service credential.
4
Click OK.
A progress dialog box appears.
5
Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.
6
Click Close.

Modifying the Location of Node Temporary Files

Temporary data collection files are created while discoveries are running. These files are stored in the user's temp folder and can be large. If storage space is limited, these files can be stored in an alternate location by adding a DiscoveryTempFolder key to the appSettings portion of the ReporterNode.Exe.config file. This alternate location is optional and if it is absent or inaccessible, the default location is used.

* 
NOTE: Ensure the user’s temporary folder or alternate location is secured as it does contain temporary data collection files.
To modify the location of a node’s temporary files
1
Open the ReporterNode.exe configuration file
c:\Program Files\Ques\Enterprise Reporter\Node\ReporterNode.exe.config.
2
Add the following key to the appSettings portion of the file.
Specify the path where the temporary files should be created.
<appSettings>
<add key="DiscoveryTempFolder" value="c:\reporter\somefolder" />​
3
Save and close the configuration file.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택