サポートと今すぐチャット
サポートとのチャット

Enterprise Reporter 3.5.1 - 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

Dealing with Unassociated Nodes

An unassociated node is one that has been either manually installed, or left behind from a previous installation of Enterprise Reporter. You can either uninstall the node, or associate the node with a cluster.

3
Click Associate Node(s) with Selected Cluster.

Dealing with Faulted Nodes

A faulted node has lost contact with the server.You should ensure that the host computer is available on the network and that the service is started.

Problems Deleting a Node

If you are deleting a node, you may see an error message indicating that the discovery node installation failed, for example:
"An error occurred copying the discovery node installation program Quest.Reporter.Core.Server.MsiInstaller.exe to \\servername\ADMIN$\Quest.Reporter.Core.Server.MsiInstaller.exe."

This indicates that there was a problem connecting to the host computer. Check your node credentials, ensure that the firewall is not enabled on the host, and ensure that the computer can be reached on the network. Once you have resolved the connection issue, you can attempt to remove the node again.

Changing the Node Logging Level

If you are experiencing difficulty, the support staff may ask you to change the logging level for nodes in a cluster. The default setting for node logging is Warning, which also includes Fatal and Error. You can increase the logging level to Information or Debug to help them troubleshoot your issue.

If you increase the node logging level, you might want to increase the node file size temporarily as well. For more information, see Changing the Size of the Node Log Files .

3
Click Apply.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択