立即与支持人员聊天
与支持团队交流

Enterprise Reporter 3.2.2 - Configuration Manager User Guide

Product Overview 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 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
Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Managing Nodes

You may want to change the credentials your node is using. Occasionally, nodes may need to be disabled or stopped in order to perform regular system maintenance, or as part of troubleshooting issues with your Enterprise Reporter deployment.

See also:

•
Modifying Node Credentials
•
Modifying the Location of a Node’s Temporary Files
•
Changing a Node to a Different Cluster
•
Removing a Node
•
Why Disable a Node?
•
Stopping a Node
•
Enabling a Node
•
Starting a Node

Modifying Node Credentials

You can modify the node credentials using the Configuration Manager. 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 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.

Occasionally a credential change will fail, for example because 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 will indicate that it failed to start in the bottom pane of the Manage Discovery Clusters view. You can manually restart the service using the Services console on the remote computer. For more information, see Troubleshooting Credential Change Failures .

* 
NOTE: The node account must be a member of the group Reporter_Discovery_Nodes.
NOTE: If you are performing a password update on credentials, see Changing Passwords Using the Credential Manager for more information.
* 
NOTE: 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.
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.
4
To modify the service credential, select a user account from the Credential Manager.
5
To modify the credential that is used to connect to the Enterprise Reporter database:
•
Click Database Credential
•
Select the type of authentication
•
If 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.
6
Click OK.
A progress dialog box appears.
7
Verify that your changes were processed. If any errors occur, you will need to troubleshoot the issue and manually make any changes.
8
Click Close.

Modifying the Location of a Node's Temporary Files

Modifying the Location of a Node’s 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 may 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.
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.

Changing a Node to a Different Cluster

Once it has been disabled, a node can be changed to a different cluster. This can be helpful when the node computer is moved into the geographical location of a different cluster. Once the node has been modified, the node must be re-enabled for it to function again.

To change the cluster of a node:
1
On the Manage Discovery Clusters pane, select the cluster.
2
In the bottom pane, select the Discovery Nodes table and select the node.
3
Click Disable Node.
4
Click Stop Node.
5
Click Change Cluster.
6
Select a new Assigned Cluster.
7
Click OK.
8
If required, select the node again.
9
Click Start Node.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级